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

Jf Writing Style

ASecurity

Use when polishing the prose of a The Journal of Finance (JF) manuscript for accessible, general-interest exposition. Tightens writing and framing; it does not change results or run analyses.

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 jf-writing-style --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jf Writing Style?

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

Security grade badge for Jf Writing Style
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jf-writing-style/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jf-writing-style)

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

Download with Pro
Files
SKILL.md
---
name: jf-writing-style
description: Use when polishing the prose of a The Journal of Finance (JF) manuscript for accessible, general-interest exposition. Tightens writing and framing; it does not change results or run analyses.
---

# Writing Style & Exposition (jf-writing-style)

## When to trigger

- The introduction does not deliver the question, finding, and magnitude in the first page
- Prose is dense, jargon-heavy, or written for a subfield rather than the broad AFA reader
- The main finding is buried; the reader has to work to extract the takeaway
- Sentences hedge so much the claim disappears

## JF house voice: accessible, precise, general-interest

JF is the **AFA flagship**, read across asset pricing, corporate finance, banking, microstructure, and household finance by 8,000+ readers. Writing must be **accessible to a finance reader outside your subfield** while staying precise. The manuscript also faces a **60-page limit** (≥1.5 spacing, 12-pt font), so lead with economics and **offload technical depth to the Internet Appendix** (bundled at the end of the same PDF; see `jf-internet-appendix`) rather than padding the body.

## The JF introduction (first ~3 pages do the work)

In order: (1) **the question and why it matters** — general-interest, concrete; (2) **what you do** — design/data/test in plain terms; (3) **what you find** — headline result with its **economic magnitude** in interpretable units; (4) **why it is credible** — the source of variation or the test; (5) **contribution** — the closest papers and your delta (see `jf-literature-positioning`); (6) brief roadmap. A reader who stops at page 3 should know the question, the answer, its size, and why to believe it.

## Sentence-level discipline

- Active voice and short declaratives for main claims.
- State magnitudes in interpretable units (bps, % of market cap, Sharpe gain), not only t-stats.
- Define notation once; do not re-derive in prose what a table shows.
- Cut hedging stacks to one calibrated claim.
- Use "significant" for economic importance, not as a synonym for the p-value.

## Checklist

- [ ] Question, finding, and economic magnitude in the first ~3 pages
- [ ] Headline number in interpretable economic units
- [ ] A non-specialist finance reader could follow the introduction
- [ ] Heavy notation/derivation moved to the Internet Appendix, keeping the body ≤60 pages
- [ ] Active voice; calibrated (not reflexive) hedging
- [ ] Abstract matches the introduction's claims

## Anti-patterns

- Opening with three paragraphs of literature before the question
- Reporting "significant at the 1% level" as if it were the finding
- Subfield jargon with no plain-language gloss for the broad AFA reader
- Padding the body toward the 60-page cap instead of using the Internet Appendix
- Over-hedged claims that blur the contribution

## Output format

```
【Question+finding+magnitude in first 3 pp?】yes / no
【Magnitude in economic units?】yes / no
【Accessible to non-specialist?】yes / no
【Notation moved to Internet Appendix?】yes / no
【Body ≤60 pp / hedging trimmed?】yes / no
【Next step】jf-submission
```

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 →