thananon/9arm-skills
4 skills4.6k installs10.8k starsGitHub
Install
npx skills add https://github.com/thananon/9arm-skillsSkills in this repo
1Scrutinizescrutinize is a 9arm-skills review ritual for solo builders who want a cold, outsider pass on plans, PRs, design docs, or proposed code changes. It refuses to stay inside the diff: after restating intent in one sentence, it asks whether doing nothing or reusing existing code would meet the goal, then follows the call graph through real execution paths to see if the change actually delivers. Output stays concise and actionable—each item names the fix, rationale, and evidence. Use it when you ask for review, audit, sanity-check, or a second opinion, or invoke /scrutinize explicitly. It fits Ship review most often but also helps Validate when a scope doc is too heavy and Build when a design proposal needs a elegance check before implementation. It is not a linter substitute or security scanner; it is judgment on necessity and correctness across the system.1.2kinstalls2Debug MantraDebug Mantra is a process skill from 9arm that turns ad-hoc bug chasing into a repeatable ritual for agent-assisted development. At the start of any debugging session the agent must recite four mantras verbatim, then execute them in order: establish reproducibility (including escalating flake rate), trace the fail path with debugger and instrumentation, actively try to disprove the leading hypothesis, and treat every run as a breadcrumb to correlate. It is built for solo builders who paste stack traces or say something is broken and want the model to slow down before proposing patches. Because it triggers proactively on errors across build, ship, and production, it is journey-wide even though Prism shelves it under Ship testing as the first formal quality gate. The outcome is fewer speculative fixes and more captured repro artifacts such as failing tests or curl scripts.1.1kinstalls3Post MortemPost-mortem is an agent skill that writes the canonical engineering record of a fixed bug: root cause, failure mechanism, fix, validation, and how the defect escaped earlier checks. It is aimed at solo and indie builders who ship fast and cannot afford to lose tribal knowledge when tickets close. Invoke it only after debugging has produced a real, validated fix—never for guesses still in flight. The output is dense and engineer-facing (identifiers and stack context are encouraged), distinct from executive summaries. When you need an up-org narrative, finish here first, then route the artifact through management-talk so engineering truth stays separate from leadership framing. Use it to close tickets with substance, onboard teammates on past incidents, and build an informal ops knowledge base without a separate incident tool.1.1kinstalls4Management Talkmanagement-talk helps solo builders and small eng teams repackage technical work for engineering-savvy leadership—VPs, directors, PMs, and release managers—without losing the facts. The skill is not a generic “make it shorter” prompt; it assumes the reader understands product and system names but should not wade through stack traces, internal codenames for trivial details, or implementation rabbit holes. You invoke it when someone asks for an executive summary, a less jargony rewrite, or a Slack, email, JIRA, standup, or meeting version of content that was originally written engineer-to-engineer. Channel choice drives length, formatting, and how much structure stays on the page. For indie operators wearing both IC and lead hats, it is the fastest path from “what I shipped in the repo” to “what leadership needs to decide or communicate next.” It is a prose workflow skill, not an integration—no APIs, no automatic posting.1.1kinstalls