unpause-subs

Re-enable the skill bus after pausing. Restores subscription processing.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skill-bus/skills/unpause-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 admirably lean and well-structured for a simple skill, but it omits the config file paths needed for fully executable guidance and substitutes a display-only confirmation for a real verification step after a destructive delete. These two gaps pull actionability and workflow clarity down to the midpoint.

Suggestions

Name the actual config file paths in Step 1 (e.g. the global and project settings files) so 'Read both config files' is unambiguous and copy-paste ready.

Replace the display-only Step 3 with a real verification step: re-read the file(s) to confirm settings.enabled is true (or the project file is gone) before announcing success.

Add an explicit validation/checkpoint before the destructive deletion in Step 2 (e.g. confirm the file contains only the enabled:false override) to satisfy the destructive-operation feedback-loop expectation.

Dimension	Reasoning	Score
Conciseness	The body is terse and direct with no explanation of concepts Claude already knows; every line is an actionable instruction and earns its place, matching the 'lean and efficient' anchor.	3 / 3
Actionability	It gives the exact field to set (settings.enabled to true) and a precise deletion condition, but never names the config file paths ('Read both config files', 'the appropriate file(s)'), leaving a key detail unspecified per the 'missing key details' anchor.	2 / 3
Workflow Clarity	A clear 3-step sequence with branching exists, but Step 3 only displays a confirmation message instead of verifying the change, and the destructive file deletion has no validation loop, so the rubric's destructive-operation rule caps this at 2.	2 / 3
Progressive Disclosure	The skill is under 50 lines, needs no external references, and is organized into clear Process/Step sections, so the simple-skill rule allows a top score with just well-organized sections.	3 / 3
	Total	10 / 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 is concise and identifies a clear niche, but it lacks an explicit 'Use when...' trigger clause, leans on internal jargon ('skill bus'), and does not enumerate multiple concrete actions. These gaps place every dimension at the midpoint anchor.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the skill bus has been paused and subscriptions need to resume.'

Replace or gloss internal jargon ('skill bus') with natural user terms like 'subscriptions' or 'skill subscriptions' to improve trigger term quality.

List the concrete actions taken (e.g. flip settings.enabled to true, optionally delete a project-only override) to lift specificity toward the top anchor.

Dimension	Reasoning	Score
Specificity	It names the domain ('skill bus', 'subscription processing') and one concrete action ('Re-enable ... Restores'), but does not list multiple distinct concrete actions, matching the 'names domain and some actions' anchor rather than the multiple-actions anchor.	2 / 3
Completeness	It states what the skill does but includes no 'Use when...' trigger clause, and the rubric guideline explicitly caps completeness at 2 when explicit trigger guidance is missing.	2 / 3
Trigger Term Quality	Terms like 'paused', 'subscription', and 're-enable' are somewhat natural, but 'skill bus' is internal jargon and common user variations ('unpause', 'resume subscriptions') are missing, fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The niche (resuming a paused subscription bus) is fairly narrow, but 'subscription processing' is abstract and could overlap with a sibling pause or general settings skill, matching the 'somewhat specific but could still overlap' anchor.	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/unpause-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.