skills/ping/SKILL.md
--- 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
npx skillsauth add agenticnotetaking/eidos skills/pingInstall 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.
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.
This skill is a no-op until the human has installed the eidos-ping menubar app and pointed at it in .eidos-config.yaml:
ping_macos: /path/to/eidos-ping/bin/eidos-ping-app
Source repo: see .repos.yaml (ping_macos entry). Without setup, /eidos:ping exits silently — no jsonl record, no notification, no popover.
/eidos:ping <name> <type> <tldr>
<name> — short context label for what this session is working on (e.g. auth-refactor, add-foo-page). Pick based on current task; change mid-session as work shifts. Two agents on the same branch should use different names so the human can tell their pings apart.<type> — one of done, question, step, fail. Open-ended; another short token is fine if the situation calls for it.<tldr> — ~5-word summary of what just happened.Notification format: title is [<name>] <type>, body is <tldr>.
done — task complete, agent is stopping. Always ping.question — blocked on a decision or clarification. Always ping.fail — hit a real blocker that can't be resolved without the human (test failure, missing creds, etc.). Always ping.step — only when the human asked to be informed after each milestone, or a phase wraps with something a human should see.When running autonomously, do not ping speculative observations — only surface when input or a decision is genuinely needed.
bash ${CLAUDE_PLUGIN_ROOT}/scripts/ping.sh <name> <type> <tldr>
ping_macos opt-in gate, JSONL queue write, NC notification, and lazy-launch of the aggregator.[<name>] <type> — <tldr>.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: 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
development
--- tldr: Resume work on existing plan category: planning --- # /eidos:plan-continue Resume work on an existing plan file. ## Usage ``` /eidos:plan-continue [plan-name] ``` ## Instructions ### 1. Find Active Plans Search `memory/` for `plan - *.md` files. Identify incomplete plans by checking: - Actions without `[x]` completion markers (note: `[p]` postponed actions don't count as incomplete — a plan with only `[x]` and `[p]` actions may be effectively done) - Status field not `completed`