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

Anmath Figures

ASecurity

Use when organizing the exposition and structure of a pure-mathematics manuscript for Annals of Mathematics — sectioning, notation, statements-before-proofs, commutative diagrams, and readability for an expert non-specialist. Figures are optional and rare; this skill is about exposition first. Does not assess the proof's correctness.

1,052 stars
0 votes
0 copies
0 views
Added 6/4/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill anmath-figures --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Anmath Figures?

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

Security grade badge for Anmath Figures
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-anmath-figures/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-anmath-figures)

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

Download with Pro
Files
SKILL.md
---
name: anmath-figures
description: Use when organizing the exposition and structure of a pure-mathematics manuscript for Annals of Mathematics — sectioning, notation, statements-before-proofs, commutative diagrams, and readability for an expert non-specialist. Figures are optional and rare; this skill is about exposition first. Does not assess the proof's correctness.
---

# Exposition and Structure (anmath-figures)

## When to trigger

- The paper is hard to follow even though the proof is correct
- Notation is inconsistent or introduced after first use
- Theorems and their proofs are interleaved confusingly
- A relation between objects would be far clearer as a commutative diagram
- You are deciding whether the rare case of an actual figure is warranted

> In pure mathematics, papers are theorem-and-proof and usually have **no experiments and
> few or no figures**. "Figures" here means *exposition and structure*: a figure or diagram
> is included only when it conveys structure more efficiently than prose.

## Exposition principles (Annals readability)

1. **Statements before proofs.** State each definition, lemma, proposition, and theorem in
   full before proving it. The reader should always know the target before the argument.
2. **Notation introduced once, used consistently.** Define every symbol at first use; keep
   a fixed convention throughout; avoid overloading the same symbol for two things.
3. **Logical sectioning.** Preliminaries → key constructions → main lemmas → proof of the
   Main Theorem → consequences. Each section has a clear job and a one-line opener.
4. **Self-contained where reasonable.** Recall the precise external statements you use so a
   reader need not reconstruct them from memory.
5. **Readable by an expert non-specialist.** Someone strong in an adjacent area should be
   able to follow the architecture; gloss the field-specific shorthand the first time.

## Sectioning template

| Section | Contents |
|---------|----------|
| Introduction | Problem, Main Theorem, what is new, method sketch, organization |
| Preliminaries / Notation | Conventions, recalled definitions, cited external results |
| Constructions / setup | The objects the proof manipulates |
| Key lemmas | The intermediate results, stated then proved |
| Proof of Main Theorem | Assembling the lemmas into the headline result |
| Consequences | Corollaries and remarks |
| Appendices | Auxiliary/technical material (see anmath-supplementary) |

## Diagrams and figures (when justified)

- **Commutative diagrams**: use `tikz-cd` (or `amscd`) when a chain of maps or an exact
  sequence is clearer drawn than written. Keep arrows labeled and consistent.
- **A genuine figure** (a configuration, a region, a graph): include only when it removes
  real ambiguity. Use vector output (PDF/EPS), label everything, and reference it in text.
- **Tables**: occasionally useful for case enumerations or notation summaries; keep clean.
- Most Annals papers have zero figures — do not add one for decoration.

## Checklist

- [ ] Every definition/lemma/proposition/theorem is stated before it is proved
- [ ] Every symbol is defined at first use and used consistently
- [ ] Sections are logically ordered with clear one-line openers
- [ ] External results used are recalled precisely (statement + citation)
- [ ] Commutative diagrams (if any) are typeset with labeled, consistent arrows
- [ ] Any figure is vector, labeled, referenced, and genuinely necessary
- [ ] An expert in an adjacent area could follow the overall architecture

## Anti-patterns

- Using a symbol before defining it, or redefining a symbol mid-paper
- Interleaving proof fragments with statements so the target is unclear
- A wall of unsegmented text with no sectioning logic
- Adding a decorative figure that conveys nothing the prose does not
- Field jargon used without a single gloss for the adjacent-area reader
- Sloppy diagram arrows (unlabeled, inconsistent direction) that obscure the maps

## Output format

```
【Section plan】1 Intro · 2 Prelim · 3 ... · n Appendix
【Notation issues fixed】...
【Statements-before-proofs】compliant / fix: ...
【Diagrams】none / commutative diagram in §... via tikz-cd
【Figure justification】none needed / figure in §... because ...
【Next step】anmath-supplementary (appendix triage) or anmath-writing-style
```

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".

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