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

Rfs Tables Figures

ASecurity

Use when main-paper exhibits are the bottleneck for a The Review of Financial Studies (RFS) manuscript — table layout, standard-error reporting, and publication-grade figures. Finalizes exhibits; does NOT decide robustness content or move material to the appendix.

1,052 stars
0 votes
0 copies
0 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 rfs-tables-figures --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Rfs Tables Figures?

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

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

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

Download with Pro
Files
SKILL.md
---
name: rfs-tables-figures
description: Use when main-paper exhibits are the bottleneck for a The Review of Financial Studies (RFS) manuscript — table layout, standard-error reporting, and publication-grade figures. Finalizes exhibits; does NOT decide robustness content or move material to the appendix.
---

# Tables & Figures (rfs-tables-figures)

## When to trigger

- The main table has too many columns or unlabeled specifications
- Standard errors, significance stars, or clustering are unclear or inconsistent
- A figure is a default software plot rather than a publication-grade exhibit
- A reader cannot tell from a table alone what the regression is

## What an RFS exhibit must do

Every main table or figure should be **self-contained**: a referee skimming exhibits should grasp the design, the result, and the inference without the text. RFS articles are typeset by **Oxford University Press** for the SFS, so build exhibits to OUP production specs (vector figures, clean two-column-friendly tables). One RFS-specific constraint shapes every exhibit: because RFS requires **public release of all code** as a condition of publication, each table and figure must be **regenerable by the released scripts** — a number a referee cannot reproduce from your code is a liability. The portfolio-sort and spanning exhibits in Hou, Xue, and Zhang (2015) "Digesting Anomalies" (RFS 28(3)) are a good template for decile monotonicity and long–short t-stats.

### Table conventions
- **One question per table.** A main paper typically has a handful of focused tables, not a dozen sprawling ones; overflow goes to the Internet Appendix (`rfs-internet-appendix`).
- **Self-contained caption**: state the sample, period, unit of observation, estimator, and what is being shown.
- **Coefficients with SE below in parentheses**; state the SE type (e.g., "standard errors clustered by firm") in the notes — not only stars.
- **Report significance honestly**: stars are a convenience; the SE/t-stat is the substance. State the convention in the notes.
- **Summary-statistics table**: means, SD, and key percentiles for every variable used; a correlation matrix when relevant.
- **Decimal alignment, consistent rounding, consistent variable names** across all tables.
- **Economic magnitude**, not only statistical significance — report effect sizes in interpretable units.

### Figure conventions
- Event-study / coefficient plots with **confidence bands** for DID and dynamic effects — strongly preferred over a pre/post dummy table.
- Binned scatter / RD plots for discontinuity designs.
- Label axes with units; legends self-explanatory; greyscale-legible (do not rely on color alone).
- Vector format (PDF/EPS) for print; consistent fonts and sizing.

### Reporting conventions that signal craft to finance referees
- Report N and within/adjusted R² (or pseudo-R²) for every regression column.
- State which fixed effects are absorbed in each column (a "FE" panel of yes/no rows).
- For Fama–MacBeth, report the number of cross-sections and the time-series length.
- For portfolio sorts, show monotonicity across deciles and the long–short spread with t-stat.
- Keep one canonical ordering of variables across all tables so readers can scan rows.
- Put units in the caption (returns in %, dollars in millions) — never leave a number unitful.

## Checklist

- [ ] Each main table answers one question; the rest is in the IA
- [ ] Every table caption states sample, period, unit, estimator
- [ ] SEs reported below coefficients; SE type stated in notes (clustering/adjustment)
- [ ] Economic magnitudes reported, not just significance
- [ ] Summary-statistics table present for all variables
- [ ] DID/dynamic effects shown as an event-study figure with CIs
- [ ] Figures legible in greyscale; axes labeled with units; vector format (OUP production-ready)
- [ ] Every reported number is regenerable from the code RFS requires you to release
- [ ] Variable names, rounding, and notation consistent across all exhibits

## Anti-patterns

- An 11-column main table where no one can tell what each column estimates.
- Stars with no statement of the standard-error type or clustering.
- Reporting t-stats but never the economic magnitude of the effect.
- A default Stata/R plot pasted in without axis labels or units.
- Color-only figures that become unreadable in print.
- Variable named `x1` in one table and `Leverage` in another.

## Output format

```
【Main exhibits】[table/figure list, one question each]
【SE reporting】type + clustering stated in every table note? yes/no
【Magnitude】economic effect sizes reported? yes/no
【Figures】event-study/RD plots with CIs? format?
【Moved to IA】[...]
【Next step】rfs-internet-appendix
```

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 →