strategy
Build and manage custom trading strategies with natural language
51
40%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/strategy/SKILL.mdQuality
Discovery
22%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 lacks both concrete action details and explicit trigger guidance. It names a domain (trading strategies) but fails to enumerate specific capabilities or provide a 'Use when...' clause, making it difficult for Claude to reliably select this skill from a large pool.
Suggestions
Add a 'Use when...' clause with trigger terms like 'trading strategy', 'backtest', 'buy/sell signals', 'algo trading', 'portfolio optimization'.
List specific concrete actions such as 'define entry/exit rules, backtest strategies against historical data, optimize parameters, and generate performance reports'.
Include natural keyword variations users might say, such as 'quant strategy', 'automated trading', 'stock signals', or 'trading bot'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description is vague — 'build and manage custom trading strategies' does not list concrete actions like backtesting, placing orders, defining entry/exit rules, or analyzing performance. 'With natural language' describes the interface, not specific capabilities. | 1 / 3 |
Completeness | The description partially addresses 'what' (build and manage trading strategies) but is vague, and there is no 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | 'Trading strategies' is a relevant keyword users might say, but the description lacks common variations like 'backtest', 'algo trading', 'portfolio', 'buy/sell signals', 'quantitative strategy', or specific asset types. | 2 / 3 |
Distinctiveness Conflict Risk | 'Trading strategies' provides some domain specificity that distinguishes it from generic coding or document skills, but 'build and manage' is broad enough to overlap with general finance or investment-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at actionability with concrete, executable TypeScript examples and clear chat commands covering the full strategy lifecycle. However, it suffers from being a monolithic reference document that mixes quick-start guidance with detailed API reference, and it lacks an explicit end-to-end workflow with validation checkpoints—critical for a skill involving real financial trades. The content would benefit from splitting into overview + detailed reference files and adding a clear sequenced workflow with error handling.
Suggestions
Add an explicit end-to-end workflow section (e.g., '1. Create → 2. Validate → 3. Dry-run → 4. Review results → 5. If errors, fix and re-validate → 6. Only when validated, activate live') with clear validation checkpoints and error recovery, especially given the financial risk involved.
Split the detailed TypeScript API reference and condition types into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with quick-start examples and links to detailed docs.
Remove the 'Best Practices' section or reduce it to non-obvious, project-specific guidance—advice like 'set stop-losses' and 'monitor actively' is generic and doesn't add value for Claude.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is fairly well-organized but includes some redundancy (e.g., the 'Best Practices' section states obvious advice like 'set stop-losses' and 'monitor actively' that Claude would already know). The API reference is comprehensive but could be tightened—some code examples are verbose with console.log statements that don't add instructional value. | 2 / 3 |
Actionability | The skill provides fully concrete, executable TypeScript code examples and specific chat commands. Every feature is demonstrated with copy-paste ready code including imports, configuration objects, and complete function calls with realistic parameters. | 3 / 3 |
Workflow Clarity | There is an implicit workflow (create → validate → dry-run → activate live), and the activate section shows dry-run first then going live. However, for a skill involving real money trading, there are no explicit validation checkpoints, error recovery loops, or a clear sequenced workflow tying the steps together. The validate and activate sections are separate code blocks without a unified workflow. | 2 / 3 |
Progressive Disclosure | This is a monolithic document with everything inline—chat commands, full TypeScript API reference, templates table, condition types table, and best practices all in one file. The API reference section alone is extensive and would benefit from being split into separate files with clear navigation from a concise overview. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- alsk1992/CloddsBot
- Commit
e71a5f6
- 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.