Agent skill
word-economy-mastery
Advanced techniques for cutting word count while maintaining clarity and impact. Use when articles exceed word limits, need to be more concise, or when writing needs to be tighter and more focused.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/word-economy-mastery
SKILL.md
Word Economy Mastery
This Skill provides systematic techniques for reducing word count without losing meaning or impact.
The Core Principle
Every word must earn its place. If removing a word doesn't change meaning or impact, remove it.
Systematic Reduction Strategies
1. Eliminate Redundancy
Common redundant phrases:
- "in order to" → "to"
- "due to the fact that" → "because"
- "at this point in time" → "now"
- "for the purpose of" → "to"
- "in the event that" → "if"
- "with regard to" → "about"
- "it is important to note that" → (delete)
- "it should be pointed out that" → (delete)
Example:
- Before: "In order to achieve success, it is important to note that you must first understand the basic principles."
- After: "To succeed, understand the basic principles first."
2. Use Active Voice
Active voice is shorter and clearer:
- "The team implemented the strategy" (5 words)
- vs. "The strategy was implemented by the team" (6 words)
Common passive patterns to fix:
- "It was decided that" → "We decided" or "The team decided"
- "It can be seen that" → "You can see" or "This shows"
- "It is believed that" → "We believe" or delete and state directly
3. Replace Phrases with Words
Phrase → Word:
- "a large number of" → "many"
- "in the near future" → "soon"
- "in the majority of cases" → "usually"
- "at a rapid rate" → "rapidly" or "quickly"
- "on a regular basis" → "regularly"
- "in a timely manner" → "promptly" or "on time"
- "with the exception of" → "except"
- "in spite of the fact that" → "although"
4. Cut Filler Words
Eliminate these words when possible:
- "very" (use stronger word instead: "very important" → "critical")
- "really" (usually unnecessary)
- "quite" (vague, cut it)
- "somewhat" (be specific or cut)
- "rather" (be direct)
- "actually" (usually unnecessary)
- "basically" (cut it)
- "essentially" (cut it or be specific)
Example:
- Before: "This is really quite important and actually very useful."
- After: "This is critical and useful."
5. Remove Unnecessary Qualifiers
Weak qualifiers to cut:
- "kind of"
- "sort of"
- "a bit"
- "a little"
- "some"
- "certain"
- "various" (be specific)
Example:
- Before: "There are various ways to approach this problem."
- After: "Three approaches work best for this problem." (then list them)
6. Eliminate Weak Verbs + Adverbs
Replace weak verb + adverb with strong verb:
- "walk slowly" → "stroll" or "amble"
- "speak loudly" → "shout" or "proclaim"
- "think carefully" → "consider" or "analyze"
- "work quickly" → "rush" or "hurry"
- "move quickly" → "rush" or "dash"
7. Cut Introductory Phrases
Unnecessary introductions:
- "It is worth noting that" → (delete)
- "It should be mentioned that" → (delete)
- "It is interesting to observe that" → (delete)
- "What is important here is that" → (delete, state directly)
- "The thing to remember is that" → (delete, state directly)
Example:
- Before: "It is worth noting that this approach requires careful planning."
- After: "This approach requires careful planning."
8. Simplify Complex Constructions
Complex → Simple:
- "The way in which" → "how"
- "The reason why" → "why" (or "because")
- "The fact that" → (delete, restructure)
- "There is a possibility that" → "possibly" or "might"
- "There is a need for" → "need" or "must"
Example:
- Before: "The fact that the team was unable to complete the project on time was the reason why the client was dissatisfied."
- After: "The team's late delivery dissatisfied the client."
Structural Reduction
Cut Redundant Examples
Rule: 2 strong examples > 3 mediocre ones
When to cut examples:
- If they illustrate the same point
- If one example is clearly stronger
- If examples don't add unique value
Trim Theoretical Elaboration
Keep theory lean:
- State the principle (1-2 sentences)
- Explain why it matters (1 sentence)
- Move to application (the focus)
Cut:
- Extended theoretical background
- Multiple theoretical perspectives (unless critical)
- Academic debates (unless directly relevant)
Remove Repetitive Phrasing
Watch for:
- Saying the same thing multiple ways
- Repeating key points unnecessarily
- Over-explaining simple concepts
Example:
- Before: "The framework is simple. It's easy to understand. You won't find it complicated."
- After: "The framework is simple."
Condense Transitions
Long transitions → Short:
- "Now that we have covered X, let us move on to consider Y" → "Y builds on X by..."
- "Having discussed the theory, we can now turn our attention to practice" → "In practice..."
- "Before we proceed, it is important to understand" → "Understanding X helps because..."
Word Count Reduction Process
Step 1: Identify Core Message
- What is the one key insight?
- What must the reader understand?
- What action should they take?
Step 2: Mark Everything Else
- Examples that don't serve the core
- Theory that doesn't support application
- Explanations that repeat points
- Transitions that are too long
Step 3: Cut Systematically
- Eliminate redundancy (phrases → words)
- Remove filler words
- Cut weak qualifiers
- Simplify constructions
- Remove redundant examples
- Trim theory
Step 4: Tighten Remaining Text
- Convert passive to active
- Replace phrases with words
- Strengthen weak verbs
- Cut unnecessary introductions
Step 5: Verify Impact
- Does the core message remain clear?
- Are key insights preserved?
- Is the article still engaging?
- Does it meet word count?
Quick Reference: Common Cuts
| Before | After | Saved |
|---|---|---|
| in order to | to | 2 words |
| due to the fact that | because | 4 words |
| at this point in time | now | 4 words |
| it is important to note that | (delete) | 6 words |
| a large number of | many | 3 words |
| in the near future | soon | 3 words |
| with the exception of | except | 3 words |
| it should be pointed out that | (delete) | 6 words |
Discipline Techniques
The 10% Rule
After first draft, cut 10% without changing meaning. Then cut another 5% if still over limit.
The Sentence Test
For each sentence, ask:
- Does this advance understanding?
- Does this create engagement?
- Does this build toward insight?
If no to all three, cut it.
The Paragraph Test
For each paragraph, ask:
- What is the core point?
- Can I say it in fewer words?
- Does every sentence serve the point?
The Section Test
For each section, ask:
- What is the key insight?
- What is the minimum needed to convey it?
- What can be cut without losing the insight?
Word Count Targets
For 800-1000 word articles:
- Opening: 100-150 words
- Each main section: 150-200 words
- Examples: 50-100 words each (2-3 total)
- Conclusion: 80-120 words
When over limit, cut in this order:
- Redundant examples
- Theoretical elaboration
- Repetitive explanations
- Long transitions
- Filler words and phrases
Checklist
- Eliminated all redundant phrases
- Converted passive to active voice
- Replaced phrases with single words
- Removed filler words
- Cut unnecessary qualifiers
- Strengthened weak verb + adverb combinations
- Removed introductory phrases
- Simplified complex constructions
- Cut redundant examples (kept only strongest)
- Trimmed theoretical elaboration
- Removed repetitive phrasing
- Condensed transitions
- Verified word count
- Confirmed core message remains clear
- Verified article still engaging
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?