agent-trading-predictor
Agent skill for trading-predictor - invoke with $agent-trading-predictor
35
0%
Does it follow best practices?
Impact
95%
3.27xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-trading-predictor/SKILL.mdQuality
Discovery
0%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 an extremely weak description that fails on every dimension. It provides no information about what the skill does, when to use it, or what user requests should trigger it. It reads as a placeholder rather than a functional description.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Analyzes market data, generates trading signals, and predicts price movements for stocks, crypto, or other financial instruments.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about trading predictions, market forecasts, price analysis, stock predictions, or financial modeling.'
Remove the invocation syntax ('invoke with $agent-trading-predictor') from the description since it wastes space that should be used for capability and trigger information.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for trading-predictor' is entirely vague and does not describe what the skill actually does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states it's an agent skill and how to invoke it, providing no functional or contextual information. | 1 / 3 |
Trigger Term Quality | The only potentially relevant term is 'trading-predictor', which is a tool name rather than a natural keyword a user would say. No natural language trigger terms like 'predict', 'stock', 'market', 'forecast', or 'trade' are included. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any trading, prediction, or financial analysis skill. The only distinguishing element is the invocation command, which doesn't help Claude select the right skill based on user intent. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an extremely verbose, largely non-actionable document that reads more like a marketing brochure for an algorithmic trading platform than an executable skill for Claude. The code examples reference undefined functions and variables, making them non-executable pseudocode. The bulk of the content consists of abstract bullet-point lists explaining financial concepts Claude already knows, with no validation steps, no error handling, and no concrete workflows.
Suggestions
Remove all explanatory content about financial concepts (VaR, Sharpe Ratio, market making, etc.) that Claude already knows, and reduce the document to only the specific MCP tool calls and their parameters.
Make code examples executable by defining all referenced variables and functions, or provide complete working examples with realistic sample data.
Add explicit validation and error-handling steps for trading workflows, especially around trade execution and risk limit checks (e.g., 'If VaR exceeds limit, halt trading and log reason').
Extract the Performance Metrics, Risk Management Framework, and Integration Patterns sections into separate reference files and link to them from a concise overview in SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~200+ lines with extensive sections explaining concepts Claude already knows (what Sharpe Ratio is, what VaR is, what market making is). Bullet-point lists of abstract concepts like 'Risk Management Framework' and 'Performance Metrics' add no actionable value and waste tokens. The marketing-style conclusion sentence is pure filler. | 1 / 3 |
Actionability | Despite containing code blocks, the code is largely pseudocode or non-executable (e.g., `connect_market_feeds()`, `calculate_temporal_lead()`, `generate_trading_signals()` are undefined functions). The MCP tool calls use `await` syntax that isn't standard JavaScript and the parameters reference undefined variables like `portfolioRiskMatrix` and `covarianceMatrix`. Most sections are abstract bullet-point descriptions rather than concrete instructions. | 1 / 3 |
Workflow Clarity | The 'Daily Trading Cycle' and 'Crisis Management' workflows are vague high-level descriptions with no concrete steps, no validation checkpoints, and no error recovery. Steps like 'Implement defensive trading strategies and risk controls' provide zero actionable guidance. No feedback loops or verification steps exist anywhere in the document. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files and no bundle files to support it. All content is inline regardless of depth or relevance. Sections like 'Performance Metrics', 'Risk Management Framework', and 'Integration Patterns' could be separate reference files but are dumped into the main skill file with only superficial organization. | 1 / 3 |
Total | 4 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- ruvnet/claude-flow
- Commit
9d4a9ea
- 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.