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

Ecta Literature Positioning

ASecurity

Use when locating an Econometrica result precisely within the methods / theory lineage it extends, and when writing the related-work paragraphs that pre-empt "how does this differ from X?" Builds the positioning — it does not judge overall fit (use ecta-topic-selection) or state the theorem (use ecta-theory-model).

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Ecta Literature Positioning?

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

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

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

Download with Pro
Files
SKILL.md
---
name: ecta-literature-positioning
description: Use when locating an Econometrica result precisely within the methods / theory lineage it extends, and when writing the related-work paragraphs that pre-empt "how does this differ from X?" Builds the positioning — it does not judge overall fit (use ecta-topic-selection) or state the theorem (use ecta-theory-model).
---

# Literature Positioning (ecta-literature-positioning)

## When to trigger

- The related-work section lists papers but never says how *this* result differs formally
- You suspect a referee will name a classic theorem/estimator your result must beat or nest
- Reviewers might think the contribution is already implied by a known result
- The lineage of assumptions (who introduced each, who relaxed it) is unclear

## The positioning bar at Econometrica

Econometrica referees are typically the people who wrote the results you are extending —
and the handling **co-editor** (one of a small board; e.g., Keisuke Hirano, Aureo de Paula,
Marciano Siniscalchi, Pete Klenow, Patrick Kline, under Editor Marina Halac, 2025–2029 —
verify the current board) routes the paper to exactly those experts. Positioning is not a
literature dump — it is a **precise statement of the formal relationship** between your
result and the closest prior results. For each key neighbor, say exactly one of: *we nest
it*, *we generalize it*, *we weaken its assumption*, *we provide what it lacked* (e.g., the
limiting distribution, uniqueness, a constructive proof).

Because the lineage here is *methods/theory* rather than *empirical findings*, the neighbors
to position against are usually theorems and estimators with names attached — the GMM
framework (Hansen 1982), HAC inference (Newey–West 1987), nested fixed-point estimation
(Rust 1987), the relevant fixed-point or representation theorem — not "the literature on
this policy." Mis-stating who proved what is a credibility hit with this pool.

## Map the lineage

Build a small map before writing prose:

1. **Foundational result** — the classic theorem/estimator the literature builds on
   (e.g., the GMM framework, the relevant fixed-point / representation theorem, the
   baseline limit theorem). Cite it precisely.
2. **Direct antecedents** — the 3–6 papers your result most directly competes with or
   extends. For each, record: their setting, their key assumption, their conclusion.
3. **Your delta** — for each antecedent, the single formal sentence describing the
   difference (weaker assumption / broader class / sharper rate / added uniqueness /
   added asymptotics / constructive vs. existential).

## Positioning paragraph template

```
The closest result is [Author, Year], who [conclusion] under [assumption A]. We obtain
[our conclusion] under [weaker assumption A′], which [permits case / yields object] not
covered there. [Author2, Year] consider [related setting] but [lack object / impose
restriction]; our [theorem N] supplies [that object]. Unlike [strand], we do not require
[restrictive condition], at the cost of [honest cost].
```

State costs honestly: a referee who finds an unacknowledged cost reads the rest of the
paper suspiciously.

## What to get right

- **Attribution of assumptions.** Name who introduced each assumption you use and who
  first relaxed it. Mis-attribution is a credibility hit with this referee pool.
- **Nesting claims.** If you claim your result nests a known one, show the special case
  explicitly (often a one-line corollary or remark). Unsupported "nests" claims invite a
  counterexample.
- **Independent / contemporaneous work.** Acknowledge concurrent results fairly; do not
  overclaim priority.
- **The right objects.** For theory, cite the precise theorem (with number) you rely on,
  not just the paper.

## Checklist

- [ ] Foundational result cited precisely (theorem-level, not just paper-level)
- [ ] 3–6 direct antecedents, each with a one-sentence formal delta
- [ ] Every "we generalize / nest" claim backed by an explicit special case
- [ ] Assumptions attributed to their originators correctly
- [ ] Honest statement of what your result costs relative to the closest prior result
- [ ] Contemporaneous / independent work acknowledged
- [ ] No padding: every cited paper bears on the contribution's boundary

## Anti-patterns

- A related-work paragraph that lists ten papers but never states a formal difference
- Claiming to "generalize" a result while quietly imposing a *stronger* assumption elsewhere
- Ignoring the obvious classic theorem a referee will immediately compare you to
- Citing a survey instead of the original theorem your proof depends on
- Overclaiming priority over contemporaneous working papers

## Output format

```
【Foundational result】...
【Direct antecedents】[A (assumption→conclusion), B, ...]
【Deltas】[vs A: weaken X; vs B: add limiting distribution; ...]
【Nesting shown?】yes (corollary N) / no — needs explicit special case
【Honest cost】...
【Next step】ecta-identification
```

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.

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