execution

Execute trades on prediction markets with slippage protection and order management

Quality

48%

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

Quality

Discovery

40%

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 identifies a clear niche (prediction market trading) which makes it distinctive, but it lacks a 'Use when...' clause and could benefit from more specific action verbs and natural trigger terms users would employ. The domain specificity is its strongest asset, but the absence of explicit trigger guidance significantly weakens its utility for skill selection.

Suggestions

Add a 'Use when...' clause with trigger terms like 'Use when the user wants to place bets, buy/sell shares on prediction markets, check positions, or manage orders on platforms like Polymarket or Manifold.'

Include more natural user-facing keywords such as 'bet', 'wager', 'buy shares', 'sell shares', 'positions', 'Polymarket', 'Manifold', and 'market odds'.

List more specific concrete actions such as 'place buy/sell orders, set limit prices, check open positions, cancel pending orders, and calculate expected returns'.

Dimension	Reasoning	Score
Specificity	Names the domain (prediction markets) and some actions (execute trades, slippage protection, order management), but doesn't list multiple concrete specific actions like placing limit orders, canceling orders, checking balances, or specifying which prediction market platforms.	2 / 3
Completeness	Describes what the skill does (execute trades with slippage protection and order management) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also only moderately detailed, warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant terms like 'trades', 'prediction markets', 'slippage', and 'order management', but misses common user variations like 'bet', 'wager', 'Polymarket', 'Manifold', 'buy shares', 'sell shares', 'positions', or 'portfolio'.	2 / 3
Distinctiveness Conflict Risk	Prediction markets with slippage protection and order management is a very specific niche that is unlikely to conflict with other skills. The combination of 'prediction markets' and 'trades' creates a clear, distinct trigger profile.	3 / 3
	Total	8 / 12 Passed

Implementation

57%

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

The skill excels at actionability with concrete, executable code examples and clear chat commands. However, it suffers from being a monolithic reference document rather than a well-structured skill file—the full API reference should be split into separate files with SKILL.md serving as an overview. The workflow for trade execution (a financially consequential operation) lacks explicit validation checkpoints and error recovery flows.

Suggestions

Split the detailed TypeScript API reference into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with quick-start examples and links to detailed docs.

Add an explicit trade execution workflow with validation checkpoints: estimate slippage → validate parameters → place order → confirm fill → handle partial fills/rejections.

Reduce repetitive buy/sell pattern examples—show one complete example and note that sell variants follow the same pattern with the obvious method name change.

Add error handling guidance for common failure modes (insufficient balance, API timeouts, rejected maker orders) as part of the workflow.

Dimension	Reasoning	Score
Conciseness	The content is fairly comprehensive but overly verbose for a skill file. The extensive API reference with numerous console.log examples and repetitive patterns (buy/sell variants shown separately when the pattern is obvious) inflates token count. Much of this would be better in a separate REFERENCE.md.	2 / 3
Actionability	The skill provides fully executable TypeScript code examples with complete import paths, configuration objects, and concrete method calls. Chat commands are copy-paste ready with clear parameter syntax. Every operation has a concrete, runnable example.	3 / 3
Workflow Clarity	While individual operations are clear, there's no explicit workflow for the multi-step process of estimating slippage → placing order → verifying fill → handling failures. The protected order example shows a basic check, but there's no comprehensive error recovery flow or validation checklist for trade execution, which is a destructive/financial operation.	2 / 3
Progressive Disclosure	The entire API reference, all order types, fee structures, and best practices are crammed into a single monolithic file. This content would benefit greatly from splitting the detailed TypeScript API reference into a separate file, keeping SKILL.md as a concise overview with links to detailed docs.	1 / 3
	Total	8 / 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.