All authors
Claude Skills by adjohn
github.com/adjohn23 skills8 installs129 views
- Reproduce And Fix IssuesReproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.Votes: 0GitHub stars: 4
- Setup BennyConfigure Benny and prepare its triage and repro automations. Use when installing Benny or changing its Slack, tracker, repository, routing, control, model, or budget settings.Votes: 0GitHub stars: 4
- Triage Issue ReportsTriage Slack issue reports with one thread-only verdict, evidence review, cause-aware routing, tracker dedupe, and fail-closed ticket creation. Use only from the configured Benny triage automation.Votes: 0GitHub stars: 4
- ArchitectSketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.Votes: 0GitHub stars: 4
- ArenaSpawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.Votes: 0GitHub stars: 4
- Automate MeUse for \"automate me\", \"create/update/refresh my -mode skill\", \"turn/capture my preferences or working style into a skill\", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via skill-creator + unslop, optionally pulling fresh evidence from recent transcripts.Votes: 0GitHub stars: 4
- Blast RadiusFind what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.Votes: 0GitHub stars: 4
- Figure It OutDesign an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.Votes: 0GitHub stars: 4
- HowUse for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.Votes: 0GitHub stars: 4
- InterrogateUse for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Multiple LLM reviewers challenge changes from independent angles.Votes: 0GitHub stars: 4
- No CommentsSpawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.Votes: 0GitHub stars: 4
- Poteto Modepoteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style; apply it to new tasks that match a playbook or need rigor, not to casual turns or when the user opts out.Votes: 0GitHub stars: 4
- Playbooks**You own the skill's voice.** 1. Use the **skill-creator** skill if installed (from anthropics/skills) for authoring SKILL.md files; otherwise author the SKILL.md directly. 2. Validate the skill: frontmatter has `name` and `description`, referenced files exist, cross-skill links resolve. 3. Test cases if structural. Skip if subjective. 4. Run **Opening a PR**. When in doubt, delete. Keep only prose that changes a decision. Tell it to do the thing and skip the reason. Explain only when the ru...Votes: 0GitHub stars: 4
- Principle Guard The Context WindowApply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.Votes: 0GitHub stars: 4
- Principle Never Block On The HumanApply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.Votes: 0GitHub stars: 4
- RecallReconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.Votes: 0GitHub stars: 4
- ReflectSpawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.Votes: 0GitHub stars: 4
- Setup PstackConfigure which models pstack uses per role and at what reasoning budget. Detects your available models and writes an always-loaded memory file that overrides the skill defaults. Use for /setup-pstack, "configure pstack models", "pstack budget", or changing pstack's model choices.Votes: 0GitHub stars: 4
- Show Me Your WorkKeep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.Votes: 0GitHub stars: 4
- SwarmFan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.Votes: 0GitHub stars: 4
- Technical WritingLayered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.Votes: 0GitHub stars: 4
- UnslopCut AI tells from any writing. Must always apply.Votes: 0GitHub stars: 4
- WhyUse for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.Votes: 0GitHub stars: 4