add-sub

Subscribe to a skill event. Adds a subscription that injects context before or after a skill runs. Supports optional conditions at both insert-level (inherited by all subscriptions) and subscription-level (AND-stacked). Conditions include fileExists, gitBranch, envSet, envEquals, fileContains (with optional regex).

Quality

80%

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/add-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 lean delegation skill: it states the single action and gives the exact command to run, with no wasted tokens. Nothing material is missing for a skill whose entire job is to route to another command.

Dimension	Reasoning	Score
Conciseness	The body is three lean lines with no concept explanations or padding, and every line earns its place by pointing to the runnable command, matching the 'lean and efficient; assumes Claude's competence' anchor.	3 / 3
Actionability	It gives a concrete, copy-paste-ready command '/skill-bus:add-sub' twice, matching 'fully executable commands; copy-paste ready' rather than the vague or pseudocode anchors.	3 / 3
Workflow Clarity	This is a simple single-task skill (run one command) under 50 lines, so the single unambiguous action satisfies the simple-skill allowance for a top score without needing multi-step sequencing.	3 / 3
Progressive Disclosure	Under 50 lines with no bundle files and no need for external references, the single clear heading satisfies the under-50-lines allowance for a top progressive-disclosure score.	3 / 3
	Total	12 / 12 Passed

Description

60%

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 is specific and technically detailed about capabilities, but leans on internal jargon and omits any explicit 'when to use' trigger guidance. Adding a natural-language 'Use when...' clause and softer trigger terms would lift completeness and trigger quality.

Suggestions

Add a 'Use when ...' clause naming natural user situations (e.g., 'Use when you want context injected before or after a skill runs based on file, git, or environment conditions').

Soften internal jargon like 'insert-level (inherited by all subscriptions)' and 'AND-stacked' into user-facing phrasing so trigger terms read more naturally.

Clarify what distinguishes this from sibling skill-bus skills (e.g., rm-sub) to reduce overlap risk.

Dimension	Reasoning	Score
Specificity	Names concrete actions ('Subscribe to a skill event', 'Adds a subscription that injects context before or after a skill runs') and enumerates specific condition primitives (fileExists, gitBranch, envSet, envEquals, fileContains), matching the 'lists multiple specific concrete actions' anchor rather than the partial-coverage anchor below.	3 / 3
Completeness	It clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2 rather than reaching the explicit-what-and-when anchor.	2 / 3
Trigger Term Quality	'skill event' and 'subscription' are reasonably natural, but most terms are technical jargon ('insert-level', 'AND-stacked', 'envEquals') with no common natural variations, so it sits at 'some relevant keywords but missing common variations' rather than full natural coverage.	2 / 3
Distinctiveness Conflict Risk	It occupies a clear niche (event subscriptions with conditions) but lacks explicit triggers, so it could still overlap with sibling skill-bus skills, matching 'somewhat specific but could still overlap' rather than a conflict-free niche.	2 / 3
	Total	9 / 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/add-sub/SKILL.md
Commit: e521f7a

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