Betfair Exchange sports betting and trading
68
55%
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/betfair/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 minimal to effectively guide skill selection. It identifies the domain (Betfair Exchange) but fails to specify concrete capabilities or provide any guidance on when Claude should select this skill. The description reads more like a category label than a functional skill description.
Suggestions
Add specific concrete actions like 'Place back/lay bets, check market odds, manage open positions, analyze betting history, calculate potential returns'
Include a 'Use when...' clause with trigger terms such as 'Use when the user mentions Betfair, betting exchange, laying bets, backing horses, sports odds, or trading positions'
Add common user terminology and file/data types like 'betting markets, horse racing, football odds, API integration, bet settlement'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names a domain ('Betfair Exchange sports betting and trading') without listing any concrete actions. It doesn't specify what operations can be performed like placing bets, analyzing odds, managing positions, etc. | 1 / 3 |
Completeness | The description only vaguely addresses 'what' (sports betting/trading) and completely lacks any 'when' guidance. There's no 'Use when...' clause or explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('Betfair', 'Exchange', 'sports betting', 'trading') that users might naturally say, but misses common variations like 'odds', 'lay', 'back', 'markets', 'horse racing', or specific bet types. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Betfair Exchange' specifically provides some distinctiveness from generic betting skills, but 'sports betting and trading' is broad enough to potentially overlap with other betting or trading-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
87%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 skill with excellent conciseness and actionability - commands are clear, examples are executable, and tables organize information efficiently. The main weakness is the lack of validation/verification workflows for trading operations that involve real money, which is a significant gap for financial operations where errors could be costly.
Suggestions
Add a validation workflow section showing how to verify order placement succeeded (e.g., check /bf orders after placing, verify balance changes)
Include error handling guidance for common failures like insufficient funds, market suspended, or invalid odds
Add a safety checklist or confirmation pattern before executing trades, especially for larger stakes
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting commands in tables without unnecessary explanation. It assumes Claude understands betting concepts and doesn't over-explain what back/lay means beyond the essential distinction. | 3 / 3 |
Actionability | Provides fully executable commands with concrete examples including real parameter formats. The command tables and bash examples are copy-paste ready with clear parameter ordering. | 3 / 3 |
Workflow Clarity | While individual commands are clear, there's no validation workflow for trading operations which involve real money. Missing confirmation steps, error handling guidance, or verification that orders executed correctly - important for financial operations. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from Quick Start to detailed commands to configuration. External resources are linked at the end. Content is appropriately sized for a single file without needing additional reference files. | 3 / 3 |
Total | 11 / 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 | |
2a8c94e
Table of Contents
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.