smarkets

Smarkets Exchange betting with 2% commission

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/smarkets/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 reads more like a tagline than a functional skill description. It identifies the domain (Smarkets Exchange betting) but fails to describe any concrete actions the skill performs and completely lacks trigger guidance for when Claude should select it. The mention of '2% commission' is a detail but not a capability.

Suggestions

Add specific actions the skill performs, e.g., 'Places bets, checks odds, manages positions, and calculates potential returns on the Smarkets betting exchange.'

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to place bets, check market odds, or interact with the Smarkets exchange API.'

Include natural trigger terms users might say, such as 'betting odds', 'place a bet', 'sports markets', 'trading', 'Smarkets API', or 'exchange betting'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Smarkets Exchange betting') and mentions '2% commission' but does not describe any concrete actions or capabilities. There are no verbs indicating what the skill actually does.	1 / 3
Completeness	The description barely answers 'what does this do' (something related to Smarkets betting) and completely lacks any 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent.	1 / 3
Trigger Term Quality	It includes 'Smarkets', 'Exchange', 'betting', and 'commission' which are relevant keywords a user might mention, but it's missing common variations like 'place bets', 'odds', 'markets', 'trading', 'wager', or 'sports betting'.	2 / 3
Distinctiveness Conflict Risk	'Smarkets' is a specific platform name which helps distinguish it from generic betting skills, but the lack of specific actions means it could still overlap with other betting or exchange-related 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 Smarkets integration with clear, actionable command syntax and good use of tables. Its main weaknesses are the lack of validation/error-handling steps for financial trading operations and some unnecessary descriptive content (features list, market types) that doesn't help Claude execute tasks. Adding verification steps after order placement and trimming marketing-style content would significantly improve it.

Suggestions

Add validation/verification steps after trading commands (e.g., check order status after placement, verify balance before trading, confirm cancellation succeeded)

Remove or significantly trim the Features and Market Types sections—they describe Smarkets as a product rather than helping Claude execute commands

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

Dimension	Reasoning	Score
Conciseness	Mostly efficient but includes some unnecessary content like the Features bullet list (marketing-style info about market types that doesn't help Claude execute tasks) and the Market Types table which is descriptive rather than actionable. The opening sentence explaining what Smarkets is adds minimal value.	2 / 3
Actionability	Commands are concrete and copy-paste ready with clear parameter formats. Examples show exact syntax with inline comments explaining what each parameter means (e.g., '0.55 = 55% price, £10'). Configuration is explicit with environment variable names.	3 / 3
Workflow Clarity	The Quick Start provides a reasonable sequence (authenticate → search → get prices → trade), but there are no validation checkpoints for trading operations. No guidance on verifying order placement succeeded, checking fills, or handling errors—important for financial operations involving real money.	2 / 3
Progressive Disclosure	Content is reasonably organized with clear sections and tables, and external links to docs are provided. However, all content is inline in one file—the Features, Market Types, and detailed command tables could be split out if this were longer. For its current length (~80 lines of content), the structure is adequate but the market types and features sections add bulk without clear navigation benefit.	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.