What it does
Pulls the full menu tree (or navigation block structure) and flags items nested more than 2-3 levels deep, vague labels like "More" or "Resources" that don't tell a visitor what's behind them, and links that resolve to a 404, a placeholder page, or an empty archive. Produces a specific list of problem items rather than a general "navigation could be better" note.
Install
This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:
Use it in your AI assistant
Claude Code
.claude/skills/navigation-menu-auditor/ (or ~/.claude/skills/navigation-menu-auditor/ for all projects)
GitHub Copilot (VS Code)
.github/skills/navigation-menu-auditor/
OpenAI Codex
.codex/skills/navigation-menu-auditor/
Cursor
.cursor/skills/navigation-menu-auditor/ (or ~/.cursor/skills/navigation-menu-auditor/ globally)
Compatibility
Any WordPress site using the built-in Menus feature or a block-based navigation block.
The complete SKILL.md for this skill:
---
name: navigation-menu-auditor
description: Use when a user wants their site navigation reviewed, mentions confusing menus, dead links in the header, or a menu that's grown too deep or cluttered.
---
# Navigation Menu Auditor
## When to use
The user wants a review of their main navigation (or another menu) for structural problems: too much nesting, unclear labels, or links that don't actually go anywhere useful.
## Procedure
1. Pull the full menu tree, including all nested sub-items, for the menu(s) in scope.
2. Flag any branch nested more than 2-3 levels deep, since visitors rarely dig past that in a dropdown or mobile menu.
3. Flag vague or generic labels ("More", "Resources", "Stuff") that don't tell a visitor what they'll find, and suggest a more specific label based on the actual linked content.
4. Test that every menu link resolves to a real, published page or post, not a 404, a draft, or an empty category archive.
5. Note any orphaned top-level item with no clear relationship to the items around it, a common sign a menu grew ad hoc over time.
6. Present findings as a specific list (item, problem, suggested fix) rather than a general structural critique.
## Guardrails
- Don't reorganize or delete menu items automatically, present the findings and let the user decide the new structure.
- Confirm a link is actually broken (checked the live URL) before flagging it, not just because the destination title looks outdated.