SKILLEMALL.ai
GitHub ↗ RU Sign in

AA site-architecture

Plan or restructure website hierarchy, navigation, URL patterns, breadcrumbs, and internal linking. Use when mapping pages, sections, and site structure, but not for XML sitemap auditing or schema markup.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 5 files body ≈ 3 328 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Plan or restructure website hierarchy, navigation, URL patterns, breadcrumbs, and internal linking.

As a process A 80/100 · Runs to the end — weak spots: failures and branches, running it twice, progress reporting

AnalyzerData and analyticsWriting and documentsMarketingtype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
92
Run on models
none yet
Process rating
A
80/100
Runs to the end
Failures and branches w 10
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills

How to improve

    For the model run — optional
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "date_added"

    Process rating: all ten parameters 80/100

    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 5 mutating operations with no state check
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 77 steps, 1 vague phrases
    • 100Tools and files. No external tools needed
    • 100Result and completion. Output format and completion criterion are stated
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3328 tokens
    • low 12 top-level sections: this looks like several domains in one skill
    • medium 6 test cases, all positive: not one "should refuse" or "should ask first"
    • low No test case covers injection arriving through data

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +1No license
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 204: enough signal without eating the budget
    • +4Structure: 40 headings
    • +3Step-by-step instructions: 77 items
    • +3Output format is stated explicitly
    • +4Has examples (5 code blocks)
    • +4Reference files are cited in the instructions (3 of 3)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.