CtrlK
BlogDocsLog inGet started
Tessl Logo

hns-oss-docs-structure-map

docs-site structure map for the oss-docs harness structure-curator: exact paths and schemas for hugo.toml, per-locale content/<locale>/_meta.yaml, data/menu/main.yaml (4-locale name maps + icon values), the icon-to-SVG-case coupling in layouts/partials/menu.html, shortcodes, the FROZEN moai-brand.css, vercel.json redirect examples, and the known design-vs-guides divergence. Loaded by the structure-curator before any navigation or config edit.

61

Quality

73%

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 ./.claude/skills/hns-oss-docs-structure-map/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 tight, information-dense structure map that assumes competence and leads with executable commands and concrete schemas, well-organized for navigation. It is strong across the board with only minor refinements possible in feedback-loop explicitness and reference formatting.

DimensionReasoningScore

Conciseness

Dense and assumes Claude's competence — no padding about what Hugo, Vercel, or YAML are — with nearly every line carrying a concrete path, schema, or gotcha; a few clarifying parentheticals could still be trimmed.

4 / 5

Actionability

Provides concrete executable commands (the icon-coupling grep, the hugo --minify --gc build check) and a copy-ready vercel.json redirect block, with only minor gaps such as the missing SVG-case addition example.

4 / 5

Workflow Clarity

The icon-edit flow ('After any icon edit: grep… If absent, add the SVG path case in the same change') and the warning-free build check give a clear sequence with a validation checkpoint, though a full validate→fix→retry loop is only implied.

4 / 5

Progressive Disclosure

Well-organized into a path-map table, schema block, coupling/redirect/divergence/tooling sections, with one-level-deep references (Skill('hns-oss-docs-verify'), the redesign report path) clearly signaled; minor gaps as those references are inline rather than formatted links.

4 / 5

Total

16

/

20

Passed

Description

71%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 highly specific, niche-scoped reference description that clearly distinguishes itself and states both contents and load timing. Its main weakness is trigger-term naturalness: it speaks in internal harness vocabulary rather than phrases a user would naturally utter.

Suggestions

Add natural-language trigger phrases users would actually say (e.g. 'Use when editing the docs-site sidebar menu, redirects, or Hugo config') alongside the harness-internal 'Loaded by the structure-curator' phrasing.

Include common synonyms/file extensions (hugo.toml, .yaml, vercel redirects) so the description matches how users refer to these surfaces in passing.

DimensionReasoningScore

Specificity

Names the domain ('docs-site structure map') and lists several specific concrete surfaces — hugo.toml, content/<locale>/_meta.yaml, data/menu/main.yaml, layouts/partials/menu.html, moai-brand.css, vercel.json — giving broad coverage, though it enumerates contents rather than discrete actions.

4 / 5

Completeness

Clearly states the 'what' (exact paths and schemas for the listed surfaces) and a 'when' ('Loaded by the structure-curator before any navigation or config edit'), but the trigger is harness-agent-oriented rather than a concrete user-spoken phrase.

4 / 5

Trigger Term Quality

Contains relevant domain terms (hugo, menu, redirects, vercel, structure) but leans on internal jargon ('structure-curator', 'harness', 'oss-docs') and misses common synonyms or file extensions a user might naturally say.

3 / 5

Distinctiveness Conflict Risk

Highly niche — pinned to a specific oss-docs docs-site with named frozen assets (moai-brand.css) and file paths, making accidental triggering by unrelated skills very unlikely.

5 / 5

Total

16

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
modu-ai/moai-adk
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.