trading-wisdom

Core trading insights learned from Agent Arena competition. Use when making any trading decision to apply institutional knowledge.

Quality

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./data/skills-md/0xhubed/agent-trading-arena/trading-wisdom/SKILL.md

Quality

Discovery

17%

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 broad to be effective for skill selection. It fails to specify what concrete actions or insights the skill provides, relying on buzzwords like 'institutional knowledge' and 'core trading insights' without substance. The overly broad trigger ('any trading decision') would cause conflicts with other trading-related skills and provides no meaningful differentiation.

Suggestions

Replace 'core trading insights' with specific concrete actions the skill performs, e.g., 'Applies position sizing rules, risk/reward thresholds, and market regime detection strategies learned from Agent Arena competition.'

Narrow the 'Use when...' clause to specific trigger scenarios instead of 'any trading decision', e.g., 'Use when evaluating trade entries/exits, sizing positions, or assessing market conditions.'

Add natural trigger terms users would actually say, such as 'buy', 'sell', 'stop loss', 'take profit', 'portfolio allocation', or specific strategy names from the competition.

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'core trading insights' and 'institutional knowledge' without listing any concrete actions. It does not specify what the skill actually does (e.g., analyze positions, calculate risk, generate signals).	1 / 3
Completeness	It has a weak 'what' (trading insights) and does include a 'when' clause ('Use when making any trading decision'), but the 'what' is too vague to be useful and the 'when' is overly broad, making it only partially complete.	2 / 3
Trigger Term Quality	The terms 'trading decision' and 'institutional knowledge' are overly generic and not natural keywords a user would say. Missing specific terms like 'buy', 'sell', 'position sizing', 'risk management', 'market analysis', or any concrete trading vocabulary.	1 / 3
Distinctiveness Conflict Risk	'Any trading decision' is extremely broad and would conflict with any other trading-related skill. There is no clear niche or distinct trigger that separates this from other potential trading skills.	1 / 3
	Total	5 / 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 auto-generated data dump of trading observations rather than an actionable skill document. It suffers from extreme verbosity with heavily redundant entries (the same insight about zero-trade strategies appears 5+ times), provides no executable guidance or decision framework, and lacks any workflow structure that would help Claude make actual trading decisions. The content would benefit from radical condensation into a concise decision framework with clear rules.

Suggestions

Consolidate redundant patterns into a concise decision matrix: e.g., a table mapping market regime (bull/bear/flat) to recommended trade frequency and strategy, eliminating the 30+ repetitive entries

Add a concrete decision workflow: 1) Classify market regime → 2) Select strategy based on regime → 3) Apply entry/exit rules → 4) Validate risk parameters → 5) Execute or hold

Replace the flat list of patterns with actionable rules (e.g., 'IF moderate bull market AND no strong directional conviction THEN make 0 trades' rather than 5 separate observations about zero-trade strategies)

Move detailed historical evidence and per-agent analysis to a separate reference file, keeping only the synthesized rules in the main skill

Dimension	Reasoning	Score
Conciseness	Extremely verbose at 400+ lines with massive repetition. Many patterns say essentially the same thing (e.g., multiple near-identical 'zero-trade strategies preserve capital' entries, multiple 'avoid overtrading' entries). The content could be condensed to ~20% of its size without losing information. Claude doesn't need 40+ individually listed patterns with redundant metadata.	1 / 3
Actionability	The skill describes observations and historical outcomes but provides no concrete, executable guidance. There are no code examples, no specific commands, no decision trees or algorithms to follow. It reads as a post-hoc analysis report rather than actionable instructions for making trading decisions.	1 / 3
Workflow Clarity	There is no workflow, decision process, or sequenced steps. The content is a flat list of observations without any structured decision-making framework. A trading skill should have clear steps like: assess market regime → determine trade frequency → select assets → validate signals → execute. None of this exists.	1 / 3
Progressive Disclosure	The content is a monolithic wall of repetitive pattern entries with no hierarchical organization. All 206 patterns are dumped inline with identical formatting. There's no summary/detail split, no references to separate files for detailed analysis, and no logical grouping beyond 'Winning Strategies' vs 'Patterns to Avoid'.	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: NeverSight/skills_feed
Commit: 868a866

Reviewed: 5 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.