CtrlK
BlogDocsLog inGet started
Tessl Logo

pillar-content-architecture

How to design a content hub that earns topical authority. Pillar topic selection, cluster planning, internal linking architecture, URL structure, pillar and cluster page anatomy, topical authority signals for SEO and AEO/GEO, and the maintenance discipline that distinguishes intentional hubs from accidental orphans. Triggers on pillar content, content hub, topic cluster, topical authority, content architecture, hub and spoke, pillar page, cluster page, content silo, internal linking strategy. Also triggers when a content set is not ranking despite individual piece quality, when a pillar was launched without a cluster, or when content has accumulated without an architecture.

71

Quality

87%

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

78%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 well-architected, highly actionable instruction-only skill with excellent progressive disclosure and concrete thresholds throughout. Its main weakness is conciseness: the body carries narrative and metaphorical prose that competes with the genuinely valuable decision guidance.

Suggestions

Trim atmospheric prose (the yard-sale metaphor intro and the "architecture is the moat" closing) to lift conciseness without losing the concrete decision guidance.

Collapse the narrative framing of each section into a one-line lead so the thresholds, ranges, and checklists dominate the token budget.

Consider moving the 11-item failure-mode list fully into common-pillar-failures.md and keeping only a 2-3 line pointer plus the headline diagnoses in SKILL.md.

DimensionReasoningScore

Conciseness

The body is mostly efficient and carries genuine domain judgment (the "80% orphans" pathology, anti-patterns, specific thresholds), but a 22KB structural-design skill includes atmospheric prose (the yard-sale metaphor intro, the "architecture is the moat" closer, narrative asides) that could be tightened without losing clarity.

3 / 5

Actionability

For an instruction-only skill the guidance is highly actionable: specific word-count and cluster-size ranges, a five-criterion selection framework with thresholds (sub-100 monthly searches, 3 vs 8-15 facets), URL patterns with concrete slug examples, anchor-text rules, page-anatomy templates, and a 12-consideration framework that produces a concrete architecture document.

5 / 5

Workflow Clarity

The 12-consideration framework and closing readiness checklist ("is the pillar selected against the five criteria, are the 10 to 12 clusters planned ...") provide a clear sequenced workflow with a verification checkpoint, plus the "If required data is unavailable" sanctioned-output rule; it stops short of explicit error-recovery feedback loops, which are not really applicable to a design skill.

4 / 5

Progressive Disclosure

The skill is a clean overview with well-signaled one-level-deep references: each section links to a dedicated reference file, all 10 referenced files (pillar-cluster-decision, topic-selection-criteria, cluster-planning-patterns, internal-linking-architecture, url-structure-patterns, pillar-page-anatomy, cluster-piece-anatomy, topical-authority-signals, content-refresh-patterns, common-pillar-failures) exist in ./references/, and a final Reference files section indexes them with descriptions.

5 / 5

Total

17

/

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.

A strong, third-person description that concretely enumerates capabilities, provides explicit trigger guidance with both keyword and situational triggers, and carves a clear hub-architecture niche. The only soft spot is minor overlap risk with sibling content/SEO skills, which keeps distinctiveness just below the top anchor.

DimensionReasoningScore

Specificity

The description lists many concrete, specific capabilities ("Pillar topic selection, cluster planning, internal linking architecture, URL structure, pillar and cluster page anatomy, topical authority signals for SEO and AEO/GEO ... maintenance discipline"), giving comprehensive coverage anchored by the lead action "design a content hub that earns topical authority."

5 / 5

Completeness

It explicitly answers both what ("How to design a content hub that earns topical authority" plus its components) and when ("Triggers on ..." and "Also triggers when a content set is not ranking despite individual piece quality, when a pillar was launched without a cluster, or when content has accumulated without an architecture").

5 / 5

Trigger Term Quality

It enumerates a broad set of natural trigger terms users would say ("pillar content, content hub, topic cluster, topical authority, content architecture, hub and spoke, pillar page, cluster page, content silo, internal linking strategy") plus situational triggers, achieving comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

The niche is clear and triggers are distinctive ("hub and spoke", "content silo", "pillar page", "cluster page"), but it sits among acknowledged adjacent skills (content-strategy, seo-keyword, content-brief-authoring), leaving minor overlap risk with closely related skills rather than minimal conflict risk.

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.

Validation15 / 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
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.