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

Rje Literature Positioning

ASecurity

Use to position a manuscript against the industrial-organization frontier for The RAND Journal of Economics (RJE) — staking the contribution against prior IO work without a standalone survey, and citing in the RJE author-date style (no page numbers, no issue numbers). Positioning, not a literature review.

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

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Rje Literature Positioning?

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

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

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

Download with Pro
Files
SKILL.md
---
name: rje-literature-positioning
description: Use to position a manuscript against the industrial-organization frontier for The RAND Journal of Economics (RJE) — staking the contribution against prior IO work without a standalone survey, and citing in the RJE author-date style (no page numbers, no issue numbers). Positioning, not a literature review.
---

# Literature Positioning (rje-literature-positioning)

## When to trigger

- The related-work section reads like a survey instead of a positioning argument
- You are unsure which IO literatures your article must engage
- You need citations to conform to the RJE Style Guide

## Positioning at the IO flagship

RJE is the **flagship industrial-organization journal** (formerly the Bell Journal of Economics), so referees are IO insiders who know the canon and the current frontier. Positioning must show **exactly what your article adds to the IO conversation** — a new structural method, new estimates for a market, a new mechanism, or a theoretical result — not summarize the field. Engage the **specific strand** your contribution touches:

- **Demand & differentiation:** discrete-choice / random-coefficients (BLP-style) demand and its descendants.
- **Supply, conduct & market power:** oligopoly pricing, conduct testing, pass-through, markups.
- **Entry, exit & dynamics:** static and dynamic entry/investment games.
- **Regulation & antitrust:** merger analysis, regulated-industry studies, market design.
- **Organizations & contracts:** vertical relationships, incentives, firm boundaries.
- **Auctions & mechanisms** where competition is the object.

For each relevant strand, name the **closest prior articles**, state what they established, and pinpoint the **gap your work closes**. Distinguish a **method** contribution (you estimate something previously hard to identify) from a **substantive** one (you answer a market/policy question prior tools could not).

## Citation form (RJE Style Guide)

- Author-date in-text, **name and year only, no page numbers** (e.g., "Berry, Levinsohn and Pakes, 1995").
- Reference list alphabetical, unnumbered, **no issue numbers** in journal citations.
- Avoid numbered or footnote-style citations.

## Anti-patterns

- A chronological survey with no claim about your marginal contribution
- Citing general-econ landmarks while ignoring the specific IO strand you extend
- Page numbers in in-text cites or issue numbers in references (off RJE style)
- Claiming novelty against a literature you have not actually engaged

## Output format

```
【Strands engaged】[demand / conduct / entry-dynamics / regulation / organizations / auctions]
【Closest prior work】[3-6 articles, author-date]
【Gap closed】one sentence
【Contribution type】method / substantive / theoretical
【Citation style】author-date, no page/issue numbers? [Y/N]
【Next step】rje-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', ...

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 →