CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

site-architecture

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

A strong, highly actionable skill body: dense reference tables, executable output templates, a concrete deliverables spec, and a well-structured one-level-deep reference bundle. Its main costs are redundancy (duplicate context-gathering and breadcrumb sections), occasional explanations of basic web conventions, and inline template material that could be offloaded to the existing references.

Suggestions

Merge the "Task-Specific Questions" section into "Before Planning" — both ask nearly identical questions (new vs. restructuring, site type, page count, important pages, URLs to preserve, audiences), so one section suffices.

Trim well-known web-convention explanations (hyphens vs. underscores, lowercase URLs, what header nav/breadcrumbs are) down to bare rule statements, and fold the "Breadcrumb-URL Alignment" table into the earlier "Breadcrumb Format" rule to remove the repetition.

Reduce the two inline Mermaid examples to one minimal example and rely on references/mermaid-templates.md for the rest, mirroring the summary-table-plus-reference pattern already used for site-type templates — and add an explicit final validation step cross-checking the URL map against the hierarchy tree and the orphan-page checklist.

DimensionReasoningScore

Conciseness

The body is mostly table-driven and token-efficient (site-type matrix, URL pattern tables, output-format spec), but includes trimmable material: the "Task-Specific Questions" section repeats the "Before Planning" context gathering nearly verbatim, "Breadcrumb-URL Alignment" restates the earlier breadcrumb rule, and some rows explain basics Claude already knows ("Hyphens, not underscores," "Lowercase always," what header nav/breadcrumbs are). Not the leanest possible form, but noticeably above the midpoint — fits anchor 4 rather than 3.

4 / 5

Actionability

Fully actionable for an instruction-only skill: copy-paste-ready ASCII tree format, executable Mermaid `graph TD` examples, a URL pattern table by page type, concrete design rules ("4-7 items max"), a 5-deliverable output spec with a worked URL map table, and a link-audit checklist — specific examples cover the common site types.

5 / 5

Workflow Clarity

A clear sequence is present (gather context in "Before Planning" → design hierarchy/nav/URLs → produce the five specified deliverables) with checkpoints like the Link Audit Checklist, but the sequence is implicit in section order rather than an explicit numbered workflow, and there is no validation/feedback loop on the produced plan (e.g., cross-checking the tree against the URL map). Not a destructive/batch skill, so no cap applies.

4 / 5

Progressive Disclosure

All three bundle files (site-type-templates.md, navigation-patterns.md, mermaid-templates.md) exist, are clearly signaled ("For full page hierarchy templates: See [references/...]"), and are one level deep with no nested references. However, the body is a ~350-line manual rather than a lean overview — the two full inline Mermaid examples and complete ASCII tree partially duplicate what the reference files hold, leaving minor organization gaps that keep it below the anchor-5 "clear overview" pattern.

4 / 5

Total

17

/

20

Passed

Description

100%Weight 40%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.

The description is exemplary: concrete third-person capability statements, an extensive set of natural trigger terms with synonyms and user-voice phrasing, explicit what/when coverage, and explicit disambiguation against adjacent SEO skills. Every dimension sits at the top anchor.

DimensionReasoningScore

Specificity

"plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking" lists multiple concrete actions applied to specific deliverables — comprehensive coverage of the skill's capabilities. It stays in third person ("When the user wants to..."), so no voice penalty applies.

5 / 5

Completeness

Explicitly answers both what ("plan, map, or restructure... page hierarchy, navigation, URL structure, or internal linking") and when ("When the user wants to... Also use when the user mentions...") with concrete trigger phrases, plus negative scope guidance ("NOT for XML sitemaps").

5 / 5

Trigger Term Quality

Fifteen quoted trigger phrases including synonyms ("sitemap," "site map," "visual sitemap"), jargon ("information architecture," "IA"), and natural user questions ("what pages do I need," "how should I organize my site") — comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

Clear niche (site structure planning) with distinct structure-focused triggers, and it actively disambiguates the two nearest conflicts ("NOT for XML sitemaps (that's technical SEO — see seo-audit). For structured data, see schema."). Minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

joshmanders/dotfiles

Path

claude/skills/site-architecture/SKILL.md

Reviewed

Table of Contents

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.