CtrlK
BlogDocsLog inGet started
Tessl Logo

docs-build

Build, preview, and validate the Uno documentation website (DocFX) locally — surface real content errors vs expected noise, drive rendered pages with Playwright, and validate external-doc commit bumps in import_external_docs.ps1 before a PR. Use when working under doc/, editing articles/** markdown, bumping an external docs ref (uno.themes, studio-docs, hd-docs, uno.chefs, workshops, …), or rendering/validating the docs site.

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, concise skill body with a clear validation workflow and explicit checkpoints. Its only weakness is progressive disclosure: everything lives in one file with no reference bundle to offload the reference/background material.

Suggestions

Move the §6 'Build mechanics (reference)' CI pipeline detail into a references/ file (e.g. references/build-mechanics.md) and link to it from a one-line pointer, keeping the main body focused on the validation loop.

Consider extracting the §1 error/warning taxonomy table into references/error-taxonomy.md and referencing it, so the SKILL.md overview stays a lean entry point.

If the Playwright checklist in §3 is reused across changes, factor the assertion script into scripts/validate-page.js and invoke it, reducing inline token weight while keeping the steps copy-paste ready.

DimensionReasoningScore

Conciseness

Lean and dense: it omits generic explanations of DocFX/Playwright and instead supplies only non-obvious domain knowledge (the error taxonomy, expected-noise list, version-pinning gotchas), so nearly every token earns its place.

3 / 3

Actionability

Provides copy-paste-ready, executable guidance throughout — the docfx/grep triage pipeline, the external-doc grep+find checks, and a complete Playwright assertion script — matching the level-3 anchor.

3 / 3

Workflow Clarity

The TL;DR loop gives a clear sequenced validation path, §2 adds baseline-diff feedback for scoping, and §3 supplies explicit pass/fail checkpoints (HTTP 200, naturalWidth, console errors) with a build-vs-runtime labeling discipline.

3 / 3

Progressive Disclosure

Well-sectioned but a single ~130-line monolith with no bundle files or one-level-deep references; reference material like the §6 build mechanics and error taxonomy is inline rather than split into separate files, fitting the level-2 anchor of good structure but content that could be separated.

2 / 3

Total

11

/

12

Passed

Description

100%

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 strong, third-person description that states concrete capabilities and gives an explicit 'Use when' trigger clause tied to specific repo artifacts. It is specific, complete, and clearly distinct from generic doc skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Build, preview, and validate', 'surface real content errors vs expected noise', 'drive rendered pages with Playwright', and 'validate external-doc commit bumps in import_external_docs.ps1' — matching the level-3 anchor of multiple specific concrete actions.

3 / 3

Completeness

Clearly answers both what (build/preview/validate, surface errors, drive pages with Playwright, validate commit bumps) and when via an explicit 'Use when ...' clause, matching the level-3 anchor.

3 / 3

Trigger Term Quality

The 'Use when' clause surfaces natural trigger phrases a docs contributor would say — 'working under doc/', 'editing articles/** markdown', 'bumping an external docs ref', 'rendering/validating the docs site' — giving good coverage of the domain's natural terms.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to the Uno DocFX documentation toolchain (doc/, import_external_docs.ps1, named external repos), a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
unoplatform/uno
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.