CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

smarkets

Smarkets Exchange betting with 2% commission

55

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/smarkets/SKILL.md
SKILL.md
Quality
Evals
Security

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 with concrete, copy-paste commands and clean organization, but trading workflows lack validation/verification checkpoints for money-moving and batch operations. Adding pre-trade confirmation and post-order verification would resolve the main gap.

Suggestions

Add an explicit validation checkpoint before placing orders, e.g. require checking '/sm balance' and confirming the price/quantity with the user before '/sm buy' or '/sm sell'.

Document a verify step after orders (e.g. '/sm orders <marketId>' to confirm the order was accepted and is open).

Add a warning/cap note for '/sm cancelall' prompting confirmation before batch cancellation of all orders.

DimensionReasoningScore

Conciseness

The body is mostly lean with command tables and commented examples and no padding of Claude-known concepts, though the intro and Features bullets carry mild promotional framing that could be trimmed, fitting 'efficient; minor over-explanation' rather than the 5.

4 / 5

Actionability

Commands are concrete and copy-paste ready with worked examples (e.g. '/sm buy 123 456 0.55 10') covering the common cases of search, pricing, buy, sell, and cancel, matching the 'fully executable; copy-paste ready' anchor.

5 / 5

Workflow Clarity

Quick Start gives a rough sequence (set token -> search -> prices -> buy/sell) but the skill performs destructive/batch operations (placing money orders, cancelall) with no validation or verification checkpoints, so workflow clarity is capped at 3 per the destructive-operations rule.

3 / 5

Progressive Disclosure

The skill is a single self-contained file with well-organized sections (Quick Start, Commands, Configuration, Market Types) and no nested references, but at ~107 lines it is slightly long for one file, fitting 'good structure; minor organization gaps' rather than the 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 names a distinct niche but lacks concrete actions and any 'Use when' trigger guidance, capping completeness. Adding specific capabilities and a trigger clause would lift specificity and completeness.

Suggestions

Add 2-3 concrete actions, e.g. 'Search markets, view live prices, and place buy/sell orders on the Smarkets exchange at 2% commission.'

Append an explicit trigger clause such as 'Use when the user wants to trade or check odds on Smarkets, or mentions betting exchanges.'

Include natural synonyms (odds, wagers, sports betting) alongside 'betting' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Smarkets Exchange betting') and a commission detail but lists no concrete actions (no search/place orders/view prices), matching the 'names domain but actions minimal' anchor rather than the 3 which requires 1-2 concrete actions.

2 / 5

Completeness

The description gives a clear 'what' (Smarkets betting at 2% commission) but no 'when'/Use-when trigger guidance, so per the missing-trigger cap it cannot exceed 3.

3 / 5

Trigger Term Quality

'betting' and 'exchange' are natural user terms and 'Smarkets' is a specific brand keyword, but common synonyms like odds, wagers, or sports betting are missing, fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The named brand 'Smarkets Exchange' is a distinct niche with low conflict risk, but the generic term 'betting' leaves minor overlap with other gambling skills, fitting 'mostly distinct; minor overlap risk' rather than the 5.

4 / 5

Total

12

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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/smarkets/SKILL.md

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.