CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

news

Monitor news and correlate with prediction market movements

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/news/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 reasonably actionable with concrete commands and a clear output spec, but it reads as a feature catalog rather than a sequenced workflow and lacks validation checkpoints for alert/correlation operations.

Suggestions

Add a numbered workflow for the core correlation task (fetch news → match to markets → measure price impact → present), with a verification step that the matched markets actually moved.

Specify how alerts are created, stored, and fired (including dedup or rate-limiting) so the alert feature is reproducible rather than illustrative.

Tighten the Output Format example to one impact tier or move the full template to a reference file once bundle files are introduced.

DimensionReasoningScore

Conciseness

The body is lean and free of concept-explanation padding (no 'what is a prediction market' filler), using short command lists, source lists, and a single illustrative output example; only the fairly long output block could be trimmed, matching 'efficient; minor instances'.

4 / 5

Actionability

Concrete command syntax (`/news alert trump`, `/news for "Trump 2028"`), named source accounts, user→response example mappings, and a specific output format give mostly executable guidance, with minor gaps around how correlation is actually computed.

4 / 5

Workflow Clarity

No explicit multi-step sequence with validation checkpoints is given; correlation and alerts are described as features rather than a validated workflow, and alert/batch operations lack verification steps, capping clarity at 3.

3 / 5

Progressive Disclosure

The skill is a single well-organized file with clear section headers (Commands, Sources, Correlation Features, Examples, Output Format) and no nested or broken references; it sits just above the simple-skill threshold so minor organization gaps keep it at 4 rather than 5.

4 / 5

Total

15

/

20

Passed

Description

53%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, third-person, and names a clear niche, but it omits any explicit trigger/usage guidance and lists only two actions, leaving it mid-pack on specificity and completeness.

Suggestions

Add a 'Use when ...' clause naming concrete triggers, e.g. 'Use when tracking market-moving news or correlating headlines with prediction market price moves'.

Expand the action list (e.g. 'monitor breaking news, match stories to affected markets, detect volume spikes, set keyword alerts') to lift specificity.

Include natural synonyms a user might say ('prediction markets', 'Polymarket', 'Kalshi', 'event markets') to broaden trigger coverage.

DimensionReasoningScore

Specificity

"Monitor news and correlate with prediction market movements" names the domain plus two concrete actions (monitor, correlate), but stops there without enumerating further capabilities, matching the anchor for 1-2 concrete actions.

3 / 5

Completeness

A clear 'what' is present (monitor and correlate news with market movements) but there is no 'Use when...' clause or equivalent trigger guidance, so per the guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

It surfaces natural terms ("news", "prediction market movements") but offers no synonyms, variations, or related phrasings a user might say, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The prediction-market-correlation niche is fairly specific and unlikely to fire for unrelated skills, though overlap with a generic news skill remains, matching 'mostly distinct; minor overlap risk'.

4 / 5

Total

13

/

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/news/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.