polymarket

Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./configs/microservice/bff-service/configs/agent-skills/clawhub/polymarket-trade/SKILL.md

Quality

Content

65%

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 copy-paste commands throughout and avoids explaining concepts Claude already knows, but it suffers from redundancy between sections, a stray external link, and the absence of validation checkpoints in the paper-trading workflow. Tightening repetition and moving the large command catalog to a reference would improve the weaker dimensions.

Suggestions

Deduplicate the Quick Start and Commands sections so each command appears once, and remove the off-topic telegra.ph URL from the top of the body.

Add an explicit validation/error-recovery step for paper-trade mutations (e.g., check portfolio.json after buy/sell and surface a clear error on invalid slugs).

Move the full command catalog and cron examples into a reference file (e.g., COMMANDS.md) and keep SKILL.md as a concise overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command listings that assume Claude's competence, but the Quick Start section repeats the Commands section, a stray telegra.ph URL adds noise, and repeated "(NEW)" tags plus mojibake artifacts could be tightened.	2 / 3
Actionability	Provides abundant concrete, executable, copy-paste bash commands with real flags and arguments across every feature, matching the top anchor for fully executable guidance.	3 / 3
Workflow Clarity	A numbered setup sequence and cron examples give a clear order, but there are no explicit validation checkpoints or error-recovery feedback loops for the state-mutating paper-trade commands, leaving checkpoints implicit.	2 / 3
Progressive Disclosure	Sections are well organized and the single bundle script is referenced correctly, but the body is a monolithic command catalog that could be offloaded to a reference file, and an off-topic external URL is poorly signaled.	2 / 3
	Total	9 / 12 Passed

Description

67%

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, third-person, and clearly niched to Polymarket, but it omits an explicit "Use when..." trigger clause and offers only partial coverage of natural user phrasings. Adding explicit usage triggers and broader keyword variations would raise the two capped dimensions.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks about Polymarket odds, prediction-market prices, trending markets, or resolving events."

Broaden trigger terms with common variations users say: betting odds, election markets, crypto markets, "what are the odds on", market resolution.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Check odds, find trending markets, search events, track price movements" — matching the top anchor for naming several specific concrete actions.	3 / 3
Completeness	Clearly states what the skill does but has no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Includes relevant natural terms (odds, trending markets, events, price movements) but lacks common variations users would say (betting, election markets, "odds on"), so coverage is partial rather than comprehensive.	2 / 3
Distinctiveness Conflict Risk	Tightly scoped to Polymarket prediction markets with domain-specific triggers, making it clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: UnicomAI/wanwu
Path: configs/microservice/bff-service/configs/agent-skills/clawhub/polymarket-trade/SKILL.md
Commit: f618458

Reviewed: about 14 hours 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.