CtrlK
BlogDocsLog inGet started
Tessl Logo

strategy-pivot-designer

Detect backtest iteration stagnation and generate structurally different strategy pivot proposals when parameter tuning reaches a local optimum.

70

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

A well-structured, actionable skill body with executable commands and lean prose. It falls short on explicit validation checkpoints in the workflow and on inline signposting of its reference files.

Suggestions

Add explicit validation checkpoints to the workflow, e.g. after stagnation detection ('verify triggers in pivot_diagnosis_*.json before generating pivots') and before export ('validate exportable YAML against references/pivot_proposal_schema.md').

Signpost references inline at the relevant workflow step, e.g. in step 3 add 'For techniques, see references/pivot_techniques.md; for archetypes, see references/strategy_archetypes.md' rather than only listing them at the end.

Add a brief error-recovery feedback loop, e.g. 'If no stagnation is detected, stop and report; if generated pivots fail schema validation, fix and re-run generate_pivots.py.'

DimensionReasoningScore

Conciseness

Lean and efficient: a short overview, a bulleted When-to-Use/Prerequisites/Output set, and copy-paste commands, with no padding or explanation of concepts Claude already knows.

3 / 3

Actionability

Quick Commands provides three fully executable bash invocations with real script paths, flags, and arguments that are copy-paste ready.

3 / 3

Workflow Clarity

The seven steps are sequenced and include one conditional ('If stagnation detected'), but there are no explicit validation checkpoints or error-recovery feedback loops (e.g., verify the diagnosis or validate generated YAML against the schema before exporting).

2 / 3

Progressive Disclosure

Content is appropriately split into real one-level-deep references and a Resources list, but references are not contextually signposted within the workflow, so a reader does not know which reference to consult at which step.

2 / 3

Total

10

/

12

Passed

Description

90%

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 concise, third-person description that clearly conveys both capability and trigger conditions with strong, domain-appropriate keywords. Its only weakness is listing just two actions rather than a more comprehensive set.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ('Detect backtest iteration stagnation' and 'generate structurally different strategy pivot proposals'), but stops at two actions rather than listing a comprehensive set, matching the level-2 anchor.

2 / 3

Completeness

States what the skill does ('detect...and generate...pivot proposals') and includes an explicit when trigger ('when parameter tuning reaches a local optimum'), satisfying both what and when.

3 / 3

Trigger Term Quality

Uses natural terms a quant user would say when stuck — 'backtest iteration stagnation', 'strategy pivot', 'parameter tuning', 'local optimum' — giving good coverage of the domain's trigger vocabulary.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (breaking out of backtest local optima via strategy redesign) with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tradermonty/claude-trading-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.