Skill Scope Collision Detector

Detect cross-scope skill version and enabled-state collisions across global, user, project, and local configuration layers

Skills per scope (JSON)

Scope collision report (JSON)

{
  "summary": {
    "totalSkills": 3,
    "collisions": 2,
    "highRiskCollisions": 1,
    "precedence": [
      "global",
      "user",
      "project",
      "local"
    ]
  },
  "effective": [
    {
      "skill": "incident-triage",
      "winnerScope": "local",
      "winnerVersion": "1.4.1",
      "enabled": true,
      "sourceCount": 4
    },
    {
      "skill": "release-note-writer",
      "winnerScope": "project",
      "winnerVersion": "1.0.0",
      "enabled": true,
      "sourceCount": 2
    },
    {
      "skill": "security-audit",
      "winnerScope": "user",
      "winnerVersion": "0.4.0",
      "enabled": true,
      "sourceCount": 1
    }
  ],
  "collisions": [
    {
      "skill": "incident-triage",
      "sources": [
        {
          "scope": "global",
          "version": "1.2.0",
          "enabled": true
        },
        {
          "scope": "user",
          "version": "1.3.0",
          "enabled": true
        },
        {
          "scope": "project",
          "version": "1.3.0",
          "enabled": false
        },
        {
          "scope": "local",
          "version": "1.4.1",
          "enabled": true
        }
      ],
      "reasons": [
        "Version mismatch across scopes",
        "Enabled/disabled state mismatch"
      ],
      "recommendedAction": "Align all scopes to local:1.4.1 and keep enabled=true."
    },
    {
      "skill": "release-note-writer",
      "sources": [
        {
          "scope": "global",
          "version": "0.9.1",
          "enabled": true
        },
        {
          "scope": "project",
          "version": "1.0.0",
          "enabled": true
        }
      ],
      "reasons": [
        "Version mismatch across scopes"
      ],
      "recommendedAction": "Align all scopes to project:1.0.0 and keep enabled=true."
    }
  ],
  "remediationChecklist": [
    "Pin a canonical version per skill and propagate to lower scopes.",
    "Avoid disabling a skill in higher-precedence scopes unless intentional.",
    "Re-run detector after each scope change before deployment."
  ]
}

Cross-check merged settings withClaude settings scope diffbefore production rollout.

Updated October 2, 2026. Provided as is. Check the output before you rely on it in production.

How to use Skill Scope Collision Detector

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

Run collision analysis

The detector compares skills across scopes and flags version drift, enable/disable mismatches, and precedence conflicts.
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

Resolve conflicts with recommended actions

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

Verify before deployment

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

Questions and answers

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 change to a global, user, project or local skill entry, so scope drift is caught before it reaches production.

For AI agents: how to call this tool

Machine-readable contract, endpoints and examples. Humans can ignore this section.

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.

Skill Scope Collision Detector