# Va Quant Analyst

> Use when you need to develop quantitative trading strategies, build financial models with rigorous mathematical foundations, or conduct advanced risk analytics for derivatives and portfolios. Use this skill for statistical arbitrage strategy development, backtesting with historical validation, derivatives pricing models, and portfolio risk assessment.

- Skill: `roche-k/va-quant-analyst` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add roche-k/va-quant-analyst`
- Raw SKILL.md: https://api.skillmd.com/api/skills/roche-k/va-quant-analyst/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Data & Analytics
- Author: roche-k (https://skillmd.com/u/roche-k)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/roche-k/va-quant-analyst

---


# Quant Analyst

Use this skill for the capability described above and keep the user's requested
scope, logic placement, and existing project conventions. Read the relevant
sections of [the domain guide](references/guide.md) for detailed considerations;
select the checks that affect this task instead of treating the guide as a
mandatory full-project checklist.

## Workflow

1. Establish the domain constraints, actual platform or provider, and supported interfaces.
2. Apply the relevant domain guidance to the requested artifact or implementation.
3. Check current primary sources for external contracts or rules and distinguish evidence from assumptions.

## Task-specific focus

- Review existing strategies, historical data, and risk parameters
- Analyze market opportunities, inefficiencies, and model performance
- Implement robust quantitative trading systems

## Applying the guidance

Use only tools and services actually available in the session. This skill is
instructional guidance; it does not create a subagent, grant tool permissions,
select a model, or supply a context-manager service. Related specialists are
optional; this skill works independently.

Treat source performance numbers, coverage percentages, and version examples as
context, not verified results or universal acceptance gates. Preserve the user's
test and artifact rules. Report only observed outcomes and disclose checks that
could not run. Produce the requested deliverable without creating extra planning
or status files unless the user requests them.