Monitor news and correlate with prediction market movements
64
52%
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
32%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 identifies a specific domain (news + prediction markets) but remains too high-level and abstract. It lacks concrete actions, explicit trigger terms users would naturally say, and critically missing any 'Use when...' guidance that would help Claude know when to select this skill over others.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about prediction market movements, Polymarket, forecasting odds, or wants to correlate news events with market prices'
List specific concrete actions such as 'fetch news headlines, track prediction market prices, identify correlations between events and odds changes, generate market movement alerts'
Include natural user terms like 'Polymarket', 'Metaculus', 'forecasting', 'betting odds', 'market prices', '.csv exports' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (news monitoring, prediction markets) and implies actions (monitor, correlate), but lacks concrete specific actions like 'fetch headlines', 'track price changes', 'generate alerts', or 'analyze sentiment'. | 2 / 3 |
Completeness | Describes what it does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'what' is also weak, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'news', 'prediction market', and 'movements', but misses common variations users might say such as 'Polymarket', 'Metaculus', 'forecasting', 'odds', 'betting markets', or 'market prices'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'news' and 'prediction market' creates a somewhat specific niche, but 'monitor news' alone could overlap with general news aggregation skills, and 'correlate' is vague enough to conflict with data analysis skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has excellent structure and conciseness, clearly defining commands and expected outputs. However, it lacks the executable implementation details needed to actually perform news monitoring and market correlation - it describes the desired behavior without providing the code or concrete steps to achieve it.
Suggestions
Add executable code for fetching news from the listed RSS feeds and Twitter accounts
Provide concrete implementation for the auto-matching logic that correlates news keywords to market names
Include actual API calls or tool usage patterns for retrieving market price data to detect movements
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, presenting commands, sources, and examples without explaining what news is or how prediction markets work. Every section adds actionable value. | 3 / 3 |
Actionability | Commands are clearly shown and output format is well-defined, but the actual implementation is missing - no code for fetching news, correlating with markets, or creating alerts. It describes what should happen rather than how to do it. | 2 / 3 |
Workflow Clarity | The examples show user queries and expected responses, but there's no clear workflow for how to actually fetch news, match it to markets, or track price impacts. The auto-matching and correlation features are described conceptually without implementation steps. | 2 / 3 |
Progressive Disclosure | For a skill of this size, the content is well-organized into logical sections (Commands, Sources, Features, Examples, Output Format) with clear headers. No unnecessary nesting or external references needed. | 3 / 3 |
Total | 10 / 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 | |
2a8c94e
Table of Contents
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.