CtrlK
BlogDocsLog inGet started
Tessl Logo

markets

Search and view prediction market data from Polymarket, Kalshi, Manifold, and Metaculus

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/markets/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 body is a concise, well-organized overview with concrete commands and clear example flows; its main gap is the lack of any executable mechanism (scripts or API calls) showing how Claude actually retrieves data from the named platforms.

Suggestions

Add a brief executable example or reference a script showing how to query at least one platform API (e.g., a curl call or a scripts/ helper) so the actionability is fully copy-paste ready.

Clarify how the slash commands map to underlying API calls, or note that the commands are handled by a bundled script.

If per-platform fetching logic differs, link to short per-platform reference notes under references/ rather than leaving the mechanism implicit.

DimensionReasoningScore

Conciseness

The body is lean with terse command listings, compact platform one-liners, and example flows; it assumes Claude's competence and explains no background concepts, so every token earns its place.

5 / 5

Actionability

Commands like "/markets trump 2028", "/price [market-id or slug]", and "/orderbook [market-id]" are concrete and copy-pasteable, but the actual mechanism for fetching data from each platform's API is absent.

4 / 5

Workflow Clarity

This is a simple, read-only skill under 50 lines; the examples give unambiguous input-to-output flows (query -> search platform -> return price), so the simple-skill exception applies and the single action is clear.

5 / 5

Progressive Disclosure

No bundle files exist and the body is well under 50 lines with clean Commands, Supported Platforms, and Examples sections, satisfying the simple-skill exception for well-organized structure.

5 / 5

Total

19

/

20

Passed

Description

65%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 concise and distinct, naming concrete platforms and two core actions, but it omits any explicit "Use when..." trigger guidance and only lists two actions, which limits completeness and specificity.

Suggestions

Add a "Use when..." clause naming concrete triggers (e.g., "Use when the user asks about prediction markets, betting odds, or prices on Polymarket/Kalshi/Manifold/Metaculus").

Expand the action list beyond search and view to reflect full coverage (e.g., compare prices across platforms, view orderbooks, track price history).

Include natural synonyms such as "betting markets", "odds", and "forecast" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the prediction-market domain and two concrete actions ("Search and view prediction market data") but offers no broader action set, matching the anchor for 1-2 concrete actions.

3 / 5

Completeness

The "what" is clear but there is no "Use when..." trigger clause, so per the rubric a missing when-clause caps completeness at 3.

3 / 5

Trigger Term Quality

Concrete platform names (Polymarket, Kalshi, Manifold, Metaculus) plus "prediction market" give good keyword coverage, but natural synonyms like betting, odds, and forecast are missing.

4 / 5

Distinctiveness Conflict Risk

Naming four specific prediction-market platforms defines a clear, distinct niche with minimal conflict risk against other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
alsk1992/CloddsBot
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.