CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

edge-hint-extractor

Extract edge hints from daily market observations and news reactions, with optional LLM ideation, and output canonical hints.yaml for downstream concept synthesis and auto detection.

Quality

75%

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-hint-extractor/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 body is a well-structured, highly actionable overview with verified executable commands and excellent progressive disclosure into the reference schema and script. Its main weakness is the absence of any validation or sanity-check step before passing hints.yaml downstream. Minor trimming of the repeated command blocks would improve token efficiency.

Suggestions

Add a validation checkpoint after hint generation, e.g. verify hint counts from the generation metadata and check hints.yaml against references/hints_schema.md before passing it to downstream stages.

Consolidate the three Quick Commands blocks by showing the full base command once and then only the differing flags (--llm-ideas-cmd / --llm-ideas-file) for the two LLM variants.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanations of what YAML, market summaries, or LLMs are. It is not 5 because the three Quick Commands blocks repeat the same base flags (--market-summary, --anomalies, --output-dir) nearly verbatim, which could be tightened to one base command plus per-variant flags.

4 / 5

Actionability

The three bash examples are fully executable and copy-paste ready (flags verified against scripts/build_hints.py), covering all common modes: rule-only, external LLM CLI via --llm-ideas-cmd, and pre-written file via --llm-ideas-file. Concrete input paths, --as-of, and output directory make the guidance immediately runnable.

5 / 5

Workflow Clarity

The 4-step workflow is clearly sequenced with a useful mutual-exclusivity note, but there are no validation checkpoints: nothing checks hint counts, YAML validity, or schema conformance before "Pass hints.yaml into concept synthesis or auto detection", even though references/hints_schema.md exists and could serve that purpose. Sequence present with checkpoints absent matches anchor 3 rather than 4's "most checkpoints present".

3 / 5

Progressive Disclosure

The SKILL.md is a clean overview: workflow, commands, and a Resources section pointing to one-level-deep, verified bundle files (references/hints_schema.md for the output schema, scripts/build_hints.py for logic). The hints.yaml schema details are appropriately split out of the main body, and navigation is easy with well-organized sections.

5 / 5

Total

17

/

20

Passed

Description

58%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 concrete capabilities and a distinct niche, but lacks any explicit "when to use" trigger clause, which caps its completeness and weakens natural invocation. Keyword coverage is adequate but misses common synonyms and input-file terms. Adding a Use-when clause with natural trigger phrases would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when turning daily market observations, anomalies, or news reactions into hints.yaml for concept synthesis or auto detection."

Include natural trigger synonyms users would actually say, such as "anomalies", "market_summary", "news reactions file", and "edge ideas", to improve trigger-term coverage.

Briefly mention the two generation modes (rule-based and LLM ideation) as distinct capabilities to make the "what" fully comprehensive.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Extract edge hints from daily market observations and news reactions", "optional LLM ideation", "output canonical hints.yaml" — with only minor coverage gaps. It falls short of 5 because coverage is not comprehensive (e.g., no mention of the rule-based generation path or input files) and clearly exceeds 3's "1-2 concrete actions".

4 / 5

Completeness

The "what" is clear (extract hints, output canonical hints.yaml), but there is no "Use when..." clause or equivalent explicit trigger guidance; "for downstream concept synthesis and auto detection" states downstream purpose, not when to invoke the skill. Per the judging guideline, a missing Use-when clause caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like "market observations", "news reactions", "hints.yaml", and "concept synthesis" are relevant to the domain, but common variations and synonyms users would naturally say ("anomalies", "market_summary", "trading signals", "edge ideas") are missing. Coverage is partial rather than "good with a few missing", so it sits at 3 rather than 4.

3 / 5

Distinctiveness Conflict Risk

The "edge hints" / "hints.yaml" niche is mostly distinct with domain-specific vocabulary, giving minimal conflict with unrelated skills. It is not 5 because explicitly naming adjacent pipeline stages ("concept synthesis", "auto detection") creates minor overlap risk with closely related sibling skills in the same workflow.

4 / 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-hint-extractor/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.