markets
Search and view prediction market data from Polymarket, Kalshi, Manifold, and Metaculus
71
63%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/markets/SKILL.mdQuality
Discovery
54%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 effectively identifies a clear niche with excellent platform-specific trigger terms that users would naturally mention. However, it lacks explicit 'when to use' guidance and could benefit from more specific capability descriptions beyond just 'search and view'. The strong platform names provide good distinctiveness but the missing trigger clause significantly weakens its completeness.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when the user asks about prediction markets, betting odds, forecasts, or mentions Polymarket, Kalshi, Manifold, or Metaculus'
Expand specific capabilities beyond 'search and view' - e.g., 'compare odds across platforms, track market movements, view trading volume, analyze probability estimates'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (prediction markets) and two actions ('search' and 'view'), but doesn't elaborate on specific capabilities like filtering, comparing odds, tracking positions, or analyzing market trends. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Includes excellent natural keywords users would say: 'prediction market', 'Polymarket', 'Kalshi', 'Manifold', 'Metaculus' - these are the exact platform names and domain terms users would mention when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche - prediction markets with specific platform names (Polymarket, Kalshi, Manifold, Metaculus) make this highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is concise and well-structured for its scope, with clear command syntax and platform coverage. However, it lacks implementation details - the commands appear to be custom slash commands but there's no indication of what tool/API actually executes them, making it unclear how Claude should fulfill these requests in practice.
Suggestions
Add concrete implementation details showing how to actually query each platform's API or what MCP tool to invoke for these commands
Include example API responses or output formats so Claude knows what data structure to expect and present to users
Add error handling guidance for common cases like market not found, platform unavailable, or ambiguous search results
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, with no unnecessary explanations. It assumes Claude knows what prediction markets are and jumps straight to actionable commands and platform descriptions. | 3 / 3 |
Actionability | Provides command syntax examples but lacks implementation details. The commands (/markets, /price, /orderbook) are shown but there's no actual code or API calls demonstrating how to execute these searches or retrieve data. | 2 / 3 |
Workflow Clarity | The examples section shows user intent → action mapping, but there's no clear workflow for multi-step processes like comparing across platforms. No validation or error handling guidance for failed searches or unavailable markets. | 2 / 3 |
Progressive Disclosure | For a simple skill under 50 lines, the content is well-organized with clear sections (Commands, Supported Platforms, Examples). No need for external references given the scope. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%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
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.