list-subs

List all active skill-bus subscriptions across global and project scopes, showing merge status, insert-level and subscription-level conditions, effective condition stacking, and what would fire for each skill.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skill-bus/skills/list-subs/SKILL.md

Quality

Content

72%

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

The body is commendably concise and well-structured for a simple listing skill, but its middle steps are underspecified: Step 2 offloads the display format to an external command and Steps 3–4 describe outcomes rather than giving concrete instructions. Making the display format and simulation procedure explicit would raise actionability and workflow clarity.

Suggestions

Replace Step 2's deferral with a concrete display format template (columns/fields for scope, merge status, insert-level and subscription-level conditions) so the skill is self-contained.

Specify the simulation procedure in Step 4 — how matching is evaluated and how per-condition pass/fail is presented — rather than only naming the outcome.

Add a light verification checkpoint (e.g. confirm both config files loaded and report which scopes are present) before presenting the merged view.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept-explaining padding — 'Read both config files', 'Present merged view', 'simulate matching' — and assumes Claude's competence, matching the 'lean and efficient; every token earns its place' anchor. Not a 2 because there is no unnecessary explanation to tighten.	3 / 3
Actionability	Step 1 gives concrete file paths ('~/.claude/skill-bus.json', '.claude/skill-bus.json'), but Step 2 defers to a command, and Steps 3–4 ('Present merged view...', 'simulate matching...') describe rather than instruct with no concrete format or method. Some concrete guidance but incomplete. Not a 1 because real paths are given; not a 3 because the core display/simulation steps lack executable specifics.	2 / 3
Workflow Clarity	A clear numbered 1→4 sequence exists, but Step 2 defers entirely ('See /skill-bus:list-subs command for full display format') and Step 3 is vague, leaving the actual workflow underspecified with no checkpoints — 'steps listed but... checkpoints missing or implicit'. Not a 1 because the sequence is present; not a 3 because validation/explicit detail is absent and the display step is pushed out of the skill.	2 / 3
Progressive Disclosure	This is a sub-50-line single-purpose skill with no bundle files and well-organized '## Process / ### Step' sections; per the guideline such skills can score 3 on progressive disclosure with just well-organized sections. The one external reference (the /skill-bus:list-subs command) is clearly signaled and one level deep. Not a 2 because organization is clean and no nested/deep references exist.	3 / 3
	Total	10 / 12 Passed

Description

67%

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 occupies a clear, low-conflict niche, but it omits any 'when to use' trigger guidance and leans heavily on internal jargon rather than natural user phrasing. Adding a 'Use when...' clause with user-facing terms would lift the two dimensions currently at 2.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to list or inspect skill-bus subscriptions, or asks what would fire for a given skill.'

Surface natural user-facing terms ('list subscriptions', 'what would fire', 'active subscriptions') earlier and reduce reliance on internal jargon like 'insert-level and subscription-level conditions'.

Keep the concrete capability list but pair it with the trigger guidance so both 'what' and 'when' are explicitly answered.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'List all active skill-bus subscriptions', 'showing merge status, insert-level and subscription-level conditions, effective condition stacking, and what would fire for each skill' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	The 'what' is clearly and specifically answered, but there is no 'when should Claude use it' guidance — no explicit trigger clause. Per the guideline, a missing 'Use when...' clause caps completeness at 2. Not a 1 because 'what' is strong; not a 3 because 'when' is entirely absent.	2 / 3
Trigger Term Quality	Beyond the natural-ish 'list...subscriptions' and 'what would fire for each skill', the description is dominated by internal jargon ('merge status', 'insert-level and subscription-level conditions', 'condition stacking') with no 'Use when...' clause; some relevant keywords but missing common variations. Not a 1 because it does contain natural phrases; not a 3 because trigger coverage is thin and jargon-heavy.	2 / 3
Distinctiveness Conflict Risk	'skill-bus subscriptions' is a narrow, well-defined niche with distinct triggers unlikely to overlap with other skills, matching the 'clear niche with distinct triggers' anchor. Not a 2 because it is not merely 'somewhat specific' — the domain is sharply scoped.	3 / 3
	Total	10 / 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/list-subs/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.