skills/init/SKILL.md
--- tldr: Bootstrap eidos folder structure for a new project category: utility --- # /eidos:init Bootstrap the eidos folder structure in the current project. ## Usage ``` /eidos:init ``` ## Instructions ### 1. Check and Create Folders Create each target, reporting what was created vs what already existed: | Target | Purpose | |--------|---------| | `eidos/` | Spec root — what the system should be | | `memory/` | Procedural artifacts — how we got here | For each: - **Missing:** create th
npx skillsauth add agenticnotetaking/eidos skills/initInstall 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.
Bootstrap the eidos folder structure in the current project.
/eidos:init
Create each target, reporting what was created vs what already existed:
| Target | Purpose |
|--------|---------|
| eidos/ | Spec root — what the system should be |
| memory/ | Procedural artifacts — how we got here |
For each:
Copy copy/seed.md (from the plugin directory) to eidos/seed.md if it does not exist.
If it exists, report "already exists".
Copy copy/human.md (from the plugin directory) to memory/human.md if it does not exist.
If it exists, report "already exists".
Check .eidos-config.yaml:
Default settings (with # comments above each key):
# branch-per-task, commit-per-action, --no-ff merges
git_workflow: true
# status report after each action
status_reporting: true
# eidos skill listing in session start context
skills_list: true
# spec/concept listing, future items at session start
specs_and_concepts: true
# session orientation: branches, todos, plans, recent memory
session_context: true
# max tokens for context window tracking (null to disable), used to warn about compaction early
context_tracking_max: 200000
# mono-repo sub-part focus injection at session start
mono_focus: true
# persist pasted images as named observation files in memory/
observation_images: true
# path to eidos-ping-app binary (macOS opt-in); empty disables /eidos:ping
ping_macos: ""
Use the format from [[skills/config/config.md]] §5. When appending, preserve existing values and comments — only add what's missing.
After creating the config, check for a .git directory in the working directory.
.git found locally: skip this step — git is available.
No .git found: present options:
No .git found in this directory.
1 - Create fresh repository (git init here)
2 - Find parent (walk ancestor directories for .git)
3 - Disable git (set git_workflow: false)
Option 1 — Create fresh:
git init in the working directoryOption 2 — Find parent:
.git.gitFound .git at <path>.
Branch prefix? (e.g. "my-experiment" → my-experiment/task/feature)
Leave empty for no prefix.
.eidos-config.yaml:
git_root: <relative-path> (e.g. ../..)git_prefix: <prefix> (only if non-empty).git not found in any ancestor, fall back to offering options 1 and 3Option 3 — Disable git:
git_workflow: false in .eidos-config.yamlShow what was created, what already existed, and git status:
Eidos initialised:
- eidos/ created
- eidos/seed.md created
- memory/ already exists
- memory/human.md created
- .eidos-config.yaml created | updated (added: ...) | already exists
- git: using parent repo (../../) with prefix "my-experiment"
Git line variants:
git: local .git found — normal casegit: created fresh repository — option 1git: using parent repo (<path>) with prefix "<prefix>" — option 2 with prefixgit: using parent repo (<path>) — option 2 without prefixgit: disabled — option 3If git_workflow is enabled (or no config existed before init), commit all created files in a single commit.
eidos/, eidos/seed.md, memory/, memory/human.md, .eidos-config.yamltools
--- 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