/clear-technical-communication
Rewrite technical prose so the reader infers nothing.
What it does
Reviews and rewrites technical communication against one rule: minimize what the reader has to reconstruct. Catches the specific failure modes — no purpose up front, undefined identifiers, invented metaphors, ambiguous references, logic hidden in punctuation, options presented without consequences, decisions requested without a recommendation — and fixes content before polishing sentences.
When to reach for it
Before sending a design summary, plan, status report, handoff, or any request for someone else's decision.
It's working if
- It adds material as often as it cuts — the missing constraint, the consequence of the option you did not recommend.
- Your draft comes back with a recommendation attached to every decision you asked someone else to make.
- You can read the rewrite cold and tell what it wants from you.
Install this skill
Then type /clear-technical-communication in your agent.
npx skills@latest add smorinlabs/smorinlabs-harness -s clear-technical-communicationOr install it as the clear-technical-communication plugin.
/plugin install clear-technical-communication@smorinlabs-harnessWhere it fits
- /explain — composes new explanations; this one repairs existing prose.
- /reader-steps — owns the one part it hands off — actions the reader must perform.