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

Ectheory Writing Style

ASecurity

Use to polish the prose, notation, and proof exposition of an Econometric Theory (ET) manuscript — theorem-proof clarity, consistent notation, APA author-date references, and ET manuscript-prep specs (11pt, 1.5 spacing, 1.25in margins, 200-word abstract, 40-char running head).

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 ectheory-writing-style --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ectheory Writing Style?

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

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

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

Download with Pro
Files
SKILL.md
---
name: ectheory-writing-style
description: Use to polish the prose, notation, and proof exposition of an Econometric Theory (ET) manuscript — theorem-proof clarity, consistent notation, APA author-date references, and ET manuscript-prep specs (11pt, 1.5 spacing, 1.25in margins, 200-word abstract, 40-char running head).
---

# Writing & Proof Style (ectheory-writing-style)

## When to trigger

- The math is correct but the proof reads as a wall of symbols
- Notation drifts or collides across sections, assumptions, and theorems
- Formatting the manuscript to ET's preparation specs before submission
- Converting references to ET's APA author-date style

## ET house style: rigorous and readable

ET expects **rigorous theorem-proof writing that a fellow theorist can follow without
reverse-engineering every step**. Aim for:

- **Theorem-environment discipline.** Number and label Assumptions, Lemmas, Propositions, Theorems,
  Corollaries consistently; reference them by number, not "the result above."
- **Proof roadmaps.** Open each nontrivial proof with one or two sentences on the strategy, then
  execute; isolate reusable steps as lemmas; name the probabilistic tool at the point you invoke it.
- **Notation hygiene.** One symbol, one meaning; introduce notation before use; keep a consistent
  convention for estimators, true values, limits, and rates. A short notation table helps in long
  papers.
- **Calibrated prose.** State assumptions in words alongside the formalism; explain *why* a condition
  is needed, not only *that* it holds.

## ET manuscript-preparation specs (current 2026 page)

- **Font/spacing/margins:** minimum **11-point** font, at least **1.5 line spacing**, margins no
  less than **1.25 inches** on all sides; pages consecutively numbered.
- **Abstract:** **no more than 200 words.** (A legacy page showed 150 words / 10pt; treat the current
  200-word / 11pt figures as authoritative — verify on the live page.)
- **Title page (p.1):** title, author name(s), affiliations, emails, title/author footnotes as
  superscripts.
- **Page 2:** proposed **running head** (abbreviated title, **no more than 40 characters**),
  corresponding author for proofs, and the abstract.
- **References:** follow the **APA Style Guide** (author-date), in-text and in the reference list.

## Checklist

- [ ] Assumptions/lemmas/theorems numbered and cross-referenced by number
- [ ] Each nontrivial proof opens with a strategy roadmap
- [ ] Notation consistent; every symbol introduced before use
- [ ] Assumptions explained in words, not only stated formally
- [ ] Abstract <=200 words; running head <=40 characters
- [ ] 11pt, >=1.5 spacing, >=1.25in margins, pages numbered
- [ ] References in APA author-date; list complete and alphabetized

## Anti-patterns

- A proof with no roadmap that forces the reader to infer the strategy from the algebra
- Reusing a symbol for two different objects across sections
- Stating regularity conditions with no intuition for why they are imposed
- An abstract over 200 words or a running head over 40 characters
- Numeric or Chicago references instead of APA author-date

## Output format

```
【Proof exposition】roadmaps + isolated lemmas? [Y/N]
【Notation】one-symbol-one-meaning, introduced before use? [Y/N]
【Abstract】<=200 words? [Y/N]  【Running head】<=40 chars? [Y/N]
【Prep specs】11pt / 1.5 spacing / 1.25in margins? [Y/N]
【References】APA author-date, alphabetized? [Y/N]
【Next step】ectheory-replication-and-data-policy
```

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 →