tighten
Skill1 starsChanged 40 days agoMITView on GitHub
Only when explicitly invoked, rewrite your previous answer much shorter, by default in at most 60 words or within a limit the user gives.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- aditya-vermax/skillstheir own version, first seen Nov 8, 2026
- nearmap/shipyardtheir own version, first seen Nov 8, 2026
- nuko-nova-dynamics/nuko-nova-unsloptheir own version, first seen Nov 6, 2026
- oneafrikan/the-gridtheir own version, first seen Oct 20, 2026
- harshil-1411/claude_plugin_video_studiotheir own version, first seen Oct 17, 2026
- captkernel/claude-writing-toolstheir own version, first seen Oct 15, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- autobrr/mkbrr★ 363same name
- oneafrikan/the-grid★ 4same name
- aditya-vermax/skills★ 1same name
- corygabrielsen/skills★ 1same name
- markrogersjr/skills★ 1same name
- nearmap/shipyard★ 1same name
- nuko-nova-dynamics/nuko-nova-unslop★ 1same name
- captkernel/claude-writing-tools★ 0same name
- harshil-1411/claude_plugin_video_studio★ 0same name
- raj-khan/tighten★ 0same 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 repository38 other files it gives its agents.
- agent-conductSkill
- bugfixSkill
- code-smellsSkill
- deliverSkill
- final-responseSkill
- frontend-designSkill
- go-conventionsSkill
- go-implementorSkill
- go-reviewerSkill
- go-test-strengthSkill
- implementation-principlesSkill
- nextflow-conventionsSkill
- nextflow-implementorSkill
- nextflow-reviewerSkill
- nextjs-fastapi-conventionsSkill
- nextjs-fastapi-implementorSkill
- nextjs-fastapi-reviewerSkill
- orchestratorSkill
- phase-creatorSkill
- phase-reviewerSkill
- prose-principlesSkill
- pr-resolverSkill
- pr-reviewerSkill
- python-conventionsSkill
- python-implementorSkill
- python-reviewerSkill
- spec-authorSkill
- spec-proofreaderSkill
- spec-reviewerSkill
- spec-writerSkill
- subagentsSkill
- swift-conventionsSkill
- swift-implementorSkill
- swift-reviewerSkill
- testing-principlesSkill
- unslopSkill
- verificationSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
4
Distinctive
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 13
Keep only the direct answer, the single best fix with its reason and command, and at most one clause for what the fix leaves uncovered.
- Distinctive: line 18
Write short, plain sentences.
- Distinctive: line 20
If the question was relayed from someone else, write to that person, ready to paste.
- Distinctive: line 22
Don't add facts. Drop any claim you didn't verify.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Tighten
Rewrite your previous answer in at most 60 words, or in the number the user
gives (/tighten 40). The **Your next action:** line that
final-response requires does not count toward the limit; keep it. Count
the words before sending.
- Keep only the direct answer, the single best fix with its reason and command, and at most one clause for what the fix leaves uncovered.
- Cut whole facts rather than compressing every fact into fewer words.
- Drop mechanism (library, function, and file names), repetition, details the asker didn't raise, and anything they'll see when they follow the fix.
- Write short, plain sentences. Don't meet the limit with semicolons, parentheses, or dropped articles.
- If the question was relayed from someone else, write to that person, ready to paste.
- Don't add facts. Drop any claim you didn't verify.
- Plain prose: no headings, bullets, bold, or code blocks. Inline code is fine.
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.