feeds
Real-time market data feeds from 8 prediction market platforms
Overall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
33%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 (prediction markets) and quantifies scope (8 platforms), but lacks actionable specificity about what operations are supported and completely omits trigger guidance. Without a 'Use when...' clause, Claude cannot reliably determine when to select this skill over others.
Suggestions
Add a 'Use when...' clause with trigger terms like 'prediction market', 'Polymarket', 'betting odds', 'election forecasts', 'probability estimates'
List specific actions the skill enables such as 'query current prices', 'compare odds across platforms', 'track probability changes'
Name the 8 platforms or categories (e.g., 'Polymarket, Metaculus, PredictIt') to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (prediction market platforms) and mentions '8 platforms' and 'real-time market data feeds', but doesn't list specific actions like querying, comparing, or analyzing data. | 2 / 3 |
Completeness | Describes what (data feeds from prediction markets) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'prediction market' and 'market data' which are relevant, but misses common variations users might say like 'Polymarket', 'betting odds', 'forecasting', 'probabilities', or specific platform names. | 2 / 3 |
Distinctiveness Conflict Risk | 'Prediction market' is fairly specific and unlikely to conflict with general market/stock skills, but 'market data feeds' could overlap with financial data skills without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive API reference with strong actionability through executable code examples and clear chat commands. However, it's overly long for a SKILL.md file, mixing quick-start content with detailed reference material that should be split into separate files. The workflow guidance is minimal, treating this as pure reference rather than teaching how to effectively use the feeds in practice.
Suggestions
Split platform-specific features and detailed API reference into separate files (e.g., PLATFORMS.md, API_REFERENCE.md) and keep SKILL.md as a concise overview with links
Add error handling examples and reconnection patterns to address the mentioned best practice about WebSocket drops
Remove the best practices section or make it more specific - current items like 'cache responses' and 'respect rate limits' are obvious to Claude
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy (e.g., the platform table duplicates information shown elsewhere, and some code examples are more verbose than necessary). The best practices section states obvious things Claude would know. | 2 / 3 |
Actionability | Provides fully executable TypeScript code examples that are copy-paste ready, with concrete chat commands and specific API calls. Examples show real usage patterns with actual output formatting. | 3 / 3 |
Workflow Clarity | This is primarily an API reference rather than a multi-step workflow, but the best practices section mentions handling reconnections without showing how. No validation checkpoints for subscription management or error handling patterns are provided. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but it's a monolithic 200+ line document that could benefit from splitting platform-specific features and advanced topics into separate files. No references to external documentation. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
91%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 | |
- 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.