Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Jpe Writing Style

ASecurity

Use when polishing the prose of a Journal of Political Economy (JPE) manuscript into its spare, analytical, economics-first register. Tightens voice, structure, and citation/format house style; it does not fix the economic argument itself (see jpe-theory-model / jpe-identification).

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill jpe-writing-style --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jpe Writing Style?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Jpe Writing Style
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jpe-writing-style/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jpe-writing-style)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: jpe-writing-style
description: Use when polishing the prose of a Journal of Political Economy (JPE) manuscript into its spare, analytical, economics-first register. Tightens voice, structure, and citation/format house style; it does not fix the economic argument itself (see jpe-theory-model / jpe-identification).
---

# Writing Style & House Conventions (jpe-writing-style)

## When to trigger

- The draft is wordy, hedged, or buries the result under qualifications
- Prose explains procedure before establishing economic purpose
- Citation style, notation, or formatting is inconsistent with JPE conventions
- This is the **late polish** stage — identification and model are already sound

## The JPE voice

JPE prose is **spare, precise, and economics-first**. The writing carries an argument; every paragraph advances the economic case. Sentences are declarative and unhedged where the evidence supports the claim. Jargon is minimized; the economic intuition is stated in words before the algebra. A generalist economist should follow the argument; a specialist should find it rigorous.

Register rules:
- Lead with the economics, then the method. "Higher entry costs reduce competition; we estimate this using..." not "We run a regression of price on entry cost."
- State results plainly. Replace "our findings appear to suggest a potentially meaningful relationship" with "entry costs raise prices by X%."
- Active voice for what the paper does; reserve hedging for genuine uncertainty.
- Define notation once, use it consistently; explain each equation's economic content in prose.
- Cut throat-clearing ("It is important to note that...", "In this paper, we will...").

## Structure conventions

- **Sections**: Introduction → (Model / Theory) → Data / Institutional setting → Empirical strategy → Results → Mechanisms / Robustness → (Counterfactuals) → Conclusion. Order theory before empirics when the model leads.
- **Introduction** does the heavy lifting (see `jpe-literature-positioning`): question, mechanism, gap, what you do, findings.
- **Conclusion** states what economics learned and the portable lesson — not a summary of every table.
- Footnotes for genuine asides, not for results that belong in the text.

## House-style format

- **References: Chicago author-date** (e.g., "(Becker 1968)", "Black and Scholes (1973)"), with an alphabetized reference list — *not* numbered citations. This is a hard University of Chicago Press house convention and a frequent reason a JPE referee flags a mis-templated submission.
- Theory and empirics are integrated within the paper; proofs and heavy robustness go to appendices / online appendix.
- American spelling; consistent decimal and unit conventions; double-spaced manuscript; equations numbered and referenced as "equation (3)."
- Follow the *Chicago Manual of Style* conventions the University of Chicago Press uses. Verify the current author guidelines (including any abstract/length limits) on the journal's official page before submission, as formatting details are updated periodically.

## Checklist

- [ ] Each paragraph advances the economic argument; throat-clearing removed
- [ ] Results stated plainly with magnitudes, hedging reserved for real uncertainty
- [ ] Economics stated before method in every key passage
- [ ] Every equation has a sentence of economic interpretation
- [ ] Citations are Chicago author-date and consistent; reference list complete
- [ ] Notation defined once and used consistently
- [ ] Conclusion states the portable economic lesson, not a table-by-table recap
- [ ] Spelling/format follow Chicago/UChicago Press conventions (verified against current guidelines)

## Anti-patterns

- Hedged, passive prose that obscures a result the evidence actually supports
- Method-first writing that makes the reader hunt for the economics
- Numbered/bracket citations (wrong house style — JPE is Chicago author-date)
- Equations dropped in with no verbal economic interpretation
- A conclusion that recaps every table instead of stating what was learned
- Over-long sentences stacking qualifications; jargon where plain economics would do

## Output format

```
【Voice】economics-first, unhedged where warranted? [y/n + fixes]
【Hedging removed】list of softened claims tightened
【Equations interpreted】all have prose meaning? [y/n]
【Citation style】Chicago author-date verified
【Format】Chicago/UChicago Press conventions checked (verify current guidelines)
【Conclusion】states portable lesson? [y/n]
【Next】jpe-referee-strategy
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →