This skill should be used when the user asks to "write an economics paper", "draft a working paper", "edit finance writing", "review my econ paper", "write for a journal", or needs guidance on economics and finance writing. Based on McCloskey's "Economical Writing" with discipline-specific word lists and examples.
/plugin marketplace add edwinhu/workflows/plugin install workflows@edwinhu-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/economical-writing-full.mdStyle guide for economics journal articles, working papers, and finance analysis based on Deirdre McCloskey's Economical Writing.
Invoke this skill for:
For general writing: Use /writing skill (Strunk & White)
For legal writing: Use /writing-legal skill (Volokh)
If you write ANY of these, DELETE the draft and START OVER:
These signal you haven't found your hook. Start fresh with a compelling finding.
One concept = One word. If you catch yourself varying terms ("industrialization" / "development" / "growth") for the same concept, you are confusing the reader. Pick ONE term and use it consistently.
| Excuse | Reality | Do Instead |
|---|---|---|
| "But journals use boilerplate" | Bad journals do | HOOK reader with finding |
| "Elegant variation shows vocabulary" | Shows you don't know what you mean | USE same word for same thing |
| "Readers need roadmap paragraph" | They skip it | DELETE table-of-contents para |
| "This terminology is standard in field" | Doesn't make it good | USE concrete Anglo-Saxon words |
| "Need to sound academic" | Sounds pompous instead | WRITE like human being |
| "Passive voice sounds objective" | Sounds evasive | USE active voice |
| "Technical writing must be formal" | Technical ≠ turgid | BE clear AND technical |
When to delete and restart:
How to restart:
Old: "This paper discusses the relationship between X and Y..."
New: "Trade liberalization increased wages by 15% for skilled workers."
Restart with THE FINDING, not with throat-clearing.
Choose an implied reader and stick with her. A skeptical but sympathetic colleague. Keep the prose at one level of difficulty. If it embarrasses you to imagine how she would read it, the stuff is embarrassing.
| Anti-Pattern | Why It Fails |
|---|---|
| "This paper discusses..." | Bores the reader; use a hook instead |
| Table-of-contents paragraph | Readers skip it; they can't understand until they've read the paper |
| Background/padding | If you discovered it was beside the point, don't include it |
| "As we shall see" | Useless anticipation; the reader will see soon enough |
| Metric conversions every time | Shows you think the reader is an ignoramus |
Never repeat without apologizing ("as I said earlier"). If apologizing too much, you're repeating too much.
End each paragraph with a simple, street-talk encapsulation. The paragraph can be technical as long as the last sentence comes down a notch. It makes the paragraph sing.
The reader should understand the table without the main text. Use words in headings, not acronyms. "Logarithm of Domestic Price" not "LPDOM". Follow Tufte: no chart junk, have a point.
Use meaningful labels in equations: "Quantity of Grain = 3.56 + 5.6(Price of Grain)" not "Q = 3.56 + 5.6P where Q is..."
Repeat key words to link sentences. (AB)(BC)(CD) is easy to understand. The figure is called polyptoton. English achieves coherence by repetition, not by "not only...but also" which marks you as incompetent.
Use one word to mean one thing. A paper used: "industrialization," "growing structural differentiation," "economic and social development," "development," "economic growth," "growth," and "revolutionized means of production" to mean the same thing. Don't.
When uncertain, look back and use the same word.
| Principle | Example |
|---|---|
| Be concrete | "sheep and wheat" not "natural resource-oriented exports" |
| Untie Teutonisms | "equalization of the prices of factors" not "factor price equalization" |
| Avoid ersatz economics | Never use "skyrocketing," "fair prices," "vicious cycle," "exploit" |
| Avoid this-ism | Replace this, these, those with the |
See references/economical-writing-full.md for extended bad words list, Teutonism examples, and ersatz economics vocabulary.
| Problem | Solution |
|---|---|
| "This paper discusses X" | Hook the reader with the finding |
| Table-of-contents paragraph | Delete it; readers skip it anyway |
| "As we shall see" | Delete; anticipation is useless |
| Elegant variation | Use the same word for the same thing |
| Five-dollar words | Anglo-Saxon roots are more concrete |
| Noun pile-ups | Untie with "of" |
| This/that/these/those | Replace with "the" |
| "Not only...but also" | Just use "and" |
For comprehensive guidance, consult:
references/economical-writing-full.md - Complete McCloskey guide covering:
Load the full reference when:
After completing any economics writing task, invoke /ai-anti-patterns to check for AI writing indicators. The /writing skill covers general prose principles (active voice, omit needless words) that complement this skill.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.