CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

edge-concept-synthesizer

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

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

68%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-organized, executable skill body with real one-level-deep bundle references and copy-paste-ready commands. Its main weakness is the absence of validation/verification checkpoints in a batch workflow, and a minor ambiguity over whether dedup is performed by the script or manually.

Suggestions

Add an explicit validation step after running the script, e.g., "Verify edge_concepts.yaml against references/concept_schema.md and check export_ready_v1 flags before promoting concepts" — the batch ticket-processing workflow currently caps workflow clarity at 3.

Clarify workflow step 4: state that dedup is controlled by --overlap-threshold/--no-dedup (and when manual merging is needed), so the script flags and the workflow step don't read as two different operations.

Link references/concept_schema.md contextually from the Output section (e.g., "Schema: see references/concept_schema.md") instead of only in the trailing Resources list, and use a consistent path base for both resource entries.

DimensionReasoningScore

Conciseness

The body is lean with terse sections ("Prerequisites", "Output", "Workflow") and no explanations of concepts Claude already knows. Not 5 because the four Quick Command blocks repeat the same base invocation nearly verbatim instead of showing the base command once plus flag variations, a minor redundancy that could be trimmed.

4 / 5

Actionability

Quick Commands are copy-paste executable with concrete paths and flag variants (--promote-hints, --max-synthetic-ratio, --overlap-threshold, --no-dedup), and the referenced script and schema files exist in the bundle. Not 5 because workflow step 4 ("Deduplicate concepts: merge same-hypothesis concepts ... (containment > threshold)") is ambiguous about whether the script's dedup flags perform this or Claude must merge concepts manually.

4 / 5

Workflow Clarity

The five numbered steps form a clear sequence (collect, hints, run script, dedup, review/promote), but there is no validation or verification checkpoint after the batch operation (e.g., verifying edge_concepts.yaml against references/concept_schema.md or checking export readiness before promotion). Per the rubric, batch operations without validation are capped at 3; it is not 2 because the sequence itself is coherent and concrete.

3 / 5

Progressive Disclosure

The body is well-sectioned with one-level-deep references to real bundle files (scripts/synthesize_edge_concepts.py and references/concept_schema.md both verified present), and no content that belongs in a separate file is inlined. Not 5 because the schema reference is listed only in a trailing Resources list rather than signposted contextually from the Output section, and the two Resources entries use inconsistent path bases (skills/-prefixed vs. bare references/).

4 / 5

Total

15

/

20

Passed

Description

62%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 specific, domain-distinct description that clearly states what the skill produces, but it lacks any explicit 'Use when...' trigger guidance, capping completeness, and its keywords are internal jargon rather than natural user phrases. Adding an invocation clause with user-natural trigger terms would lift the two weakest dimensions.

Suggestions

Add an explicit trigger clause, e.g., "Use when you have raw detector tickets or hints and need concept-level structure before drafting or exporting strategies."

Include natural trigger terms and synonyms a user would actually say, such as "tickets", "hints", "concepts", "edge_concepts.yaml", or "before strategy design".

Consider naming the concrete output file (edge_concepts.yaml) in the description so it also matches file-oriented invocations.

DimensionReasoningScore

Specificity

The description names the domain ("detector tickets and hints") and concrete output artifacts ("reusable edge concepts with thesis, invalidation signals, and strategy playbooks"), giving several specific elements. It falls short of 5 because it rests on a single action verb ("Abstract...") rather than listing multiple concrete actions, and ahead of 3 because the enumerated artifacts go beyond a minimal 1-2 action description.

4 / 5

Completeness

The "what" is clear ("Abstract detector tickets and hints into reusable edge concepts..."), but the "when" is only weakly implied: "before strategy design/export" describes pipeline sequencing, not explicit trigger guidance. Per the rubric, a missing 'Use when...' clause or equivalent caps completeness at 3; not 4 because there is no concrete invocation trigger.

3 / 5

Trigger Term Quality

Relevant keywords exist ("detector tickets", "hints", "edge concepts", "strategy playbooks") but they are domain jargon with no natural variations, synonyms, or file-format terms (e.g., "tickets", "concepts", "edge_concepts.yaml") that a user would naturally say. Not 4 because common phrasings users would actually utter when needing this skill are missing.

3 / 5

Distinctiveness Conflict Risk

Highly niche vocabulary ("detector tickets", "edge concepts", "invalidation signals", "strategy playbooks") carves out a clear position in the pipeline, explicitly distinct from the downstream strategy-design step. Minimal realistic conflict risk with other skills; not lower because the jargon, while not user-natural, is unambiguous within its domain.

5 / 5

Total

15

/

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-concept-synthesizer/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.