finman-internet-appendix
Use when deciding what belongs in a Financial Management (FM) internet appendix vs. the main paper, and how to organize it so each supplementary exhibit maps to a main-text claim. Structures supporting material; it does not establish results (finman-identification / finman-robustness) or finalize the data/code package (finman-submission).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill finman-internet-appendix --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Internet Appendix (finman-internet-appendix) ## When to trigger - The main paper is bloated with secondary tables that crowd the headline result - A referee asked for a check whose result is reassuring but not central to the story - Variable-construction detail, sample screens, or derivations are too long for the main text - You are about to submit and need the supplementary materials organized and labeled ## The FM internet-appendix bar FM's "people actually read" brand and its **less weight on trivial robustness** stance make the internet appendix a strategic tool, not a dumping ground. The main paper should carry only what a reader needs to be convinced; everything that is *reassuring but not load-bearing* belongs in the internet appendix. The discipline is **traceability**: every internet-appendix exhibit must map to a specific main-text claim or referee concern, and the main text must point to it where relevant. An appendix that is a disorganized pile of leftover tables undercuts the paper; one that is a clean, indexed companion makes the main paper lean and the author look in command of the evidence. (FM's exact archiving/hosting and data-and-code policy — 待核实 against the W
- When to trigger
- The FM internet-appendix bar
- What goes where
- Organizing sequence
- Checklist
- Anti-patterns
- Worked vignette (illustrative)
- The promote / park / cut decision
- Referee pushback mapped to the appendix fix
- Code and data alongside the appendix
- Output format
What does the finman-internet-appendix skill do?
Use when deciding what belongs in a Financial Management (FM) internet appendix vs. the main paper, and how to organize it so each supplementary exhibit maps to a main-text claim. Structures supporting material; it does not establish results (finman-identification / finman-robustness) or finalize the data/code package (finman-submission).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill finman-internet-appendix --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.