CtrlK
BlogDocsLog inGet started
Tessl Logo

prediction-market-oracle-research

Research prediction markets as data sources or oracle signals for products, agents, dashboards, and corporate decision intelligence. Use for source-grounded analysis of market-implied probabilities, caveats, and integration patterns without investment advice. Use when evaluating prediction markets as a data source or oracle signal for a product, agent, or dashboard.

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-organized, token-efficient skill body that provides concrete research guidance and a defined output contract. It could push actionability to 5 with one or two executable examples of fetching/normalizing market-implied probabilities.

Suggestions

Add a brief executable snippet or named tool/API for retrieving and timestamping market-implied probabilities to lift actionability.

Make the signal-quality validation explicit as a checkpoint (e.g. 'halt and downgrade the signal if liquidity/spread fail thresholds') to strengthen the workflow's feedback loop.

DimensionReasoningScore

Conciseness

Lean and efficient throughout; assumes Claude's competence, never explains what prediction markets are, and every section (Guardrails, Workflow, Integration Patterns, Output Contract) earns its place.

5 / 5

Actionability

Concrete, specific guidance (a 6-step workflow with named signal-quality dimensions, defined integration patterns, and a fixed output contract), but as an instruction-only research skill it lacks copy-paste executable commands or data-fetch examples.

4 / 5

Workflow Clarity

A clearly sequenced 6-step research workflow with implicit checkpoints via the Guardrails and a synthesis/recommendation step; no explicit validate→fix→retry loop, though the research context is non-destructive so that cap does not apply.

4 / 5

Progressive Disclosure

A single-purpose skill organized into well-signaled sections with no need for external references and no bundle files; structure is clear and easy to navigate.

5 / 5

Total

18

/

20

Passed

Description

87%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 strong, well-scoped description that clearly states both capability and trigger conditions with good keyword coverage and a distinct niche. Slight room to broaden trigger-term synonyms and tighten the duplicated 'Use' phrasing.

Suggestions

Add natural synonyms users might say, e.g. 'forecasting markets' or 'betting markets', to broaden trigger coverage.

Consolidate the two 'Use for.../Use when...' clauses to avoid redundancy while preserving the explicit trigger.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Research prediction markets as data sources or oracle signals', 'source-grounded analysis of market-implied probabilities, caveats, and integration patterns') with minor gaps; not quite the comprehensive multi-action coverage of a 5.

4 / 5

Completeness

Explicitly answers both what ('Research prediction markets... source-grounded analysis of market-implied probabilities, caveats, and integration patterns') and when ('Use when evaluating prediction markets as a data source or oracle signal...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good coverage of natural terms ('prediction markets', 'data source', 'oracle signal', 'product, agent, or dashboard') including synonyms, though common variants like 'forecasting' or 'betting markets' are absent.

4 / 5

Distinctiveness Conflict Risk

A clear niche (prediction-market oracle research) with distinct triggers and minimal conflict risk; the body even boundary-flags the related llm-trading-agent-security skill.

5 / 5

Total

18

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.