CtrlK
BlogDocsLog inGet started
Tessl Logo

smarkets

Smarkets Exchange betting with 2% commission

68

Quality

55%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/smarkets/SKILL.md
SKILL.md
Quality
Evals
Security

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 severely underdeveloped, functioning more as a label than a useful skill description. It identifies the platform and a commission detail but fails to explain what actions the skill performs or when Claude should select it. The 2% commission detail is irrelevant for skill selection purposes.

Suggestions

Add specific actions the skill performs (e.g., 'Place bets, check market odds, view open positions, calculate potential returns on Smarkets Exchange').

Add an explicit 'Use when...' clause with trigger terms like 'Smarkets', 'betting exchange', 'place a bet', 'check odds', 'sports markets'.

Include common user phrases and file types/formats if applicable to improve trigger term coverage.

DimensionReasoningScore

Specificity

The description only names the platform and commission rate but provides no concrete actions. It doesn't describe what the skill actually does (e.g., place bets, check odds, manage positions).

1 / 3

Completeness

Missing both 'what does this do' (no actions described) and 'when should Claude use it' (no explicit trigger guidance or 'Use when...' clause).

1 / 3

Trigger Term Quality

Contains 'Smarkets', 'Exchange', and 'betting' which are relevant keywords users might say, but misses common variations like 'odds', 'wager', 'sports betting', 'markets', or 'trading'.

2 / 3

Distinctiveness Conflict Risk

'Smarkets' is a specific platform name which helps distinguish it, but 'Exchange betting' is generic enough to potentially conflict with other betting exchange skills (e.g., Betfair).

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, concise skill that provides clear, actionable commands for Smarkets integration. The main weakness is the lack of validation/verification workflows for trading operations - there's no guidance on confirming orders were placed successfully, handling errors, or verifying account state after trades. For a financial trading skill, explicit feedback loops would improve safety.

Suggestions

Add a validation workflow section showing how to verify order placement succeeded (e.g., check /sm orders after placing, confirm balance changes)

Include error handling guidance - what to do if an order fails, how to check order status, common error scenarios

DimensionReasoningScore

Conciseness

The content is lean and efficient, presenting commands in tables without unnecessary explanation. It assumes Claude understands exchange betting concepts and doesn't waste tokens explaining what a betting exchange is or how percentages work.

3 / 3

Actionability

Provides fully executable commands with concrete examples including specific parameters. The Quick Start section and command examples are copy-paste ready with clear parameter explanations.

3 / 3

Workflow Clarity

Commands are clearly listed but there's no validation workflow for trading operations. Missing feedback loops for order confirmation, error handling, or verification steps after placing bets - important for financial operations.

2 / 3

Progressive Disclosure

Well-organized with clear sections (Quick Start, Commands, Configuration, Features). Content is appropriately structured for a single skill file with external links to official documentation for deeper reference.

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
alsk1992/CloddsBot
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.