strategy
Build and manage custom trading strategies with natural language
68
56%
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
32%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 identifies a clear domain (trading strategies) but is too brief and lacks the explicit trigger guidance required for Claude to reliably select it. It needs concrete action details and a 'Use when...' clause to be effective in a multi-skill environment.
Suggestions
Add a 'Use when...' clause with trigger terms like 'trading bot', 'algo trading', 'backtest strategy', 'automated trading', or 'trading rules'
Expand specific capabilities beyond 'build and manage' - include actions like 'backtest strategies', 'set entry/exit rules', 'configure risk parameters', or 'analyze performance'
Include file types or platforms if applicable (e.g., 'works with .py strategy files' or 'integrates with broker APIs')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (trading strategies) and mentions two actions (build and manage), but lacks concrete specifics about what building or managing entails - no mention of backtesting, order types, risk parameters, or other specific capabilities. | 2 / 3 |
Completeness | Describes what (build/manage trading strategies) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains relevant keywords like 'trading strategies' and 'natural language', but misses common variations users might say such as 'algo trading', 'automated trading', 'trading bot', 'backtest', or 'portfolio'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'trading strategies' domain is fairly specific, but 'natural language' is vague and could overlap with other NLP or finance-related skills. Without explicit triggers, it could conflict with general finance or coding skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured API reference with excellent actionability and conciseness. The code examples are executable and comprehensive, covering chat commands, TypeScript APIs, and templates. However, it lacks a clear end-to-end workflow with validation checkpoints for deploying strategies safely, and the content could be better organized across multiple files for a reference of this size.
Suggestions
Add an explicit workflow section showing the complete create → validate → dry-run → fix errors → activate sequence with validation checkpoints
Consider splitting into separate files: SKILL.md (overview + quick start), TEMPLATES.md (template details), API-REFERENCE.md (full TypeScript API)
Add error handling examples showing what to do when validation fails or dry-run reveals issues
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting commands, code examples, and tables without unnecessary explanation. It assumes Claude understands trading concepts and TypeScript without over-explaining. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples that are copy-paste ready, concrete chat commands with clear syntax, and specific parameter examples for all templates and conditions. | 3 / 3 |
Workflow Clarity | While individual operations are clear, the overall workflow for creating and deploying a strategy lacks explicit validation checkpoints. The 'Best Practices' section mentions dry-run but doesn't integrate it into a clear sequential workflow with feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but it's a monolithic document that could benefit from splitting API reference, templates, and conditions into separate files. No references to external documentation for advanced topics. | 2 / 3 |
Total | 10 / 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
2a8c94e
- 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.