skills/reflect/SKILL.md
--- tldr: Extract learnings from session or file category: observation --- # /eidos:reflect Extract learnings, tasks, and incoherences from a file. ## Usage ``` /eidos:reflect [file] ``` ## Instructions ### 1. Read the Source Read the target file (session export, research, or any file with insights to extract). ### 2. Identify Extractables Categorise findings: - **Learnings** — insights worth preserving (`learning -` prefix) - **Tasks** — things that need doing (`todo -` prefix) - **Inc
npx skillsauth add agenticnotetaking/eidos skills/reflectInstall 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.
Extract learnings, tasks, and incoherences from a file.
/eidos:reflect [file]
Read the target file (session export, research, or any file with insights to extract).
Categorise findings:
learning - prefix)todo - prefix)incoherence - prefix)question - prefix)Use [[spec - numbered lists - structured selectable output]] format:
1 - Learnings
- 1.1 - Session tokens are simpler than JWT for our use case
- 1.2 - Rate limiting should be middleware, not per-endpoint
2 - Tasks
- 2.1 - Audit existing error handling for consistency
3 - Incoherences
- 3.1 - Auth spec says stateless but session spec assumes state
4 - Questions
- 4.1 - Should we support multiple simultaneous sessions?
Which items to externalise? (e.g., "1.1, 2.1, 3.1")
Run date '+%y%m%d%H%M' to get the current timestamp.
For each selected item, create the appropriate file (per [[spec - naming - prefixes structure filenames as prefix claim pairs]]):
memory/learning - <timestamp> - <claim>.md (e.g. learning - 2602101500 - rate limiting belongs in middleware.md)memory/todo - <timestamp> - <claim>.md (e.g. todo - 2602101400 - audit error handling consistency.md)memory/incoherence - <timestamp> - <claim>.md (e.g. incoherence - 2602101500 - auth spec contradicts session spec.md)memory/question - <claim>.mdCommit all created files together.
Add => wiki links in the numbered list snapshot to track what was created:
- 1.1 - Session tokens are simpler than JWT
- => [[learning - session tokens simpler than JWT for single server]]
memory/memory/reflect - <timestamp> - <claim>.md (e.g. reflect - 2602141030 - session learnings snapshot.md)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