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

Qje Tables Figures

ASecurity

Use when finalizing the main exhibits of a Quarterly Journal of Economics (QJE) manuscript — making the paper figure-forward, with clean tables and self-contained notes that read well in QJE's single-PDF, author-date format. Designs exhibits; it does not run new analysis.

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

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Qje Tables Figures?

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

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

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

Download with Pro
Files
SKILL.md
---
name: qje-tables-figures
description: Use when finalizing the main exhibits of a Quarterly Journal of Economics (QJE) manuscript — making the paper figure-forward, with clean tables and self-contained notes that read well in QJE's single-PDF, author-date format. Designs exhibits; it does not run new analysis.
---

# Tables & Figures (qje-tables-figures)

## When to trigger

- The main result is a dense table with too many columns
- The paper is "table-heavy" when the design would land better as a figure
- Table notes are incomplete (sample, units, clustering, significance unclear)
- An event-study / RDD / binscatter result is hidden in a table instead of plotted

## QJE aesthetic: figure-forward, self-contained exhibits

QJE has moved firmly toward **figure-forward presentation** — the Opportunity Insights / Chetty-style QJE paper makes its central result legible in one well-designed graph (e.g., the binned mobility maps and exposure-effect plots of the QJE 2014/2018 neighborhoods papers). Identification designs are inherently visual: event-study plots, RDD discontinuity plots, and binned scatters communicate credibility better than a coefficient buried in a regression column. Tables remain essential for estimates and robustness, but the *headline* should often be a figure a reader grasps in five seconds. Practical QJE constraints: at initial submission **everything is one PDF with figures embedded** (no separate figure files), exhibits are numbered and called out in order, and in-text references are **author-date (Chicago)**.

## The headline-figure decision

| Design          | Headline figure                                              |
|-----------------|--------------------------------------------------------------|
| DID / event std | Event-study plot: leads ≈ 0, clean post-treatment dynamics   |
| RDD             | Discontinuity plot: binned means + local polynomial fit      |
| IV              | First-stage and reduced-form scatter / binscatter            |
| RCT             | Treatment-vs-control outcome distributions or effect-by-arm  |
| Descriptive     | The new fact, plotted with the data doing the talking        |

## Table craft

- **Width discipline.** Main results table should be readable; if it sprawls past a handful of columns, split it or move variants to the appendix (no page limit means you can — but readability still wins).
- **Self-contained notes.** Every table/figure note states: sample and time span, unit of observation, what each column is, fixed effects included, standard-error clustering level, and how significance is denoted.
- **Standard errors in parentheses**, clustering level named in the note; report N and relevant fit statistics.
- **Coefficients with meaning.** Report units so the magnitude is interpretable (effect in SDs, in dollars, in percentage points), not just a bare number.
- Author-date (Chicago) in-text references; figures and tables numbered and called out in order.

## Figure craft

- Show the data: binned scatters, confidence bands, and raw-ish patterns build credibility.
- Avoid chartjunk: no 3D, no needless color, legible axis labels with units; figures must remain legible embedded in the single submission PDF and at print resolution.
- Confidence intervals shown, not just point estimates; bandwidth/bin choices noted.
- A figure should be interpretable from its caption alone.

## Checklist

- [ ] The central result has a headline figure a reader grasps quickly
- [ ] Main table is readable; sprawling variants moved to the appendix
- [ ] Every exhibit note is self-contained (sample, units, FE, clustering, significance)
- [ ] Magnitudes are interpretable (units stated), not bare coefficients
- [ ] Event-study / RDD / first-stage results are plotted, not only tabulated
- [ ] Confidence intervals / bands shown on figures
- [ ] Figures embedded and legible in the single submission PDF; numbered, author-date citations

## Anti-patterns

- A 9-column main table when a single event-study figure would carry the result
- Table notes that omit the clustering level or the sample definition
- Reporting coefficients with no units, so magnitude is uninterpretable
- Decorative 3D/colored charts that add no information
- Burying the cleanest evidence (the discontinuity, the leads) in an appendix table

## Output format

```
【Headline exhibit】figure type chosen + why
【Main table】column count + what moved to appendix
【Notes audit】sample / units / FE / clustering / significance present? [Y/N each]
【Magnitude legibility】units stated? [Y/N]
【Figures plotted】[event study / RDD / first stage / ...]
【Next step】qje-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 →