Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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".
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-04 | ✗→✓ | ▲ Improved | 11% | 0% |
| case-07 | ✗→✓ | ▲ Improved | 11% | 0% |
| case-15 | ✗→✓ | ▲ Improved | 11% | 0% |
| case-19 | ✓→✗ | ▼ Worse | 11% | 0% |
| case-20 | ✓→✗ | ▼ Worse | 31% | 0% |
Produce a single, three-column documentation page in one HTML file.
prose; the mono token for code; respect line-height and max-width rules.
a generic wireframe. Concrete API names, command examples, plausible parameters.
layout flips correctly under dir="rtl":
page bolded with an inline-start-edge accent stripe. 3–5 groups of 4–8 links.
H1, lede paragraph, H2 sections, code blocks, callout boxes (note / warning), inline links, lists.
H2/H3 anchors, current section highlighted as the user scrolls.
<!doctype html> through </html>, all CSS inline.(visual only — no JS needed).
data-od-id on the nav, article, and TOC.one shell command, one code snippet (5–15 lines), one callout, one table.
monospace.border. Not on body text.
out, nav becomes a top drawer).
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.
Other measured skills in the registry, with their headline benchmark lift.