prediction-markets-dome

Prediction markets data - Polymarket, Kalshi markets, prices, positions, and trades

Quality

63%

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 ./skills/research-tools/capabilities/prediction-markets-dome/SKILL.md

Quality

Content

71%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 a well-structured, fully executable API reference with copy-paste-ready curl examples and a clear setup prerequisite, though it is verbose due to a redundant Capabilities list and inlines all endpoint specs rather than offloading them to reference files. It serves its read-only single-purpose role effectively.

Suggestions

Remove the '## Capabilities' bullet list (or shrink it to a short one-line summary) since every entry is repeated verbatim under its Usage subsection.

Disambiguate duplicate headers (two 'Market Price', 'Orderbook History', 'Trade History', 'Markets') by suffixing the platform, e.g. 'Market Price (Polymarket)' vs 'Market Price (Kalshi)'.

Move the bulk per-endpoint reference into a references/ file (e.g. ENDPOINTS.md) and keep SKILL.md as an overview + setup + key examples, adding a short error-handling note for common HTTP status codes.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows (no 'what is a prediction market' padding) and uses dense reference format, but the '## Capabilities' list duplicates every endpoint's one-line description that is then repeated verbatim under each Usage subsection, which is unnecessary padding that could be trimmed.	3 / 5
Actionability	Every endpoint provides a copy-paste-ready curl command with real auth headers, correct path, and a concrete example query (e.g. {"search":"election"}, {"currency":"btcusdt"}), and parameters are fully specified with types, defaults, and limits, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	Setup is clearly sequenced with an explicit validation/fallback ('If ~/.gooseworks/credentials.json does not exist, tell the user to run npx gooseworks login') and each endpoint is a single unambiguous curl call, but there is no per-call error/recovery guidance (e.g. 401 handling), leaving a minor validation gap below a 5.	4 / 5
Progressive Disclosure	There is some structure (a Capabilities TOC, Use Cases, and a Discover More pointer to a live /search endpoint), but all 16 full endpoint specifications are inlined in SKILL.md rather than split into separate reference files, fitting 'content that should be separate is inline' at 3.	3 / 5
	Total	15 / 20 Passed

Description

56%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 clearly identifies a niche (Polymarket/Kalshi prediction market data) with strong trigger terms, but it lacks any concrete action verbs and omits an explicit 'Use when' trigger clause, capping specificity and completeness. Adding a verb-led capability statement and a trigger clause would move it toward the top anchors.

Suggestions

Lead with concrete verbs, e.g. 'Fetches prediction market data — prices, orderbooks, positions, and trades from Polymarket and Kalshi.'

Add an explicit trigger clause, e.g. 'Use when the user asks about prediction markets, Polymarket or Kalshi prices/positions/trades, or cross-platform market data.'

Include common synonyms/extensions (e.g. 'prediction markets, market sentiment, PnL') to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and data nouns ('Polymarket, Kalshi markets, prices, positions, and trades') but contains no concrete verbs or actions, so it falls below the '1-2 concrete actions' anchor at 3 and matches 'Names the domain but actions are minimal or generic' at 2.	2 / 5
Completeness	It gives a reasonably clear 'what' (prediction market data access) but has no 'Use when...' trigger clause, so per the missing-trigger guidance completeness is capped at 3 with the 'when' only weakly implied.	3 / 5
Trigger Term Quality	It includes strong natural keywords users would actually say — 'Polymarket', 'Kalshi', 'prices', 'positions', 'trades' — giving good coverage of platform names and data types, though it lacks synonyms and broader variations needed for a 5.	4 / 5
Distinctiveness Conflict Risk	Naming two specific platforms (Polymarket, Kalshi) creates a distinct niche with minimal conflict risk, but the generic nouns 'prices, trades' create minor overlap with general crypto-trading skills, keeping it just below a 5.	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: gooseworks-ai/goose-skills
Path: skills/research-tools/capabilities/prediction-markets-dome/SKILL.md
Commit: 2523432

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