CtrlK
BlogDocsLog inGet started
Tessl Logo

generating-trading-signals

Generate trading signals using technical indicators (RSI, MACD, Bollinger Bands, etc.). Combines multiple indicators into composite signals with confidence scores. Use when analyzing assets for trading opportunities or checking technical indicators. Trigger with phrases like "get trading signals", "check indicators", "analyze for entry", "scan for opportunities", "generate buy/sell signals", or "technical analysis".

73

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The content is highly actionable with clean progressive disclosure and clear workflow sequencing for a read-only tool, but it loses points on conciseness due to repeated commands and restated signal-type information between sections. Trimming the duplicated Examples commands would recover the remaining score.

Suggestions

Remove the duplicate commands in the Examples section that already appear in the numbered Instructions (e.g. the crypto_top10 --period 6m scan and the BTC-USD --detail call), or reframe Examples around distinct use cases not already covered.

Avoid restating the signal types in the Output section since they already appear in the Overview; reference the existing list instead.

Link the existing references/examples.md bundle file from the body so all bundled references are discoverable, since it is currently unreferenced.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable commands and no concept over-explanation, but the Examples section repeats commands already shown in Instructions (e.g. the crypto_top10 scan and BTC --detail) and the Output section restates signal types from the Overview, adding redundancy that could be tightened. It falls short of level 3 because not every token earns its place.

2 / 3

Actionability

All guidance consists of complete, copy-paste-ready bash commands with real flags (--watchlist, --symbols, --detail, --filter, --min-confidence, --rank, --output) using ${CLAUDE_SKILL_DIR}, matching the fully-executable anchor rather than the pseudocode of level 2.

3 / 3

Workflow Clarity

The four usage modes are clearly sequenced and unambiguous, and since this is a read-only analysis tool rather than a destructive or batch-write operation, no validation/feedback loop is required; the Error Handling table adds cause/fix recovery. This meets the clear-sequence bar rather than the validation-gap cap of level 2.

3 / 3

Progressive Disclosure

The body is a concise overview pointing to clearly signaled one-level-deep references that exist as real bundle files (references/implementation.md, references/errors.md) and directly invoking scripts/scanner.py, matching the well-signaled-navigation anchor rather than the poorly-signaled structure of level 2.

3 / 3

Total

11

/

12

Passed

Description

100%

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, complete, and distinctive with a strong set of natural trigger phrases and explicit use-when guidance, all in third person. It is a strong model description with no notable weaknesses.

DimensionReasoningScore

Specificity

Names multiple concrete actions ("Generate trading signals", "Combines multiple indicators into composite signals with confidence scores") and specific indicators (RSI, MACD, Bollinger Bands), matching the multiple-specific-actions anchor rather than the partial domain-naming of level 2.

3 / 3

Completeness

Explicitly answers both what ("Generate trading signals...") and when ("Use when analyzing assets for trading opportunities or checking technical indicators. Trigger with phrases like..."), meeting the explicit-trigger bar of level 3 rather than the implied-when of level 2.

3 / 3

Trigger Term Quality

Lists natural trigger phrases users would say ("get trading signals", "check indicators", "scan for opportunities", "generate buy/sell signals"), giving good coverage rather than the partial keyword set of level 2.

3 / 3

Distinctiveness Conflict Risk

The trading-signals niche with domain-specific triggers is clearly distinguishable and unlikely to conflict with other skills, matching the clear-niche anchor rather than the overlap risk of level 2.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-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.