Get the FREE Ultimate OpenClaw Setup Guide →

remove-sub

Scanned
npx machina-cli add skill ComposioHQ/awesome-claude-plugins/remove-sub --openclaw
Files (1)
SKILL.md
308 B

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

Source

git clone https://github.com/ComposioHQ/awesome-claude-plugins/blob/master/skill-bus/skills/remove-sub/SKILL.mdView on GitHub

Overview

This skill unsubscribes you from a skill event by delegating to the /skill-bus:remove-sub command for the full interactive flow. It can remove or disable existing subscriptions with scope-aware options, enabling precise control over which events you stop receiving. Use it to tidy up subscriptions and reduce event noise in your environment.

How This Skill Works

It delegates the work to the /skill-bus:remove-sub command, launching an interactive flow to select and remove a subscription. The command applies scope-aware options, letting you target global, per-skill, or per-event subscriptions, and executes the unsubscribe or disable action.

When to Use It

  • You need to unsubscribe from a specific skill event (targeted cleanup).
  • You’re deprecating a skill and want to remove its subscriptions.
  • You’re cleaning up test or noisy subscriptions after debugging.
  • You want to temporarily disable a subscription without deleting it.
  • You’re auditing subscriptions for compliance or cost reasons.

Quick Start

  1. Step 1: Run /skill-bus:remove-sub to start the interactive flow.
  2. Step 2: Select the target subscription (global, per-skill, or per-event) to remove or disable.
  3. Step 3: Confirm your choice and review the result in the confirmation prompt.

Best Practices

  • Use scope-aware options to target global, per-skill, or per-event subscriptions.
  • Always confirm the list of active subscriptions before removal.
  • Prefer temporary disables if you may re-enable later.
  • Document changes in team notes to maintain traceability.
  • After removal, verify downstream workflows are still healthy.

Example Use Cases

  • An admin unsubscribes all listeners for the deprecated inventory-update event.
  • A team disables a non-critical subscription to reduce event traffic during peak hours.
  • A developer removes test subscriptions created during integration tests.
  • An org migrates to a new event model and clears old subscriptions.
  • During compliance audit, all global subscriptions to sensitive events are removed.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers