Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This collection provides a structured approach to resolving software defects. It guides engineers through a four-step debugging mantra—reproduction, path tracing, hypothesis falsification, and breadcrumb cross-referencing—to ensure fixes are based on evidence rather than intuition.
Beyond the fix, the tools facilitate the creation of canonical engineering records. These post-mortems document the root cause and mechanism of a failure, providing a formal validation record before a ticket is closed.
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Installs: Every shippable skill in the 9arm-skills repository, symlinked into ~/.claude/skills/. · Claude Code
Before you start
A local checkout of the 9arm-skills repository containing scripts/link-skills.sh.
A Bash-compatible environment.
Platform: Bash-compatible environment
Run from: Repository root
In a terminal, change to the root of the local 9arm-skills checkout, then run the documented script to symlink every shippable skill into ~/.claude/skills/.
Use the debug-mantra skill to investigate this bug: [describe the symptom and paste the error or logs]. The codebase is at [absolute repository path], and the relevant environment and current reproduction steps are [describe them]. Begin with the required mantra, then establish the fastest reliable reproduction and create an initial breadcrumb ledger. Do not propose a fix before the failure is reproducible and its path has been traced.
Use the scrutinize skill to review [PR, diff, plan, or design-document path] in the codebase at [absolute repository path]. The intended goal is [one-sentence goal]. Question whether a simpler change would achieve it, trace the affected behavior through the real code path, and return concise severity-ordered findings with rationale, evidence, a minimal suggested change, and a one-line verdict. Do not publish the review.
Turn an engineering update into a leadership Slack post
Uses management-talk
Engineer-to-engineer source update
Relevant status, impact, owner, issue or PR references, and next step
Use the management-talk skill to rewrite the following engineer-to-engineer update as a concise Slack post for engineering-org leadership. Preserve relevant product or framework names, issue keys, PR numbers, status, impact, owner, and next step. Remove function names, file paths, commit SHAs, and other code-level identifiers, and translate the mechanism into plain-English cause and effect. Do not send the message. Source update: [paste update].
Claude