execution

Execute trades on prediction markets with slippage protection and order management

Quality

59%

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 domain (prediction market trading) with some specific features but lacks explicit trigger guidance, which is critical for skill selection. The 'what' is reasonably defined but the 'when' is entirely missing, and trigger terms could be expanded to include more natural user language.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to place bets on prediction markets, buy/sell shares on Polymarket or Manifold, or manage existing market positions.'

Include more natural trigger terms users would say: 'bet', 'wager', 'Polymarket', 'Manifold', 'buy shares', 'sell shares', 'market odds'

Expand specific actions to include: placing limit/market orders, checking positions, viewing order history, canceling pending orders

Dimension	Reasoning	Score
Specificity	Names the domain (prediction markets) and some actions (execute trades, slippage protection, order management), but doesn't list comprehensive specific actions like placing limit orders, checking positions, or canceling orders.	2 / 3
Completeness	Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	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', or 'buy/sell shares'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'prediction markets' with 'slippage protection' and 'order management' creates a clear, distinct niche that is unlikely to conflict with general trading or betting skills.	3 / 3
	Total	8 / 12 Passed

Implementation

79%

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 API reference with excellent actionability and conciseness. The code examples are complete and executable, and the tables efficiently convey structured information. However, it lacks explicit workflow guidance for safe trading operations (e.g., pre-trade validation, error recovery) and could benefit from splitting detailed API reference into a separate file.

Suggestions

Add a workflow section showing the recommended sequence for safe trade execution: check balance → estimate slippage → place order → verify fill → log result

Include error handling examples showing how to recover from common failures (insufficient funds, order rejected, network timeout)

Consider moving the detailed TypeScript API reference to a separate REFERENCE.md file, keeping SKILL.md as a quick-start overview with chat commands

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, using tables for structured data, minimal prose, and letting code examples speak for themselves. No unnecessary explanations of concepts Claude would already know.	3 / 3
Actionability	Provides fully executable TypeScript code examples that are copy-paste ready, concrete chat commands with exact syntax, and specific parameter values. Every API method has a working example.	3 / 3
Workflow Clarity	While individual operations are clear, there's no explicit workflow for multi-step trading processes. Missing validation checkpoints for risky operations like checking account balance before trades, or verifying order placement succeeded before proceeding.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections and tables, but it's a monolithic file (~200 lines) that could benefit from splitting API reference into a separate file. No references to external documentation for advanced topics.	2 / 3
	Total	10 / 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: 2a8c94e

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