A documentation page — inline-start nav, scrollable article body, inline-end table of contents. Use when the brief mentions "docs", "documentation", "guide", "API reference", or "tutorial".
71
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
The canonical home for this skill is docs-page in nexu-io/open-design
Produce a single, three-column documentation page in one HTML file.
dir="rtl":
inline-start-edge accent stripe. 3–5 groups
of 4–8 links.<!doctype html> through </html>, all CSS inline.data-od-id on the nav, article, and TOC.monospace.margin-inline-start, border-inline-start,
inset-inline-end, text-align: start) on the rails and accent
stripe so the layout flips correctly under dir="rtl".Emit between <artifact> tags:
<artifact identifier="docs-slug" type="text/html" title="Docs — Page Title">
<!doctype html>
<html>...</html>
</artifact>One sentence before the artifact, nothing after.
1b47e60
Canonical home
since Sep 28, 2026
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.