skills/config/SKILL.md
--- tldr: View and toggle eidos project settings category: utility --- # /eidos:config View and change project settings. ## Usage ``` /eidos:config /eidos:config <key> ``` ## Instructions ### 1. Check Config Read `.eidos-config.yaml` in the project root. - **File missing or incomplete** (missing keys): tell the user and offer to run `/eidos:init` to set up. If they accept, invoke `/eidos:init`. After init completes, continue to step 2. If they decline, stop — config can't be changed
npx skillsauth add agenticnotetaking/eidos skills/configInstall 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.
View and change project settings.
/eidos:config
/eidos:config <key>
Read .eidos-config.yaml in the project root.
/eidos:init to set up.
If they accept, invoke /eidos:init. After init completes, continue to step 2.
If they decline, stop — config can't be changed without a complete file.Parse format: YAML key-value pairs.
key: true / key: false = booleankey: 200000 = numeric valuekey: null = explicitly disabled/unsetkey: value = string valueShow all available settings with current values:
Eidos config (.eidos-config.yaml):
git_workflow: true # branch-per-task, commit-per-action, --no-ff merges
status_reporting: true # status report after each action
skills_list: true # eidos skill listing in session start context
specs_and_concepts: true # spec/concept listing, future items at session start
session_context: true # session orientation: branches, todos, plans, recent memory
context_tracking_max: 200000 # max tokens for context window tracking (null to disable)
mono_focus: true # mono-repo sub-part focus injection at session start
observation_images: true # persist pasted images as named observation files in memory/
ping_macos: "" # path to eidos-ping-app binary (macOS opt-in); empty disables /eidos:ping
Change which? (e.g., "git_workflow", "context_tracking_max 100000")
If a specific key was provided as argument, show only that setting and its description.
| Key | Default | Type | Description |
|-----|---------|------|-------------|
| git_workflow | true | bool | Branch-per-task, commit-per-action, --no-ff merges |
| status_reporting | true | bool | Status report after each action (branch, commits, summary) |
| skills_list | true | bool | Skill listing in session start context |
| specs_and_concepts | true | bool | Spec/concept listing, open comments, future items at session start |
| session_context | true | bool | Session orientation: branches, todos, plans, recent memory |
| context_tracking_max | 200000 | int/null | Max tokens for context tracking; null to disable |
| mono_focus | true | bool | Mono-repo sub-part focus injection at session start (reads external mapping) |
| observation_images | true | bool | Persist pasted images as named observation files in memory/ |
| ping_macos | (empty) | string | Path to the eidos-ping-app binary (macOS opt-in); empty disables /eidos:ping |
| git_root | (omitted) | string | Relative path to parent .git directory (for nested projects) |
| git_prefix | (omitted) | string | Branch name prefix (for nested projects) |
String keys are only present when explicitly set (e.g. via /eidos:init git detection flow).
How changes work depends on the setting type:
true ↔ false). Just the key name is enough.context_tracking_max 100000 or context_tracking_max null.
If user provides just the key name, ask for the new value.git_prefix my-project.Steps:
.eidos-config.yaml fileWhen writing .eidos-config.yaml, each setting gets a # comment on the line above:
# 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: ""
Comments are preserved when changing values. String keys appear below other keys, separated by a blank line:
# persist pasted images as named observation files in memory/
observation_images: true
# nested project git
git_root: ../..
git_prefix: my-experiment
.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