alerts

Create and manage price alerts for prediction markets

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/alerts/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise and actionable command reference documentation with good structure, but the destructive delete path lacks a validation/confirmation checkpoint and there is minor duplication between the Commands and Alert Types sections.

Suggestions

Add an explicit confirmation step before '/alert delete' (e.g. confirm the alert-id and show its details before removing) to satisfy validation requirements for destructive operations.

Consolidate the Commands and Alert Types sections to remove duplicated '/alert' syntax examples and tighten token usage.

Specify the alert-id format and the exact output of '/alerts' so the list/delete flow is fully executable without inference.

Dimension	Reasoning	Score
Conciseness	The body is lean with inline-commented commands and almost no over-explanation, but the Commands section partially duplicates the Alert Types section, leaving minor redundancy that could be trimmed.	4 / 5
Actionability	Commands are concrete and copy-paste ready with worked examples covering common cases, but minor gaps remain (e.g. alert-id format, what /alerts returns), so it is mostly rather than fully executable guidance.	4 / 5
Workflow Clarity	Commands are clearly organized but the destructive '/alert delete' operation has no confirmation or validation step; per the rubric, missing validation for destructive operations caps workflow clarity at 3.	3 / 5
Progressive Disclosure	The single file is well-organized into Commands, Alert Types, and Examples with no nested references, but at ~80 lines with some duplication it slightly exceeds the under-50-line simple-skill threshold that would merit a 5.	4 / 5
	Total	15 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 clearly states a specific, distinctive capability but stops short of providing trigger guidance or natural-language cues. Adding a 'Use when...' clause with user-facing phrases would raise completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to be notified, alerted, or tracked on prediction-market price moves.'

Expand action coverage beyond 'create and manage' to concrete verbs like 'list, delete, and trigger' to reflect the skill's actual scope.

Include natural synonyms users say ('notify me', 'alert me when', 'track this market') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('price alerts for prediction markets') and two actions ('Create and manage'), but 'manage' is generic and coverage is not comprehensive, matching the anchor for a clear what with 1-2 concrete actions.	3 / 5
Completeness	The 'what' is clear ('Create and manage price alerts for prediction markets') but there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Includes relevant terms ('price alerts', 'prediction markets') but misses natural user phrasings like 'notify me', 'alert me when', or 'track price', so keyword coverage has gaps rather than being comprehensive.	3 / 5
Distinctiveness Conflict Risk	The prediction-market price-alert niche is specific and unlikely to conflict with unrelated skills, though the absence of explicit trigger phrases keeps it just below the clearly-distinctive anchor 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alsk1992/CloddsBot
Path: src/skills/bundled/alerts/SKILL.md
Commit: 715fd4a

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.