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

Rof Literature Positioning

ASecurity

Use when positioning a Review of Finance (RoF) manuscript against the finance frontier — citing the right top-three work, honoring RoF's strict author-responsibility citation norm, and staking the contribution without a standalone survey.

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 rof-literature-positioning --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Rof Literature Positioning?

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

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

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

Download with Pro
Files
SKILL.md
---
name: rof-literature-positioning
description: Use when positioning a Review of Finance (RoF) manuscript against the finance frontier — citing the right top-three work, honoring RoF's strict author-responsibility citation norm, and staking the contribution without a standalone survey.
---

# Literature Positioning (rof-literature-positioning)

## When to trigger

- The related-work section reads as a survey, not a staking of position
- You are unsure you have found the closest prior finance papers
- A referee could say "this is already in [paper X]"
- Citations skew to one's own subfield and miss the general-finance frame

## The RoF citation norm (strict)

RoF enforces a **strong author-responsibility citation norm**: authors **must search for and cite relevant work**, and **not being aware** of a paper that should reasonably have been found is **not a valid defense** — omissions **can be sanctioned**. Combined with the **top-three-finance-journal standard**, positioning must be (a) complete with respect to the closest work and (b) framed for a **general finance** audience. Because RoF spans **empirical and theoretical** finance, place the paper relative to both the evidence and the mechanism it speaks to.

## Positioning moves

1. **Map the frontier** — identify the 3–6 closest papers (often top-three finance) and state, for each, what they do and where they stop.
2. **Stake the delta** — one clause per close paper: "X shows A; we show B." No vague "we complement."
3. **Bridge empirical and theory** — if empirical, cite the theory you test or discipline; if theory, cite the empirical regularity you rationalize.
4. **Exhaustive search** — run keyword, citation-chain, and recent-working-paper searches; assume a referee owns the paper you missed.
5. **No standalone survey** — weave positioning into the introduction and a short related-work paragraph; the 60-page cap (incl. bibliography) penalizes bloat.

## Anti-patterns

- A two-page literature review that never says what *this* paper adds.
- Citing only your own subfield and missing the general-finance reference everyone knows.
- Omitting a close paper and hoping the referee misses it — RoF treats this as your fault and may sanction it.
- Padding the bibliography (it counts against the 60-page cap) instead of citing precisely.

## Output format

```
【Closest papers】[3-6], venue + where each stops
【Delta per paper】X→A, we→B
【Empirical↔theory bridge】mechanism/evidence link
【Search done】keywords / citation-chain / WP scan [Y/N]
【Omission risk】close paper not yet cited? [Y/N]
【Next step】rof-identification-strategy
```

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 →