skills/compact/SKILL.md
--- tldr: Pre-compact readiness check — verify nothing is lost before clearing session category: utility --- # /eidos:compact Readiness check before compacting or clearing a session. Not a wrap-up — a pre-flight check that confirms it's safe to let go of current context. ## Usage ``` /eidos:compact ``` ## Instructions ### 1. Check Git Status Run `git status`. Flag: - Uncommitted changes (staged or unstaged) - Untracked files in `eidos/` or `memory/` that might be lost If clean, note it a
npx skillsauth add agenticnotetaking/eidos skills/compactInstall 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.
Readiness check before compacting or clearing a session. Not a wrap-up — a pre-flight check that confirms it's safe to let go of current context.
/eidos:compact
Run git status.
Flag:
eidos/ or memory/ that might be lostIf clean, note it and move on. If dirty, list what's pending — the user decides whether to commit or discard.
Look for active plans in memory/ (files matching plan - * with an active phase).
If an active plan exists:
[x] actions missing => notes[ ]) actions that look started but unfinishedIf the plan is current, note it. If the plan needs updating, say what's stale — don't fix it automatically.
Scan memory/ for todo - * files.
List any that were relevant to this session's work (based on branch name or recent commits).
Not a blocker — just awareness.
Summarise as one of:
Clean:
Ready to compact.
- Git: clean
- Plan: up to date
- No loose ends
Safe to /compact or start a new session.
Pending items:
Not quite ready:
- [list items that need attention]
Fix these first, or proceed if they're intentional.
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