verify
Build, launch and drive wayfinder-maps to verify a change end-to-end (server + headless browser).
Profile →npx skills add rengwu/wayfinder-maps --skill verify --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Verifying wayfinder-maps ## Build & fixture ```bash go build -o /tmp/wayfinder-maps ./cmd/wayfinder-maps ``` There is no sample map in the repo. Create an effort dir with `map.md` + `tickets/NN-slug.md`. Ticket format: YAML frontmatter (`type:`, `blocked_by: [01]`, `claimed_by:`, `undermined_by: [NN]`) then `# Title`, `## Question`; a `## Answer` section with prose = resolved, `## Ruled out` = o
What does the verify skill do?
Build, launch and drive wayfinder-maps to verify a change end-to-end (server + headless browser).
How do I install it?
Run `npx skills add rengwu/wayfinder-maps --skill verify --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rengwu/wayfinder-maps, a repository with 86 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.