unpause-subs
Re-enable the skill bus after pausing. Restores subscription processing.
npx skills add composio-community/awesome-claude-plugins --skill unpause-subs --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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."
- Process
- Step 1: Check Current State
- Step 2: Resume
- Step 3: Confirm
What does the unpause-subs skill do?
Re-enable the skill bus after pausing. Restores subscription processing.
How do I install it?
Run `npx skills add composio-community/awesome-claude-plugins --skill unpause-subs --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From composio-community/awesome-claude-plugins, a repository with 1,858 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.