CtrlK
BlogDocsLog inGet started
Tessl Logo

generate-sitemap

Generate hierarchical site structure and navigation maps. Creates visual representations of information architecture and content relationships.

52

Quality

57%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/generate-sitemap/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The skill is well-structured and reasonably concise with a useful worked example, but its workflow steps are more descriptive than executable and lack verification checkpoints. Resolving the EXPORT_FORMAT/OUTPUT_FORMAT inconsistency and tightening the steps would lift actionability and workflow clarity.

Suggestions

Make the workflow steps executable by specifying how to traverse the directory tree and how each EXPORT_FORMAT is produced, rather than describing the intent.

Fix the naming inconsistency between EXPORT_FORMAT (Inputs) and OUTPUT_FORMAT (Required Outputs) so the contract is unambiguous.

Add a verification step (e.g., validate sitemap.xml compliance or confirm all referenced pages exist) before returning the output.

DimensionReasoningScore

Conciseness

The body is mostly efficient with brief, well-scoped steps and a concrete mermaid example; the intro sentence about 'visualizes the information architecture to support user experience design' is mild over-explanation that could be trimmed.

4 / 5

Actionability

Provides concrete inputs and a copy-paste mermaid example, but the workflow steps are high-level descriptions ('Traverse the PATH', 'Build a tree representation') rather than executable guidance, and the EXPORT_FORMAT vs OUTPUT_FORMAT naming inconsistency introduces ambiguity.

3 / 5

Workflow Clarity

Four steps are clearly sequenced, but there are no validation checkpoints and Step 3 only details mermaid and XML while omitting markdown and SVG handling; the export-format handling gap leaves the sequence incomplete.

3 / 5

Progressive Disclosure

Content is well-organized into clear sections (Inputs, Workflow, Required Outputs, Quick Reference) in a single self-contained file with no nested references; the body is slightly over the 50-line simple-skill threshold and the Quick Reference partially repeats earlier content.

4 / 5

Total

14

/

20

Passed

Description

53%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 clearly conveys what the skill does but omits any explicit 'when to use' trigger guidance and misses the most natural keyword ('sitemap'). It is specific enough to be distinct but would benefit from a Use-when clause and richer trigger terms.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., when the user mentions sitemaps, site structure, navigation maps, or information architecture).

Include the natural term 'sitemap' and file extensions like 'sitemap.xml' to improve trigger term coverage.

Replace the generic 'Creates visual representations of information architecture and content relationships' with more concrete output actions (e.g., 'Exports to mermaid, XML, markdown, or SVG').

DimensionReasoningScore

Specificity

Names the domain ('site structure and navigation maps') with 1-2 concrete actions ('Generate hierarchical site structure', 'Creates visual representations'), but the actions are somewhat generic and not comprehensive.

3 / 5

Completeness

Has a clear 'what' (generate hierarchical site structure and navigation maps) but no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Includes relevant keywords like 'site structure', 'navigation maps', and 'information architecture', but omits the most natural term 'sitemap' and any file extensions, missing common variations.

3 / 5

Distinctiveness Conflict Risk

Occupies a fairly clear niche (sitemap/site structure generation) with minor overlap risk against related IA/visualization skills, though lack of explicit triggers keeps it just below 5.

4 / 5

Total

13

/

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
dandye/ai-runbooks
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.