Skip to main content
Agent skill

Docs Page

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".

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Docs Page when an AI agent needs a reusable SKILL.md workflow for this job: 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".

When not to use it

Skip Docs Page when the task is outside the writing category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/docs-page
# Save SKILL.md to ~/.claude/skills/docs-page/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/docs-page/SKILL.md. For a shared project, commit the folder at .claude/skills/docs-page/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Docs Page skill for this task: Read the active DESIGN.md (injected above). Use the body type token for. Confirm any required inputs or files before making changes.

What supports this recommendation?

74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
82/100
Practical detail
74/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Docs Page Skill

Produce a single, three-column documentation page in one HTML file.

## Workflow

1. **Read the active DESIGN.md** (injected above). Use the body type token for prose; the mono token for code; respect line-height and max-width rules. 2. **Pick a topic** from the brief — the page should look like real docs, not a generic wireframe. Concrete API names, command examples, plausible parameters. 3. **Lay out** three regions, expressed on the inline axis so the layout flips correctly under `dir="rtl"`: - **Inline-start nav** (240–280px, sticky): grouped link list, current page bolded with an `inline-start`-edge accent stripe. 3–5 groups of 4–8 links. - **Article body** (max-width ~720px, centered in the middle column): H1, lede paragraph, H2 sections, code blocks, callout boxes (note / warning), inline links, lists. - **Inline-end TOC** (200–240px, sticky): "On this page" with the H2/H3 anchors, current section highlighted as the user scrolls. 4. **Write** a single HTML document: - `<!doctype html>` through `</html>`, all CSS inline. - CSS Grid for the three columns; sticky positioning for the rails. - Code blocks: monospace token, soft surface fill, copy-button affordance (visual only — no JS needed). - Anchor IDs on every H2/H3 so the TOC links work. - `data-od-id` on the nav, article, and TOC. 5. **Prose**: write at least 350 words of believable docs. Include at least one shell command, one code snippet (5–15 lines), one callout, one table. 6. **Self-check**: - Body text wraps at the DS line-length sweet spot (60–75 chars). - Code uses the DS mono token, not generic `monospace`. - Accent is restrained — used for active nav item, links, one callout border. Not on body text. - Page is readable at 1280w and collapses gracefully below 900w (TOC drops out, nav becomes a top drawer). - Use logical CSS (`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"`.

## Output contract

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.

Intended uses

  • Read the active DESIGN.md (injected above). Use the body type token for
  • Pick a topic from the brief — the page should look like real docs, not
  • Lay out three regions, expressed on the inline axis so the
  • Inline-start nav (240–280px, sticky): grouped link list, current
  • Article body (max-width 720px, centered in the middle column):
  • Inline-end TOC (200–240px, sticky): "On this page" with the
  • Write a single HTML document:
  • <!doctype html> through </html>, all CSS inline.
  • CSS Grid for the three columns; sticky positioning for the rails.
  • Code blocks: monospace token, soft surface fill, copy-button affordance
  • Anchor IDs on every H2/H3 so the TOC links work.
  • data-od-id on the nav, article, and TOC.
  • Prose: write at least 350 words of believable docs. Include at least
  • Self-check:
  • Body text wraps at the DS line-length sweet spot (60–75 chars).
  • Code uses the DS mono token, not generic monospace.
  • Accent is restrained — used for active nav item, links, one callout
  • Page is readable at 1280w and collapses gracefully below 900w (TOC drops
  • Use logical CSS (margin-inline-start, border-inline-start,

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.