SKILLEMALL.ai
GitHub ↗ RU Sign in

AF site-architecture

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema-markup.

skytiger6724/qwen-skills Agent Skills author: skytiger6724 5 files body ≈ 3 181 tokens Open the sourcegithub.com↗ analyzed 3 d ago

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking.

As a process F 48/100 · Will not run — References files that are not bundled: /features/analytics

AnalyzerMarketingtype and topics are labelled automatically from the skill text
Runs in: Qwen Code Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS 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%
94
Run on models
none yet
Process rating
F
48/100
Will not run
References files that are not bundled: /features/analytics
Tools and files w 18
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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

  • warning missing-ref reference to a missing file: /features/analytics

Process rating: all ten parameters 48/100

Will not run. References files that are not bundled: /features/analytics
  • 0Tools and files. 1 referenced file(s) missing: /features/analytics
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 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
  • 60Result and completion. Output format stated, no completion criterion
  • 85Steps. 71 steps, 1 vague phrases
  • 100When it triggers. States when to use and when not to
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3181 tokens
  • low 10 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

  • +1No license
  • +2Single-language instructions
  • +5Description quotes 14 example trigger phrases
  • +4Description says when NOT to use the skill
  • +3Description length 677: enough signal without eating the budget
  • +4Structure: 38 headings
  • +3Step-by-step instructions: 71 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: 94.