maintain-verify

Synchronize the Invoker verification feature map with sidebar testids and e2e specs.

18|5|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Neko-Catpital-Labs/Invoker --skill maintain-verify-neko-catpital-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maintain-verify
Source: https://github.com/Neko-Catpital-Labs/Invoker/tree/main/skills/maintain-verify
Command: npx skills add https://github.com/Neko-Catpital-Labs/Invoker --skill maintain-verify-neko-catpital-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? The Invoker verification feature map drifts out of sync with the actual UI as new sidebar surfaces, modals, data-testids, and Playwright e2e specs are added, causing catalog --check failures and stale prove commands for agents. ## Core Features & Use Cases - Catalog Consistency Gate: Runs node skills/verify/control-invoker.mjs catalog --check --json to validate the feature-map index as a cheap CI gate via scripts/test-verify-skill.sh. - Feature File Maintenance: Guides adding or updating feature files under skills/verify/references/features/ with frontmatter id, prove, and testids, pointing prove commands at existing Playwright specs or repro scripts. - Use Case: After adding a new sidebar surface with a data-testid, run catalog --check, update the matching feature file and sweep-order README, then re-run the check until it exits 0. ## Quick Start Run the maintain-verify skill to check the verification catalog and repair any stale feature-map entries.

Frequently Asked Questions about maintain-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a catalog --check failure in the Invoker verify skill?

Run catalog --check and read the error list, then add or update the feature file under skills/verify/references/features/ with frontmatter id, prove, and testids for each missing sidebar testid. Re-run the check until it exits 0, then run scripts/test-verify-skill.sh.

What should the prove field point to in a verification feature file?

Point prove at an existing Playwright spec, a scripts/repro case, an e2e-dry-run case, or a cheap existence check. Do not invent new heavy CI jobs just to satisfy the catalog.

When should I run the maintain-verify pass?

Run it after adding a sidebar surface, modal, or data-testid, after adding Playwright e2e specs under packages/app/e2e/, when catalog --check fails, or as a daily pass whenever prove commands feel stale.

Can the maintain-verify pass change product code to fix the catalog?

No. The maintain pass is a map-only repair and reindex loop limited to files under skills/verify/references/features/ and related index documentation. It must never edit packages/ or rewrite product UI to satisfy the catalog.

Does catalog --check evaluate how effective the verification skill is?

No. catalog --check is a cheap consistency gate that validates the feature-map index, run in CI via scripts/test-verify-skill.sh. Efficacy is assessed separately using the Tier A-D rubric in references/efficacy-rubric.md.