manage-market-registry

Manage Market Registry

Why This Exists

${CLAUDE_PLUGIN_ROOT}/references/supported-markets-registry.json is the canonical taxonomy that every market-aware insight-wave plugin reads through ${CLAUDE_PLUGIN_ROOT}/scripts/get-market-config.py. There is one source of truth and no sync — plugin overlays carry only plugin-specific metadata keyed against the registry's canonical domain set, and the merge utility joins them at read time.

This skill owns both directions over that one registry: the read path reports what the taxonomy holds and where an overlay has drifted from it, and the write path adds a market. They were two skills once, and the split cost a routing decision on every market question while giving the host router no tiebreaker — the read skill's report was reachable from the write skill as well, so one was a superset of the other in all but name.

What this skill does not do (intentionally — these are gone in the centralized model):

• No sync — there's no copy of shared fields to propagate.
• No promote — domains live in the registry only, so there's nothing to promote from drift findings.
• No baseline-refresh — there's no baseline file because there's no drift on shared fields.

Sub-action Router

When invoked without arguments, ask the user which action to take:

Which manage-market-registry action?
  1. status — coverage matrix per market across registry/research/trends, plus orphan overlay domains
  2. add    — interactive new-market workflow (registry-first)

Use AskUserQuestion. If $ARGUMENTS starts with one of the two sub-action names, dispatch directly without asking.

Operations

1. status

Read-only coverage and drift report. Write nothing.

The set arithmetic behind this report is not done in prose — it is computed by a script and read back. That matters for the orphan check specifically: it was described here for a long time and computed nowhere, so nothing ever proved it could fire.

ORPHANS="${CLAUDE_PLUGIN_ROOT}/scripts/check-market-orphans.py"
python3 "$ORPHANS"