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 Tables Figures

ASecurity

Use when finalizing the main exhibits (tables and figures) of a Journal of Political Economy (JPE) manuscript so each one carries economic content and is self-contained. Sets exhibit design and notes standards; it does not decide which results to report (see jpe-robustness).

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jpe Tables Figures?

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

Security grade badge for Jpe Tables Figures
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jpe-tables-figures/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jpe-tables-figures)

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

Download with Pro
Files
SKILL.md
---
name: jpe-tables-figures
description: Use when finalizing the main exhibits (tables and figures) of a Journal of Political Economy (JPE) manuscript so each one carries economic content and is self-contained. Sets exhibit design and notes standards; it does not decide which results to report (see jpe-robustness).
---

# Tables & Figures (jpe-tables-figures)

## When to trigger

- Tables are overloaded with columns; the reader cannot find the economic point
- Figures are decorative rather than carrying the argument
- Notes are thin — a reader cannot reconstruct units, sample, or specification from the exhibit alone
- You are deciding what belongs in the main text vs. the online appendix

## The JPE exhibit philosophy

A JPE table or figure should be **self-contained and economically legible**: a referee skimming exhibits should grasp the result, the magnitude, and what it means. As a **University of Chicago Press** journal, JPE typesets accepted exhibits to Chicago Press production standards — no chartjunk, no gratuitous color, units and economic magnitudes front and center. Every exhibit must also be regenerated by the master script in the **JPE Dataverse** replication deposit, so the numbers in the paper and the numbers the code produces must match exactly when the **JPE Data Editor** verifies them at conditional accept (see `jpe-replication-package`). The headline result usually deserves a *figure* (an event-study plot, a fit-of-model plot, a counterfactual) because magnitudes and dynamics read faster than a coefficient.

### Tables
- Report **economic magnitudes**, not just stars: effect relative to the mean, an elasticity, a standardized effect, or a dollar/welfare figure.
- One table = one idea. Main results table should fit on a page and be readable without the text.
- Columns build an argument (baseline → +controls → preferred → alternative design), not an undifferentiated grid.
- Standard errors in parentheses; state the clustering level in the note. Prefer reporting CIs or exact SEs over star-only inference.
- Self-contained note: sample, period, unit of observation, dependent-variable definition, specification, SE structure, and what each column adds.

### Figures
- Use a figure to carry the main result when dynamics/magnitudes matter (event studies, dose-response, model fit, counterfactual paths).
- Plot confidence bands, not just point estimates. Label axes with units and economic meaning.
- Grayscale-safe and legible in print; no 3-D effects, no unnecessary gridlines.
- Each figure's caption states what the reader should conclude economically.

### Main text vs. online appendix
- Main text: the identifying result, the mechanism evidence, the key magnitude, the headline counterfactual — typically a small number of exhibits.
- Online appendix: the full robustness battery, descriptive tables, secondary heterogeneity, and supporting derivations.

## Checklist

- [ ] Headline result expressed as an economic magnitude (relative to mean / elasticity / welfare), not stars alone
- [ ] Main results readable without the surrounding text
- [ ] Every table note states sample, period, unit, DV definition, spec, and clustering level
- [ ] Columns/panels build an argument rather than dumping specifications
- [ ] At least one figure carries the main result with confidence bands
- [ ] Figures legible in grayscale; axes labeled with units and meaning
- [ ] Heavy robustness/descriptive material moved to the online appendix
- [ ] Exhibit numbering matches in-text references exactly

## Anti-patterns

- Star-only tables with no economic magnitude — a referee cannot tell if the effect matters
- Numbers in an exhibit that the deposited code does not reproduce — fatal at JPE Data Editor verification
- A 12-column main table that no one can parse
- Figures with no confidence bands, or with chartjunk / 3-D / rainbow palettes
- Notes too thin to reconstruct the specification
- Reporting R² and stars but never the units of the dependent variable
- Putting the full robustness battery in the main text and crowding out the economic story

## Output format

```
【Main exhibits】tables: N, figures: N
【Magnitude reported】mean-relative / elasticity / welfare / standardized
【Headline figure】what it shows + has CIs? [y/n]
【Notes complete】sample/period/unit/DV/spec/clustering present? [y/n]
【Main vs. appendix split】...
【Next】jpe-writing-style
```

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 →