Agent skill · Documentation

finman-writing-style

Use when the prose, abstract, or introduction of a Financial Management (FM) manuscript buries the idea or its managerial/market payoff — FM's brand is "articles people actually read." Shapes exposition for a general finance audience; it does not establish results (finman-identification) or run the submission preflight (finman-submission).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill finman-writing-style --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 8 KB
Bundled scripts: none
Path: Financial-Management-Skills/skills/finman-writing-style/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Writing Style (finman-writing-style) ## When to trigger - The abstract and intro state what was done but not why a finance reader (or a practitioner) should care - The paper reads like a technical report — correct, dense, and unread - The contribution is buried under literature review or methodology before the finding appears - You are doing the final exposition pass before submission (do this *after* the evidence settles) ## The FM writing bar FM is unusually explicit that it wants **"a finance journal that publishes academic articles that people actually read."** That is a writing standard, not a slogan. The exposition is judged on whether a **general finance audience** — not just the immediate subfield — grasps the question, the answer, and the **practical relevance** quickly, and whether the paper **provokes and furthers debate.** Concretely: the abstract and first page must deliver the finding and its managerial/market implication before any apparatus; jargon that only insiders parse is a cost; and the "so-what for managers, investors, or regulators" must be stated, not left for the reader to infer. This is the lane that separates FM from siblings whose house voice tolerates

What's inside
Steps it walks through
  1. When to trigger
  2. The FM writing bar
  3. The exposition build (in order)
  4. The first-page test (FM's hardest sentence-level bar)
  5. Checklist
  6. Writing the implications so they survive a skeptical read
  7. Anti-patterns
  8. Worked vignette (illustrative)
  9. Referee pushback mapped to the writing fix
  10. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the finman-writing-style skill do?

Use when the prose, abstract, or introduction of a Financial Management (FM) manuscript buries the idea or its managerial/market payoff — FM's brand is "articles people actually read." Shapes exposition for a general finance audience; it does not establish results (finman-identification) or run the submission preflight (finman-submission).

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill finman-writing-style --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.

Keep going