skills/toskill/SKILL.md
--- tldr: Create new skill from conversation category: utility --- # /eidos:toskill Turn a discovered pattern into a reusable skill. ## Usage ``` /eidos:toskill [name] ``` ## Instructions 1. If no name provided, ask what the skill should do 2. Extract the pattern from conversation 3. Create `skills/<name>/<name>.md` with: - tldr in frontmatter - Skill heading with `# /eidos:<name>` - Usage section - Instructions section - Output section 4. Create `skills/<name>/SKILL.md` sym
npx skillsauth add agenticnotetaking/eidos skills/toskillInstall 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.
Turn a discovered pattern into a reusable skill.
/eidos:toskill [name]
skills/<name>/<name>.md with:
# /eidos:<name>skills/<name>/SKILL.md symlink → <name>.mdeidos/skills/spec - <name> skill - <claim>.md (every skill gets a spec)skills/<name>/<name>.md + SKILL.md symlinkeidos/skills/spec - <name> skill - <claim>.mdtools
--- 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