CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research

Research prediction markets - base rates, resolution rules, historical data

54

Quality

68%

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

Fix and improve this skill with Tessl

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

Quality

Content

61%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 concise and well-structured with useful command and output templates, but it stops at illustrative patterns rather than executable retrieval guidance and lacks a sequenced workflow with validation. Providing real data-source access and a stepped research process would lift actionability and workflow clarity.

Suggestions

Add concrete, executable data-retrieval steps or scripts for base-rate lookups (e.g., specific datasets, APIs, or commands to fetch FEC/Cook data) rather than only command-syntax templates.

Define a sequenced research workflow with explicit checkpoints (gather sources → compute base rate → cross-check resolution rules → cite sources) instead of a flat reference layout.

Move the worked Output Format example into a references/ file or trim it to a compact schema so the main body stays a lean overview.

DimensionReasoningScore

Conciseness

Lean, well-organized content with no over-explanation of concepts Claude already knows; only minor padding in the worked output-format example keeps it just below anchor 5.

4 / 5

Actionability

Provides command-syntax templates and an output template, but no executable code, real data-retrieval steps, or concrete source access — guidance is pattern-level rather than copy-paste ready, matching anchor 3.

3 / 5

Workflow Clarity

Content is a sectioned reference (Commands, Research Areas, Examples, Output Format) rather than a sequenced workflow, with no validation checkpoints; anchor 3 fits the present-but-checkpoints-missing case.

3 / 5

Progressive Disclosure

Single self-contained file with no bundle files present and clear section headers; slightly over 50 lines and with examples inlined that could be split out, fitting anchor 4 rather than 5.

4 / 5

Total

14

/

20

Passed

Description

61%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 and several concrete research deliverables with natural trigger terms, but lacks an explicit 'when to use' clause and leans on a single generic verb. Adding a trigger phrase and more action verbs would raise completeness and specificity.

Suggestions

Add an explicit 'Use when...' clause naming prediction-market research triggers (e.g., 'Use when the user asks about prediction-market base rates, resolution criteria, or historical analogs').

Replace the single generic verb 'Research' with concrete action verbs (e.g., 'Look up base rates, parse resolution rules, find historical analogs for prediction markets').

Include common user synonyms/platforms (Polymarket, Kalshi, odds, betting markets) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the prediction-markets domain plus three concrete deliverable areas ('base rates, resolution rules, historical data'), but uses only one generic verb ('Research') with topic nouns rather than distinct actions, matching anchor 3.

3 / 5

Completeness

Has a clear 'what' but no 'Use when...' or equivalent explicit trigger clause; per the judging guidelines a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural domain terms a user would say ('prediction markets', 'base rates', 'resolution rules', 'historical data'), but misses common synonyms/platforms like 'Polymarket', 'Kalshi', 'odds', or 'betting', fitting anchor 4.

4 / 5

Distinctiveness Conflict Risk

'prediction markets' is a clear niche with distinct triggers, but the bare verb 'Research' creates minor overlap risk with a general research skill, matching anchor 4.

4 / 5

Total

14

/

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.

Validation — 15 / 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

Path

src/skills/bundled/research/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.