remove-sub
$
npx mdskill add ComposioHQ/awesome-claude-plugins/remove-subRemove unwanted skill subscriptions with precise scope control.
- Agents need this to stop receiving specific skill event notifications.
- The skill uses the /skill-bus:remove-sub command for execution.
- Scope-aware options allow targeting specific subscription contexts.
- Results confirm successful removal of the targeted event subscription.
SKILL.md
.github/skills/remove-subView on GitHub ↗
--- name: remove-sub description: Unsubscribe from a skill event. Removes or disables subscriptions with scope-aware options. --- # Unsubscribe from Skill Event This skill delegates to the `/skill-bus:remove-sub` command for the full interactive process. Run the command directly: `/skill-bus:remove-sub`
More from ComposioHQ/awesome-claude-plugins
- add-subSubscribe 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).
- helpShow skill-bus overview, status, and available commands. Quick reference for all skill-bus features.
- list-subsList 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.
- pause-subsTemporarily disable the skill bus. Quick toggle to stop all subscriptions from firing without removing them.
- perf-analyzer"Use when synthesizing perf findings into evidence-backed recommendations and decisions."
- perf-baseline-manager"Use when managing perf baselines, consolidating results, or comparing versions. Ensures one baseline JSON per version."
- perf-benchmarker"Use when running performance benchmarks, establishing baselines, or validating regressions with sequential runs. Enforces 60s minimum runs (30s only for binary search) and no parallel benchmarks."
- perf-code-paths"Use when mapping code paths, entrypoints, and likely hot files before profiling."
- perf-investigation-logger"Use when appending structured perf investigation notes and evidence."
- perf-profiler"Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence."