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".
87
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly communicates its purpose, lists specific capabilities and indicators, and provides explicit trigger guidance with natural user phrases. It uses proper third-person voice throughout and covers both the 'what' and 'when' comprehensively. The trading/technical analysis domain is well-defined with minimal conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: generating trading signals, using named technical indicators (RSI, MACD, Bollinger Bands), combining indicators into composite signals with confidence scores. | 3 / 3 |
Completeness | Clearly answers both 'what' (generate trading signals using technical indicators, combine into composite signals with confidence scores) and 'when' (explicit 'Use when' clause plus specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'get trading signals', 'check indicators', 'analyze for entry', 'scan for opportunities', 'generate buy/sell signals', 'technical analysis'. These are phrases a trader would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused on technical trading indicators and signal generation. The specific indicator names (RSI, MACD, Bollinger Bands) and trading-specific terminology make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured skill with strong actionability — every command is concrete and executable with clear CLI flags and options. The main weaknesses are some redundancy between the Instructions and Examples sections, and the lack of validation/verification steps in the workflow (e.g., checking data quality, handling conflicting indicators). Progressive disclosure is well-handled with appropriate references to supporting files.
Suggestions
Remove or consolidate the Examples section with Instructions to eliminate redundant commands — the examples repeat nearly identical commands already shown in steps 1-3.
Add a validation step after scanning, such as verifying sufficient data was retrieved or checking for stale/missing price data before trusting signal output.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some redundancy — the Examples section largely repeats commands already shown in Instructions. The Output section could be tighter. However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | Provides fully executable CLI commands with specific flags, watchlist names, and filter options. Every instruction is copy-paste ready with concrete examples of different use cases. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced from quick scan to detailed analysis to filtering, but there are no validation checkpoints or feedback loops. For a trading signal system, there's no guidance on verifying data quality or handling cases where indicators conflict, which matters for financial decision-making. | 2 / 3 |
Progressive Disclosure | Clean overview structure with well-signaled one-level-deep references to implementation.md and errors.md. Content is appropriately split between the main skill file (usage) and reference files (details, output formats, error handling). | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.