agenticnotetaking/skills/spiral
skills/spiral/SKILL.md
--- tldr: Stop spiraling and hand off to the user with actionable next steps category: utility --- # /eidos:spiral The user is telling you that you're spiraling — repeatedly trying things that aren't working, whether that's terminal commands, code fixes, or debugging attempts. ## Instructions 1. **Stop immediately.** Do not retry, try another variation, or make another speculative attempt. 2. **Summarise** what you were trying to do, what you tried, and what went wrong (briefly). 3. **Hand o
$ install --global
skillsauthnpx skillsauth add agenticnotetaking/eidos skills/spiralInstall 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:37 AM55.5s2 files scanned
SKILL.md
- tldr:
- Stop spiraling and hand off to the user with actionable next steps
- category:
- utility
/eidos:spiral
The user is telling you that you're spiraling — repeatedly trying things that aren't working, whether that's terminal commands, code fixes, or debugging attempts.
Instructions
- Stop immediately. Do not retry, try another variation, or make another speculative attempt.
- Summarise what you were trying to do, what you tried, and what went wrong (briefly).
- Hand off using whichever approach fits the situation:
Terminal / environment failures
- Pasteable command: give the user a command they can run in their own terminal, then share the output with you.
- Diagnostic script: write a small script that includes debugging output (env vars, paths, versions, error details), make it executable, and ask the user to run it and paste back the results.
Code / bug fix failures
- Logging: suggest adding targeted logging to narrow the cause — specify exactly where and what to log.
- Debug overlay: in UI contexts, suggest a togglable debug overlay that encodes diagnostic info (state tooltips, debug panel, visible bounding boxes).
- Isolation script: suggest a small standalone script or test that reproduces the issue outside the full system.
General
- Present options: if multiple approaches exist, list them and ask the user which to try.
- Ask for help: describe what information you'd need to make progress and ask the user to provide it.
- Wait for the user's response before continuing.
Example handoffs
Pasteable command:
Could you run this and paste the output?
node -e "console.log(process.env.PATH)" && which npx && npx --version
Diagnostic script:
I wrote
debug-build.sh— could you run it?chmod +x debug-build.sh && ./debug-build.shIt checks toolchain versions and prints the failing step with verbose output.
Logging suggestion:
I've tried X and Y but can't tell where it breaks. Can I add a
console.loginhandleSubmitat line 45 to print the form state before validation?
Presenting options:
I've tried the obvious fix and it didn't work. I see three possible causes:
- State race condition in the effect
- Stale closure over the callback
- Missing dependency in the memo Which should I dig into first?
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