CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

edge-strategy-designer

Convert abstract edge concepts into strategy draft variants and optional exportable ticket YAMLs for edge-candidate-agent export/validation.

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 ./skills/edge-strategy-designer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

83%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 tight, highly actionable skill body with executable commands and zero padding, held back only by a missing post-generation validation step for its batch output. Bundle structure is well organized with a genuine one-level reference, though cross-signaling from the body to that reference could be stronger.

Suggestions

Add an explicit validation step after generation, e.g. verify each draft in strategy_drafts/ against references/strategy_draft_schema.md and check run_manifest.json before export handoff.

Signal the schema reference contextually in the Output section (e.g. 'Draft format: see references/strategy_draft_schema.md') rather than only in Resources.

DimensionReasoningScore

Conciseness

Every section is lean and operational — short Overview, bulleted When to Use/Prerequisites/Output, and two command blocks — with no padding and no explanation of concepts Claude already knows. Not score 4 because there are no instances of over-explanation to trim; the positional note ('sits after concept synthesis and before pipeline export validation') earns its place.

5 / 5

Actionability

Two complete, copy-paste-ready bash commands cover the common cases (drafts only, drafts + exportable tickets) with all flags and concrete paths, plus explicit prerequisites and outputs. Not score 4 because the commands are fully executable with no gaps for the documented use cases.

5 / 5

Workflow Clarity

The 7 steps are clearly sequenced with specifics (HYPOTHESIS_EXIT_OVERRIDES, RR_FLOOR=1.5, handoff to export_candidate.py), but the skill batch-generates many files with no verify/validate step after generation — the batch-operation cap of 3 applies. Not score 4 because a verification checkpoint (e.g. checking drafts against the schema or inspecting run_manifest.json) is missing; not score 2 because the sequence itself is well defined.

3 / 5

Progressive Disclosure

Short overview body with a real, one-level-deep reference (references/strategy_draft_schema.md, verified present) listed under Resources, plus the script path. Not score 5 because references are only listed in a Resources section rather than contextually signaled — the Output and Workflow sections never point to the schema doc — leaving minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

57%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 a clear, distinctive niche with concrete actions, but reads as internal pipeline jargon rather than user-facing trigger language. Its main weakness is the complete absence of a 'when to use' clause, which both caps completeness and limits trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when you have edge_concepts.yaml and need strategy candidates or exportable ticket files.'

Include natural trigger phrases users would actually say (e.g. 'strategy drafts', 'ticket YAML', 'edge concept to strategy') alongside the internal terminology.

Briefly enumerate the variant types (core/conservative/research-probe) and risk-profile selection to improve coverage specificity.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ('Convert abstract edge concepts into strategy draft variants' and 'optional exportable ticket YAMLs'), but coverage is not comprehensive — no mention of risk-profile selection, exit calibration, or variant types. Not score 4 because only two actions are listed with notable gaps; not score 2 because the actions are concrete rather than generic.

3 / 5

Completeness

Has a clear 'what' (convert concepts into strategy draft variants and optional ticket YAMLs) but no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the judging guidelines. Not score 4 because the 'when' is entirely absent rather than just imprecise.

3 / 5

Trigger Term Quality

Contains relevant domain keywords ('edge concepts', 'strategy draft variants', 'ticket YAMLs', 'edge-candidate-agent') but they are internal-pipeline jargon rather than natural phrases a user would say, and common variations/synonyms are missing. Not score 4 because natural trigger phrasing is largely absent; not score 2 because the terms are domain-relevant rather than fully generic.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche ('edge concepts' → 'strategy draft variants' for 'edge-candidate-agent export/validation') with distinct, ecosystem-specific triggers and minimal conflict risk with generic skills. Not score 4 because the named downstream consumer and specialized vocabulary make overlap risk negligible.

5 / 5

Total

14

/

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/edge-strategy-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.