CtrlK
BlogDocsLog inGet started
Tessl Logo

edge-strategy-designer

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

56

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/edge-strategy-designer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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 content is well-structured, lean, and highly actionable with executable commands and a clear sequence. Its main gap is the absence of an explicit validation/verification step for a batch-generation workflow that hands artifacts off to a downstream agent.

Suggestions

Add an explicit validation checkpoint to the workflow (e.g., verify generated strategy_drafts/*.yaml conform to references/strategy_draft_schema.md and that run_manifest.json was written before handoff).

Include a feedback loop ('if validation fails, fix and re-run') to lift workflow clarity above the batch-operation cap.

Trim the repeated full script path in the two Quick Command blocks to improve conciseness toward a 5.

DimensionReasoningScore

Conciseness

The body is lean, sectioned, and assumes Claude's competence, with only minor redundancy (the full script path is repeated in both Quick Command blocks).

4 / 5

Actionability

Two complete copy-pasteable bash invocations with concrete flags and a step list referencing real script paths give fully executable guidance for the common cases.

5 / 5

Workflow Clarity

A clear 7-step sequence exists, but this batch generator (many variant YAMLs per concept) has no validation/verification checkpoint before handoff, so per the batch-operations cap workflow clarity cannot exceed 3.

3 / 5

Progressive Disclosure

SKILL.md is a concise overview pointing one level deep to a real references/strategy_draft_schema.md and the real design_strategy_drafts.py, with a clearly signaled Resources section and easy navigation.

5 / 5

Total

17

/

20

Passed

Description

46%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 but lacks any 'when to use' trigger and leans on technical jargon over user-natural keywords. It is reasonably distinctive within its domain but would benefit from explicit use-when guidance.

Suggestions

Add an explicit 'Use when ...' clause naming the natural user triggers (e.g., 'when you need strategy draft variants from edge_concepts.yaml or exportable ticket YAMLs for export_candidate.py').

Soften jargon with user-natural synonyms so the description surfaces on everyday phrasing, not only domain terms.

Consider mentioning the core/conservative/research-probe variants explicitly to strengthen completeness of the 'what'.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ('strategy draft variants' and 'optional exportable ticket YAMLs'), but coverage is not comprehensive enough for a 4.

3 / 5

Completeness

It states a clear 'what' but provides no explicit 'when/Use when' guidance, so per the missing-trigger clause completeness is capped at 3.

3 / 5

Trigger Term Quality

Keywords like 'edge concepts', 'strategy draft', 'exportable ticket YAMLs', and 'export/validation' are domain jargon rather than phrases a user would naturally say, and no 'Use when' trigger is present.

2 / 5

Distinctiveness Conflict Risk

The niche ('strategy draft variants', 'edge-candidate-agent export/validation') is mostly distinct with only minor overlap risk against the sibling edge-candidate-agent skill.

4 / 5

Total

12

/

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.

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.