site-architecture

Plan or restructure website hierarchy, navigation, URL patterns, breadcrumbs, and internal linking. Use when mapping pages, sections, and site structure, but not for XML sitemap auditing or schema markup.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/site-architecture/SKILL.md

Quality

Content

67%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured, comprehensive site architecture skill that provides concrete guidance through tables, templates, and specific rules. Its main weakness is verbosity — it explains concepts Claude already understands (navigation types, breadcrumbs, URL best practices) and could be significantly tightened. The workflow is clear but would benefit from an explicit validation checkpoint before finalizing deliverables.

Suggestions

Trim explanations of concepts Claude already knows (e.g., what breadcrumbs are, what footer nav is, why readable URLs matter) and focus on the specific rules and patterns unique to this skill's approach.

Add a brief worked example showing a complete mini-deliverable for one site type (e.g., a SaaS site with 15 pages) to demonstrate the full output format in action.

Add an explicit validation step in the workflow (e.g., 'Before finalizing: verify no orphan pages, check all URLs follow consistent patterns, confirm breadcrumbs align with URL hierarchy').

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some content Claude already knows (e.g., explaining what breadcrumbs are, what header nav is, the concept of 'flat vs deep' hierarchy). The tables and examples are useful but some sections like 'Common Mistakes' explain obvious web development concepts. The overall length (~300+ lines) could be tightened significantly.	3 / 5
Actionability	The skill provides concrete output formats (ASCII trees, Mermaid diagrams, URL map tables), specific rules with numbers (4-7 nav items, 5-10 internal links per 1000 words), and clear templates. However, it's an instruction-only skill with no executable code, which is appropriate for the domain. Minor gap: no worked example showing a complete end-to-end architecture plan for a specific scenario.	4 / 5
Workflow Clarity	The workflow is reasonably clear: gather context → determine site type → design hierarchy → design navigation → plan URLs → plan internal linking → produce deliverables. The 'Before Planning' section establishes a clear starting sequence, and the 'Output Format' section defines clear deliverables. However, there's no explicit validation/review step (e.g., 'verify no orphan pages before finalizing') integrated into the workflow sequence, though the link audit checklist partially addresses this.	4 / 5
Progressive Disclosure	The skill references three external files (site-type-templates.md, navigation-patterns.md, mermaid-templates.md) which appropriately offload detailed templates. However, no bundle files were provided, so we can't verify these references exist. The main file itself is quite long and some content (like the full Mermaid examples) could potentially be moved to the referenced files. The structure with clear section headers is good for navigation.	4 / 5
	Total	15 / 20 Passed

Description

87%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly communicates its scope with concrete capabilities, explicit trigger guidance, and well-defined boundaries excluding related but distinct skills. The only minor weakness is that it could include a few more natural synonyms (e.g., 'information architecture,' 'IA,' 'menu structure') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Lists several specific actions: 'plan or restructure website hierarchy, navigation, URL patterns, breadcrumbs, and internal linking.' These are concrete, distinct capabilities. Minor gaps—could mention wireframing, content grouping, or taxonomy design—but coverage is solid.	4 / 5
Completeness	Clearly answers 'what' (plan/restructure hierarchy, navigation, URL patterns, breadcrumbs, internal linking) and 'when' ('Use when mapping pages, sections, and site structure'). Also includes explicit exclusion boundaries ('not for XML sitemap auditing or schema markup'), which strengthens the 'when' clause.	5 / 5
Trigger Term Quality	Includes strong natural keywords like 'website hierarchy,' 'navigation,' 'URL patterns,' 'breadcrumbs,' 'internal linking,' 'pages,' 'sections,' and 'site structure.' Missing some synonyms like 'information architecture,' 'IA,' 'nav structure,' or 'menu structure' that users might naturally say.	4 / 5
Distinctiveness Conflict Risk	Carves out a clear niche around site structure and architecture, and explicitly excludes XML sitemap auditing and schema markup, which are likely neighboring skills. This boundary-setting minimizes conflict risk significantly.	5 / 5
	Total	18 / 20 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/site-architecture/SKILL.md
Commit: 7520423

Reviewed: ~7 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.