CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

strategy-discovery

Strategy Discovery: evidence-gated facade over Alpha Zoo + the SDM strategy store — answers what strategies exist and what state they are in, with per-regime evidence instead of scenario tags; reports evidence freshness on every returned row and rebuilds the disposable evidence cache from local backtest runs.

Quality

68%

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-discovery/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 dense, well-validated operational contract with genuinely strong actionability — exact parameters, commands, gates, and failure semantics — but it is padded by heavy cross-section repetition and keeps all reference-grade detail inline with no progressive-disclosure split, and the bolted-on adaptation section dilutes the otherwise crisp tool story.

Suggestions

State each tool's scope once (in its Tools subsection) and replace the repeated refresh/caching guarantees elsewhere with a single cross-reference; this would cut roughly 20% of the body.

Move the Evidence Row Contract, decay threshold tables, and cost-screen derivation into a references/ file (e.g., EVIDENCE.md), keeping SKILL.md as the routing-and-semantics overview.

Reconcile the tool count and integrate "Description-driven adaptation" properly — the body says "the three query tools… the fourth tool" while later declaring adapt_strategy "the fifth tool", and the adaptation workflow itself is compressed and unclear about when to choose it.

DimensionReasoningScore

Conciseness

Mostly domain-specific contract detail Claude cannot derive (thresholds, gates, fail-closed semantics), but the same refresh/caching guarantees are restated across ~5 sections ("rebuilds the disposable cache from run artifacts… it is NOT strategy creation" appears in When to Use, Tools, Populating, Honest-Empty, and Composition Guarantee), and "no network, no credentials" is repeated twice in one section. Could be tightened without losing information — not anchor 2 because the bulk is non-derivable, not filler.

3 / 5

Actionability

Concrete parameter tables for all tools, exact CLI invocations ("vibe-trading strategy-evidence refresh --manifest <path>"), a copy-paste manifest JSON example, the breakeven formula, and exact hard-gate failure tokens. Not a 5 because there are no example tool calls or example response rows/envelopes to anchor expected outputs.

4 / 5

Workflow Clarity

The routing decision tree, the ordered 5-gate hard-gate checklist with stable failure tokens and per-entry skip reasons, and the 3-step periodic recipe provide explicit validation and feedback loops. Not a 5 because the appended "Description-driven adaptation" section introduces a fifth tool with a muddier workflow and stale contradictions ("the three query tools" vs. the earlier "four tools" framing), slightly muddying the overall sequence.

4 / 5

Progressive Disclosure

Well-sectioned with clear headers and internal cross-references ("see Populating & Refreshing Evidence"), but there are no bundle files at all — all ~200 lines of evidence-row contract, decay tables, cost-screen math, and gate definitions live inline in SKILL.md. Content that clearly belongs in a reference file (e.g., the evidence row contract and decay thresholds) is inline, matching anchor 3.

3 / 5

Total

14

/

20

Passed

Description

58%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 communicates concrete capabilities and a clear niche with specific named subsystems, but it buries its user-facing query functions under implementation jargon and omits any explicit "Use when…" trigger guidance, capping completeness and weakening natural trigger-term coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks what strategies exist, how a strategy is performing, or wants evidence behind a regime claim".

Include natural user vocabulary — "list strategies", "query strategies", "Sharpe", "bear market", "evidence" — so the description matches how users actually phrase these requests.

Trim implementation jargon ("evidence-gated facade", "disposable cache") in favor of one plain-language sentence about the three read-only query tools.

DimensionReasoningScore

Specificity

Lists several concrete actions — "answers what strategies exist and what state they are in", "reports evidence freshness on every returned row", "rebuilds the disposable evidence cache from local backtest runs" — with named sources (Alpha Zoo, SDM strategy store). Not a 5 because the query/filtering capabilities (regime filters, Sharpe thresholds) that dominate the skill's actual use are absent, leaving minor coverage gaps.

4 / 5

Completeness

The "what" is clear and specific, but there is no "Use when…" clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It sits above anchor 2 because the "what" is concrete, not vague.

3 / 5

Trigger Term Quality

Relevant terms exist ("what strategies exist", "backtest runs", "evidence", "freshness"), but the natural vocabulary users would actually say — "list strategies", "which strategies work", "Sharpe", "bear market" — is missing, and jargon like "evidence-gated facade" dominates. Fits anchor 3 (some relevant keywords, missing common variations) better than anchor 4.

3 / 5

Distinctiveness Conflict Risk

Names its specific niche (read-only strategy discovery over Alpha Zoo + SDM store, evidence reporting) with distinct triggers; it fronts sibling skills (strategy-dev-manager, alpha-zoo) which creates minor overlap risk with those creation/registration workflows. Mostly distinct — anchor 4 rather than 5.

4 / 5

Total

14

/

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-discovery/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.