AGENT SKILLS · MISSION KIT / michael-denyer

michael-denyer · Agent Skills

59 Skills with substantive, source-verified documentation. Open a card to read the original instructions and review package and installation details.

michael-denyer
Community

arena

Spawn 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.

1h installs
3
GitHub stars
3.1K
Updated
Oct 20
michael-denyer
Community

automate-me

Use 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 plugin-dev:skill-development + unslop, optionally pulling fresh evidence from recent transcripts.

1h installs
3
GitHub stars
3.1K
Updated
Oct 20
michael-denyer
Community

interrogate

Use 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.

1h installs
3
GitHub stars
3.1K
Updated
Oct 20
michael-denyer
Community

principle-build-the-lever

Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.

1h installs
3
GitHub stars
3.1K
Updated
Oct 20
michael-denyer
Community

principle-prove-it-works

Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'

1h installs
3
GitHub stars
3.1K
Updated
Oct 20
michael-denyer
Community

principle-type-system-discipline

Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, exhaust variants, derive from authoritative schemas.

1h installs
3
GitHub stars
3.1K
Updated
Oct 20
michael-denyer
Community

typescript-best-practices

TypeScript best practices. Use when reading or editing any .ts or .tsx file.

1h installs
3
GitHub stars
3.1K
Updated
Oct 20
michael-denyer
Community

why

Use 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.

1h installs
3
GitHub stars
3.1K
Updated
Oct 20
michael-denyer
Community

correct

Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each time the operator corrects you. Use for /correct.

1h installs
2
GitHub stars
3.1K
Updated
Oct 20
michael-denyer
Community

how

Use 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.

1h installs
2
GitHub stars
3.2K
Updated
Oct 21
michael-denyer
Community

principle-boundary-discipline

Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.

1h installs
2
GitHub stars
3.2K
Updated
Oct 21
michael-denyer
Community

principle-experience-first

Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.

1h installs
2
GitHub stars
3.2K
Updated
Oct 21
michael-denyer
Community

principle-fix-root-causes

Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.

1h installs
2
GitHub stars
3.2K
Updated
Oct 21
michael-denyer
Community

principle-minimize-reader-load

Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.

1h installs
2
GitHub stars
3.1K
Updated
Oct 20
michael-denyer
Community

principle-subtract-before-you-add

Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.

1h installs
2
GitHub stars
3.2K
Updated
Oct 21
michael-denyer
Community

recall

Reconstruct 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, and before telling the user that something was never recorded.

1h installs
2
GitHub stars
3.2K
Updated
Oct 21
michael-denyer
Community

technical-writing

Layered 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.

1h installs
2
GitHub stars
3.2K
Updated
Oct 21
michael-denyer
Community

thermo-nuclear-code-quality-review

Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.

1h installs
2
GitHub stars
3.2K
Updated
Oct 21
michael-denyer
Community

unslop

Cut AI tells from any writing.

1h installs
2
GitHub stars
3.1K
Updated
Oct 20
michael-denyer
Community

architect

Sketch 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.

1h installs
1
GitHub stars
4K
Updated
Nov 4
michael-denyer
Community

babysit

Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.

1h installs
1
GitHub stars
4K
Updated
Nov 4
michael-denyer
Community

benchmark-checklist

Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.

1h installs
1
GitHub stars
4K
Updated
Nov 4
michael-denyer
Community

blast-radius

Find 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', reviewing a small diff you don't trust, or a brief that asserts something about existing code ('make X public', 'X already handles Y') before you design against that assertion.

1h installs
1
GitHub stars
4K
Updated
Nov 4
michael-denyer
Community

create-formal-verification-skill

Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in any language, with whichever verification tool fits. Use for /create-formal-verification-skill, \"model-check this race\", \"prove this invariant\", or when concurrency, retries, state machines, parsers, or unsafe code need more than tests.

1h installs
1
GitHub stars
4K
Updated
Nov 4