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

Jet Writing Style

ASecurity

Apply the Journal of Economic Theory (JET) house style to a manuscript — the Elsevier elsarticle theorem-proof format with definition/assumption/proposition/theorem/proof structure, disciplined notation, full references in the abstract, and an Elsevier reference style. For drafting and polishing JET prose; it does not check proofs.

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

Installs into .claude/skills of the current project.

Are you the author of Jet Writing Style?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jet-writing-style
description: Apply the Journal of Economic Theory (JET) house style to a manuscript — the Elsevier elsarticle theorem-proof format with definition/assumption/proposition/theorem/proof structure, disciplined notation, full references in the abstract, and an Elsevier reference style. For drafting and polishing JET prose; it does not check proofs.
---

# Writing Style (jet-writing-style)

## When to trigger

- Drafting or polishing a JET theory manuscript
- Converting a working paper into JET's elsarticle theorem-proof format
- Tightening notation and statements before submission

## JET house style

- **Typeset in LaTeX, Elsevier `elsarticle` class.** Source must be editable `.tex`; PDF is not
  accepted as a source file. Use proper theorem environments (`amsthm`): Definition, Assumption,
  Proposition, Lemma, Theorem, Corollary, Proof.
- **Theorem-proof structure, not narrative-empirical.** Set up the environment and primitives, state
  assumptions, then results, then proofs (heavy ones to an appendix). The reader should be able to read
  every formal statement without hunting through prose.
- **Notation discipline.** Introduce each symbol once, never reuse a symbol for two objects, keep the
  body and proofs identical. A notation table helps in long papers.
- **References.** Elsevier style — `elsarticle-harv` (name-year) or `elsarticle-num` (numbered); the
  required one is **待核实**, confirm in the live guide. **References cited in the abstract must be given
  in full.** Keep **unpublished results / personal communications out of the reference list.**
- **JEL codes and keywords** are expected per standard Elsevier economics practice (verbatim-rule
  status is **待核实**).
- **Generative-AI disclosure** belongs in the submission, not the prose; reviewers/editors are barred
  from using such tools — write so a human expert can follow every step.

## Prose targets

- State each theorem so it is **self-contained** — readable without the surrounding paragraph.
- Give a **one-line intuition** before a long proof; do not let intuition substitute for rigor.
- Prefer "We prove that …" over hedged "essentially / roughly" phrasing the theorem does not support.

## Anti-patterns

- Submitting PDF source instead of `.tex`
- Mixed reference styles, or abstract citations abbreviated to "et al."
- Symbol reuse and notation drift between statement and proof
- An empirical-paper voice (data-story framing) imposed on a theory result

## Output format

```
【Format】elsarticle .tex, amsthm environments? [Y/N]
【Notation】one symbol ↔ one object, body=proof? [Y/N]
【References】Elsevier style; abstract refs in full; no personal comms? [Y/N]
【Disclosures】JEL+keywords; AI declared at submission? [Y/N]
【Next】jet-tables-figures / jet-submission
```

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 →