Skill Scope Collision Detector

Cross-check merged settings withClaude Settings Scope Diffbefore production rollout.

What This Tool Does

Skill Scope Collision Detector is built for deterministic developer and agent workflows.

Detect version and enabled-state collisions across global, user, project, and local skill scopes with effective-configuration mapping.

Use How to Use for execution steps and FAQ for constraints, policies, and edge cases.

Last updated:

This tool is provided as-is for convenience. Output should be verified before use in any production or critical context.

Agent Invocation

Best Path For Builders

Browser workflow

Runs instantly in the browser with private local processing and copy/export-ready output.

Browser Workflow

This tool is optimized for instant in-browser execution with local data handling. Run it here and copy/export the output directly.

/skill-scope-collision-detector/

For automation planning, fetch the canonical contract at /api/tool/skill-scope-collision-detector.json.

How to Use Skill Scope Collision Detector

  1. 1

    Paste all scope layers

    Add global, user, project, and local arrays with skill name, version, and enabled state to reflect your live configuration hierarchy.

  2. 2

    Run collision analysis

    The detector compares skills across scopes and flags version drift, enable/disable mismatches, and precedence conflicts.

  3. 3

    Inspect effective winners

    Review the effective configuration map to see which scope currently wins for each skill under local > project > user > global precedence.

  4. 4

    Resolve conflicts with recommended actions

    Apply recommended alignment actions per skill so every scope converges on the intended version and enabled state.

  5. 5

    Verify before deployment

    Re-run the detector after scope edits and before release promotion to prevent silent shadowing in production.

Frequently Asked Questions

What counts as a scope collision?
A collision occurs when the same skill appears in multiple scopes with conflicting versions or enabled states, causing hidden overrides at runtime.
How is effective scope chosen?
The detector uses precedence order local > project > user > global and reports which scope currently wins for each skill definition.
Can this detect disabled-skill shadowing?
Yes. If one scope disables a skill while another enables it, the mismatch is flagged and included in remediation guidance.
Does this tool modify my configs automatically?
No. It performs analysis and outputs recommended actions. You decide when and how to apply configuration changes.
How often should I run collision checks?
Run checks before every release and after any managed/user/project config update to prevent scope drift from reaching production.