GitHub
error-recovery
Use when tasks fail due to transient errors. Provides structured retry strategies and graceful degradation patterns. Invoke on network errors, rate limits, or intermittent failures.
☆ 0View skill
BaxterCooper AI Skills
GitHub ↗Browse published AI skills maintained by BaxterCooper. Compare skill descriptions and follow each source repository for setup instructions.
Author statistics
Indexed skills
10Repository stars across indexed skills
0Repository forks
0Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Popular categories
Recent indexing activity
Browse skills
GitHub
orchestration
This skill should be used when orchestrating complex tasks, decomposing work into atomic units, dispatching to subagents, verifying outputs, or when discussing task verification and deviation tracking patterns.
☆ 0View skill
GitHub
parallel-dispatch
Use when facing multiple tasks or failures. Provides decision framework for concurrent vs sequential execution. Invoke before dispatching multiple subagents.
☆ 0View skill
GitHub
verification
This skill MUST be invoked before any completion claim, success report, or task transition. Mandates 5-step evidence protocol. Use when about to claim "done", "complete", "working", "fixed", or any success stat...
☆ 0View skill
GitHub
estimation
Use before committing to a task. Provides complexity analysis and scope assessment. Invoke when user asks "how complex" or before large features.
☆ 0View skill
GitHub
finishing
Use when all tasks are complete. Presents completion options and enforces test gate. Work is never left in limbo.
☆ 0View skill
GitHub
context-gathering
Use when entering an unfamiliar codebase, starting a new feature, or before any implementation task. Provides structured exploration protocol to understand before acting.
☆ 0View skill
GitHub
systematic-debugging
Invoke when debugging failures. MANDATORY when 3+ fix attempts have failed. Enforces root cause investigation before fixes.
☆ 0View skill
GitHub
tdd
Use for any code implementation task. Enforces RED-GREEN-REFACTOR cycle. "If you didn't watch it fail, you don't know if it tests the right thing."
☆ 0View skill
GitHub
writing-plans
Use when creating implementation plans. Mandates exact file paths, complete code samples, and expected output. No vague language allowed.
☆ 0View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.