alerts
Create and manage price alerts for prediction markets
80
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/alerts/SKILL.mdQuality
Discovery
40%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 clear niche (prediction market price alerts) which provides good distinctiveness, but suffers from incomplete guidance. It lacks explicit trigger conditions and could benefit from more specific action verbs and natural user keywords to improve discoverability.
Suggestions
Add a 'Use when...' clause with trigger terms like 'prediction market', 'Polymarket', 'price alert', 'market notification', 'betting odds'
Expand the action list to be more specific, e.g., 'Create price alerts, track market movements, notify on threshold changes, monitor prediction market positions'
Include common platform names or file types users might mention when working with prediction markets
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (prediction markets) and two actions (create, manage price alerts), but lacks comprehensive detail about what 'manage' entails or other specific capabilities. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'price alerts' and 'prediction markets' that users might say, but misses common variations like 'Polymarket', 'betting odds', 'market notifications', or 'price tracking'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'price alerts' and 'prediction markets' creates a clear, specific niche that is unlikely to conflict with other skills like general alerting or financial tools. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently documents alert commands with concrete syntax examples. It assumes Claude's competence, avoids unnecessary explanation, and provides actionable command patterns. The structure is clean and appropriate for the skill's scope.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, presenting commands and examples without unnecessary explanation. No verbose descriptions of what alerts are or how they work conceptually. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands for every alert type with clear syntax. Examples show exact user inputs mapped to expected actions. | 3 / 3 |
Workflow Clarity | For a simple skill focused on single commands, the workflow is unambiguous. Each command type is clearly documented with its syntax and purpose. No multi-step processes requiring validation checkpoints. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized with clear sections (Commands, Alert Types, Examples). Structure is appropriate for the scope. | 3 / 3 |
Total | 12 / 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
2a8c94e
- 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.