CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

strategy-generate

Create, modify, and optimize quantitative trading strategies, then backtest and evaluate them.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/strategy-generate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 exceptionally actionable and the workflow is clearly sequenced with strong validation and error-recovery loops, but it is a long monolithic file: the config/market reference material belongs in separate bundle files, the only bundle reference is a broken link, and the double-delay rule is repeated across three sections. Splitting reference material out and fixing the examples.md link would address the two weakest dimensions.

Suggestions

Move the field-by-field `config.json` documentation and market-specific minutiae (Argentina/BYMA, HK lot sizes, crypto funding) into reference files (e.g. references/config.md, references/markets.md) with clearly signaled links from SKILL.md.

Fix or remove the broken [examples.md](examples.md) link — the file does not exist in the bundle (and verify the ../cross-market-strategy reference).

Consolidate the double-delay explanation, currently repeated in Hard constraints, the Quality Checklist, "Verify execution timing", and Bug Categories #5, into one authoritative section with short pointers elsewhere.

DimensionReasoningScore

Conciseness

Most content is proprietary engine knowledge Claude cannot know (SignalEngine contract, warmup_bars semantics, rebalance modes, funding rules), so it is not padded with known concepts — but it is noticeably verbose: the double-delay rule is explained three times (Hard constraints, Quality Checklist, "Verify execution timing", plus Bug Categories #5), the rebalance/tolerance bullets embed measured anecdotes in long prose, and the Argentina/BYMA paragraph is a single ~20-line inline wall of text. This fits anchor 3 ("mostly efficient but includes some unnecessary explanation or could be tightened") better than 4's "minor instances".

3 / 5

Actionability

Fully executable throughout: a copy-paste `config.json` example, the exact `SignalEngine` signature with signal semantics, a literal syntax-check command `bash("python -c \"import ast; ast.parse(open('code/signal_engine.py').read()); print('OK')\"")`, per-market regex patterns, exact field and error names (`income_total_revenue`, `signal_timing_double_delay`, `BYMA backtest configuration incomplete`), and a standalone validation CLI (`python -m backtest.validation <run_dir>`). Matches anchor 5: copy-paste ready with examples covering the common cases.

5 / 5

Workflow Clarity

The 7-step Workflow is explicitly sequenced with validation checkpoints (syntax check at step 4, evaluation at step 6, fix-and-rerun at step 7), a self-check Quality Checklist, hard gates in Review Criteria, and a genuine feedback loop in "Verify execution timing": remove the extra delay, rerun, and "report only the corrected run's metrics", plus error-recovery guidance for `signal_timing_double_delay` and incomplete BYMA configs. Matches anchor 5: explicit validation steps, feedback loops, and checklists.

5 / 5

Progressive Disclosure

Section headers are clear and navigation is possible, but the bundle contains no references/, scripts/, or assets/ files at all; the sole inline reference [examples.md](examples.md) in "Supporting Files" is a broken link (the file does not exist), and ~100 lines of reference-grade material (the field-by-field `config.json` documentation, Argentina/BYMA rules, HK lot sizes, crypto notes) are inlined rather than split out. This fits anchor 3 ("content that should be separate is inline"); it stays above 2 only because the structure itself is genuinely well organized.

3 / 5

Total

16

/

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.

A clear, domain-specific description with good concrete verbs and the key natural trigger "backtest", but it omits any explicit "Use when..." guidance, which both caps completeness and leaves trigger terms thinner than ideal. Adding a when-clause with common synonyms (quant, algo trading) would lift it substantially.

Suggestions

Add a 'Use when...' clause, e.g. "Use when the user asks to backtest, optimize, or compare quant/algo trading strategies, or mentions backtesting, Sharpe ratio, or trading signals."

Include natural synonyms such as 'quant', 'algo trading', and 'algorithmic trading' alongside 'quantitative trading strategies'.

Optionally name supported markets or instruments (stocks, crypto, cross-market) to sharpen distinctiveness and trigger coverage.

DimensionReasoningScore

Specificity

Quotes "Create, modify, and optimize quantitative trading strategies, then backtest and evaluate them" — five concrete verbs in a clearly named domain, close to anchor 5's "multiple specific concrete actions". It falls short of 5 because the actions all target the same single object and coverage has minor gaps (no mention of markets/instruments, validation, or strategy adaptation), matching anchor 4's "several specific actions; minor gaps in coverage".

4 / 5

Completeness

The "what" is clear ("Create, modify, and optimize quantitative trading strategies, then backtest and evaluate them") but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines. This matches anchor 3 ("clear 'what' but 'when' is missing") and cannot be 4 since no 'when' is even weakly present.

3 / 5

Trigger Term Quality

"quantitative trading strategies", "backtest", "optimize", and "trading" are natural phrases users would say, and "backtest" is the dominant trigger for this need. Not 5: common synonyms such as "quant", "algo trading", "algorithmic trading", and instrument terms (stocks, crypto) are missing; not 3 because the core natural terms are all present rather than merely "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

The niche — quant strategy backtesting — is well differentiated and unlikely to trigger for unrelated skills, matching anchor 4's "mostly distinct; minor overlap risk". Not 5 because "create/modify/optimize strategies" could mildly overlap with general coding or generic trading-analysis skills.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 missing, 1 suspicious

Warning

Total

14

/

16

Passed

Repository

HKUDS/Vibe-Trading

Path

agent/src/skills/strategy-generate/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.