CtrlK
BlogDocsLog inGet started
Tessl Logo

trading-strategy

Use this skill for developing and evaluating trading strategies by synthesizing technical analysis, market sentiment, and risk management principles into actionable trading recommendations.

60

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./packages/tentacles/Agent/teams/simple_ai_evaluator_agents_team/resources/skills/summarization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

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

The content is a well-structured, actionable trading-strategy framework with concrete decision rules and a clear output schema. Its main weaknesses are token weight from generic best-practice/common-mistake lists Claude already knows and a lack of progressive disclosure via separate reference files.

Suggestions

Trim or move the 'Best Practices' and 'Common Mistakes to Avoid' sections into a separate reference file, keeping only non-obvious guidance inline to improve conciseness.

Add an explicit validation checkpoint in the workflow (e.g. 'Confirm the Strong Conviction checklist passes before issuing a BUY/SELL; otherwise default to HOLD') to strengthen feedback loops.

Split the detailed eval_note scale and position-sizing matrix into a referenced reference file so SKILL.md reads as an overview with one-level-deep navigation.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete decision rules and an output template, but the 'Best Practices' (10 items) and 'Common Mistakes to Avoid' (10 items) sections largely restate generic trading wisdom Claude already knows and could be trimmed.

3 / 5

Actionability

Provides concrete, actionable guidance including a numeric eval_note scale with specific ranges, a position-sizing matrix, entry/exit placement rules, and a copy-paste-ready JSON output schema, though some entry/exit guidance remains qualitative rather than executable.

4 / 5

Workflow Clarity

A clear numbered 1-8 sequence (synthesize -> resolve conflicts -> eval_note -> risk -> sizing -> entry/exit -> timeframes -> regime) is reinforced by a Strong Conviction checklist and Trade Rejection criteria that act as validation gates, but there are no explicit validate->fix->retry feedback loops.

4 / 5

Progressive Disclosure

The file is well-organized with clear headers, but at ~200 lines it is a single monolithic document with no external references; sections like the detailed eval_note scale, best practices, and common mistakes are inlined rather than split into one-level-deep reference files.

3 / 5

Total

14

/

20

Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, well-structured, and uses natural domain trigger terms with clear what/when guidance. It would benefit from more explicit user-utterance trigger phrases and broader synonym coverage to reach the top anchor.

Suggestions

Add concrete user-utterance trigger phrases, e.g. 'Use when the user asks for trade recommendations, entry/exit plans, or wants to synthesize multiple analyses into a trading decision.'

Broaden trigger term coverage with synonyms users actually say, such as 'stocks', 'positions', 'buy/sell signals', or 'trade setup'.

Decouple the actions into a clearer list so the breadth of capabilities reads as comprehensive rather than bundled.

DimensionReasoningScore

Specificity

Lists several concrete actions ('developing and evaluating trading strategies', 'synthesizing technical analysis, market sentiment, and risk management principles into actionable trading recommendations') rather than vague language, though the actions are bundled into one sentence rather than comprehensively enumerated.

4 / 5

Completeness

Provides a clear 'what' (synthesize analyses into actionable recommendations) and a 'when' via 'Use this skill for developing and evaluating trading strategies', but the when is activity-based rather than concrete user-utterance trigger phrases like 'when the user asks for X'.

4 / 5

Trigger Term Quality

Includes natural domain terms a user would say ('trading strategies', 'technical analysis', 'market sentiment', 'risk management', 'trading recommendations') with good coverage, but misses common synonyms and variations a user might phrase differently.

4 / 5

Distinctiveness Conflict Risk

Targets a fairly distinct niche (multi-signal trading strategy synthesis) with minimal conflict risk, though it could overlap with a pure technical-analysis or risk-management skill.

4 / 5

Total

16

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Drakkar-Software/OctoBot
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.