betfair

Betfair Exchange sports betting and trading

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/betfair/SKILL.md

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and well structured, with concrete copy-paste commands and clear tables. Its main weakness is workflow safety: order placement and bulk cancellation are destructive financial operations presented without any validation or confirmation checkpoints.

Suggestions

Add a validation step before placing orders, e.g. run '/bf balance' and '/bf prices <marketId>' to confirm funds and odds before '/bf back' or '/bf lay'.

For destructive/batch commands like '/bf cancelall', include an explicit confirmation or preview step in the workflow and note the financial risk.

Trim marketing fluff ('world's largest', the Features bullets) to tighten conciseness toward a lean score 5.

Dimension	Reasoning	Score
Conciseness	The body is largely lean command tables and copy-paste examples that assume Claude's competence, with only minor padding such as 'the world's largest sports betting exchange' and the marketing-style Features bullets ('Low Fees', 'Deep Liquidity'); this fits the score-4 anchor of efficient content with minor trimmable instances rather than the fully lean score 5.	4 / 5
Actionability	Commands are fully executable with concrete arguments (e.g. '/bf back 1.234 5678 2.0 10 # Back at 2.0 odds, £10 stake') and parameter tables cover the common cases, matching the score-5 anchor of copy-paste-ready commands with specific examples.	5 / 5
Workflow Clarity	The Quick Start gives a rough sequence (set credentials, search markets, get prices, place order) but lacks validation checkpoints, and because placing/cancelling orders and 'cancelall' are destructive/batch financial operations the rubric caps workflow clarity at 3; it cannot reach score 4 without explicit verification steps.	3 / 5
Progressive Disclosure	Content is well organized into clearly headed sections (Quick Start, Commands, Configuration, Event Types, Trading Notes, Resources) with no nested references and external links kept one level deep; at roughly 100 lines it slightly exceeds the under-50-line simple-skill exception, so it lands at score 4 (good structure, minor gaps) rather than 5.	4 / 5
	Total	16 / 20 Passed

Description

48%Weight 40%Scale 1-5

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 is concise and clearly identifies the Betfair Exchange niche, but it is too terse: it states no concrete actions and omits any 'Use when' trigger guidance. Adding specific capabilities and an explicit trigger clause would lift specificity and completeness.

Suggestions

Add concrete actions to the description, e.g. 'Search markets, view live prices, and place back/lay orders on Betfair Exchange'.

Append an explicit trigger clause such as 'Use when the user wants to trade or bet on Betfair Exchange markets, check odds, or place back/lay orders'.

Include natural synonyms users say ('odds', 'markets', 'back/lay') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Betfair Exchange sports betting and trading' names the domain but gives only generic activity nouns ('betting', 'trading') with no concrete actions like placing orders, viewing prices, or cancelling bets; this matches the score-2 anchor ('Names the domain but actions are minimal or generic') and falls below score 3, which requires 1-2 concrete actions.	2 / 5
Completeness	A clear 'what' is present (Betfair sports betting and trading) but there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3; it does not reach score 4, which requires an explicit 'when'.	3 / 5
Trigger Term Quality	Natural terms 'Betfair Exchange', 'sports betting', and 'trading' are present and would be said by users, but common variations like 'odds', 'markets', 'back/lay', or 'wagering' are missing, matching the score-3 anchor of some relevant keywords missing synonyms rather than the fuller coverage of score 4.	3 / 5
Distinctiveness Conflict Risk	Naming the specific 'Betfair Exchange' platform gives a clear niche with minimal conflict risk, but the absence of explicit trigger context keeps it just short of the score-5 anchor, landing at 'mostly distinct; minor overlap risk with closely related skills'.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alsk1992/CloddsBot
Path: src/skills/bundled/betfair/SKILL.md
Commit: 715fd4a

Reviewed: 4 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.