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

Joe Writing Style

ASecurity

Use to make a Journal of Econometrics (JoE) manuscript read in house style — a precise abstract under 250 words, a contribution-first introduction, legible theorem-and-proof exposition, and Elsevier elsarticle/[dataset] reference conventions. Late-stage polish; it does not invent results.

1,052 stars
0 votes
0 copies
1 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 joe-writing-style --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Joe Writing Style?

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

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

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

Download with Pro
Files
SKILL.md
---
name: joe-writing-style
description: Use to make a Journal of Econometrics (JoE) manuscript read in house style — a precise abstract under 250 words, a contribution-first introduction, legible theorem-and-proof exposition, and Elsevier elsarticle/[dataset] reference conventions. Late-stage polish; it does not invent results.
---

# Writing Style (joe-writing-style)

## When to trigger

- The abstract exceeds 250 words or buries the methodological contribution
- The introduction lists what you did but never states the advance plainly
- Proofs are correct but unreadable — no roadmap, lemmas dumped without motivation
- References or math formatting do not follow Elsevier/elsarticle conventions

## JoE house style

The *Journal of Econometrics* publishes mathematically rigorous methodology, and its prose has to make rigor **legible**. Editors screen before assigning a **minimum of two referees**, so the abstract and introduction must land the contribution fast. Key house facts to write to:

- **Abstract ≤ 250 words**, concise and factual; any references cited in the abstract must be given **in full**. (待核实: confirm on the live Guide for Authors.)
- **elsarticle** LaTeX document class; **Elsevier** reference style (numbered or author-year, any CSL-compatible manager). Dataset citations tagged **`[dataset]`** with author/title/repository/version/year/persistent ID.
- Initial submission is a **single PDF** (~40 pages, ≥1.5 spacing, 11pt); write for that length norm rather than a hard word count.

## Abstract (≤ 250 words)

- Sentence 1: the econometric problem and why existing methods fail.
- Sentence 2: the proposed estimator/test/result and its key property (weaker assumptions, efficiency, valid inference).
- Sentence 3: the asymptotic guarantee and the Monte Carlo / empirical evidence.
- Keep it factual; no hype, no undefined notation. Spell out any cited reference in full.

## Introduction (contribution-first)

1. The problem and its stakes for econometric practice.
2. What is known and exactly where it falls short (the gap from `joe-literature-positioning`).
3. **The contribution, stated as a property**, in plain words before any notation.
4. A preview of the assumptions, the main theorem, and the finite-sample evidence.
5. A short roadmap. Write the introduction **last**, after theorems and Monte Carlo are settled.

## Theorem-and-proof exposition

- State assumptions once, label them, and refer back by label — do not silently re-use.
- Give each theorem a one-line **intuition** before the formal statement; say what drives the result.
- Provide a **proof roadmap** (consistency → rate → distribution); relegate routine algebra to an appendix but keep the logical skeleton in view.
- Define every symbol on first use; keep notation consistent across theory, Monte Carlo, and illustration.

## Anti-patterns

- A 300-word abstract, or one that states the model but not the contribution
- An introduction that is a related-work list with the advance hidden on page 6
- Proofs with no roadmap; lemmas appearing before the reader knows why
- Inconsistent or undefined notation; reference style that ignores Elsevier/elsarticle conventions

## Output format

```
【Abstract】≤250 words, states problem + property + evidence? [Y/N]
【Intro】contribution stated as a property before notation? [Y/N]
【Proof exposition】intuition + roadmap + labeled assumptions? [Y/N]
【Notation】defined on first use, consistent throughout? [Y/N]
【References】Elsevier style + [dataset] tags? [Y/N]
【Next step】joe-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.

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 →