Overview

List all active skill-bus subscriptions from both global and project scopes. It presents a merged view that shows merge status, insert-level and subscription-level conditions, and the effective stacking of those conditions, along with what would fire for each skill.

How This Skill Works

It loads both skill-bus.json configurations from global and project locations, merges subscriptions, and displays a unified view of insert-level and subscription-level conditions. It can optionally simulate matching to show what would fire for a given event by evaluating per-condition pass/fail at both levels.

When to Use It

• Auditing all active subscriptions across global and project scopes.
• Debugging why a particular skill would or would not fire for a given event.
• Understanding how insert-level and subscription-level conditions stack to form the effective criteria.
• Verifying the merge status and conflicts between global and project settings.
• Preparing to run a 'what would fire for X?' simulation for a test case.

Quick Start

1. Step 1: Load both skill-bus.json configs from global (~/.claude/skill-bus.json) and project (.claude/skill-bus.json) locations.
2. Step 2: Run the list-subs command to view the merged subscriptions and their states.
3. Step 3: (Optional) Run a simulate pass to test what would fire for a specific event or skill.

Best Practices

• Ensure both global and project skill-bus.json files exist and are accessible before running the scan.
• Review merge status first to identify overrides or conflicts between scopes.
• Carefully examine the sequence of condition checks and their pass/fail outcomes.
• Use the simulate option to validate outcomes against representative events.
• Document any discrepancies between insert-level and subscription-level conditions for future reference.

Example Use Cases

• Audit all active subscriptions across a monorepo to view merged conditions and what would fire for each skill.
• Debug a misfiring skill by simulating a specific event and confirming per-condition pass/fail at both levels.
• Plan a controlled rollout by validating merge status across global and project scopes before enabling a new skill.
• Optimize performance by comparing effective condition stacking across multiple subscriptions.
• When troubleshooting why a skill ignored an event, inspect the insert-level vs subscription-level evaluation results.

Frequently Asked Questions