features
Real-time market features and trading signals
37
22%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/features/SKILL.mdQuality
Discovery
22%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 description is too vague and lacks actionable detail. It reads more like a category label than a skill description—it doesn't specify what concrete actions the skill performs (e.g., generating signals, analyzing indicators, fetching prices) and completely omits any guidance on when Claude should select it. It would be difficult for Claude to reliably choose this skill from a list of similar financial or data-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates buy/sell trading signals based on technical indicators, fetches real-time stock/crypto prices, and calculates moving averages and RSI.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about trading signals, stock prices, technical analysis, market indicators, or real-time financial data.'
Include common file types, asset classes, or platform names to improve distinctiveness and trigger term coverage, e.g., 'stocks, crypto, forex, candlestick charts, .csv market data'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language. 'Real-time market features' and 'trading signals' are broad domain terms without any concrete actions like 'analyze', 'generate', 'calculate', or 'monitor'. | 1 / 3 |
Completeness | The description weakly addresses 'what' (market features and trading signals) but provides no 'when' clause or explicit trigger guidance. Both components are very weak. | 1 / 3 |
Trigger Term Quality | It includes some relevant keywords like 'market', 'trading signals' that users might mention, but misses common variations such as 'stocks', 'crypto', 'forex', 'buy/sell signals', 'technical analysis', 'price alerts', etc. | 2 / 3 |
Distinctiveness Conflict Risk | While 'trading signals' is somewhat specific to a financial domain, 'real-time market features' is broad enough to overlap with general market analysis, financial data, or portfolio management skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a bare command reference with no actionable detail. It lacks examples of command usage with real parameters, expected output formats, and any workflow guidance on how to interpret or act on the features and signals. Claude would not know what valid platforms or marketIds look like, what the output means, or how to chain these commands effectively.
Suggestions
Add concrete usage examples with sample platform/marketId values and expected output (e.g., `/features get binance BTC-USDT` with a sample JSON response).
Document what constitutes valid `platform` and `marketId` parameters, or explain how to discover them using `/features all`.
Add a brief workflow showing how to go from listing markets → getting features → interpreting signals, with guidance on what the signal recommendations mean.
Include example output formats so Claude knows how to present and interpret the returned data.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Reasonably lean but the opening sentence ('View real-time market features and trading signals computed from tick and orderbook data') is somewhat redundant given the command list already conveys the purpose. The introductory line adds minimal value. | 2 / 3 |
Actionability | The skill only lists command signatures with brief descriptions but provides no concrete examples of usage, expected output formats, parameter details (what is a valid platform or marketId?), or how to interpret results. It describes rather than instructs. | 1 / 3 |
Workflow Clarity | There is no workflow, sequencing, or guidance on how to use these commands together. No validation steps, no explanation of when to use which command, and no error handling guidance. | 1 / 3 |
Progressive Disclosure | The content is short and organized with a clear Commands section, but there are no references to additional documentation for advanced usage, signal interpretation, or parameter details that would clearly be needed. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- alsk1992/CloddsBot
- Commit
e71a5f6
- 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.