Goal

Add a drift detector to skill-reconciler that flags any two skills writing to different external identifiers (Notion DB IDs, Salesforce org IDs, GitHub repos, etc.).

Why

The notion-knowledge-base vs notion-session-export conflict went undetected for weeks because both skills referenced Notion but targeted different databases. A reconciler check for external-ID drift would have caught it on the first pass.

Implementation Sketch

1. Extend the existing skill-reconciler at /var/folders/.../claude-hostloop-plugins/.../skills/skill-reconciler/ (or the user-writeable mirror if one exists) to scan each SKILL.md for well-known ID patterns:
   • Notion: UUIDs adjacent to database_id, data_source_id, notion.so/{id} URLs.
   • Salesforce: 15/18 char case-sensitive IDs.
   • GitHub: owner/repo strings.
   • WordPress: page/post IDs in URLs.
2. Cluster skills by domain (anything that mentions notion, anything that mentions salesforce, etc.).
3. For each cluster, compare extracted IDs. Any mismatch triggers a high-priority reconciliation ticket.
4. Output format: the same 4-way multi-choice format Sam uses for QA recommendations. Option A is the most conservative merge.

Pickup Prompt

Open skill-reconciler. Add an external_id_drift module that runs after the duplicate-name check. For each pair of related skills (clustered by vendor keyword), extract external IDs and flag mismatches. Report through the standard multi-choice interface so Sam can approve merges without combing through entire files. Test against the 2026-04-23 merge case by running it on the pre-merge state in /Users/samaguiar/Documents/Codex/skill-merges/backups-2026-04-23/.