pmo-skill-refiner-selftest-canarylisted

Smoke test for the pmo-skill-refiner factory — produced via the refiner's Create-New workflow during an AC demonstration. Reports the count of skill directories currently present in `release/skills/` and flags any that are missing from the `deploy.sh` per-module skill arrays (`OPERATIONS_SKILLS` / `RELEASE_SKILLS` / `CORE_SKILLS` / `CANARY_SKILLS`). Report-only (no decision-class outputs, no recommendations, no actions). Permanent fixture per ADR-04 (Stage 5 design for ) — functions as an always-on smoke test that detects factory regressions. Use when the user wants to check skill-roster consistency ("check the skill roster", "count tracked skills", "audit skill deployment drift", "verify skills/ folder matches deploy.sh", "are all my skills deployed").
cody-hutson/pmo-platform · ★ 0 · AI & Automation · score 62

Install: claude install-skill cody-hutson/pmo-platform

# PMO Skill Refiner Selftest Canary A minimal report-only skill that verifies consistency between the `release/skills/` directory and the `deploy.sh` per-module skill arrays (`OPERATIONS_SKILLS` / `RELEASE_SKILLS` / `CORE_SKILLS` / `CANARY_SKILLS`, together the deploy roster). Produced by `pmo-skill-refiner` during an AC demonstration; preserved as a permanent smoke test per ADR-04. ## When to use Use when the user wants a quick consistency check on the PMO skill roster — specifically the invariant that every skill directory present under `release/skills/` is also registered in the `deploy.sh` per-module skill arrays (`OPERATIONS_SKILLS` / `RELEASE_SKILLS` / `CORE_SKILLS` / `CANARY_SKILLS`), and vice versa for the non-SUPPLEMENTARY case. Typical triggers: - "Check the skill roster" - "Count tracked skills" - "Audit skill deployment drift" - "Are all my skills deployed?" - "Does deploy.sh match the skills folder?" Skip and route elsewhere when: - Deep audit of skill content → route to `pmo-qa-auditor` Mode D (Document Management Compliance) - Structural skill edits → route to `pmo-skill-editor` - Creating a new skill → route to `pmo-skill-refiner` ## Workflow 1. **Inventory `release/skills/`** via `ls` — produce the list of skill directory names. 2. **Parse the `deploy.sh` per-module skill arrays** — read the `OPERATIONS_SKILLS`, `RELEASE_SKILLS`, `CORE_SKILLS`, and `CANARY_SKILLS` array declarations and union them to form the deploy roster (the tracked skill names). 3.