CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

information-architecture

Design the structure of a website or product including sitemap, navigation, URL structure, content types, taxonomy, and labeling. Use this skill whenever the user asks to plan a sitemap, design navigation, structure URLs, define content types, build taxonomies, design site search, or organize content at the system level. Triggers on sitemap, site structure, navigation, IA, information architecture, URL structure, content types, taxonomy, categorization, breadcrumbs, hub pages, faceted navigation, site search, labeling. Also triggers when content is being created without a structural plan, or when an existing site's structure is being audited or restructured.

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

86%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, well-structured strategy skill: concrete domain guidance Claude cannot be assumed to know, a sequenced workflow with validation and data-gap rules, and clean progressive disclosure to two real reference files. The two minor gaps are a handful of trimmable general-knowledge sentences and the absence of an error-recovery feedback loop after label validation.

Suggestions

Trim the motivational opener ('A well-designed IA makes the rest of the project easier...') and the sentence explaining that URLs are user-facing and indexed by search engines — both restate general knowledge.

Add a feedback loop after the step-7 label validation: what to do when a tree test or closed card sort fails (e.g., revise the contested labels, re-sort, re-test) rather than only stating the gap.

Clarify in the 'When NOT to use' section that navigation-visual design (styling, layouts) belongs to design-standards, since 'navigation' alone as a trigger could pull visual-design requests into this skill.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive with concrete numbers throughout ('5 to 7 items maximum', 'under 60 characters', 'typically 5 to 15'), but a few sentences are trimmable general knowledge — the motivational opener ('A well-designed IA makes the rest of the project easier...') and 'URLs are... user-facing, indexed by search engines'. Not 5: those minor instances mean not every token earns its place; not 3: there is no noticeable padding or explanation of concepts Claude already knows.

4 / 5

Actionability

As an instruction-only skill the guidance is fully actionable: a concrete URL pattern block, defined test methods (card sort, tree test, first-click), specific counts for navigation/categories/tags, named failure patterns with remedies, a 9-step workflow, and an 8-section output format.

5 / 5

Workflow Clarity

The 9-step workflow is clearly sequenced with conditional branching ('If audience is unclear, run brand-discovery first') and a validation step ('Validate labels. Tree test or closed card sort with target users, or state the gap per the data-availability rule'). Not 5: there is no feedback loop for what to do when validation fails or how to iterate; not capped at 3 because the skill involves no destructive or batch operations.

4 / 5

Progressive Disclosure

The body serves as a clear overview with two verified, well-signaled one-level-deep references (ia-document-template.md and url-pattern-library.md), linked both inline in the workflow and in a dedicated 'Reference files' section; the fillable template and expanded URL library are appropriately split out of SKILL.md.

5 / 5

Total

18

/

20

Passed

Description

96%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.

An excellent description: third-person voice, explicit what-and-when structure, comprehensive natural trigger terms including synonyms and the 'IA' abbreviation. The only weakness is minor conflict risk from a few broad triggers that overlap with adjacent content and design skills.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — 'plan a sitemap, design navigation, structure URLs, define content types, build taxonomies, design site search' — comprehensively covering all six framework layers; no gaps in coverage remain.

5 / 5

Completeness

It clearly answers both 'what' ('Design the structure of a website or product including sitemap, navigation, URL structure, content types, taxonomy, and labeling') and 'when' ('Use this skill whenever the user asks to...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

The explicit trigger list covers natural terms comprehensively, including the abbreviation 'IA', synonyms like 'site structure', 'categorization', and specific phrases such as 'faceted navigation', 'breadcrumbs', and 'hub pages'.

5 / 5

Distinctiveness Conflict Risk

The IA niche is mostly distinct with dedicated triggers, but broad terms like 'navigation', 'categorization', and 'organize content' carry minor overlap risk with closely related content-strategy and design skills. Not 5: some triggers are generic enough that a user seeking content production or single-page design could land here first.

4 / 5

Total

19

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

rampstackco/claude-skills

Path

skills/information-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.