Publisher: Corey Haines · Editorial profile by AI Tools Ratings · Review method
What task is this skill designed for?
Organize a small tool directory into useful hubs without changing existing listing URLs.
What input and output should you expect?
Input: An inventory of current URLs, page purposes, navigation labels, audience tasks and any known redirects or high-value inbound links.
Output: A proposed hierarchy, navigation zones and link map, plus a change list explaining which URLs stay and which need migration handling.
What does it need to run?
An Agent Skills client and the current URL inventory. Read the platform-and-migration reference if changing hosting or routes; diagram generation is optional, not required for a usable text hierarchy.
The pinned publisher README declares support for Agent Skills clients including Claude Code, Codex and Cursor. Compatibility follows the publisher’s stated support.
How should you approach installation?
- Inspect the pinned SKILL.md, license and referenced files needed for your specific task before installation.
- Follow the publisher README for your actual Agent Skills client.
- Try the illustrative prompt with synthetic material in a separate workspace. Review the checklist and approve any publishing, account or external-message action separately.
Installation guide: discovery, dependencies and runtime checks
What files, accounts or data can it access?
Reads route inventories and may propose edits to navigation code. Crawl exports can expose unpublished URLs. Keep the first output as a document; do not deploy redirects or delete pages during the planning trial.
What does the skill cost?
MIT-licensed source. Agent subscriptions, model usage and optional research or analytics services have separate costs.
What are its limits and alternatives?
A shallow tree does not establish good findability. Three-click and menu-size suggestions are design heuristics, not universal SEO rules. Redirect behavior and real user navigation still need testing.
Use Programmatic SEO when the primary issue is whether a repeated page family deserves to exist. Use this skill when known content needs a coherent hierarchy.
What could you ask in a small trial?
Try this with a small sample:
Group these 30 synthetic URLs around visitor tasks. Preserve all listing paths. Return a navigation tree, five contextual links and an explicit redirect proposal only for genuinely duplicated destinations.
How would you verify the result?
- Account for every existing URL.
- Ensure priority pages are reachable through visible links.
- Check proposed merges against distinct user intent before approving redirects.
Use a baseline and record acceptance evidence before treating a successful task as a reliable workflow.
Which source and license were checked?
Read the reviewed SKILL.md at its pinned commit · Complete reviewed folder
Repository and current publisher guidance
Checked:
MIT — identified in the repository LICENSE at the pinned commit. External services and dependencies have their own terms. License evidence
Version details and review scope
Source: coreyhaines31/marketingskills/skills/site-architecture
Reviewed commit: e85f3cbc2e4a79bf33b2a12e9bdd9087d414735b
SKILL.md SHA-256: 55c0128ac29f628944444f8850b97913517f57131673824ebcad4d5ffb26ddd2
Source-document review. This profile covers the source workflow, stated dependencies and license evidence. See our editorial methodology for how we distinguish source reviews and hands-on evaluations.