news
Monitor news and correlate with prediction market movements
37
22%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/news/SKILL.mdQuality
Discovery
22%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 too vague and lacks both concrete actions and explicit trigger guidance. While the domain (prediction markets + news correlation) is somewhat distinctive, the description fails to specify what concrete outputs or analyses the skill produces and provides no 'Use when...' clause to guide skill selection.
Suggestions
Add a 'Use when...' clause with trigger terms like 'prediction market', 'Polymarket', 'Metaculus', 'forecasting odds', 'market movements', 'event probabilities'.
Specify concrete actions such as 'Fetches prediction market prices, tracks news events, identifies correlations between headlines and market probability shifts, and generates alerts or summaries.'
Include common platform names and file types/data sources to improve trigger term coverage and distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain (news and prediction markets) but uses vague actions like 'monitor' and 'correlate' without specifying concrete actions such as fetching RSS feeds, scraping market prices, generating alerts, or producing reports. | 1 / 3 |
Completeness | The description provides a weak 'what' (monitor and correlate) but completely lacks a 'when' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'news', 'prediction market', and 'movements', but misses common user variations such as 'Polymarket', 'Metaculus', 'forecasting', 'betting odds', 'market prices', or 'event contracts'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'news' and 'prediction market' is somewhat distinctive, but 'monitor news' is generic enough to overlap with general news aggregation or financial monitoring skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a product requirements document or feature wishlist than an actionable skill for Claude. It describes what the system should do (track news, correlate prices, detect volume spikes) without providing any implementation guidance—no API endpoints, no code for fetching data, no concrete steps for correlation logic. The output format example is well-structured but without instructions on how to produce it, the skill lacks practical utility.
Suggestions
Add concrete implementation steps: which APIs or tools to call for fetching news (e.g., specific RSS parsing, Twitter API endpoints), how to query prediction market prices, and how to perform the correlation.
Provide executable code examples for at least the core workflow: fetching recent news, querying market prices, and matching news to affected markets.
Define a clear multi-step workflow with validation checkpoints, e.g., 1) Fetch news from sources, 2) Parse and extract entities, 3) Query matching markets, 4) Calculate price deltas, 5) Validate data freshness before presenting.
Clarify what tools/capabilities Claude actually has access to for this skill—can it make HTTP requests? Access specific APIs? Or is it working with user-provided data?
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some padding. The news sources section lists specific accounts and feeds which is useful, but the auto-matching examples and correlation features describe capabilities rather than instructing how to implement them. Some sections could be tightened. | 2 / 3 |
Actionability | The skill describes desired behaviors and outputs but provides no executable code, no API calls, no implementation details for fetching news, correlating with markets, or detecting volume spikes. It reads more like a feature spec than actionable instructions Claude can follow. | 1 / 3 |
Workflow Clarity | There is no clear multi-step workflow for how to actually fetch news, match it to markets, or calculate price impacts. The examples section shows input/output pairs but not the process steps. No validation or error handling is mentioned for any operation. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections (commands, sources, features, examples, output format) which aids readability. However, it's all inline in one file with no references to supporting files, and some sections like correlation features could benefit from being split out with implementation details. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- alsk1992/CloddsBot
- Commit
e71a5f6
- 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.