agenticnotetaking/skills/process
skills/process/SKILL.md
--- tldr: Work through a structured document point by point, resolving each item category: planning --- # /eidos:process Work through a structured document (coherence report, drift analysis, or any file with numbered findings) item by item — reading context, asking questions, making changes, and updating the source document with resolutions. Like `/eidos:plan-continue` but for any document with actionable items, not just plans. ## Usage ``` /eidos:process [file path or wiki link] ``` ## In
$ install --global
skillsauthnpx skillsauth add agenticnotetaking/eidos skills/processInstall 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:32 AM58.6s2 files scanned
SKILL.md
- tldr:
- Work through a structured document point by point, resolving each item
- category:
- planning
/eidos:process
Work through a structured document (coherence report, drift analysis, or any file with numbered findings) item by item — reading context, asking questions, making changes, and updating the source document with resolutions.
Like /eidos:plan-continue but for any document with actionable items, not just plans.
Usage
/eidos:process [file path or wiki link]
Instructions
1. Load the Document
Read the target file.
If no file is given, search memory/ for recent unresolved documents (coherence, drift, review, etc.) and present options.
2. Identify Actionable Items
Scan for numbered items, sections with Fix: markers, or any structured findings that need resolution. Present an overview:
Processing: [[coherence - 2602140242 - spec graph contradictions]]
Items:
1 - Config file path contradiction (Contradictions §1)
2 - Claim file naming prefix (Contradictions §2)
3 - Progressive disclosure vs session context (Contradictions §3)
4 - Main spec missing 4 skills (Missing Cross-References §4)
...
11 total items. Start from the beginning?
The user may choose to start at a specific item or skip items.
3. Process Each Item
For each item:
- Read — read the relevant files referenced by the item
- Present — show the issue with enough context to decide
- Ask — if the resolution isn't obvious, ask the user what to do (use AskUserQuestion or numbered options)
- Act — make the agreed changes (edit files, update specs, add links)
- Commit — commit the changes immediately
- Update source — mark the item as resolved in the source document with a brief note
4. Update the Source Document
After resolving an item, update it in place in the source file. Never delete or rewrite original content — resolution is always additive.
General documents (coherence, drift, review, etc.)
Append a **Resolved:** note below the original finding:
### 1 - Config file path: `eidos/.config` vs `.eidos-config`
...original finding preserved as-is...
**Resolved:** Updated two references in main spec. `abc1234`
Refinement files (from /eidos:refine)
Refinement files have a specific structure: lettered sections with status: open, feedback slots (- [ ]), and structured fields (Comment, Context, Question, Reasoning, Options).
Work within this structure:
- Fill in the
- [ ]slot with the resolution (e.g.- [x] Applied option 1 — updated spec accordingly) - Change
status: open→status: resolvedin the section header - Preserve all original fields (Comment, Context, Question, Reasoning, Options) untouched
# B. [Topic] — status: resolved
**Comment:** `{{original comment text}}`
**Reasoning:** [original reasoning preserved]
**Options:**
1. Agree (apply suggested change)
2. Disagree (remove annotation)
- [x] Applied option 1 — removed annotation and updated claim. `def5678`
Commit the source document update.
5. Continue Loop
After each item:
Resolved: Item 1 — Config file path contradiction
Next: Item 2 — Claim file naming prefix
continue?
Wait for confirmation before proceeding. The user may skip items, reorder, or stop at any point.
6. Wrap Up
When all items are processed (or user stops):
Processed: [[coherence - 2602140242 - spec graph contradictions]]
Resolved: 8/11 items
Skipped: 2 (items 6, 9)
Deferred: 1 (item 3 — needs broader discussion)
Options:
1 - Continue with skipped items
2 - Done
Output
- Modifies: files referenced by each item (specs, claims, inject snippets, etc.)
- Updates: the source document with resolution notes
- No new file created — the source document becomes the record
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