agenticnotetaking/skills/annotate
skills/annotate/SKILL.md
--- tldr: Leave inline AI feedback in files for human review category: core --- # /eidos:annotate Leave `{{AI ...}}` annotations inline in files — observations, questions, and suggestions for the human to review. ## Usage ``` /eidos:annotate [file ...] # annotate specific file(s) /eidos:annotate [file ...] --focus <type> # constrain annotation focus ``` Focus types: `coherence`, `clarity`, `gaps`, `stale` ## Instructions ### 1. Identify Targets - **File args** → use th
$ install --global
skillsauthnpx skillsauth add agenticnotetaking/eidos skills/annotateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 1, 2026, 6:17 AM58.6s2 files scanned
SKILL.md
- tldr:
- Leave inline AI feedback in files for human review
- category:
- core
/eidos:annotate
Leave {{AI ...}} annotations inline in files — observations, questions, and suggestions for the human to review.
Usage
/eidos:annotate [file ...] # annotate specific file(s)
/eidos:annotate [file ...] --focus <type> # constrain annotation focus
Focus types: coherence, clarity, gaps, stale
Instructions
1. Identify Targets
- File args → use those files
- No args → ask the user what to annotate
2. Determine Focus
--focus coherence— contradictions within the file or against linked specs--focus clarity— vague claims, missing specificity, ambiguous language--focus gaps— missing sections, uncovered edge cases, absent rationale--focus stale— claims that may no longer match the codebase (read relevant code to check)- No focus → use judgement, err toward fewer, higher-signal observations
3. Read and Analyse
Read each target file thoroughly.
If focus is stale or coherence, also read linked specs and mapped code files.
For each observation, check:
- Is this actionable? (vague concern → skip)
- Is this non-obvious? (restating what the file already says → skip)
- Does this earn its place? (if removing it loses nothing → skip)
4. Insert Annotations
Place {{AI ...}} markers inline at the relevant point in the file.
Use GID prefixes where they add signal:
{{AI ? ...}}— question{{AI ! ...}}— important observation{{AI ^ ...}}— claim/correction{{AI > ...}}— suggestion{{AI ...}}— general observation (no prefix)
Each annotation should be self-contained — readable without external context. Keep annotations concise: one observation per marker.
Target density: 3-7 annotations for a typical spec file. If you have more than 7, prioritise and drop the weakest.
5. Commit and Report
Commit the annotated file.
Annotated [file name]:
- N annotations added (focus: [focus or "general"])
- Key observations: [1-2 sentence summary of themes]
Review inline, then /eidos:refine to process.
Output
- Modifies: target file(s) with
{{AI ...}}markers
Related Skills
agenticnotetaking/skills/video
tools
VerifiedTrustedCommunity
--- 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
51SKILL.mdUpdated May 25, 2026
agenticnotetaking/skills/ping
tools
VerifiedTrustedCommunity
--- 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
51SKILL.mdUpdated May 25, 2026
agenticnotetaking/skills/toclaude
tools
VerifiedTrustedCommunity
--- 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
51SKILL.mdUpdated Mar 30, 2026
agenticnotetaking/skills/plan
development
VerifiedTrustedCommunity
--- 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
51SKILL.mdUpdated Mar 30, 2026