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

Mathfin Identification Strategy

ASecurity

Use when the mathematical core of a Mathematical Finance (Wiley) manuscript is the bottleneck — adapted for a theory journal, this means assumptions, theorem statements, proof architecture, and generality, not causal/empirical identification. Stress-tests rigor before exposition is polished.

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 mathfin-identification-strategy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mathfin Identification Strategy?

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

Security grade badge for Mathfin Identification Strategy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-mathfin-identification-strategy/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-mathfin-identification-strategy)

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

Download with Pro
Files
SKILL.md
---
name: mathfin-identification-strategy
description: Use when the mathematical core of a Mathematical Finance (Wiley) manuscript is the bottleneck — adapted for a theory journal, this means assumptions, theorem statements, proof architecture, and generality, not causal/empirical identification. Stress-tests rigor before exposition is polished.
---

# Assumptions, Theorems & Proof Architecture (mathfin-identification-strategy)

## Note on framing

*Mathematical Finance* is a **theory-first** journal: papers are evaluated on **methodological
novelty and rigor**, not empirical causal identification. The "identification" that matters
here is **mathematical identification** — pinning down the right assumptions, the precise
theorem, and a complete proof. This skill therefore covers assumptions, results, proof
exposition, and generality. (Empirical causal design is out of scope for this venue.)

## When to trigger

- A "model" is proposed but its formal properties (existence, uniqueness, no-arbitrage) are unproved
- The assumptions are vague (which filtration? which integrability? which regularity?)
- A proof has a gap, an unstated measurability/integrability condition, or a circular step
- You are unsure your generality is the right level for the contribution

## The rigor bar (the journal requires self-contained full proofs)

1. **State assumptions precisely.** Probability space, filtration and its conditions (usual
   conditions?), integrability ($L^p$, square-integrability), regularity, market structure
   (complete/incomplete), admissibility of strategies. Number them (A1, A2, ...) and reuse them.
2. **State the theorem cleanly.** Hypotheses → conclusion, with the object's existence,
   uniqueness, and characterization separated. Avoid burying conditions in prose.
3. **Make the proof self-contained.** Full proofs of all formal results are required; cite
   external theorems with exact hypotheses and check they apply (e.g., that a martingale is
   genuinely a martingale, not just a local one).
4. **Get the generality right.** Too narrow → looks like a special case (see
   mathfin-literature-positioning); too broad → the proof breaks. Justify each assumption:
   is it essential, or a convenience that could be relaxed?
5. **Guard the standard pitfalls.** Local vs. true martingale, integrability of stochastic
   integrals, applicability of Itô / Girsanov / Feynman–Kac, well-posedness of SDEs/BSDEs,
   verification of HJB solutions, smooth-fit at free boundaries, NFLVR/FTAP conditions.

## Branch paths

- **Pricing / no-arbitrage:** establish the (equivalent) martingale measure; verify NFLVR /
  FTAP hypotheses; confirm the discounted price is a true martingale.
- **Stochastic control / portfolio:** state the HJB / verification theorem; check admissibility
  and the transversality/integrability conditions; prove the candidate is optimal, not just stationary.
- **BSDE / duality:** existence–uniqueness under stated drivers; comparison theorem if used;
  rigorous duality gap = 0 argument.
- **Optimal stopping / free boundary:** Snell envelope or variational inequality; smooth-pasting
  justified, not assumed.

## Anti-patterns

- "It is well known that..." standing in for a required step.
- Assuming an integrability/measurability condition only where convenient.
- Treating a local martingale as a martingale without a uniform-integrability argument.
- Stating maximal generality the proof cannot support.
- Relegating a load-bearing lemma to "the reader can verify."

## Output format

```
【Main theorem】hypotheses → conclusion (one line)
【Assumptions】[A1, A2, ...] with role of each
【Proof architecture】lemmas → main steps → where external theorems enter
【Generality check】each assumption: essential / relaxable
【Pitfalls cleared】[martingale, integrability, well-posedness, smooth-fit, ...]
【Gaps remaining】[...]
【Next step】mathfin-contribution-framing
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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', ...

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