remove-sub

Unsubscribe from a skill event. Removes or disables subscriptions with scope-aware options.

Quality

75%

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 ./skill-bus/skills/remove-sub/SKILL.md

Quality

Content

100%

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

The body is an exemplary concise delegation: it states exactly what to run with no filler, and the single-step task is unambiguous and self-contained, so it scores maximally on every dimension.

Dimension	Reasoning	Score
Conciseness	Two lean sentences with no padding or explanation of concepts Claude already knows; every token earns its place, matching anchor 3.	3 / 3
Actionability	It provides a concrete, copy-paste-ready executable command (`/skill-bus:remove-sub`), matching the anchor for fully executable commands.	3 / 3
Workflow Clarity	As a single-task delegation skill under 50 lines, the single action is unambiguous and no validation feedback loop is needed, so it qualifies for 3 under the simple-skills note.	3 / 3
Progressive Disclosure	The skill is tiny, self-contained, and well-organized with a heading and clear delegation, with no nested or external references to manage, qualifying for 3 under the under-50-lines note.	3 / 3
	Total	12 / 12 Passed

Description

50%

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 conveys the skill's purpose and a couple of actions in third person, but lacks an explicit trigger/"Use when" clause and broad natural-language coverage, leaving all dimensions at the mid level.

Suggestions

Add a "Use when..." clause naming concrete triggers, e.g. "Use when the user wants to unsubscribe from, mute, or stop notifications for a skill event subscription."

Expand trigger-term coverage with natural variations users would say (stop notifications, mute, leave, unsubscribe).

Specify the concrete actions more granularly (e.g. remove by event ID, disable scoped to a channel) to lift specificity toward 3.

Dimension	Reasoning	Score
Specificity	It names the domain and a couple of actions ("Removes or disables subscriptions with scope-aware options") but does not list multiple specific concrete actions, matching anchor 2 rather than 3.	2 / 3
Completeness	It clearly states what the skill does but has no "Use when..." trigger clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	"Unsubscribe" and "subscriptions" are natural user terms, but coverage is narrow with no common variations (e.g. stop notifications, mute), so it sits at anchor 2.	2 / 3
Distinctiveness Conflict Risk	"Unsubscribe from a skill event" with "scope-aware options" is a specific niche, but without an explicit trigger clause it could still overlap with other notification/subscription skills, matching anchor 2.	2 / 3
	Total	8 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: composio-community/awesome-claude-plugins
Path: skill-bus/skills/remove-sub/SKILL.md
Commit: e521f7a

Reviewed: about 13 hours 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.