CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

strategy-pivot-designer

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

Quality

88%

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

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

A well-engineered skill body: token-efficient, fully executable commands, and a sequenced workflow with an explicit review_required validation gate and a feedback loop. The only notable weakness is navigation — the Resources section lists reference files as bare paths rather than labeling what each contains and when to consult it.

Suggestions

Annotate the Resources entries with what each file contains and when to read it (e.g., '**Stagnation triggers**: see references/stagnation_triggers.md for trigger thresholds and edge cases') so navigation is signposted like the anchor-5 pattern.

Replace wildcard arguments in the generate command (reports/pivot_diagnosis_*.json) with a concrete example filename to keep every command literally copy-paste runnable.

Move the cryptic profit-factor edge-case note in workflow step 2 into references/stagnation_triggers.md, keeping the workflow line as a pointer.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: a two-sentence Overview, terse bullet lists for When to Use / Prerequisites / Output, a compact 7-step workflow, and three command blocks with no padding or explanation of concepts Claude already knows. Every section earns its place, matching the anchor-5 example of lean, efficient structure.

5 / 5

Actionability

Three complete, copy-paste-ready bash commands with realistic arguments (--append-eval with a concrete --changes example, --strategy-id, --max-pivots) cover the common cases of appending history, detecting stagnation, and generating pivots, plus concrete output file paths. This matches 'fully executable; copy-paste ready; specific examples cover the common cases'.

5 / 5

Workflow Clarity

The 7-step workflow is clearly sequenced with an explicit validation gate ("If the diagnosis says review_required, repair or re-evaluate the underlying metrics first; do not generate pivots") and a feedback loop (step 7 feeds the selected pivot back into backtest-expert), mirroring the validate-then-proceed pattern of the anchor-5 example.

5 / 5

Progressive Disclosure

Content is appropriately split: detailed triggers, archetypes, techniques, and schema live in real one-level-deep reference files (verified present in references/ with no nested references), while commands stay inline. However, the Resources section is a bare list of paths without labels, when-to-read guidance, or links, which is the minor organization gap described by anchor 4 rather than the well-signaled navigation of anchor 5.

4 / 5

Total

19

/

20

Passed

Description

73%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 precise, domain-specific description with a clear what-and-when structure and minimal conflict risk. Its main limitations are modest action coverage (two verbs) and a single trigger condition, leaving common stagnation phrasings like 'plateaued' or 'overfitting' unstated.

Suggestions

Enumerate the concrete capabilities more fully (e.g., 'diagnose stagnation triggers such as plateau, overfitting, and cost defeat; rank and export pivot proposals') to lift specificity.

Broaden the trigger clause to cover natural user phrasings: 'Use when backtest results have plateaued, the strategy is overfit, or parameter tuning has hit a local optimum.'

Consider naming the output artifacts (pivot drafts, diagnosis reports) so the description communicates deliverables as well as actions.

DimensionReasoningScore

Specificity

Names the domain and exactly two concrete actions — "Detect backtest iteration stagnation" and "generate structurally different strategy pivot proposals" — which matches the 1-2-concrete-actions anchor. It is not comprehensive (no mention of diagnosis output, ranking, or pipeline integration), so it falls below the 'several specific actions' of anchor 4.

3 / 5

Completeness

Clearly answers 'what' (detect stagnation, generate pivot proposals) and includes an explicit 'when' clause ("when parameter tuning reaches a local optimum"), so it has both elements. The 'when' names only a single condition and lacks 'Use when...'-style phrasing with multiple concrete triggers, so it does not reach the explicit trigger-phrase coverage of anchor 5.

4 / 5

Trigger Term Quality

Contains good natural domain keywords — "backtest", "stagnation", "parameter tuning", "local optimum", "strategy", "pivot" — that a quant user would plausibly say. A few common variations are missing (e.g., "plateaued", "stuck", "overfitting"), keeping it below the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — detecting backtest iteration stagnation and proposing structurally different strategy architectures — with trigger terms (backtest, parameter tuning, local optimum) that would not fire for unrelated skills. Minimal conflict risk, matching anchor 5.

5 / 5

Total

16

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

tradermonty/claude-trading-skills

Path

skills/strategy-pivot-designer/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.