difference
Skill142 starsChanged 22 days agoMITView on GitHub
Compare A vs B, weigh pros and cons of A, B, C, ..., or explain the nuance between sentences — a quick answer from what the model already knows
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- publish-pluginsSkill
- upgrade-playbooksSkill
- audit-agent-settingsSkill
- best-practicesSkill
- blindspotSkill
- commitSkill
- fuck-over-engineeringSkill
- prSkill
- refactor-agents-mdSkill
- refactor-memorySkill
- refactor-skillSkill
- simple-englishSkill
- write-like-meSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 21
Keep it as short as the question allows, and let the items decide the shape.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Difference
The user wants a fast answer, not research. Invoking this skill is their explicit opt-out of any standing rule to check docs or search before answering, except the lookup below: answer from what you already know.
Compare what the arguments name. With no arguments, compare the items just discussed; ask only when nothing comparable is there.
Lookups
What you already know includes docs read or fetched earlier in this session; check those first. Then run one web search (WebSearch in Claude Code, web_search in Codex) before answering when an item is a named identifier (setting key, CLI flag, env var, API field) or something you cannot identify at all, such as a tool released after your training. An identifier's name only suggests what it does, so recognizing the name is no reason to skip the search. Being unsure of an item's latest version does not count. Use no subagents.
Answer
Keep it as short as the question allows, and let the items decide the shape. Spend the words on where they actually differ, not on what they share.
- Alternatives someone picks between (tools, approaches, patterns): give each one's pros and cons.
- Sentences: how each lands differently — tone, implication, what a reader infers.
- An answer that hinges on a version, price, or "latest" fact: add one line saying it is as of your training data.
The last line of the answer is still comparison: no verdict, no offer to dig deeper.
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.