CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

forecast-os-lite

Look up live prediction-market odds from Polymarket, Kalshi, and Precog, plus upcoming Precog launchpad proposals (not live, no odds), read-only. Use whenever the user asks the odds, probability, or likelihood of a future event (elections, Fed and rate decisions, crypto prices, sports, geopolitics, "will X happen by Y", "what does the market think"), wants to compare platforms, or wants upcoming markets, even if they never say "prediction market." Not for quotes, trades, funding, claims, or market creation; redirect those to forecast-os.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%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.

An exceptionally actionable, well-sequenced read-only API skill with copy-paste commands, explicit validation gates, and thorough failure handling. Its weaknesses are structural: the read-only boundary and Precog search semantics are duplicated across sections, and the per-platform API reference bulk is inlined in SKILL.md instead of being split into one-level-deep reference files.

Suggestions

State the read-only/redirect boundary once (e.g., in Redirects) and reference it from 'Do not use for', 'Quote boundary', and 'Done when' instead of restating it in each section.

Explain the Precog `search` substring-filter semantics once and link the launchpad section to it, rather than duplicating the explanation in both Precog sections.

Move the per-platform endpoint, field, and filter detail for Polymarket, Kalshi, and Precog into references/<platform>.md files, keeping SKILL.md as an overview with one-line pointers, so the ~375-line body shrinks to a navigable core.

DimensionReasoningScore

Conciseness

Mostly dense, operational content that earns its tokens (exact curl commands, field lists, filter rules), but there is real redundancy: the read-only/redirect boundary is restated across "Do not use for", "Quote boundary", "Redirects", and "Done when"; the redirect wording appears twice nearly verbatim; and the Precog `search` substring-filter semantics are explained identically in both the markets and launchpad sections. The intro also spends lines explaining what a prediction market price means. This fits anchor 3 (mostly efficient but could be tightened) better than anchor 4, where over-explanation would be only minor.

3 / 5

Actionability

Fully executable throughout: copy-paste curl commands for every endpoint on all three platforms, exact response field names and filter values (`closed == false`, `status == "active"`, `status=OPEN`), fallback strategies (Kalshi open-events pagination, omitting Precog `search`), the freshness command `date -u +%Y-%m-%dT%H:%MZ`, and a worked output table example. Placeholders like `<query>` are appropriate parameterization, not pseudocode.

5 / 5

Workflow Clarity

The numbered Workflow (determine platforms → preflight → fetch → filter via Search quality gates → extract listed fields → report) is explicitly sequenced with validation checkpoints: Preflight catches blocked networks before they masquerade as "no market found", Search quality verifies entity/year/resolution match before showing a market, Failures defines per-error recovery (429/401/403 stop, continue with other platforms, never invent probabilities), and "Done when" acts as a completion checklist. This matches the anchor-5 pattern of explicit validation, error-recovery feedback, and checklists; the skill is read-only so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so everything lives in a single ~375-line SKILL.md. Section headers and internal organization are good, but roughly 200 lines of per-platform endpoint and field reference (Polymarket/Kalshi/Precog API detail) are inlined — the anchor-3 pattern of "content that should be separate is inline". It cannot reach anchor 4, which expects references to external material, and the under-50-lines simple-skill exception does not apply.

3 / 5

Total

16

/

20

Passed

Description

95%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.

A model description: concrete platform-specific capabilities, exhaustive natural trigger phrasing including verbatim user utterances, explicit when-to-use and when-not-to-use guidance, and clean separation from the sibling full skill. The only minor gap is that the 'what' compresses to a single look-up action rather than enumerating several distinct operations.

DimensionReasoningScore

Specificity

Concrete actions are named with their exact targets: "Look up live prediction-market odds from Polymarket, Kalshi, and Precog, plus upcoming Precog launchpad proposals (not live, no odds), read-only" names three platforms, the odds-lookup action, upcoming-proposal discovery, and the read-only constraint. It stops short of anchor 5 because the 'what' rests on essentially one verb (look up) applied to specific objects rather than multiple distinct concrete actions like extract/fill/merge/convert.

4 / 5

Completeness

Both halves are explicit: the 'what' ("Look up live prediction-market odds from Polymarket, Kalshi, and Precog, plus upcoming Precog launchpad proposals... read-only") and the 'when' ("Use whenever the user asks the odds, probability, or likelihood of a future event..., wants to compare platforms, or wants upcoming markets"). It even adds a negative scope boundary ("Not for quotes, trades, funding, claims, or market creation; redirect those to forecast-os"), exceeding the anchor-5 example's clarity.

5 / 5

Trigger Term Quality

Comprehensive natural-language coverage with synonyms and literal user utterances: "the odds, probability, or likelihood of a future event", "will X happen by Y", "what does the market think", plus domain examples (elections, Fed and rate decisions, crypto prices, sports, geopolitics) and the explicit note "even if they never say 'prediction market.'" This matches the anchor-5 example's breadth of natural terms and phrasing users would actually say.

5 / 5

Distinctiveness Conflict Risk

Clear niche (read-only prediction-market odds lookup) with minimal conflict risk: it distinguishes itself from the sibling full skill by name ("redirect those to forecast-os") and explicitly fences off the actions that belong to the other skill. Triggers (odds/probability/likelihood of future events) are specific enough that unrelated skills would not fire.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

precog-markets/forecast-os-lite

Path

SKILL.md

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.