make-it-sound-human
Skill0 starsChanged 4 months agoMITView on GitHub
Cut a draft before adding to it, kill banned phrasing, replace abstraction with the specific numbers already in the data, and name the weakest paragraphs rather than silently rewriting everything.
In this repository26 other files it gives its agents.
- beat-my-competitorsSkill
- brief-my-writerSkill
- can-i-actually-rankSkill
- check-before-i-publishSkill
- explain-this-numberSkill
- find-my-quick-winsSkill
- follow-the-moneySkill
- get-cited-elsewhereSkill
- get-mentioned-by-aiSkill
- know-my-buyerSkill
- make-me-quotableSkill
- map-my-siteSkill
- pick-my-battlesSkill
- put-it-on-autopilotSkill
- rainmakerSkill
- revive-old-pagesSkill
- say-it-their-waySkill
- show-me-progressSkill
- show-up-in-communitiesSkill
- spread-one-piece-everywhereSkill
- stop-losing-visitorsSkill
- unblock-my-money-pagesSkill
- what-actually-workedSkill
- what-changed-in-searchSkill
- what-to-target-nextSkill
- write-the-pageSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 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.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Run rainmaker context --check first.
- Very specific: line 30
Only the data/ files listed in this skill's Consumes table.
- Very specific: line 32
If strategy.json.context_hash does not match the current hash of context/business.md, say exactly:
- Very specific: line 38
If context/business.md carries confidence: stub, continue, and stamp every output with: "Built on a stub context.
- Distinctive: line 63
Never soften an unsourced claim into a vaguer unsourced claim.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
make-it-sound-human
Context load
Run rainmaker context --check first. It prints what exists, what is stale, and exits 1 if anything this skill requires is missing.
Then read, in this order:
context/business.mdin full. If absent, stop: "No business context. Runrainmaker audit, then theknow-my-buyerskill."context/voice.mdif this skill writes prose. If absent, stop and say so.context/glossary.mdif this skill names products, features or competitors.data/strategy.jsonif this skill reads or writes strategy.- Only the
data/files listed in this skill's Consumes table. Never crawl or call an API the core already covers.
If strategy.json.context_hash does not match the current hash of context/business.md, say exactly:
"Business context was edited after the strategy was written. Re-run know-my-buyer, or run rainmaker context --sync to accept the prose as authoritative."
Then stop.
If context/business.md carries confidence: stub, continue, and stamp every output with: "Built on a stub context. Nothing in it came from a buyer. Run know-my-buyer to replace it."
Consumes
| File | Why | If missing |
| the draft | what to edit | ask for the draft or the slug |
context/voice.md | the fixed floor plus site-specific rules and samples | continue with the fixed floor only, and say so |
data/strategy.json | optional, to verify any number being sharpened is real | continue without it, note the gap |
Produces
The draft in place, and a change log of what was cut and why.
Procedure
- Cut before adding. Report the word count before and after; a punch-up that grows the draft by more than 10 percent has failed.
- Kill every banned phrase from
skills/_shared/voice-rules.mdand any additional ones incontext/voice.md. - Replace abstraction with the specific number already present in the data. Never invent one to replace a vague claim; if no real number exists, cut the claim instead of sharpening it into a false precision.
- Move the strongest claim into the first 100 words.
- Report the three weakest paragraphs by name and why, rather than silently rewriting everything the user did not ask you to touch.
Decision rules
- A punch-up is not a rewrite. Preserve the author's structure and claims; tighten them.
- Never soften an unsourced claim into a vaguer unsourced claim. Cut it.
- The em-dash rule and the rest of the slop check apply to the edited output, checked again after editing, not only before.
Output
Before: <n> words After: <n> words (<+/-n%>)
Cut:
"<removed line>": <why: cliche / unsourced / redundant>
Weakest paragraphs (named, not rewritten silently):
Paragraph <n>: <why it's weak>
Slop check after edit: <passed / issues remaining>Done when
Word count moved down or stayed flat, the slop check passes on the edited version, and the three weakest paragraphs are named with a reason rather than quietly changed.
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.

