What happens if both global and project scopes are paused?

The tool prompts you to choose which scope to resume, then enables the selected scope(s) accordingly.

What should I do if the project config file only contains a disabled stub?

Delete the project config file to clean state after resuming.

unpause-subs

Scanned

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

Files (1)

SKILL.md

777 B

Resume Skill Bus

Announce: "Resuming skill-bus."

Process

Step 1: Check Current State

Read both config files. Identify which level(s) are paused.

Step 2: Resume

If only one level is paused, resume it automatically.

If both levels are paused, ask: "Both global and project are paused. Resume which?"

Both
Global only
Project only

Set settings.enabled to true in the appropriate file(s).

If the project config file only contains {"settings": {"enabled": false}} and nothing else, delete it entirely (clean state).

Step 3: Confirm

Show: "Skill bus resumed at [scope] level. Subscriptions are active again."

Source

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

Overview

This skill re-enables the paused skill bus and restarts subscription processing. It inspects both global and project configs to determine what is paused, resumes the appropriate scope, and confirms the change.

How This Skill Works

It reads both config files to detect which levels are paused, then sets settings.enabled to true for the chosen scope. If both global and project scopes are paused, it prompts which to resume; when the project file only contains a disabled stub, it deletes it to clean state; finally it announces the resume and shows a confirmation.

When to Use It

Both global and project scopes are paused and you need to choose which to resume
Global pause only and you want to resume everything globally
Project pause only and you want to resume project-level subscriptions
Project config is a minimal disabled stub (only {'settings': {'enabled': false}}) and needs cleanup
After resuming, you want a clear confirmation that subscriptions are active again

Quick Start

Step 1: Read both global and project config files to determine paused scopes.
Step 2: If one scope is paused, resume it; if both paused, choose which to resume and enable it.
Step 3: Confirm the resume with the message that subscriptions are active again.

Best Practices

Check both global and project config files to identify all paused levels
If only one level is paused, resume it automatically to minimize disruption
When both are paused, prompt clearly to avoid unintended global changes
Set settings.enabled = true in the selected config(s) to re-enable processing
If the project config is a minimal disabled stub, delete it to maintain a clean state

Example Use Cases

You paused both scopes; you choose 'Global only' to resume all subscriptions across projects
Only the global scope was paused; unpause-subs re-enables global processing
Only the project scope was paused; unpause-subs reactivates project-level subscriptions
Project config shows only {'settings': {'enabled': false}}; the tool deletes the stub and resumes
After resuming, you see the message 'Skill bus resumed at [scope] level. Subscriptions are active again.'

Frequently Asked Questions

Add this skill to your agents