CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

quant-analyst

Build financial models, backtest trading strategies, and analyze market data. Implements risk metrics, portfolio optimization, and statistical arbitrage. Use for quantitative finance, trading algorithms, or risk analysis.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/quant-analyst/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, well-sectioned persona/cheat-sheet that correctly names the domain's tools and concepts, but it provides almost nothing executable — no code, commands, or concrete procedures — and its Approach sequence lacks explicit validation checkpoints. It reads more as a topic outline than actionable guidance for a quant workflow.

Suggestions

Add at least one concrete, executable artifact — e.g., a minimal vectorized backtest snippet with transaction costs, or a VaR/Sharpe computation example using pandas/numpy — to lift actionability beyond high-level hints.

Make the Approach sequence a real workflow with explicit validation checkpoints: e.g., 'clean data → verify no lookahead bias → in-sample fit → out-of-sample/walk-forward test → only then report metrics', including what to do when validation fails.

Remove the vacuous 'Do not use this skill when' bullets and the generic Instructions filler ('Clarify goals...', 'Apply relevant best practices...') to tighten conciseness and reduce duplication with the frontmatter description.

DimensionReasoningScore

Conciseness

The body is short and free of concept explanations, but contains genuine padding: 'The task is unrelated to quant analyst' is vacuous and 'Clarify goals, constraints, and required inputs. Apply relevant best practices' is generic filler. Anchor 3 (mostly efficient but could be tightened) rather than 4 (the boilerplate goes beyond minor trimmable instances).

3 / 5

Actionability

Concrete touches exist ('Use pandas, numpy, and scipy', named metrics like VaR, Sharpe ratio, Markowitz, Black-Litterman), but there is no code, no commands, and no executable procedure — only topic lists and principles. Anchor 2 (high-level hints missing the specific steps) rather than 1 (some real, specific guidance is present) or 3 (nothing here is executable).

2 / 5

Workflow Clarity

The five-step 'Approach' gives a coherent sequenced methodology (data quality, backtesting with costs, risk-adjusted returns, out-of-sample testing, research/production separation), but validation is only implicit — there are no explicit checkpoints or error-recovery loops. Anchor 3 (steps listed, validation gaps) rather than 2 (the sequence is well defined) or 4 (checkpoints are absent, not just minor).

3 / 5

Progressive Disclosure

No bundle files exist and the 42-line body is well organized into clear sections (Use when, Instructions, Focus Areas, Approach, Output), qualifying for the simple-skill exception. However, the 'Use/Do not use this skill when' sections duplicate the frontmatter description's job and add organizational noise. Anchor 4 (good structure, minor gaps) rather than 5.

4 / 5

Total

12

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with concrete capability statements and an explicit 'Use for' trigger clause containing three natural phrases. Its main weaknesses are the broad 'build financial models / analyze market data' phrasing and the slightly generic 'risk analysis' trigger, which keeps it just short of top marks on specificity and distinctiveness.

DimensionReasoningScore

Specificity

Lists several concrete actions ('backtest trading strategies', 'Implements risk metrics, portfolio optimization, and statistical arbitrage'), though 'Build financial models' and 'analyze market data' are broad and body-covered areas like time series forecasting and options pricing are absent. Fits anchor 4 (several specific actions, minor coverage gaps) rather than 5 (not comprehensive) or 3 (well beyond 1-2 actions).

4 / 5

Completeness

Explicitly answers both 'what' (six concrete capabilities) and 'when' via the trigger clause 'Use for quantitative finance, trading algorithms, or risk analysis', mirroring the anchor-5 example structure. Not 4 because the when-clause is already explicit and concrete rather than merely implied or needing more specificity.

5 / 5

Trigger Term Quality

'Use for quantitative finance, trading algorithms, or risk analysis' provides good natural-phrase coverage, but common variations users would say — 'quant', 'backtesting', 'portfolio' — are missing. Anchor 4 (good coverage, a few natural terms missing) rather than 3 (coverage is solid, not merely 'some') or 5 (no synonyms or variations included).

4 / 5

Distinctiveness Conflict Risk

Quantitative finance with statistical arbitrage and portfolio optimization is a clear niche, but 'risk analysis' is a generic trigger that could overlap with security or general risk-assessment skills. Anchor 4 (mostly distinct, minor overlap risk) rather than 5 (one trigger carries real conflict potential).

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

skills/quant-analyst/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.