list-subs
List 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.
Profile →npx skills add composio-community/awesome-claude-plugins --skill list-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.
# List Skill Bus Subscriptions **Announce:** "Listing skill-bus subscriptions." ## Process ### Step 1: Load Configs Read both config files: - `~/.claude/skill-bus.json` (global) - `.claude/skill-bus.json` (project, if exists) ### Step 2: Show Settings (See `/skill-bus:list-subs` command for full display format) ### Step 3: Show All Subscriptions Present merged view showing effective state with insert-level and subscription-level conditions. ### Step 4: Simulate (optional) If the user asks "what would fire for X?", simulate matching with per-condition pass/fail at both insert and subscription levels.
- Process
- Step 1: Load Configs
- Step 2: Show Settings
- Step 3: Show All Subscriptions
- Step 4: Simulate (optional)
What does the list-subs skill do?
List 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.
How do I install it?
Run `npx skills add composio-community/awesome-claude-plugins --skill list-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.