CtrlK
BlogDocsLog inGet started
Tessl Logo

quant-analyst

Build financial models, backtest trading strategies, and analyze market data. Implements risk metrics, portfolio optimization, and statistical arbitrage.

48

Quality

51%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/quant-analyst/SKILL.md

The canonical home for this skill is quant-analyst in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

36%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 content is well-sectioned and concise but lacks executable guidance and a real validated workflow, and it points to a non-existent reference file.

Suggestions

Replace the generic Instructions with concrete, copy-paste-ready examples (e.g. a vectorized backtest snippet or a VaR computation) using pandas/numpy/scipy.

Turn the Approach principles into a sequenced workflow with explicit validation checkpoints (e.g. validate data, run backtest, check out-of-sample, report metrics).

Either create `resources/implementation-playbook.md` (and place it under a real bundle directory) or remove the dangling reference so navigation is sound.

DimensionReasoningScore

Conciseness

The body is mostly lean with concise lists, but the generic Instructions boilerplate ("Apply relevant best practices and validate outcomes", "Provide actionable steps and verification") adds little quant-specific value and could be tightened.

3 / 5

Actionability

Guidance is high-level ("Clarify goals, constraints, and required inputs", "Use pandas, numpy, and scipy") with no executable code, commands, or concrete step detail, leaving only minimal concrete direction.

2 / 5

Workflow Clarity

The numbered Approach lists principles ("Data quality first", "Out-of-sample testing") rather than a sequenced executable workflow, and validation is only implied with no explicit checkpoints.

2 / 5

Progressive Disclosure

Sections are reasonably organized, but the body references `resources/implementation-playbook.md` which does not exist in any bundle directory, making the reference broken rather than clearly navigable.

3 / 5

Total

10

/

20

Passed

Description

66%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.

The description is specific and clearly niched, naming multiple quant capabilities in third person, but it omits any explicit trigger guidance for when to use the skill, capping its completeness.

Suggestions

Append an explicit trigger clause, e.g. "Use when building or backtesting trading strategies, computing risk metrics, or optimizing portfolios."

Add a few natural synonyms and tooling cues (e.g. "VaR", "Sharpe ratio", "pairs trading", ".csv/.parquet market data") to broaden trigger coverage.

Tighten domain-naming entries ("statistical arbitrage") into concrete actions to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ("Build financial models, backtest trading strategies, and analyze market data") plus capabilities ("risk metrics, portfolio optimization, and statistical arbitrage"), but several entries name domains rather than discrete executable actions, leaving minor coverage gaps relative to the comprehensive anchor.

4 / 5

Completeness

The description gives a clear "what" but no explicit "when" trigger guidance (no "Use when..." clause), which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Natural quant terms like "financial models", "backtest trading strategies", "market data", "risk metrics", and "portfolio optimization" match what users would say, but common synonyms and tooling/extension cues are missing, so it is good rather than comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The quant/algo-trading niche is mostly distinct with specific triggers, with only minor overlap risk against general data-analysis or finance skills.

4 / 5

Total

15

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.