CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

strategy-dev-manager

Strategy Development Manager: convert academic papers and research reports into validated factors and strategies with automated backtesting, persistent storage, and decay monitoring.

Quality

76%

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 ./agent/src/skills/strategy-dev-manager/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 workflow is a strong, well-validated five-phase procedure with concrete thresholds, tool calls, and error-recovery loops. The main weaknesses are reference integrity — several referenced files (examples.md, templates/, src/factors/base.py) are missing from the bundle while existing reference files are unmentioned — and some duplicated guidance between the phases and Common Pitfalls.

Suggestions

Ship or fix the broken references: create templates/factor_signal_engine.py and templates/strategy_signal_engine.py (Phase 3 depends on them), add examples.md, and correct the src/factors/base.py path.

Link the existing but unmentioned bundle files (scheduled_decay_scan.md, strategy_extraction_guide.md, strategy_metrics.md) from the relevant phases or the References section so they are discoverable.

Consolidate the duplicated deduplication IC guidance (Phase 2 vs. 'Factor Deduplication' pitfall) into one location to trim tokens.

DimensionReasoningScore

Conciseness

The body is dense, procedural, and assumes competence — no space is spent explaining concepts Claude already knows. Minor trimming opportunities exist: the dedup IC thresholds (0.99 / 0.90-0.99) are explained in Phase 2 and again verbatim in "Factor Deduplication", and the decay state machine transitions appear in both Phase 5 and the pitfalls. These redundancies keep it below the lean 5 anchor but well above the noticeably-verbose 3.

4 / 5

Actionability

Highly concrete: named tool calls with parameters (sdm_register, generate_backtest_config with bench_type semantics), exact statistical thresholds (IC > 0.03, IR > 0.5, Sharpe > 0.5, DD < 30%), a runnable AST-validation command, and a full SignalEngine code contract. The gap: Phase 3 directs implementation "using the appropriate template from templates/" but the templates/ directory does not exist in the bundle, so that step is not fully executable as written.

4 / 5

Workflow Clarity

Five phases are clearly sequenced with routing guidance, and validation checkpoints with feedback loops are explicit throughout: AST syntax validation before backtest, bench_record confirmation with "fix the config and re-run" recovery, OCR quality branches, a dedup gate, and a closing Quality Checklist. This matches the anchor for clear sequence plus explicit validation, error-recovery loops, and a checklist.

5 / 5

Progressive Disclosure

In-body structure is good (sections, tool reference table, References list), but scored against the actual bundle it navigates poorly: of the referenced paths, only references/decay_thresholds.md exists — examples.md, templates/, and src/factors/base.py are missing — while three real bundle files (scheduled_decay_scan.md, strategy_extraction_guide.md, strategy_metrics.md) are never mentioned in SKILL.md and are undiscoverable. References are present but unreliable/mis-signaled, fitting the 3 anchor better than the well-organized 4 anchor and better than the 2 anchor given the body's solid internal structure.

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.

The description states a clear, specific capability set in third person with domain-natural keywords, but omits any explicit 'when to use this' trigger guidance, which caps completeness. Adding a 'Use when...' clause with concrete user phrasings would lift it to the top anchor.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user provides an academic paper or research report and wants factors or strategies extracted, backtested, and monitored."

Include a few natural user phrasings as trigger terms (e.g. "backtest this paper", "turn this paper into a factor", "factor decay").

Consider naming the ingestion/evaluation steps to round out lifecycle coverage in the 'what'.

DimensionReasoningScore

Specificity

Lists several concrete actions — "convert academic papers and research reports into validated factors and strategies", "automated backtesting", "persistent storage", "decay monitoring" — with only minor coverage gaps (document ingestion and threshold evaluation are not named). It names more than 1-2 actions (not a 3) but 'persistent storage' is generic and the lifecycle is not comprehensive (not a 5).

4 / 5

Completeness

The 'what' is clearly and concretely stated (paper-to-validated-strategy conversion with backtesting, storage, decay monitoring), but there is no 'Use when...' clause or equivalent trigger guidance. Per the rubric guideline, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "academic papers", "research reports", "factors", "strategies", "backtesting", "decay monitoring" — terms a quant user would say. A few natural synonyms are missing (e.g. "backtest this paper", "alpha", "replicate results"), so it falls short of the comprehensive-with-synonyms anchor at 5 but is well above the partial-coverage anchor at 3.

4 / 5

Distinctiveness Conflict Risk

The niche — turning academic papers into validated, monitored trading factors/strategies — is distinct with domain-specific triggers unlikely to fire for unrelated skills. Minor overlap risk with generic backtesting or quant-research skills keeps it below 5.

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.

Validation — 15 / 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

HKUDS/Vibe-Trading

Path

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