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.

Quality

83%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

A solid, actionable skill with concrete commands and clear examples for sending ntfy notifications. The main weakness is redundancy between the Prerequisites, Configure, and .env Sample sections, which repeat the same environment variables and configuration details. Consolidating these overlapping sections would improve conciseness without sacrificing clarity.

Suggestions

Merge the Prerequisites, Configure, and .env Sample sections into a single 'Setup' section to eliminate redundant repetition of NTFY_DEFAULT_TOPIC, NTFY_ACCESS_TOKEN, and NTFY_SERVER.

Include the bundle files (especially scripts/ntfy_send.sh) so that referenced paths can be verified and the skill is self-contained.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but has some redundancy — the Prerequisites and Configure sections overlap significantly (both explain NTFY_DEFAULT_TOPIC, NTFY_ACCESS_TOKEN, etc.), and the .env sample section repeats what's already shown. Could be tightened by consolidating.	2 / 3
Actionability	Provides concrete, copy-paste ready commands for every operation: environment variable exports, .env file contents, and script invocations with various flag combinations. The examples cover basic, explicit topic, and advanced (title/priority/tags) use cases.	3 / 3
Workflow Clarity	For this simple single-task skill (sending notifications), the workflow is clear and unambiguous. Configuration steps are sequenced, the send examples are straightforward, and the --dry-run flag serves as an explicit validation checkpoint before real sends.	3 / 3
Progressive Disclosure	The content is reasonably well-structured with clear section headers, but the Prerequisites, Configure, and .env Sample sections contain overlapping information that could be consolidated. No bundle files were provided to verify referenced paths like scripts/ntfy_send.sh or the .env-path file.	2 / 3
	Total	10 / 12 Passed

Description

89%

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 solid skill description with excellent trigger terms and completeness, clearly specifying both what the skill does and when to use it. The main weakness is that the 'what' portion could enumerate more specific actions beyond just 'send push notifications' to better convey the full range of capabilities. Overall, it's well-targeted and distinctive.

Suggestions

Add more specific concrete actions such as 'set message priority, attach files, add action buttons, or configure notification tags' to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (push notifications via ntfy.sh) and mentions 'shell workflow' and 'token auth or public topics', but doesn't list multiple concrete actions beyond 'send push notifications'. It could specify actions like composing messages, setting priority levels, attaching files, or scheduling notifications.	2 / 3
Completeness	Clearly answers both 'what' (send push notifications via ntfy.sh with a shell workflow) and 'when' (explicit 'Use when' clause covering alerts, job status updates, reminders, automation results, and specifying auth modes). The trigger guidance is explicit and well-structured.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms: 'push notifications', 'ntfy', 'ntfy.sh', 'alerts', 'job status updates', 'reminders', 'automation results', 'ntfy topic', 'token auth'. These cover a good range of terms a user would naturally use when wanting this functionality.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — ntfy.sh is a specific service, and the description narrows scope to shell-based push notifications with token auth. This is unlikely to conflict with other notification or messaging skills due to the specific tool and method mentioned.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: gitstua/stu-skills
Commit: 3fe35d2

Reviewed: 22 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.