betfair

Betfair Exchange sports betting and trading

Quality

43%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/betfair/SKILL.md

Quality

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 extremely terse and lacks both concrete actions and explicit trigger guidance. While 'Betfair Exchange' provides some distinctiveness, the description fails to communicate what the skill actually does or when it should be selected. It reads more like a topic label than a functional skill description.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Places back/lay bets, monitors market prices, calculates profit/loss, retrieves odds from Betfair Exchange API.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Betfair, placing bets, exchange trading, odds analysis, or sports betting markets.'

Include common user-facing keywords and variations such as 'odds', 'lay bet', 'back bet', 'Betfair API', 'betting exchange', 'market prices', 'horse racing betting'.

Dimension	Reasoning	Score
Specificity	The description names a domain ('Betfair Exchange sports betting and trading') but lists no concrete actions. There are no verbs describing what the skill actually does—no 'place bets', 'analyze odds', 'monitor markets', etc.	1 / 3
Completeness	The description only vaguely hints at 'what' (sports betting and trading) with no specifics, and completely lacks any 'when' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	It includes some relevant keywords a user might say ('Betfair', 'sports betting', 'trading', 'Exchange'), but misses common variations like 'odds', 'lay', 'back', 'market', 'bet placement', 'betting strategy', or 'Betfair API'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Betfair Exchange' is fairly distinctive and unlikely to conflict with most other skills, but 'sports betting and trading' is broad enough that it could overlap with general sports or trading skills.	2 / 3
	Total	6 / 12 Passed

Implementation

64%

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 command reference for a Betfair Exchange integration with clear, actionable commands and good use of tables. Its main weaknesses are the lack of validation/error-handling workflows for financial operations and some unnecessary marketing-style content. The skill would benefit from explicit verification steps after placing orders and trimming promotional language.

Suggestions

Add validation steps after trading commands (e.g., verify order placement with `/bf orders`, check balance after trades) to create a proper feedback loop for financial operations.

Remove the Features section (marketing copy about 'Deep Liquidity', 'Low Fees') as it provides no actionable guidance for Claude.

Add error handling guidance: what to do if authentication fails, if an order is rejected, or if a market is suspended.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary content like the Features section (marketing-style bullet points about 'Low Fees', 'Deep Liquidity') and the introductory line explaining what Betfair Exchange is. The Event Types table and Trading Notes add moderate value but could be tighter. However, the command tables and examples are reasonably efficient.	2 / 3
Actionability	Commands are concrete and copy-paste ready with specific syntax patterns, parameter names, and realistic examples. The configuration section provides exact environment variable names and the quick start gives a clear executable sequence.	3 / 3
Workflow Clarity	The quick start provides a reasonable sequence (authenticate → search → price → trade), but there are no validation checkpoints for trading operations which involve real money. There's no guidance on verifying order placement succeeded, checking positions after trades, or handling errors—important for destructive financial operations.	2 / 3
Progressive Disclosure	Content is reasonably organized with clear sections and tables, but everything is in a single file. The Features section and some reference material (Event Types, Resources) could be separated. The external links at the bottom are helpful but the skill doesn't reference any companion files for advanced topics like streaming or error handling.	2 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

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: 11 days ago

Table of Contents

Discovery Implementation Validation

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.