showdown
Skill1 starsChanged 3 months agoMITView on GitHub
Use when the user knows what they want to build or change but not how to approach it, and wants the options compared before anyone plans or codes. Triggers on "how should I approach this", "which way should I go", "compare my options", "what are the trade-offs", "help me decide between", "is X or Y better here", or when the user is weighing architectures, libraries, or designs for a known goal.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- 2389-research/speed-runtheir own version, first seen Jul 6, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- 2389-research/speed-run★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- anger-translatorSkill
- cache-moneySkill
- codebase-memoirSkill
- codex-reviewSkill
- goalpostSkill
- grand-tourSkill
- identity-theftSkill
- relocate-sessionSkill
- right-stuffSkill
- rubicon-wordpress-version-labSkill
- second-lookSkill
- secret-santa-generatorSkill
- star-chartSkill
- work-evidence-researchSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Put two or three genuinely different approaches head to head on the same terms, pick one, and stop.
- Distinctive: line 21
Ask a question only when a missing fact would change which options exist or which one wins.
- Distinctive: line 38
Every cell is specific to this repo and this goal.
- Distinctive: line 42
Before you build: only the open questions whose answer would change the pick, numbered.
- Distinctive: line 46
If you find a bug or a blocker in the existing code while investigating, state it in one sentence before the Goal line, and treat fixing it …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Showdown
Put two or three genuinely different approaches head to head on the same terms, pick one, and stop. The output is a decision, not a plan and not code. Once the user picks, planning or building is a separate step.
1. Investigate first
Read the code the decision touches: the relevant modules, the existing patterns, the data shapes, and the constraints. Every option and every cell in the comparison must be grounded in what the repo actually does. Make sure you understand what the user is trying to achieve and why.
Ask a question only when a missing fact would change which options exist or which one wins. Ask it in plain text, numbered, at most three, and wait.
2. Choose the contenders
Two or three options. Each one must be an approach a competent engineer would choose in some real situation, and you must be able to name that situation. If you cannot, the option is a straw man: replace it with a real alternative or drop to two.
Include the option that fully delivers the goal even when it is the hardest. Include the cheapest option that plausibly works, so the user sees what the extra effort buys.
3. Answer in this shape
Goal: one sentence restating what the user is trying to achieve, in their terms.
The contenders: one table, one row per option, these columns in this order:
| Option | What it involves | How fully it meets the goal | Fit with this codebase | Effort and risk | Right choice when |
Every cell is specific to this repo and this goal. "Right choice when" names a concrete situation in which that option wins, stated on its own terms, not "it depends". Whether that situation applies to this user is argued in the Pick.
Pick: one paragraph. Which option, and why, argued from the goal. Effort and risk are reasons only when two options meet the goal about equally well. Then one sentence that starts "Pick <other option> instead if" and names an observable condition that would flip the decision.
Before you build: only the open questions whose answer would change the pick, numbered. Omit this part when there are none.
The answer ends there. Anything you could not check while investigating, such as tests you could not run, goes in one sentence inside the opening bug line or a Before you build question, not after them.
If you find a bug or a blocker in the existing code while investigating, state it in one sentence before the Goal line, and treat fixing it as a constraint every option must meet.
Example
Goal: let support staff resend a failed order-confirmation email without asking engineering.
Option What it involves How fully it meets the goal Fit with this codebase Effort and risk Right choice when Admin button that re-enqueues the existing SendConfirmationjobOne endpoint and one button in the existing admin panel Fully, for single orders Reuses the job queue and audit log already in admin/Low; double-sends possible without an idempotency key Resends are occasional and one at a time Bulk resend screen with filters A filtered order list, select-all, and a batch job Fully, including outage recovery New batch job type; the admin panel has no bulk actions yet Medium; a wrong filter can email thousands Outages produce hundreds of failures at once Self-serve "resend my email" link for customers A public endpoint with rate limiting Partly; support still handles customers who never got the first email Needs a public route, which the app has none of Medium; new abuse surface Most failures are spam-folder issues, not send failures Pick: the admin button. It fully meets the goal as stated, reuses the queue and audit log, and adding an idempotency key closes its one real risk. Pick the bulk screen instead if the failure log shows more than a few dozen failures at a time.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

