generate-sitemap
Generate hierarchical site structure and navigation maps. Creates visual representations of information architecture and content relationships.
Install with Tessl CLI
npx tessl i github:dandye/ai-runbooks --skill generate-sitemap46
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%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 identifies a clear domain (site structure and information architecture) but suffers from missing explicit trigger guidance and incomplete keyword coverage. It would benefit significantly from a 'Use when...' clause and more natural user-facing terms like 'sitemap' or 'IA diagram'.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks for a sitemap, site structure, navigation hierarchy, or information architecture diagram'.
Include common user terms and file references such as 'sitemap', 'IA', 'page hierarchy', 'website structure', 'nav tree', or 'XML sitemap'.
Add more specific actions like 'export sitemap XML', 'define page hierarchies', 'map content relationships', or 'generate breadcrumb structures'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (site structure, navigation maps) and some actions (generate, creates visual representations), but lacks comprehensive specific actions like 'export to XML', 'define parent-child relationships', or 'create breadcrumb paths'. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'when' is entirely absent, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'site structure', 'navigation maps', 'information architecture', but misses common user phrases like 'sitemap', 'IA diagram', 'page hierarchy', 'website map', or 'nav structure'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to information architecture domain, but 'visual representations' and 'content relationships' could overlap with diagramming tools, documentation skills, or general visualization skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable high-level framework for sitemap generation but lacks the concrete, executable guidance Claude needs. The workflow describes concepts rather than providing actual code for directory traversal, link parsing, or format generation. The Mermaid example is helpful but insufficient without implementation details for the other formats.
Suggestions
Add executable Python/shell code for directory traversal and tree building instead of abstract descriptions
Provide concrete code examples for each output format (XML sitemap generation, SVG creation) not just Mermaid
Add validation steps to verify generated output is well-formed before returning (e.g., XML validation, Mermaid syntax check)
Include error handling guidance for common issues like permission errors, circular links, or missing index files
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanation like describing what sitemaps are for ('support user experience design'). The inputs section could be more compact. | 2 / 3 |
Actionability | The skill describes what to do at a high level but provides no executable code for traversing directories, parsing links, or generating output formats. The workflow steps are abstract descriptions rather than concrete implementations. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence but lack validation checkpoints. There's no guidance on handling errors (missing files, broken links, malformed content) or verifying the output is valid before returning. | 2 / 3 |
Progressive Disclosure | Content is organized into clear sections but everything is inline. For a skill covering multiple output formats (markdown, xml, svg, mermaid), detailed format specifications could be split into separate reference files. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%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 | |
- 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.