ai-strategy
AI Strategy - natural language to trades
56
39%
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/ai-strategy/SKILL.mdQuality
Discovery
0%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 critically underdeveloped and would be nearly impossible for Claude to correctly select from a pool of skills. It lacks concrete actions, natural trigger terms, explicit usage guidance, and distinctive identifiers. The phrase 'natural language to trades' is the only hint at functionality but remains too vague to be actionable.
Suggestions
Add specific concrete actions: e.g., 'Converts natural language trading instructions into executable trade orders, analyzes market sentiment, generates buy/sell signals'
Include a 'Use when...' clause with natural trigger terms: e.g., 'Use when the user wants to place trades, asks about buying/selling stocks, mentions trading strategies, or needs to convert trading ideas into orders'
Specify the domain more clearly: e.g., mention specific asset types (stocks, crypto, forex), platforms, or trading contexts to distinguish from other financial or AI skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description is extremely vague - 'natural language to trades' hints at a domain but provides no concrete actions. It doesn't specify what kind of trades, what processing occurs, or what outputs are produced. | 1 / 3 |
Completeness | Fails to answer both 'what' and 'when'. There is no 'Use when...' clause, no explicit triggers, and the capability description is too vague to understand what the skill actually does. | 1 / 3 |
Trigger Term Quality | Contains only generic terms 'AI Strategy' and 'trades' without natural user keywords. Missing terms users would actually say like 'trading', 'buy', 'sell', 'stock', 'execute order', 'trading strategy', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'AI Strategy' is extremely generic and could conflict with any AI-related skill. 'Natural language to trades' is slightly more specific but still ambiguous - could overlap with financial analysis, trading bots, or NLP skills. | 1 / 3 |
Total | 4 / 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 skill excels at conciseness and actionability with clear, executable command examples covering multiple strategy types. However, it lacks validation checkpoints and error handling guidance for what are potentially high-stakes financial operations. The absence of feedback loops for trade execution and strategy monitoring is a notable gap.
Suggestions
Add validation/confirmation steps after strategy creation (e.g., '/strategy status <id>' to verify strategy was created correctly before it executes)
Include error handling guidance: what happens if a trade fails, how to retry, and how to verify execution
Add a section on common pitfalls or warnings (e.g., slippage, insufficient balance, token liquidity issues)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, presenting commands and examples without explaining what trading strategies are or how DCA works. Every section adds actionable value without padding. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready command examples for every strategy type. The examples are specific with actual values ($100, 5%, 24 hours) rather than abstract placeholders. | 3 / 3 |
Workflow Clarity | While commands are clear, there's no validation or error handling guidance. Missing feedback loops for failed trades, no mention of what happens if conditions aren't met, and no verification steps after strategy creation. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is inline in one file. Templates table could link to detailed template documentation, and monitoring section could reference a more detailed guide for complex scenarios. | 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.