2
Skill4 starsChanged 3 months agoMITView on GitHub
Short execution timebox for straightforward tasks requiring a little investigation and verification. Use when the user invokes /2 and target completion within 8 minutes.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- 1Skill
- 3Skill
- 4Skill
- 5Skill
- ae-extendscriptSkill
- asapSkill
- backbeforeSkill
- componentsSkill
- githubSkill
- huhSkill
- instantSkill
- motion-animateSkill
- motion-assetsSkill
- motion-designSkill
- motion-pipelineSkill
- motion-planSkill
- quick-contextSkill
- shader-uiSkill
- thumbnailSkill
- ui-intergritySkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 19
Follow existing architecture and conventions.
- Distinctive: line 21
Test the primary behavior and obvious nearby edge cases.
- Distinctive: line 23
Avoid unrelated cleanup and speculative improvements.
- Distinctive: line 24
Do not narrate routine work.
≈ “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
/2 — Short
Complete the task efficiently while maintaining full implementation quality.
Timebox
Target completion in under 8 minutes. Quality stays constant; spend the additional time on necessary understanding and verification rather than unnecessary explanation.
Behavior
- Quickly inspect the relevant code before changing it.
- Form a lightweight implementation approach internally.
- Make the smallest complete change.
- Follow existing architecture and conventions.
- Investigate dependencies only when necessary.
- Test the primary behavior and obvious nearby edge cases.
- Fix regressions introduced by the change.
- Avoid unrelated cleanup and speculative improvements.
- Do not narrate routine work.
Prioritize: understand → implement → verify → finish. Return a concise completion summary.
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.