Individual skill
readability
Technical copyediting workflow that replaces corporate jargon with plain English, removes synthetic AI phrasing, and resolves paragraph-level readability and grammar issues.
skills/readability/SKILL.md
Source commit f13434b33285c5aba297f57c657974492808eb68
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 52
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- antigravity Repository topic
- geo Repository topic
- golang Repository topic
- gunning-fog Repository topic
- markdown Repository topic
- mcp Repository topic
- mcp-server Repository topic
- readability Repository topic
- seo Repository topic
- readability,-copyediting,-editing,-jargon,-style,-grammar,-prose Declared skill tag
- operations Derived category
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 11,988 bytesreferences/tropes-and-jargon.mddoc · 16,379 bytes
Read excerpt
# Readability: jargon mitigation, deslopification & copyediting
`readability` turns dense, bureaucratic, or synthetic drafts into clear, human-authored technical prose. It combines three complementary disciplines:
1. **The 4-Step HBR Framework** to remove status-signaling jargon and raw acronyms while preserving technical accuracy.
2. **The 5-Dimension AI Slop Purge (`deslopify`)** to eliminate LLM clichés and re-establish natural syntax.
3. **Per-Paragraph `fog` and `vale` Hotspot Remediation** to fix density issues via Speedgrapher MCP metrics and [`references/tropes-and-jargon.md`](references/tropes-and-jargon.md).
---
## 1. Why Technical Prose Gets Bogged Down: The HBR Jargon Insight
Writing loaded with jargon signals insecurity, not mastery. They found that professionals who feel low status lean on unexpanded acronyms and abstract vocabulary to manufacture authority. The strategy backfires: readers trust plain, concrete explanations more. In ["Does Your Office Have a Jargon Problem?"](https://hbr.org/2021/03/do-you-have-a-jargon-problem) (*Harvard Business Review*, March 2021), Zachariah Brown, Eric M. Anicich, and Adam D. Galinsky analyzed thousands of texts to track why people hide behind buzzwords.
