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

Rfs Literature Positioning

ASecurity

Use when the related-work framing is the bottleneck for a The Review of Financial Studies (RFS) manuscript — defining the precise delta against JF/JFE/RFS and prior literature. Builds positioning, not the empirical design or the topic itself.

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

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill rfs-literature-positioning --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Rfs Literature Positioning?

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

Security grade badge for Rfs Literature Positioning
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-rfs-literature-positioning/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-rfs-literature-positioning)

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

Download with Pro
Files
SKILL.md
---
name: rfs-literature-positioning
description: Use when the related-work framing is the bottleneck for a The Review of Financial Studies (RFS) manuscript — defining the precise delta against JF/JFE/RFS and prior literature. Builds positioning, not the empirical design or the topic itself.
---

# Literature Positioning (rfs-literature-positioning)

## When to trigger

- The related-work section is a list ("X did A, Y did B") with no synthesis
- You cannot state your contribution as a single crisp delta
- A reader asks "how is this different from [recent RFS/JF/JFE paper]?"
- The novelty claim from `rfs-topic-selection` needs to be defended against the literature

## How RFS reviewers read positioning

RFS referees and editors are typically the authors of the papers you cite. The handling editor pool is concrete — Executive Editor Tarun Ramadorai plus editors such as Viral Acharya, Xavier Giroud, Andrey Malenko, Anna Pavlova, Clemens Sialm, David Sraer, and Jessica Wachter — so the person screening an intermediation, household-finance, or asset-pricing paper may well be a primary author in that literature. Positioning is judged on whether you (1) know the *current* frontier, (2) cite the right primary sources rather than secondary surveys, and (3) state a delta that is real and defensible — not rhetorical. When you build on an RFS-defining result (e.g., Brunnermeier–Pedersen 2009 on the liquidity-funding spiral, RFS 22(6)), cite the RFS original, not a later survey that paraphrases it.

The contribution must clear two bars simultaneously:
- **Against the literature** — what do we now know that we did not before?
- **Against the closest 2–3 papers** — what specifically do you do that they could not?

## Positioning structure

Organize related work by **the question**, not chronologically:

1. **The anchor literatures** — name the 2–4 strands you sit at the intersection of (e.g., intermediary asset pricing × household finance). Cite the canonical theory and the most-cited recent empirics.
2. **The frontier** — the 3–5 most recent, most relevant papers (last ~3 years). Show you know what is in the pipeline.
3. **The wedge** — one paragraph that names the closest paper(s) and states the precise gap: data they lacked, identification they could not achieve, mechanism they could not test, or theory they did not have.
4. **Your delta** — one or two sentences, falsifiable: "We are the first to [X], which lets us [Y]."

## Delta types that work at RFS

| Delta type            | Example phrasing                                                       |
|-----------------------|-------------------------------------------------------------------------|
| New question          | "Prior work studies pricing; we study the *allocation* consequences."   |
| Cleaner identification| "Earlier estimates were confounded by selection; our shock breaks it."  |
| New mechanism evidence| "The correlation was known; we provide the first direct test of *why*." |
| Theory + evidence     | "We embed the fact in a model that yields a new, tested prediction."    |
| New data              | "We observe [previously unobservable margin], revising prior estimates."|

## Citing across the top-3 and field journals
- Cite the primary RFS/JF/JFE source for each claim, not a later survey that summarizes it.
- When a result first appeared in a field journal but the framing is now at the top-3, cite both.
- For theory anchors, cite the foundational paper even if decades old — referees expect it.
- Distinguish "first to document" from "first to explain" — over-claiming either is easily disproven.

## Checklist

- [ ] Related work is organized by question/theme, not by author or date
- [ ] The 2–3 closest papers are named explicitly and the delta vs. each is stated
- [ ] Recent (last ~3 years) RFS/JF/JFE work is cited — not just classics
- [ ] Canonical theory references for each anchor literature are present
- [ ] The delta is falsifiable, not "we add to the literature on X"
- [ ] You have not overstated novelty in a way a referee can disprove with one cite
- [ ] Cross-checked your closest cites against the likely RFS handling-editor's own work (they may referee it)

## Anti-patterns

- A laundry-list literature review with no synthesis or wedge.
- Citing surveys/handbooks instead of the primary papers a referee wrote.
- Missing an obvious close competitor — reads as either ignorance or evasion.
- A delta phrased as "to the best of our knowledge, we are the first" with no defense.
- Positioning against field journals when the real competitors are at RFS/JF/JFE.

## Output format

```
【Anchor literatures】[strand 1] × [strand 2] (+ canonical theory cites)
【Frontier papers】[3–5 recent JF/JFE/RFS papers]
【Closest competitors】[paper] → our delta vs. each
【One-sentence delta】"We are the first to ... which lets us ..."
【Open risk】a competitor a referee might raise
【Next step】rfs-identification
```

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 →