Tessl • The management layer for AI agent skills

Blog Docs Log inGet started

SkillPublic

execution

Execute trades on prediction markets with slippage protection and order management

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/execution/SKILL.md

Quality

Content

72%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 content is highly actionable with comprehensive executable TypeScript and chat-command examples and lean, well-sectioned prose, but it inlines a large API reference without any progressive disclosure into separate files and lacks an explicit validation-checkpoint workflow for its destructive, real-money order operations.

Suggestions

Split the TypeScript API Reference into a separate reference file (e.g. references/api.md) and keep only a quick-start plus key examples in SKILL.md, linking out for the full surface.

Add an explicit execution workflow with validation checkpoints (estimate slippage → place order → verify fill/status → handle rejection → reconcile), which is required given the destructive nature of live trading.

Move the time-sensitive "Polymarket (Verified Jan 2026)" fee note into a dedicated, clearly labeled fees/deprecated section so it does not penalize conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean tables and executable code with minimal conceptual padding, but it carries some redundancy (chat commands mirror the TS API) and a time-sensitive marker ("Polymarket (Verified Jan 2026)") not placed in a deprecated/old-patterns section, fitting anchor 4 "efficient; minor instances that could be trimmed."	4 / 5
Actionability	It provides fully executable, copy-paste-ready TypeScript covering limit/market/maker/protected orders, order management, and slippage estimation, plus concrete chat commands, with parameter values and return shapes shown — matching anchor 5 "fully executable; copy-paste ready; covers the common cases."	5 / 5
Workflow Clarity	Order execution is a destructive (real-money) and batch (cancel-all) operation, and while rejection handling and a Best Practices list are shown, there is no sequenced workflow with explicit validation checkpoints (e.g., place → verify fill → reconcile), so per the destructive-operation cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	There are no bundle files and no external references; the entire ~270-line API reference is inlined in SKILL.md with good section headers, but the bulk reference content that clearly belongs in a separate file is inline — matching anchor 3 "some structure but content that should be separate is inline."	3 / 5
	Total	15 / 20 Passed

Description

53%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 specific and distinct, naming the prediction-market trading domain and key features in third person, but it lacks any explicit "Use when" trigger guidance and omits the platform names users would naturally invoke. It is solid but incomplete rather than exemplary.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to place or manage trades on Polymarket or Kalshi, asks about prediction-market orders, or mentions slippage or maker rebates."

Name the supported platforms (Polymarket, Kalshi) and order types (limit, market, maker, protected) so trigger terms match what users actually say.

Expand coverage to mention order management and slippage estimation as distinct capabilities to lift specificity above a single verb.

Dimension	Reasoning	Score
Specificity	"Execute trades on prediction markets with slippage protection and order management" names the domain and a few concrete actions (execute trades, slippage protection, order management), but omits platforms (Polymarket/Kalshi), maker orders, and other capabilities, so it is not comprehensive — matching the anchor 3 "names domain and 1-2 concrete actions."	3 / 5
Completeness	The "what" is clear (execute trades with slippage protection and order management), but there is no "Use when..." clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3 — matching anchor 3 "clear 'what' but 'when' is missing."	3 / 5
Trigger Term Quality	It includes relevant keywords ("trades", "prediction markets", "slippage protection") a user might say, but misses common variations and platform names users actually use (Polymarket, Kalshi, betting markets, order placement), fitting anchor 3 "some relevant keywords but missing common variations or synonyms."	3 / 5
Distinctiveness Conflict Risk	"Execute trades on prediction markets" describes a clear, fairly specific niche with distinct triggers and only minor overlap risk with adjacent trading skills, fitting anchor 4 "mostly distinct; minor overlap risk with closely related skills."	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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/execution/SKILL.md
Revision: c930628

Reviewed: 1 month ago

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.

execution

Table of Contents

Is this your skill?