agent-trading-predictor

Agent skill for trading-predictor - invoke with $agent-trading-predictor

3.27x

Quality

Does it follow best practices?

Impact

95%

3.27x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-trading-predictor/SKILL.md

Quality

Discovery

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 provides virtually no useful information for skill selection. It reads as a placeholder or auto-generated stub, containing only the skill's invocation command without describing any capabilities, use cases, or trigger conditions. It fails on every dimension of the rubric.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Analyzes market data, generates trading signals, and predicts price movements for stocks and cryptocurrencies.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about trading predictions, stock forecasts, market analysis, price trends, or buy/sell signals.'

Remove the invocation command from the description (it belongs in usage instructions, not the description) and replace it with capability and trigger information.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for trading-predictor' is entirely vague and does not describe what the skill actually does.	1 / 3
Completeness	The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides an invocation command, which is not a substitute for either.	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. There are no natural trigger terms like 'trading', 'stock prediction', 'market analysis', etc.	1 / 3
Distinctiveness Conflict Risk	While the name 'trading-predictor' hints at a niche, the description is so vague that Claude cannot reliably distinguish when to use this skill versus any other agent skill or trading-related skill.	1 / 3
	Total	4 / 12 Passed

Implementation

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. It explains numerous concepts Claude already knows, provides pseudocode disguised as real code, lacks any validation or error-handling workflows despite dealing with high-risk financial operations, and dumps everything into a single monolithic file with no progressive disclosure.

Suggestions

Strip all conceptual explanations (what Sharpe Ratio is, what VaR is, etc.) and reduce to only the MCP tool signatures, their actual parameters, and concrete usage examples with real executable code.

Replace pseudocode functions like `connect_market_feeds()` and `calculate_temporal_lead()` with actual executable implementations or remove them entirely if they don't exist.

Add explicit validation checkpoints and error-handling feedback loops to trading workflows, especially given the high-risk nature of financial operations (e.g., validate temporal advantage before execution, verify trade confirmation, handle API failures).

Move reference material (performance metrics, risk framework, integration patterns) into separate bundle files and keep SKILL.md as a concise overview with clear pointers to those files.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~200+ lines with extensive sections that explain concepts Claude already knows (what Sharpe Ratio is, what VaR is, what market making is). Massive amounts of bullet-point descriptions that add no actionable value. The 'Performance Metrics', 'Risk Management Framework', and 'Advanced Trading Strategies' sections are pure padding with no executable guidance.	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 outside async contexts and reference tools/APIs without explaining actual parameters or return values. Nothing is copy-paste ready.	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. For a skill involving financial trading (destructive/high-risk operations), there are no verification steps, no feedback loops, and no concrete validation procedures.	1 / 3
Progressive Disclosure	Monolithic wall of text with no bundle files to reference. All content is inlined regardless of importance, with no clear hierarchy between essential quick-start information and advanced reference material. No external files are referenced, and the content that could be split (metrics, risk framework, integration patterns) bloats the main file.	1 / 3
	Total	4 / 12 Passed

Validation

100%

Warnings & errors only

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: d29d87f

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.