ai-strategy
AI Strategy - natural language to trades
43
30%
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
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 far too terse and vague to serve as an effective skill selector. It fails to enumerate concrete capabilities, lacks a 'Use when...' clause, and provides minimal trigger terms. While the trading domain gives it slight distinctiveness, the description needs substantial expansion to be functional.
Suggestions
Add specific concrete actions such as 'Parses natural language trade instructions, generates buy/sell orders, maps user intent to trading parameters'.
Include an explicit 'Use when...' clause, e.g., 'Use when the user wants to convert plain English instructions into trade orders, mentions buying/selling assets, or asks about executing trades'.
Add natural trigger term variations like 'trading', 'buy', 'sell', 'order', 'execute trade', 'portfolio', 'stock', 'position' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description is extremely vague. 'AI Strategy' and 'natural language to trades' hint at a domain but do not list any concrete actions like parsing orders, generating trade signals, or executing trades. | 1 / 3 |
Completeness | The description barely addresses 'what' (converting natural language to trades) and completely omits any 'when' guidance or explicit trigger clause. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also very weak, warranting a 1. | 1 / 3 |
Trigger Term Quality | It includes some relevant keywords like 'natural language', 'trades', and 'AI Strategy' that a user might mention, but it lacks common variations such as 'trading', 'orders', 'buy/sell', 'portfolio', or 'execute trades'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Natural language to trades' is somewhat specific to a trading/finance domain, which provides some distinctiveness, but 'AI Strategy' is generic enough to overlap with many AI-related skills, and the lack of detail increases conflict risk. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-structured command reference with good examples of natural language strategy descriptions, but it fundamentally lacks implementation guidance—there's no code, no parsing logic, no workflow for how strategies are created/validated/executed, and no error handling for failed trades. For a domain involving real financial transactions, the absence of validation steps and safety guardrails is a significant gap.
Suggestions
Add a clear multi-step workflow showing how a strategy is parsed, validated, confirmed with the user, and executed—including explicit validation checkpoints and error recovery for failed trades.
Include implementation code or concrete logic for parsing natural language into structured strategy objects (e.g., JSON schema for a strategy, parsing rules).
Add safety guardrails: confirmation prompts before execution, maximum trade size limits, validation of token addresses, and handling of insufficient balance or failed transactions.
Reduce redundancy by consolidating the Examples section into the Strategy Types section rather than listing similar examples twice.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy—strategy examples are repeated across the Commands/Examples section and the Strategy Types section. The Supported Tokens and Monitoring sections add minor padding but aren't egregious. | 2 / 3 |
Actionability | The skill provides concrete command syntax and many examples of natural language inputs, but lacks any implementation details—there's no code showing how strategies are parsed, stored, monitored, or executed. It reads more like a user-facing command reference than an actionable skill for Claude to implement the functionality. | 2 / 3 |
Workflow Clarity | There is no clear multi-step workflow for how a strategy goes from natural language input to execution. The monitoring section vaguely describes a pipeline but lacks validation checkpoints, error handling, or feedback loops—critical for financial operations involving real trades. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headers and a templates table, which aids navigation. However, everything is in a single file with no references to external files for detailed implementation, and the strategy types section is somewhat lengthy and could be split out. | 2 / 3 |
Total | 7 / 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.