CtrlK
BlogDocsLog inGet started
Tessl Logo

edge-concept-synthesizer

Abstract detector tickets and hints into reusable edge concepts with thesis, invalidation signals, and strategy playbooks before strategy design/export.

62

Quality

72%

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

Quality

Content

87%

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

The content is lean, actionable, and well-structured with real bundle references, but the multi-step workflow omits an explicit validation checkpoint for its batch dedup/promotion operations.

Suggestions

Add an explicit validation step to the workflow, e.g., after running the script, verify edge_concepts.yaml against references/concept_schema.md before promoting concepts.

Inline-link the schema reference from the Output section (e.g., "See references/concept_schema.md for the full structure") so the reference is signaled at the point of need, not only in the trailing Resources list.

DimensionReasoningScore

Conciseness

The body is lean with well-organized sections and executable commands; it avoids explaining concepts Claude already knows and every section earns its place.

3 / 3

Actionability

Quick Commands provide fully executable, copy-paste-ready invocations whose flags (--tickets-dir, --promote-hints, --max-synthetic-ratio, --overlap-threshold, --no-dedup) all match the script's argparse, with distinct usage variants.

3 / 3

Workflow Clarity

The five workflow steps are clearly sequenced, but the batch dedup and promotion steps lack an explicit validation/verification checkpoint (e.g., checking the output against concept_schema.md), so per the scoring note workflow clarity is capped at 2.

2 / 3

Progressive Disclosure

The body is a concise overview with a dedicated Resources section pointing to real one-level-deep references (references/concept_schema.md and scripts/synthesize_edge_concepts.py), providing easy navigation.

3 / 3

Total

11

/

12

Passed

Description

57%

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 is specific and occupies a clear niche, but it omits an explicit "Use when..." trigger clause and relies on specialized jargon, which caps both completeness and trigger-term quality.

Suggestions

Add an explicit "Use when..." clause naming the situations that should activate this skill (e.g., "Use when clustering detector tickets into concepts before strategy drafting").

Broaden trigger terms with more natural phrasings alongside the jargon (e.g., "edge concepts", "ticket clustering", "strategy inputs") so users are more likely to match it.

Consider naming a second concrete action (e.g., "deduplicate and validate concepts") to push specificity from a single transformation verb toward multiple distinct actions.

DimensionReasoningScore

Specificity

"Abstract detector tickets and hints into reusable edge concepts with thesis, invalidation signals, and strategy playbooks" names the domain and concrete deliverables but rests on a single transformation verb rather than multiple distinct actions, so it is not comprehensive enough for a 3.

2 / 3

Completeness

The description clearly states what the skill does but provides no explicit "Use when..." trigger clause; "before strategy design/export" only implies timing, so per the guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

Terms like "detector tickets", "hints", "edge concepts", and "strategy playbooks" are domain-relevant but specialized jargon lacking common natural variations a user would say, so coverage is partial rather than broad.

2 / 3

Distinctiveness Conflict Risk

The narrow pipeline scope (synthesizing edge concepts from detector tickets and hints) is a clear niche unlikely to fire for unrelated skills, matching the distinct-triggers anchor.

3 / 3

Total

9

/

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.