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

Jbes Literature Positioning

ASecurity

Use when positioning a Journal of Business & Economic Statistics (JBES) methods paper against prior econometric and statistical methods. Stakes what is new relative to the existing toolkit; it does not write a standalone literature survey.

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

Installs into .claude/skills of the current project.

Are you the author of Jbes Literature Positioning?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jbes-literature-positioning
description: Use when positioning a Journal of Business & Economic Statistics (JBES) methods paper against prior econometric and statistical methods. Stakes what is new relative to the existing toolkit; it does not write a standalone literature survey.
---

# Literature Positioning (jbes-literature-positioning)

## When to trigger

- A referee will ask "how is this different from method X already in the literature?"
- The contribution relative to the closest existing estimator/test/algorithm is fuzzy
- You are unsure whether your improvement is incremental or genuinely new
- You need to map your method onto the right strand (time series, panel, GMM, ML, Bayesian, etc.)

## Why positioning is the methods-paper crux at JBES

JBES referees are method experts: they judge a paper first by **what it adds to the existing toolkit**. Because the journal explicitly welcomes **adaptation of methods from machine learning and data science** alongside classical econometrics, your closest competitors may live in **two literatures at once** — the statistics/ML method you adapt *and* the econometric problem you apply it to. Position against **both**. The contribution must be stated as a delta against named prior methods, not as a freestanding survey: which assumptions you relax, which rates you improve, which computational barrier you remove, or which empirical setting prior methods cannot handle.

## Positioning protocol

1. **Name the incumbents.** List the 3–6 methods a referee would consider state of the art for your problem (estimator, test, or algorithm — with citations).
2. **State your delta per incumbent.** For each: weaker assumptions? better asymptotics/rates? valid under dependence/heavy tails/high dimension where they are not? faster/feasible at scale? Honest deltas only.
3. **Locate the strand.** Place the paper in its method family (e.g., HAC inference, GMM, factor models, quantile methods, debiased ML, Bayesian computation) so referees from that strand recognize the lineage.
4. **Bridge to the application.** Tie the methodological delta to the empirical payoff: the new method changes a substantive conclusion or makes a previously infeasible analysis feasible.
5. **Concede gracefully.** Where an incumbent dominates (simpler, or better in a regime you do not target), say so; over-claiming invites a hostile report.

## Checklist

- [ ] 3–6 closest prior methods named and cited
- [ ] A concrete delta stated against each (assumptions / rates / robustness / computation)
- [ ] Both the statistics/ML side and the econometrics side covered if you adapt across fields
- [ ] The method family / strand is explicit
- [ ] The positioning connects to the empirical payoff, not just abstract properties
- [ ] Limitations vs. incumbents conceded honestly

## Anti-patterns

- A chronological survey ("Smith (1990) did..., Jones (1995) did...") with no delta
- Comparing only to a strawman or to outdated methods, ignoring the current frontier
- Claiming novelty against econometrics while missing the identical idea in the statistics/ML literature (or vice versa)
- Vague superiority ("our method performs better") with no stated dimension of improvement
- Hiding the regime where an existing method still wins

## Output format

```
【Incumbents】[3–6 prior methods + citations]
【Delta per incumbent】method → what you improve (assumptions/rates/robustness/computation)
【Strand】method family this paper joins
【Cross-field check】statistics/ML side AND econometrics side covered? [Y/N]
【Empirical payoff】how the delta changes a substantive result
【Conceded】where incumbents still win: ...
【Next step】jbes-contribution-framing
```

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 →