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

Jfi Writing Style

ASecurity

Use to revise a Journal of Financial Intermediation manuscript for the journal's house conventions — numbered sections, author–date Elsevier referencing, a concise stand-alone abstract, and prose that explains the intermediation mechanism before the specifications. It edits for style; it does not invent content.

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agents

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill jfi-writing-style --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jfi Writing Style?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jfi-writing-style
description: Use to revise a Journal of Financial Intermediation manuscript for the journal's house conventions — numbered sections, author–date Elsevier referencing, a concise stand-alone abstract, and prose that explains the intermediation mechanism before the specifications. It edits for style; it does not invent content.
---

# Writing Style (jfi-writing-style)

## When to trigger

- Polishing a JFI draft before submission or revision
- Aligning references, sections, and abstract with JFI/Elsevier conventions

## JFI house conventions (verified 2026-06-01; re-confirm on the official page)

- **Numbered sections** (1, 1.1, 1.1.1) structure the manuscript.
- **References:** "your-paper-your-way" at submission — any **internally consistent** style is accepted;
  the journal applies an **author–date (name–year) Elsevier** style at proof. In-text citations give
  surname(s) and year, with "et al." for three or more authors; the list is alphabetical then
  chronological, with a/b/c disambiguation for same-author/same-year items. Keep author–year fields clean.
- **Abstract:** concise, factual, and able to stand alone, with references avoided; there is **no stated
  numeric word cap** (待核实).
- **Optional Highlights:** 3–5 bullets, max 85 characters each, strongly encouraged.
- **Generative-AI disclosure:** if AI writing tools were used, declare them in a dedicated section
  **before the References** (see jfi-submission).

## Make the mechanism land

JFI is read by intermediation specialists who reward a clearly motivated **economic mechanism**:

- Explain the intermediary friction and channel **before** the econometric specification or the formal
  model — the reader should know *why* before *how*.
- Tie every result back to the intermediation contribution (see jfi-contribution-framing); avoid
  coefficient-by-coefficient narration with no economic interpretation.
- Define institutional terms on first use; precision about banks, loans, and regulation signals fluency.

## Anti-patterns

- A numbered/footnote citation style left in at submission with no internal consistency
- An abstract stuffed with references or with no stated finding
- Specifications introduced before the mechanism is explained
- Forgetting the AI-disclosure section when such tools were used

## Output format

```
【Sections】numbered (1, 1.1)? [Y/N]
【References】internally consistent, author–year-ready? [Y/N]
【Abstract】concise, stand-alone, no refs? [Y/N]  (word cap 待核实)
【Mechanism-first】explained before specs? [Y/N]
【AI disclosure】present-if-used? [Y/N]
【Next skill】jfi-replication-and-data-policy
```

Attribution

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

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