Agent skill
spool
Unified entry point for spool commands with intelligent skill-first routing and CLI fallback.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/spool
SKILL.md
Route spool commands to the best handler.
Goal
Users may type requests like spool archive 001-03_add-spool-skill or spool dashboard.
This skill MUST:
- Prefer matching spool-* skills (skill-first precedence)
- Fall back to the spool CLI when no matching skill is installed
- Preserve argument order and content
Input
The requested command is provided either:
- As plain text following the word "spool" in the user request
- In prompt arguments (if your harness provides them)
- In a
<SpoolCommand>block
Steps
-
Parse the command:
- Extract the primary command (first token) and the remaining args
- If no command is provided, output a concise error: "Command is required" and show a one-line usage example
-
Resolve skill target:
- Build candidate skill id:
spool-${command} - Determine if that skill is installed/available in this harness
- OpenCode: check for a directory under
.opencode/skills/ - Claude: check for a directory under
.claude/skills/ - GitHub Copilot: check for a directory under
.github/skills/ - Codex: skills are global; if unsure, assume not installed and use CLI fallback
- OpenCode: check for a directory under
- Build candidate skill id:
-
Execute:
- If matching skill exists: follow that skill's instructions, passing along the original args
- Otherwise: invoke the CLI using Bash:
spool <command> <args...>
-
Error handling:
- If the invoked skill fails: prefix with
[spool-* skill error]and preserve the original error - If the CLI fails: prefix with
[spool CLI error]and preserve the original error
- If the invoked skill fails: prefix with
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?