alerts
Create and manage price alerts for prediction markets
50
38%
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 distinct niche (prediction market price alerts) but is too terse to be effective for skill selection. It lacks a 'Use when...' clause, specific action details, and natural trigger terms users might employ. Its main strength is its distinctiveness, but it needs significantly more detail to help Claude reliably choose this skill.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to set up, edit, or remove price alerts on prediction market platforms like Polymarket or Kalshi.'
Expand the list of concrete actions beyond 'create and manage'—specify operations like setting price thresholds, listing active alerts, editing alert conditions, and receiving notifications.
Include natural trigger terms users would say, such as 'Polymarket alerts,' 'betting market notifications,' 'odds tracking,' 'market price threshold,' or specific platform names.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (prediction markets) and two actions (create and manage price alerts), but lacks detail on what 'manage' entails—no mention of specific operations like editing thresholds, deleting alerts, listing active alerts, or notification mechanisms. | 2 / 3 |
Completeness | Describes what the skill does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2—and since the 'what' is also thin, a score of 1 is appropriate. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'price alerts' and 'prediction markets,' but misses common user variations such as 'Polymarket,' 'Kalshi,' 'betting odds,' 'notifications,' 'threshold alerts,' or 'market monitoring.' | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'price alerts' and 'prediction markets' is a clear, narrow niche that is unlikely to conflict with other skills such as general market analysis, stock trading, or generic notification tools. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a clear command syntax reference for creating price alerts but lacks implementation depth — there's no code showing how alerts are stored, monitored, or triggered, making it more of a command cheat sheet than an actionable skill. The redundancy between the Commands and Alert Types sections wastes tokens, and the complete absence of workflow for the alert lifecycle (creation → monitoring → triggering → notification) is a significant gap for what is inherently a multi-step, stateful process.
Suggestions
Add implementation details: how are alerts stored (file, database), how are they polled/checked, and how are notifications delivered when triggered?
Define a clear workflow: create alert → persist → monitor loop → trigger condition met → notify → cleanup, with validation at each step.
Remove redundancy between the 'Commands' and 'Alert Types' sections — consolidate into a single reference with all alert types and their syntax.
Clarify the execution context: are these slash commands in a chat interface, CLI commands, or natural language patterns that Claude should parse? Include executable code for at least one complete alert flow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably concise but has some redundancy — the 'Commands' section and 'Alert Types' section overlap significantly (e.g., 'above' and 'below' are shown twice with nearly identical examples). The 'Examples' section at the end adds some value but partially repeats what's already shown. | 2 / 3 |
Actionability | The commands are concrete and specific, but there's no implementation detail — no code for how alerts are stored, checked, or triggered. It's unclear whether these are slash commands in a specific system, CLI commands, or natural language patterns. There's no executable code, just command syntax. | 2 / 3 |
Workflow Clarity | There is no workflow for the lifecycle of an alert — how alerts are persisted, how they're monitored/polled, what happens when triggered, or how notifications are delivered. For a system that involves creating, monitoring, and triggering alerts, the absence of any process flow or validation steps is a significant gap. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections (Commands, Alert Types, Examples) which provides decent structure. However, there are no references to external files for implementation details, storage mechanisms, or notification systems, and the content could benefit from separating the command reference from implementation guidance. | 2 / 3 |
Total | 7 / 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.