skills/image/SKILL.md
--- tldr: Persist an image with a markdown companion that captures its essence category: utility --- # /eidos:image Persist a dropped image with a markdown file that describes what the image shows. ## Usage ``` /eidos:image ``` User drops an image into chat (or has just dropped one). ## Instructions 1. **Look at the image.** Understand what it shows — a UI, a diagram, a sketch, an error, a photo, whatever it is. 2. Run `date '+%y%m%d%H%M'` to get the current timestamp. 3. Derive a short c
npx skillsauth add agenticnotetaking/eidos skills/imageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Persist a dropped image with a markdown file that describes what the image shows.
/eidos:image
User drops an image into chat (or has just dropped one).
date '+%y%m%d%H%M' to get the current timestamp..png, .jpg, .webp, etc.).memory/:
memory/image - <timestamp> - <claim>.<ext>memory/image - <timestamp> - <claim>.md:---
tldr: [one-line description]
---
# [claim]
[[image - <timestamp> - <claim>.<ext>]]
[Description of what the image shows — layout, key elements, relationships, text, colours, whatever matters.
Write enough that someone who can't see the image gets the essential information.
Don't over-describe — capture the essence, not every pixel.]
=> [[image - <timestamp> - <claim>.md]] reference in the relevant action.[[image - ... .png]].memory/image - <timestamp> - <claim>.<ext> (the image)memory/image - <timestamp> - <claim>.md (the description)tools
--- tldr: Generate a manim explainer video through staged research → outline → scenes → code → render → merge, with the outline doubling as a plan/state document category: utility --- # /eidos:video Turn a topic (or a folder of wiki-linked md) into a rendered manim video through a fixed pipeline. Pauses after each stage for review by default. Outline doubles as the plan/state document — wiki-linked checklist tracks progress. Full design in [[spec - video skill - outline driven manim pipeline
tools
--- tldr: Surface session status to the human via a native OS notification category: utility --- # /eidos:ping Send a short out-of-band signal to the human — "I'm done", "I have a question", "I hit a wall" — as a native OS notification. The agent picks the moment; the human gets a popup without watching the terminal. ## Setup (macOS, opt-in) This skill is a no-op until the human has installed the **eidos-ping** menubar app and pointed at it in `.eidos-config.yaml`: ```yaml ping_macos: /path
tools
--- tldr: Persist behaviour corrections to CLAUDE.md category: utility --- # /eidos:toclaude Update CLAUDE.md or specs to correct undesired behaviour. ## Usage ``` /eidos:toclaude [description of correction] ``` ## Instructions 1. Understand the correction — what went wrong, what should happen instead 2. Identify the right location: - **`inject/core/*.md`** — plugin rules that apply to all eidos projects (pick the matching section file) - **`inject/feature/*.md`** — rules tied to a c
development
--- tldr: Create persistent plan for multi-step work category: planning --- # /eidos:plan Create a persistent plan file for multi-step work. ## Usage ``` /eidos:plan [brief description] ``` ## Instructions ### 1. Gather Context If the target file already exists with `status: seed`, read it — its content is raw context that seeds the plan. Use the seed's notes, links, and brain dumps to draft phases and actions. Skip clarification questions the seed already covers. Search for related arti