How do I re-enable the skill bus?

Run /skill-bus:unpause-subs. If paused globally, re-enable globally; if per-project, re-enable in the project config.

What happens to active or future subscriptions when paused?

Subscriptions are prevented from firing while enabled is false; they are not removed.

What if the config file doesn't exist?

The command will create the .claude directory and a skill-bus.json file with settings.enabled set to false.

pause-subs

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-plugins/pause-subs --openclaw

Files (1)

SKILL.md

888 B

Pause Skill Bus

Announce: "Pausing skill-bus."

Process

Step 1: Determine Scope

Ask using AskUserQuestion: "Pause at which level?"

Global - Pauses skill-bus everywhere. Sets enabled: false in ~/.claude/skill-bus.json
Project - Pauses skill-bus for this project only. Sets enabled: false in .claude/skill-bus.json

Step 2: Update Config

Read the appropriate config file. Set settings.enabled to false. If the file doesn't exist, create the directory first (mkdir -p .claude for project scope) then create the file with just:

{
  "settings": {
    "enabled": false
  }
}

Step 3: Confirm

Show: "Skill bus paused at [scope] level. Run /skill-bus:unpause-subs to re-enable."

Source

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

Overview

Temporarily disable the skill bus to stop all subscriptions without removing them. You can pause globally or per project by flipping enabled to false in the respective config file, then re-enable with a command.

How This Skill Works

You choose the scope via a prompt. The system updates the correct config (global: ~/.claude/skill-bus.json or project: ./.claude/skill-bus.json) and sets settings.enabled to false, creating the directory if needed. It then displays a confirmation: 'Skill bus paused at [scope] level. Run /skill-bus:unpause-subs to re-enable.'

When to Use It

During critical debugging or outages to silence all subscriptions quickly.
Before large plugin updates to prevent new subscriptions from firing.
When focusing on a single project and you don't want cross-project triggers.
During maintenance windows or demos to avoid noisy results.
To pause temporarily while you investigate unexpected subscription activity.

Quick Start

Step 1: Choose scope — Global (all projects) or Project (this repo).
Step 2: Update Config — set settings.enabled to false; if missing, mkdir -p .claude and write the JSON.
Step 3: Confirm — you’ll see 'Skill bus paused at [scope] level. Run /skill-bus:unpause-subs to re-enable.'

Best Practices

Ask for scope before pausing to avoid global impact.
Prefer project scope for per-repo pauses.
Document the pause in your team notes or changelog.
Test the unpause flow to ensure quick restoration.
Verify that settings.enabled is false after updating the config.

Example Use Cases

Pausing subs during a plugin refresh in a multi-project setup.
Silencing subscriptions for a hotfix in a single repo.
Freezing the bus during a data migration to prevent events.
Demos where you don't want accidental triggers.
Maintenance window for Claude integration updates.

Frequently Asked Questions

Add this skill to your agents