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 Writing Style

ASecurity

Use as a late-stage polish for an Econometrica manuscript to enforce the terse, formal, theorem-numbered house style and clean mathematical exposition. Polishes prose and notation; it does not fix the proof (use ecta-theory-model) or the simulations (use ecta-robustness).

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Ecta Writing Style?

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

Security grade badge for Ecta Writing Style
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-ecta-writing-style/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-ecta-writing-style)

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

Download with Pro
Files
SKILL.md
---
name: ecta-writing-style
description: Use as a late-stage polish for an Econometrica manuscript to enforce the terse, formal, theorem-numbered house style and clean mathematical exposition. Polishes prose and notation; it does not fix the proof (use ecta-theory-model) or the simulations (use ecta-robustness).
---

# Writing Style (ecta-writing-style)

## When to trigger

- The introduction spends pages on motivation before stating any result
- Assumptions and definitions are buried in prose instead of numbered and set off
- Notation is inconsistent, overloaded, or introduced after first use
- The draft reads like an applied paper (long narrative) rather than a formal one

Trigger this **late**, after the theorems and simulations are stable. Do not polish prose
over an unstable proof.

## The Econometrica register

Econometrica prose is **terse, precise, and formal**. The reader is a specialist. Value is
signaled by the result and its proof, not by rhetorical motivation. The journal's house
style is theorem-numbered LaTeX (the de facto standard is `amsthm`/`amsmath`), and the
**45-page** main-text limit (incl. references and appendices; font ≥12pt, line spacing ≥1.5,
margins ≥1.25in) actively rewards economy — verbose motivation costs pages you need for the
proof architecture. This is a sharper formal register than the narrative style that suits
AER / QJE / JPE / REStud. Concretely:

1. **State the result early.** The introduction should reach the contribution — ideally an
   informal statement of the main theorem — quickly, then explain why it is hard and how the
   proof works. Avoid a long throat-clearing literature tour up front.
2. **Definitions and assumptions are displayed, numbered objects**, not asides in a sentence.
   A reader should be able to find Assumption 2 instantly.
3. **Every symbol is defined before use**, used consistently, and not reused for two things.
   Keep a private notation table to enforce this.
4. **Say what is proven and what is assumed.** Distinguish clearly between an assumption, a
   claim proven in the paper, and a claim cited from elsewhere.
5. **Economy.** Cut sentences that restate the math in words without adding interpretation.
   But *do* give the one sentence of economic / inferential interpretation each key result deserves.

## Mathematical exposition

- **Theorem environments** (Definition / Assumption / Lemma / Proposition / Theorem /
  Corollary) numbered consistently; cross-reference by number.
- **Proof sketches** in the body, full proofs in the **Supplemental Material** when long (the
  body's 45 pages are scarce) — but the body must convey the architecture and the hard step.
- **Display long equations**; number only those referenced later.
- **Interpretation paragraphs.** After a theorem, one short paragraph: what it means, what is
  surprising, what assumption is doing the work. This is where the economics lives.

## Structure of a methods/theory paper

A common, referee-friendly skeleton:
1. Introduction (problem, informal main result, relation to closest prior work, roadmap)
2. Model / setup and assumptions (numbered)
3. Main results (theorems, with proof sketches)
4. Monte Carlo / numerical illustration
5. (If applicable) empirical application
6. Conclusion (brief)
7. Appendix / Supplemental Material (full proofs, additional results, Monte Carlo detail)

## Checklist

- [ ] Contribution / informal main theorem stated within the first ~2 pages
- [ ] Definitions and assumptions are numbered, displayed objects
- [ ] Every symbol defined before use; no symbol overloaded
- [ ] Assumed vs. proven vs. cited is unambiguous throughout
- [ ] Each main result followed by one short interpretation paragraph
- [ ] Theorem numbering consistent; cross-references by number, not "above/below"
- [ ] Full proofs in the Supplemental Material; body conveys architecture + hard step
- [ ] Body fits the 45-page limit (incl. references and appendices); secondary material moved to Supplemental Material
- [ ] Prose trimmed of restating-the-math-in-words filler

## Anti-patterns

- Three pages of motivation before the first formal statement
- Assumptions stated inline in a paragraph so a referee cannot find them
- The same letter used for a parameter and an index in different sections
- "It is well known that ..." doing the work of a citation or a proof
- Verbose narrative that mimics an applied paper's storytelling
- A theorem with no interpretation paragraph — the reader is left to guess the point
- Cross-references like "the theorem above" that break when the paper is reorganized

## Output format

```
【Result stated early?】yes / no — currently first appears p...
【Assumptions numbered/displayed?】yes/no
【Notation conflicts】[...]
【Interpretation paragraphs present?】yes/no — missing after: [...]
【Register】formal-terse / too narrative — fixes: [...]
【Next step】ecta-replication-package
```

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 →