writing-econ

Internal skill for economics and finance writing. Loaded by /writing when style=econ. Based on McCloskey's "Economical Writing".

6 stars

Best use case

writing-econ is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Internal skill for economics and finance writing. Loaded by /writing when style=econ. Based on McCloskey's "Economical Writing".

Teams using writing-econ should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/writing-econ/SKILL.md --create-dirs "https://raw.githubusercontent.com/edwinhu/workflows/main/skills/writing-econ/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/writing-econ/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How writing-econ Compares

Feature / Agentwriting-econStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Internal skill for economics and finance writing. Loaded by /writing when style=econ. Based on McCloskey's "Economical Writing".

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Economics and Finance Writing

Style guide for economics journal articles, working papers, and finance analysis based on Deirdre McCloskey's *Economical Writing*.

## On Skill Load

**Step 1: Load base writing rules**

Read `${CLAUDE_SKILL_DIR}/../../skills/writing/SKILL.md` and follow its instructions.

**Step 2: Check for active workflow**

If `.planning/ACTIVE_WORKFLOW.md` exists and `workflow: writing`, update `style: econ`.

If no `.planning/PRECIS.md` exists in the project:
- Suggest: "No PRECIS.md found. Consider `/writing` to set up thesis, audience, and claims first."

**Step 3: Apply econ-specific rules below**

## When to Use

Invoke this skill for:
- Economics journal articles and working papers
- Finance analysis and market commentary
- Policy briefs and economic reports
- Editing economics/finance prose for clarity

**For general writing**: Use `/writing` skill (Strunk & White)
**For legal writing**: Use `/writing-legal` skill (Volokh)

## Enforcement

### IRON LAW #1: NO BOILERPLATE WITHOUT DELETE & RESTART

If you write ANY of these, DELETE the draft and START OVER:
- "This paper discusses..."
- Table-of-contents paragraph
- "As we shall see"
- "It is interesting to note that..."
- "The rest of this paper is organized as follows..."

These signal you haven't found your hook. Start fresh with a compelling finding.

### IRON LAW #2: NO ELEGANT VARIATION

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.

### Econ Writing Facts

- Describing an empirical strategy without understanding its identification assumption is a fatal methodological gap — referees reject papers for it, and not addressing endogeneity is the canonical fatal omission. Pattern-matching the design from similar papers is not econometric reasoning; presenting it as such is an unverified claim wearing a methods section.
- Openers like "In recent years..." read as AI filler to academic readers — an opening written "to seem academic" destroys credibility before the finding lands.

### Red Flags

- About to write a "standard introduction" → STOP. Find the hook first.
- About to leave boilerplate in place "to improve later" → STOP. Fix it now or restart — boilerplate left in stays in.
- About to vary terms for the same concept → STOP. Consistency beats variation; the reader thinks varied terms are different concepts.
- About to keep a phrase because "readers expect it" → STOP. Expectations can be wrong.

### Delete & Restart Pattern

**When to delete and restart:**

1. **Boilerplate detected in first paragraph** → Delete entire intro, write finding-first
2. **Three different terms for same concept** → Delete section, pick ONE term
3. **Table-of-contents paragraph exists** → Delete it, no replacement needed
4. **Metric conversions every time** → Delete all but first, trust reader

**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.

## Core Principles

### Speak to One Reader

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.

### Avoid Boilerplate

| 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.

### Control Tone

- Avoid invective: "This is pure nonsense" arouses suspicion the argument is weak
- Delete every "very" and "absolutely" - most things aren't
- Use wit to compensate for strong opinions
- Relax the pose of The Scientist; write like a human being

### One Point Per Paragraph

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.

### Make Tables Self-Explanatory

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..."

### Make Writing Cohere

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.

## Word Choice

### Avoid Elegant Variation

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.

### Key Principles

| 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.

## Quick Reference

| 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" |

## Progressive Disclosure

For comprehensive guidance, consult:

### Reference File

- **`references/economical-writing-full.md`** - Complete McCloskey guide covering:
  - 35 rules with full explanations and examples
  - Extended bad words list with usage notes
  - Historical and etymological context

### When to Load Reference

Load the full reference when:
- Encountering specific vocabulary questions
- Needing detailed examples for economics jargon
- Working on substantial manuscript revision
- Teaching economics writing

## Integration

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.

Related Skills

writing

6
from edwinhu/workflows

This skill should be used when the user asks to 'write a paper', 'start a writing project', 'draft an article', 'write about', 'brainstorm writing topics', 'gather sources for a paper', 'what should I write about', or needs the writing workflow entry point for any writing task.

writing-validate

6
from edwinhu/workflows

Validate draft sections cover all PRECIS claims before review.

writing-setup

6
from edwinhu/workflows

Internal skill for creating PRECIS.md, OUTLINE.md, and ACTIVE_WORKFLOW.md. Called after brainstorm sources are gathered.

writing-revise

6
from edwinhu/workflows

This skill should be used when the user asks to 'revise writing', 'fix review issues', 'polish draft', 'apply review feedback', 'complete writing workflow', or after /writing-review produces REVIEW.md with issues to fix.

writing-review

6
from edwinhu/workflows

Internal skill for hierarchical document review. Called by writing-validate after claim validation passes.

writing-precis-reviewer

6
from edwinhu/workflows

Internal skill used by writing-setup at exit gate. Dispatches a reviewer subagent to verify PRECIS.md quality before outlining. NOT user-facing.

writing-outline

6
from edwinhu/workflows

Internal skill for creating detailed section outlines. Called by /writing workflow after PRECIS and master OUTLINE are complete.

writing-outline-reviewer

6
from edwinhu/workflows

Internal skill used by writing-outline at exit gate. Dispatches a reviewer subagent to verify OUTLINE.md quality before drafting. NOT user-facing.

writing-lit-review

6
from edwinhu/workflows

Internal skill for literature review and source materialization. Called after brainstorm, before setup. NOT user-facing.

writing-legal

6
from edwinhu/workflows

Internal skill for academic legal writing. Loaded by /writing when style=legal. Based on Volokh's "Academic Legal Writing".

writing-handoff

6
from edwinhu/workflows

Create structured handoff document for writing workflow session pause/resume.

writing-general

6
from edwinhu/workflows

Internal skill for Strunk & White writing rules. Loaded by /writing for quick edits or as base layer for domain skills.