introvenk/clear-business-writing-skills / skills/diagnosing-drafts
diagnosing-drafts
Verified| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.3 KB |
| meaning-ratio.md | markdown | 1.6 KB |
meaning-ratio.md
View on GitHub# Meaning Ratio
**Method:** meaning ratio = meaningful words ÷ total words. A word is meaningful if removing it would remove information the reader needs — not just anything that "sounds important."
Below 70%: bullshit territory. Around 80%+: readable. This is a judgment heuristic, not a metric to optimize — a technical RFC with dense but necessary jargon can carry more real information than its raw ratio suggests. Use it to flag suspicious passages, not to score a whole document.
## Worked example
**Before** (30 words):
> "At this point in time, it is important to note that, going forward, we will be looking into the possibility of potentially exploring a migration to a new vendor solution."
Meaningful words: *migration*, *new*, *vendor* — 3 of 30. Ratio: 10%. Nearly every other word is throat-clearing ("at this point in time," "it is important to note that," "going forward," "looking into the possibility of potentially exploring," the vague trailing "solution") that could be deleted without losing information.
**After** (6 words):
> "We're evaluating a new vendor migration."
Meaningful words: *evaluating*, *new*, *vendor*, *migration* — 4 of 6. Ratio: 67%. Every word in the compressed version carries information the original also had — the original just buried it under 24 extra words.
## How to apply it
Read a passage. Cross out words that could be deleted without losing anything the reader needs to know. If more than 30% of the passage disappears, flag it as bullshit-heavy and propose the compressed version directly — don't just report a percentage back to the author.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |