CtrlK
BlogDocsLog inGet started
Tessl Logo

signal-analysis

Use this skill for analyzing market signals, price trends, volume patterns, and identifying potential trading opportunities from multiple data sources.

53

Quality

58%

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 ./packages/tentacles/Trading/Mode/ai_trading_mode/resources/skills/signal_analyst/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The body is well-organized and self-contained with a useful output schema, but it functions largely as a glossary of trading concepts Claude already knows and lacks the concrete computational guidance and validation steps needed to make the analysis reproducible. It is a clear but shallow instruction skill.

Suggestions

Replace definitions of well-known concepts (uptrend, support, resistance, volume surge) with the specific decision logic that matters — which indicators to compute, what thresholds qualify a signal, and how to weight each factor into the final strength/confidence values.

Add concrete computational guidance (named indicators, formulas, or numeric thresholds) so the analysis is reproducible rather than descriptive.

Insert a validation/sanity-check step before emitting signals (e.g. require volume to confirm price, reject setups with conflicting timeframes) so the workflow has explicit checkpoints instead of an open checklist.

DimensionReasoningScore

Conciseness

The bullets are tersely formatted, but most of the body restates concepts Claude already knows (e.g. "Uptrend: Series of higher highs and higher lows", definitions of support/resistance and volume surge), which is unnecessary context even though it is not prose-padding.

2 / 3

Actionability

It provides a structured five-part framework and a concrete JSON output schema, which is actionable in shape, but offers no specific indicators, formulas, or thresholds to compute, so the guidance is incomplete for reproducible analysis.

2 / 3

Workflow Clarity

The five numbered sections supply a sequence (price, volume, structure, quality, news, output) but include no validation checkpoints or feedback loops to confirm a signal before emitting it, leaving the workflow a checklist rather than a gated process.

2 / 3

Progressive Disclosure

The skill is a single self-contained file with no bundle references, organized into clearly headed sections with no nested reference chains, which is appropriately structured for a skill of this scope.

3 / 3

Total

9

/

12

Passed

Description

60%

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 about capabilities and includes an explicit use-trigger, but the trigger terms lack common natural variations and the "when" guidance largely restates the "what" rather than naming distinct triggering situations. It is a competent but not exemplary description.

Suggestions

Add a distinct when-clause naming user-facing situations, e.g. "Use when the user asks about market signals, price trends, volume, or potential trading setups for crypto/stocks," separating it from the capability statement.

Broaden trigger terms with concrete variations users actually say — "charts", "breakouts", "support/resistance", "crypto", "stocks" — rather than only abstract analytical concepts.

Tighten distinctiveness by scoping the data sources or asset class so the skill is less likely to collide with generic technical-analysis skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "analyzing market signals, price trends, volume patterns" and "identifying potential trading opportunities from multiple data sources" — matching the anchor for listing several specific actions rather than vague language.

3 / 3

Completeness

An explicit "Use this skill for..." trigger is present, but the "when" merely restates the capability rather than naming distinct user-facing situations, so the when-clause is weakly differentiated from the what.

2 / 3

Trigger Term Quality

It includes relevant terms ("market signals", "price trends", "volume patterns", "trading opportunities") but misses common variations a user would naturally say such as "charts", "crypto", "stocks", "support/resistance", or "breakouts", so coverage is partial rather than comprehensive.

2 / 3

Distinctiveness Conflict Risk

The trading-signal niche is reasonably specific, but the abstract framing could overlap with other trading, technical-analysis, or finance skills, so it is not clearly a conflict-free distinct trigger set.

2 / 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
Drakkar-Software/OctoBot
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.