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

Jfe Internet Appendix

ASecurity

Use when organizing the journal-hosted Internet Appendix for a Journal of Financial Economics (JFE) manuscript — what to move off the main text, how to cross-reference it, and how to keep it self-contained. Structures the appendix; it does not decide which robustness tests to run (jfe-robustness).

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 jfe-internet-appendix --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jfe Internet Appendix?

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

Security grade badge for Jfe Internet Appendix
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jfe-internet-appendix/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jfe-internet-appendix)

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

Download with Pro
Files
SKILL.md
---
name: jfe-internet-appendix
description: Use when organizing the journal-hosted Internet Appendix for a Journal of Financial Economics (JFE) manuscript — what to move off the main text, how to cross-reference it, and how to keep it self-contained. Structures the appendix; it does not decide which robustness tests to run (jfe-robustness).
---

# Internet Appendix (jfe-internet-appendix)

## When to trigger

- Robustness tables, proofs, and extra derivations are crowding the main text
- The main text exceeds a readable length and you must triage exhibits
- A referee asks for many additional tests you cannot fit in the body
- You need every main-text claim that says "untabulated" or "in the appendix" to actually land somewhere

## Why the Internet Appendix matters at JFE

JFE hosts an Internet Appendix where exhaustive robustness, proofs, additional tests, and detailed methodology live. Given JFE's robustness-heavy culture, a deep, well-organized appendix is expected — it is where the "every alternative ruled out" work is documented without making the main paper unreadable.

**JFE specifics (verify on jfinec.com):** the journal's submission instructions ask that any online/internet appendix be **attached to the end of the main manuscript file** at submission, rather than uploaded as a wholly separate document. Number it as its own IA series regardless. Keep the Internet Appendix conceptually distinct from the **replication package** (code + non-proprietary data deposited to Mendeley Data at acceptance, mandatory for papers submitted on/after 1 July 2021) — the appendix holds *results and proofs*, the deposit holds *code and data*.

## What belongs in the Internet Appendix

- **Proofs and derivations** for any theoretical results stated in the main text.
- **Secondary robustness** — alternative measures, additional subsamples, extra cluster levels, wild bootstrap — beyond the headline checks kept in the body.
- **Variable construction details** too granular for the main text (filters, matching algorithms, data cleaning).
- **Additional results** referenced as "untabulated" or "see Internet Appendix."
- **Supplementary figures** and diagnostic plots.
- **Replication notes** that complement (not replace) the required code/data deposit.

## What stays in the main text

- The headline result and the 3–6 most decisive robustness checks.
- The identification evidence a reader needs to believe the result (parallel trends, first-stage strength).
- The core variable-definition table.

## Organization rules

- Number appendix exhibits in their own series (e.g., Table IA.1, Figure IA.1).
- Every main-text pointer ("untabulated," "Internet Appendix Table IA.3") must resolve to a real exhibit.
- The appendix should be self-contained: a reader who never opens the main paper can still read each appendix table from its title and notes.
- Mirror the main text's reporting conventions (SEs, stars, cluster level) so cross-reading is frictionless.

## Checklist

- [ ] Every "untabulated"/"see appendix" claim resolves to a real exhibit
- [ ] Proofs and granular derivations are in the appendix, not the body
- [ ] Headline robustness kept in main text; the long tail moved out
- [ ] Appendix exhibits numbered in their own IA series
- [ ] Appendix appended to the end of the main manuscript file (JFE practice)
- [ ] Appendix exhibits are self-contained (titles + notes)
- [ ] Reporting conventions match the main text
- [ ] Mendeley Data code/data deposit prepared separately (mandatory for post-2021 submissions)

## Anti-patterns

- Main-text pointers to appendix tables that do not exist
- Treating the appendix as a dumping ground with no ordering or notes
- Moving the *identification* evidence to the appendix to shorten the body
- An appendix whose tables cannot be read without the main text
- Confusing the Internet Appendix with the mandatory code/data replication package

## Output format

```
【Main-text kept】headline result + decisive checks
【Moved to IA】proofs / robustness / construction / extra results
【Pointer audit】all "untabulated"/"see IA" claims resolve? yes/no
【IA numbering】IA series applied? yes/no
【IA placement】appended to main file (JFE practice)? yes/no
【Code/data deposit】Mendeley Data package prepared separately? yes/no
【Next】jfe-writing-style
```

Attribution

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

693161 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 →