A skill your agent uses 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…

MITAuto-check passedWriting & Content

Install Finman Writing Style

skills CLI
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill finman-writing-style -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install brycewang-stanford/Awesome-Journal-Skills finman-writing-style --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Financial-Management-Skills/skills/finman-writing-style .claude/skills/finman-writing-style && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
finman-writing-style
GitHub stars
1.2k
Token cost
~2k tokens
SKILL.md length
1,044 words
Files
1
Skills in repo
2,387
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses 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…

  • Works in 6 steps: Abstract: finding-first. Lead with the… → First page: the hook and the payoff.… → Contribution paragraph. One paragraph… → …
  • Introduction of a Financial Management (FM) manuscript buries the idea
  • SKILL.md covers When to trigger, The FM writing bar, The exposition build (in order) and The first-page test (FM's…, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Finman Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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).

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Writing & Content, covering Brand voice and tone. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. | 覆盖主流期刊的… The licence is MIT.

When your agent uses it

  • Introduction of a Financial Management (FM) manuscript buries the idea
  • Its managerial/market payoff — FMs brand is articles people actually read. Shapes exposition for a general finance audience
  • It does not establish results (finman-identification)
  • Run the submission preflight (finman-submission)

Example prompts

  • “s brand is”
  • “/finman-writing-style”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Abstract: finding-first. Lead with the result and its implication in the first two sentences; method and data come after. A reader should…
  2. First page: the hook and the payoff. State the live financial question, the answer, and who should change a decision because of it…
  3. Contribution paragraph. One paragraph naming the specific delta (from finman-literature-positioning) and the general-interest implication…
  4. Mechanism and magnitude in plain finance language. Explain the channel and the economic magnitude in terms a CFO, investor, or regulator…
  5. Practical-relevance close. End sections (and the paper) by connecting the estimate to a decision; FM rewards a paper that tells the reader…
  6. Cut for readability. Remove throat-clearing, redundant caveats, and apparatus that does not change a conclusion — every sentence should…

What it can do on your machine

Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Finman Writing Style loads about 2k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 1,044 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~91
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 1,044 words, ~2,000 tokens.

Download SKILL.mdSave it as .claude/skills/finman-writing-style/SKILL.md (or your agent's skills folder).
name
finman-writing-style
description
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).

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 a denser, more specialist register.

The exposition build (in order)

  1. Abstract: finding-first. Lead with the result and its implication in the first two sentences; method and data come after. A reader should know the "so-what" without reading the paper. (Exact abstract word limit 待核实 — check the Wiley author guidelines.)
  2. First page: the hook and the payoff. State the live financial question, the answer, and who should change a decision because of it — within the first page, before the literature.
  3. Contribution paragraph. One paragraph naming the specific delta (from finman-literature-positioning) and the general-interest implication; resist the temptation to bury it on page 4.
  4. Mechanism and magnitude in plain finance language. Explain the channel and the economic magnitude in terms a CFO, investor, or regulator would use, not only in regression-speak.
  5. Practical-relevance close. End sections (and the paper) by connecting the estimate to a decision; FM rewards a paper that tells the reader what to do with the finding.
  6. Cut for readability. Remove throat-clearing, redundant caveats, and apparatus that does not change a conclusion — every sentence should earn its place.

The first-page test (FM's hardest sentence-level bar)

FM editors and referees decide interest fast. Treat the first page as the audition and engineer four sentences deliberately:

  1. The hook sentence — the live financial tension or puzzle a general reader recognizes ("Boards routinely set covenants without knowing how creditors will use control rights").
  2. The finding sentence — the answer, with the direction and a magnitude in plain terms ("We show creditors cut investment by ~7% after a breach").
  3. The why-it-matters sentence — the decision that changes ("Boards can price this into covenant design ex ante").
  4. The how-we-know sentence — the design in one line ("using a staggered covenant-rule change as quasi-exogenous variation"). A first page that delivers these four before the literature review passes FM's interest screen; one that opens with data counts and estimators fails it.

Checklist

  • Abstract leads with the finding and its implication, not the method
  • The first-page four sentences (hook / finding / why-it-matters / how-we-know) are present
  • The question, answer, and decision-maker appear on the first page, before the literature
  • The contribution and its general-interest payoff are stated in one clear paragraph
  • The mechanism and economic magnitude are explained in plain finance terms
  • At least one explicit "so-what for managers / investors / regulators" statement
  • Jargon minimized; a non-specialist finance reader can follow the argument
  • Prose trimmed of throat-clearing and apparatus that changes no conclusion
Show full SKILL.md (453 more words)Show less

Writing the implications so they survive a skeptical read

The "so-what" is where FM papers most often slide into either vagueness or overreach. Calibrate:

  • Be specific, not gestural. "Has implications for policy" persuades no one; "regulators weighing covenant disclosure rules should expect investment to fall ~7% post-breach" does.
  • Stay inside the evidence. Tie each implication to a result you actually identified; a managerial recommendation that outruns the design invites a "you didn't show this" report.
  • Address the decision-maker by name. CFO, board, lender, investor, regulator — naming who acts makes the relevance concrete and FM-typical.
  • Distinguish positive from normative. Separate "this is what happens" from "this is what they should do," and flag the assumptions the normative step requires. A skeptical referee should finish the implications paragraph thinking "supported and useful," not "nice story, unproven."
  • Lead the title with the finding, not the method. An FM-typical title names the financial phenomenon and its twist, not the estimator; it is the first interest signal the editor sees.

Anti-patterns

  • A method-first abstract that withholds the finding until the last sentence
  • A first page dominated by literature review with the contribution deferred to page 4
  • Stating significance but never the managerial/market implication — fails FM's relevance brand
  • Subfield jargon that locks out the general finance audience FM is written for
  • Hedging every sentence into unreadability "to be careful"
  • Polishing prose before identification and the evidence hierarchy have settled

Worked vignette (illustrative)

A draft's abstract opens "Using a panel of 4,312 firm-years and a two-way fixed-effects specification, we estimate…" and the finding arrives in sentence five. A referee says it is "well-executed but a slog." The FM rewrite: open with "Firms cut investment by 7% when creditors gain control after a covenant breach — a response boards can anticipate and price into covenant design," then give the design in one sentence and the magnitude in plain terms. Move the contribution paragraph to page one, and close the introduction with the implication for how CFOs should negotiate covenants. The paper now reads — and a general finance audience reaches the "so-what" in the first two sentences.

Referee pushback mapped to the writing fix

  • "Well-executed but I lost interest by page three." → Rebuild the first page around the four-sentence test; move the contribution and so-what forward.
  • "I can't tell why this matters in practice." → Add an explicit managerial/market implication and translate the coefficient into a decision-relevant unit (basis points, dollars, % of the mean).
  • "This reads like a specialist paper." → Strip subfield jargon, define the mechanism in general finance terms, and frame the takeaway for the broad FM audience.
  • "The abstract buries the result." → Reorder so the finding and implication are the first two sentences; demote method and sample to the end.

Output format

【Abstract】finding-first, implication stated up front? [Y/N]
【First page】question + answer + decision-maker before the literature? [Y/N]
【Contribution paragraph】delta + general-interest payoff, one paragraph? [Y/N]
【Magnitude in plain terms】economic significance legible to a practitioner? [Y/N]
【So-what】explicit managerial/market implication present? [Y/N]
【Limits checked】abstract word limit verified or 待核实
【Next skill】finman-referee-strategy

© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in Financial-Management-Skills/skills/finman-writing-style of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Finman Writing Style next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Finman Writing Style compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Finman Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~2kAutomated safety check: PassMIT
Avoid AI Writingconorbronsdon/avoid-ai-writing4.9k3 repos~8.1kAutomated safety check: PassMIT
BrandOhh-889/skyroc79513 repos~733Automated safety check: PassMIT
Khazix WeChat Article WriterKKKKhazix/khazix-skills21k1 repos~2.9kAutomated safety check: PassMIT
Writing Guidelinesvercel-labs/agent-skills32k7 repos~309Automated safety check: PassNone
Unslop AI Writing Cleanuptheclaymethod/unslop518—~1.7kAutomated safety check: PassMIT

Similar skills

  • Avoid AI Writing

    conorbronsdon/avoid-ai-writing

    Audit and rewrite content to remove AI writing patterns ("AI-isms").

    4.9k GitHub starsUsed in 3 repos~8.1k tokens
    Writing & ContentAuto-check passed
  • Brand

    Ohh-889/skyroc

    Brand voice, visual identity, messaging frameworks, asset management, brand consistency.

    795 GitHub starsUsed in 13 repos~733 tokens
    Writing & ContentAuto-check passed
  • Khazix WeChat Article Writer

    KKKKhazix/khazix-skills

    Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.

    21k GitHub starsUsed in 1 repo~2.9k tokens
    Writing & ContentAuto-check passed
  • Writing Guidelines

    vercel-labs/agent-skills

    Official

    Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.

    32k GitHub starsUsed in 7 repos~309 tokens
    Writing & ContentAuto-check passed
  • Unslop AI Writing Cleanup

    theclaymethod/unslop

    Removes AI writing tells from prose through an audit-first flow, routing to a two-pass rewrite, a report-only cleanup, voice teaching or mimicry depending on the sub-command used.

    518 GitHub stars~1.7k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed
  • UX Writing

    content-designer/ux-writing-skill

    Applies UX writing practice to interface copy such as buttons, errors, forms and onboarding, using four quality standards and accessibility guidance.

    224 GitHub starsUsed in 1 repo~3.8k tokens
    Writing & ContentAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo
  • Aaag Data Analysis

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed
  • Aaag Literature Positioning

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed
  • Aaag Rebuttal

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…

    1.2k GitHub stars~1.4k tokensUpdated 14 days ago
    Auto-check passed
  • Aaag Research Design

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…

    1.2k GitHub stars~1.4k tokensUpdated 14 days ago
    Auto-check passed
  • Aaag Review Process

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed
  • Aaag Submission

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…

    1.2k GitHub stars~1.6k tokensUpdated 14 days ago
    Auto-check passed

Questions about Finman Writing Style

What does Finman Writing Style do?

A skill your agent uses 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…. Finman Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills." Shapes exposition for a general finance audience; it does not establish results (finman-identification) or run the submission preflight (finman-submission).

When should I use Finman Writing Style?

Finman Writing Style fits situations like: introduction of a Financial Management (FM) manuscript buries the idea; its managerial/market payoff — FMs brand is articles people actually read. Shapes exposition for a general finance audience; it does not establish results (finman-identification); run the submission preflight (finman-submission).

How do I install Finman Writing Style in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill finman-writing-style -a claude-code`. Or copy the skill folder (Financial-Management-Skills/skills/finman-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/finman-writing-style in your project. Claude Code loads it when a task matches its description.

How do I install Finman Writing Style in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill finman-writing-style -a codex`. Or copy the skill folder (Financial-Management-Skills/skills/finman-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/finman-writing-style in your project. Codex loads it when a task matches its description.

Can I use Finman Writing Style in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill finman-writing-style -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/finman-writing-style, .gemini/skills/finman-writing-style, .github/skills/finman-writing-style and .opencode/skills/finman-writing-style in your project.

What does Finman Writing Style need to run?

SKILL.md names no scripts, command-line tools or credentials: Finman Writing Style is instructions for the agent only.

Does Finman Writing Style access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Finman Writing Style safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Finman Writing Style use?

Finman Writing Style is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Finman Writing Style use?

About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Finman Writing Style?

Skills that share tags, products or a category with Finman Writing Style: Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), Brand (Ohh-889/skyroc, 795 stars), Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars) and Writing Guidelines (vercel-labs/agent-skills, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Finman Writing Style?

brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.

Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.