ntfy-notify
Send push notifications via ntfy.sh with a lightweight shell workflow. Use when posting alerts, job status updates, reminders, or automation results to an ntfy topic using token auth or public topics.
95
93%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It clearly identifies the specific service (ntfy.sh), lists concrete use cases (alerts, job status, reminders, automation results), and provides explicit 'Use when' guidance. The description is concise yet comprehensive, using third person voice appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Send push notifications', 'posting alerts, job status updates, reminders, or automation results'. Also specifies the method: 'lightweight shell workflow' with 'token auth or public topics'. | 3 / 3 |
Completeness | Clearly answers both what ('Send push notifications via ntfy.sh with a lightweight shell workflow') and when ('Use when posting alerts, job status updates, reminders, or automation results to an ntfy topic'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'push notifications', 'ntfy.sh', 'alerts', 'job status updates', 'reminders', 'automation results', 'ntfy topic'. Good coverage of both the service name and use case terms. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche targeting ntfy.sh specifically. The combination of 'ntfy.sh', 'push notifications', 'ntfy topic', and 'token auth' creates clear, unique triggers unlikely to conflict with other notification or messaging skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%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 a notification script with concrete, executable examples. The content respects Claude's intelligence and provides actionable commands. The main weakness is the workflow could better integrate the --dry-run validation step into the configuration process rather than burying it in Notes.
Suggestions
Integrate --dry-run into the Configure section as an explicit validation step (e.g., 'After setup, verify with: scripts/ntfy_send.sh --dry-run "test"')
Add a brief troubleshooting note for when the script exits requesting topic input, showing the expected agent behavior
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only necessary configuration and usage examples without explaining what ntfy is or how push notifications work. Every section serves a clear purpose. | 3 / 3 |
Actionability | Provides fully executable shell commands for all operations, concrete .env examples, and copy-paste ready command patterns with various flag combinations. | 3 / 3 |
Workflow Clarity | The Configure section lists steps but lacks explicit validation checkpoints. While --dry-run is mentioned in Notes, it's not integrated into a clear workflow sequence for verifying setup before sending real notifications. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with clear sections (Prerequisites, Configure, .env Sample, Send, Notes) that allow quick scanning and reference. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- gitstua/stu-skills
- Commit
8dd0dc8
- 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.