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 fails on all dimensions. 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, predicts price movements for stocks/crypto/commodities.'

Add an explicit 'Use when...' clause with natural trigger terms like 'trading', 'stock prediction', 'market forecast', 'price analysis', 'buy/sell signal'.

Remove the invocation syntax ('invoke with $agent-trading-predictor') from the description as 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', etc. are present.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it provides no clear niche. 'Trading-predictor' hints at a domain but without specifics, it could overlap with any trading, finance, or prediction-related skill.	1 / 3
	Total	4 / 12 Passed

Implementation

14%

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

This skill is excessively verbose, mixing vague conceptual descriptions with incomplete code examples across 200+ lines without any external file references or validation checkpoints. Much of the content describes concepts Claude already knows (financial metrics, risk management basics) or lists abstract capabilities without actionable instructions. The few code examples that exist rely on undefined helper functions, reducing their practical utility.

Suggestions

Cut the content by 60-70%: remove all explanatory bullet lists about well-known financial concepts (Sharpe Ratio, VaR, drawdown definitions) and marketing language, keeping only the MCP tool signatures and concrete usage examples.

Make code examples fully executable by replacing undefined functions like `connect_market_feeds()` and `calculate_temporal_lead()` with actual implementations or concrete MCP tool calls.

Add explicit validation and error-handling steps to workflows—especially for trade execution—including pre-trade validation, post-execution verification, and rollback procedures for failed trades.

Split detailed sections (Risk Management Framework, Performance Metrics, Integration Patterns) into separate referenced files, keeping SKILL.md as a concise overview with clear navigation links.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~200+ lines with extensive sections that describe concepts Claude already knows (Sharpe Ratio definitions, what VaR is, basic risk management concepts). Bullet-point lists of abstract descriptions like 'Latency Arbitrage', 'Market Making', and 'Performance Metrics' add no actionable value and waste tokens. The concluding sentence is pure marketing fluff.	1 / 3
Actionability	Contains some concrete code examples with specific MCP tool calls and parameters, which is useful. However, much of the code is pseudocode or incomplete (e.g., `connect_market_feeds()`, `calculate_temporal_lead()`, `generate_trading_signals()` are undefined functions). Many sections are purely descriptive bullet lists with no executable guidance.	2 / 3
Workflow Clarity	The 'Daily Trading Cycle' and 'Crisis Management' workflows are vague high-level descriptions with no concrete commands, validation steps, or feedback loops. For a system involving financial trading (destructive/high-risk operations), there are no explicit validation checkpoints, error recovery procedures, or verification steps anywhere in the skill.	1 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. All content is inline regardless of depth or relevance. Sections like 'Performance Metrics', 'Risk Management Framework', and 'Integration Patterns' could easily be split into separate reference files. No navigation structure or clear hierarchy for discovery.	1 / 3
	Total	5 / 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: f547cec

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.