Agent skill

Write User Guide

by pymc-labs in pymc-labs/pathmc

Write and maintain narrative user-guide pages for a Great Docs site.

MITAuto-check passedWriting & Content

Install Write User Guide

skills CLI
$ npx skills add pymc-labs/pathmc --skill write-user-guide -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install pymc-labs/pathmc write-user-guide --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/pymc-labs/pathmc.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/write-user-guide .claude/skills/write-user-guide && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
write-user-guide
GitHub stars
132
Token cost
~2.3k tokens
SKILL.md length
761 words
Files
3 (incl. references)
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Write and maintain narrative user-guide pages for a Great Docs site.

  • Works in 4 steps: Rename files to adjust numeric prefixes. → Update guide-section values to regroup. → Rebuild. Great Docs regenerates the… → …
  • Improving user-guide content
  • SKILL.md covers Quick start, Skill directory structure, When to use this skill and Core concepts, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Write User Guide is an agent skill from pymc-labs/pathmc. Write and maintain narrative user-guide pages for a Great Docs site. Covers page creation, QMD frontmatter, section grouping, sidebar ordering, callouts, executable code cells, cross-references, and content guidelines. Use when adding, reorganizing, or improving user-guide content.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/page-anatomy.md` and `references/writing-guidelines.md`). Compatibility notes: Requires Great Docs =0.8, Quarto CLI installed.

It sits in Writing & Content, covering Technical writing and Static sites and blogs. The repository describes itself as: Structural causal models with Bayesian estimation and interventional simulation via a concise DSL. The licence is MIT.

When your agent uses it

  • Improving user-guide content
  • Tasks that involve Technical writing
  • Tasks that involve Static sites and blogs

Example prompts

  • “/write-user-guide”

Requirements

  • Python 3
  • Compatibility (from SKILL.md): Requires Great Docs >=0.8, Quarto CLI installed.

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Rename files to adjust numeric prefixes.
  2. Update guide-section values to regroup.
  3. Rebuild. Great Docs regenerates the sidebar automatically.
  4. Check for broken cross-references.

What it can do on your machine

Read from SKILL.md and the folder at commit e3b9467. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown, bash and yaml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires Great Docs >=0.8, Quarto CLI installed.

    From compatibility in the SKILL.md frontmatter.

Context cost

Write User Guide loads about 2.3k tokens when it runs, and up to ~4.3k if it reads all its reference files. Until then it costs about 75 tokens; SKILL.md has 761 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~75
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from pymc-labs/pathmc at commit e3b9467, republished under its MIT licence (© pymc-labs). 761 words, ~2,255 tokens.

Download SKILL.mdSave it as .claude/skills/write-user-guide/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
write-user-guide
description
Write and maintain narrative user-guide pages for a Great Docs site. Covers page creation, QMD frontmatter, section grouping, sidebar ordering, callouts, executable code cells, cross-references, and content guidelines. Use when adding, reorganizing, or improving user-guide content.
compatibility
Requires Great Docs >=0.8, Quarto CLI installed.
license
MIT
metadata.author
rich-iannone
metadata.version
1.0
metadata.tags
documentation, user-guide, quarto, content-authoring

Write User Guide

Skill for authoring user-guide pages in a Great Docs documentation site. User guides provide narrative documentation (tutorials, conceptual explanations, and task walkthroughs) that complement the auto-generated API reference.

Quick start

bash
mkdir -p user_guide
cat > user_guide/00-introduction.qmd << 'EOF'
---
title: "Introduction"
guide-section: "Getting Started"
tags: [Getting Started]
---

# Introduction

Welcome to the project. This guide walks you through...
EOF

great-docs build

Skill directory structure

skills/write-user-guide/
├── SKILL.md
└── references/
    ├── page-anatomy.md
    └── writing-guidelines.md

When to use this skill

NeedAction
Add a new guide pageCreate user_guide/NN-topic.qmd
Reorder pagesRename numeric prefixes
Group pages into sectionsSet guide-section in frontmatter
Add an interactive exampleUse {python} code cells in the .qmd
Cross-reference another pageUse [text](../user-guide/page.qmd) links
Embed a calloutUse :::{.callout-tip} / :::{.callout-note}
Add imagesPlace in assets/ and reference from QMD

Core concepts

File naming convention

Every page in user_guide/ must have a two-digit numeric prefix that controls sidebar ordering:

user_guide/
├── 00-introduction.qmd     # appears first
├── 01-installation.qmd
├── 02-quickstart.qmd
├── 03-authoring-qmd-files.qmd
└── 04-writing-docstrings.qmd

Great Docs strips the prefix for clean URLs: 00-introduction.qmd → user-guide/introduction.html.

QMD frontmatter

Every user-guide page starts with YAML frontmatter:

yaml
---
title: "Writing Docstrings"
guide-section: "Getting Started"
tags: [API, Content]
---

Required keys:

KeyDescription
titlePage heading and sidebar label

Optional keys:

KeyDescription
guide-sectionGroup pages under a sidebar section header
tagsContent tags for discoverability
bread-crumbsSet false to hide breadcrumb navigation
statusPage status badge: experimental, new, stable
Guide sections

Pages with the same guide-section value are grouped together in the sidebar under a collapsible section heading:

Getting Started
├── Introduction
├── Installation
└── Quick Start
Site Content
├── Authoring QMD Files
├── Writing Docstrings
└── User Guides

If no guide-section is set, the page appears at the top level.

Page body structure

A well-structured page follows this outline:

markdown
# Page Title

Opening paragraph: 2-3 sentences explaining what this page covers
and why the reader cares.

## First Major Section

Narrative prose. Keep paragraphs short (3-5 sentences).

### Subsection

More detail. Use tables, code blocks, and callouts to break up text.

## Second Major Section

...

Guidelines:

  • Start every page with a single # heading matching the title.
  • Use ## for major sections, ### for subsections.
  • Keep the hierarchy flat; avoid #### if possible.
  • Lead each section with a sentence explaining what follows.
  • End with a summary or "next steps" when appropriate.
Callouts

Quarto callouts highlight important information:

markdown
:::{.callout-tip}

## Pro tip

You can combine `guide-section` with `tags` to make pages
discoverable from multiple angles.
:::

:::{.callout-warning}

## Watch out

Renaming a page file changes its URL. Update any cross-references.
:::

:::{.callout-note}
This feature requires Great Docs 0.8 or later.
:::

Available types: note, tip, warning, caution, important.

Executable code cells

Embed live Python examples that run during the build:

markdown
```{python}
import great_docs
gd = great_docs.GreatDocs()
print(gd.project_path)
```

{python} vs {.python}: this distinction is critical.

  • {python} (no dot) creates an executable code cell. Quarto runs it through the Jupyter kernel during the build and captures the output.
  • {.python} (with a dot) creates a display-only code block. Quarto syntax-highlights it but never executes it.

Use {python} when the output matters (tables, plots, printed values). Use {.python} for illustrative snippets where execution is unnecessary or undesirable.

Additional cell-level controls:

  • Use #| eval: false to show code without executing it.
  • Use #| echo: false to show only the output.
Table previews and explorers

When a page involves sample datasets or transformed DataFrames, use the built-in table widgets instead of raw print() output.

Shortcodes (for static data files in assets/data/):

markdown
{{< tbl-preview file="assets/data/students.csv" >}}
{{< tbl-explorer file="assets/data/students.csv" >}}

Python API (for DataFrames produced in executable cells):

markdown
```{python}
from great_docs import tbl_preview, tbl_explorer

tbl_preview(df)           # compact head/tail preview
tbl_explorer(df)          # interactive: sort, filter, paginate
```

Use tbl-preview (or tbl_preview()) for a quick glance at a dataset. Use tbl-explorer (or tbl_explorer()) when readers need to sort, search, or paginate the data. Both accept Pandas DataFrames, Polars DataFrames, and file paths (CSV, TSV, Parquet, Arrow, JSONL).

Cross-references

Link to other pages in the site:

markdown
See the [Configuration](../user-guide/configuration.qmd) page.
See the [API reference](../reference/GreatDocs.qmd) page.

Use relative paths from the rendered output location (great-docs/user-guide/), not the source.

Show full SKILL.md (297 more words)Show less
Images and assets

Place images in assets/ at the project root:

markdown
![Architecture diagram](../assets/architecture.png)

Great Docs copies the assets/ directory into the build automatically.

Workflows

Adding a new page
Task Progress:
- [ ] Step 1: Choose a filename
- [ ] Step 2: Write frontmatter
- [ ] Step 3: Write content
- [ ] Step 4: Build and preview

Step 1: Pick the next numeric prefix. If the last file is 08-user-guides.qmd, name your file 09-new-topic.qmd.

Step 2: Add frontmatter with title, guide-section, and optional tags.

Step 3: Write the body using the page structure guidelines above.

Step 4: Run great-docs build && great-docs preview and check the sidebar ordering and rendered content.

Reorganizing existing pages
  1. Rename files to adjust numeric prefixes.
  2. Update guide-section values to regroup.
  3. Rebuild. Great Docs regenerates the sidebar automatically.
  4. Check for broken cross-references.
Converting a README into a guide page
  1. Copy the README content into a new .qmd file.
  2. Add frontmatter with title and guide-section.
  3. Replace any GitHub-flavored Markdown extensions with Quarto equivalents (e.g., > [!NOTE] → :::{.callout-note}).
  4. Rebuild and verify.

Gotchas

  1. Numeric prefixes control ordering by default. Without them, pages sort alphabetically. Alternatively, you can omit prefixes and define an explicit page order in great-docs.yml.
  2. Don't skip numbers. Gaps are fine (01, 03, 05) but large jumps make it hard to insert pages later.
  3. Title must match the # heading. If title: "Foo" but the body starts with # Bar, the sidebar says "Foo" but the page says "Bar".
  4. guide-section is case-sensitive. "Getting Started" and "getting started" create separate sections.
  5. Don't nest directories. All pages must be directly in user_guide/, not in subdirectories.
  6. Hyphens, not underscores, in filenames. Great Docs converts underscores to hyphens in URLs, so my_page.qmd becomes my-page.html.
  7. Lists need a blank line before them. A bullet or numbered list that immediately follows a paragraph (no blank line) will not be parsed as a list by Quarto; it renders as plain text.

© pymc-labs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .agents/skills/write-user-guide of pymc-labs/pathmc.

  • SKILL.md
  • references/page-anatomy.md
  • references/writing-guidelines.md

Open the folder on GitHubat commit e3b9467

Compare with similar skills

Write User Guide next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Write User Guide compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Write User Guide this skillpymc-labs/pathmc132—~2.3kAutomated safety check: PassMIT
Docs Websitekurotu/VRCQuestTools373—~1.3kAutomated safety check: PassMIT
Doc Writermicrosoft/aspire.dev196—~7.6kAutomated safety check: PassMIT
JavaScript Concept Fact Checkerleonardomso/33-js-concepts67k1 repos~5kAutomated safety check: PassMIT
Beads Documentation Style Guidegastownhall/beads28k—~3.2kAutomated safety check: PassMIT
JavaScript Concept Page Workflowleonardomso/33-js-concepts67k—~3.9kAutomated safety check: PassMIT

Similar skills

  • Docs Website

    kurotu/VRCQuestTools

    Use this skill FIRST for any task whose output lives in the Website/ directory — the VRCQuestTools user manual / docs site (Docusaurus, bilingual en/ja).

    373 GitHub stars~1.3k tokensUpdated 7 days ago
    Writing & ContentAuto-check passed
  • Doc Writer

    microsoft/aspire.dev

    Official

    Guidelines for producing accurate and maintainable documentation for the Aspire documentation site.

    196 GitHub stars~7.6k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • JavaScript Concept Fact Checker

    leonardomso/33-js-concepts

    Verifies the technical accuracy of JavaScript concept pages by checking code examples, MDN and ECMAScript claims and external links through a five-phase method.

    67k GitHub starsUsed in 1 repo~5k tokens
    Writing & ContentAuto-check passed
  • Sets the house style for the beads user docs: the canonical concept model, required terminology, prose and diagram conventions, and checks before docs work is done.

    28k GitHub stars~3.2k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • JavaScript Concept Page Workflow

    leonardomso/33-js-concepts

    Orchestrates five skills to produce a complete JavaScript concept documentation page, from resource curation through writing, tests, fact-checking and SEO.

    67k GitHub stars~3.9k tokensUpdated 27 days ago
    Writing & ContentAuto-check passed
  • JS Concept Resource Curator

    leonardomso/33-js-concepts

    Finds, vets, writes up and maintains external articles, videos and courses for JavaScript concept pages, including audits for broken and outdated links.

    67k GitHub stars~4.9k tokensUpdated 27 days ago
    Writing & ContentAuto-check passed

More from pymc-labs/pathmc

  • Great Docs

    pymc-labs/pathmc

    Generate documentation sites for Python packages with Great Docs.

    132 GitHub stars~2.7k tokensUpdated 5 days ago
    Auto-check passed
  • Author Skills

    pymc-labs/pathmc

    Author, configure, and distribute Agent Skills for a Great Docs site.

    132 GitHub stars~2.6k tokensUpdated 5 days ago
    Auto-check passed
  • Configure Site

    pymc-labs/pathmc

    Configure a Great Docs documentation site through great-docs.yml.

    132 GitHub stars~2k tokensUpdated 5 days ago
    Auto-check passed
  • Revise Docstrings

    pymc-labs/pathmc

    Review and improve Python docstrings for Great Docs API reference generation.

    132 GitHub stars~2.3k tokensUpdated 5 days ago
    Auto-check passed
  • Fix Bug

    pymc-labs/pathmc

    Autonomous bug-fix workflow. An agent skill from pymc-labs/pathmc.

    132 GitHub stars~4.6k tokensUpdated 5 days ago
    Auto-check passed
  • Pathmc

    pymc-labs/pathmc

    Bayesian path analysis (observed-variable SEM) in PyMC. An agent skill from pymc-labs/pathmc.

    132 GitHub stars~4k tokensUpdated 5 days ago
    Auto-check passed

Questions about Write User Guide

What does Write User Guide do?

Write and maintain narrative user-guide pages for a Great Docs site. Write User Guide is an agent skill from pymc-labs/pathmc. Write and maintain narrative user-guide pages for a Great Docs site.

When should I use Write User Guide?

Write User Guide fits situations like: improving user-guide content; tasks that involve Technical writing; tasks that involve Static sites and blogs.

How do I install Write User Guide in Claude Code?

Run `npx skills add pymc-labs/pathmc --skill write-user-guide -a claude-code`. Or copy the skill folder (.agents/skills/write-user-guide in pymc-labs/pathmc) into .claude/skills/write-user-guide in your project. Claude Code loads it when a task matches its description.

How do I install Write User Guide in Codex?

Run `npx skills add pymc-labs/pathmc --skill write-user-guide -a codex`. Or copy the skill folder (.agents/skills/write-user-guide in pymc-labs/pathmc) into .agents/skills/write-user-guide in your project. Codex loads it when a task matches its description.

Can I use Write User Guide in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pymc-labs/pathmc --skill write-user-guide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-user-guide, .gemini/skills/write-user-guide, .github/skills/write-user-guide and .opencode/skills/write-user-guide in your project.

What does Write User Guide need to run?

SKILL.md names no scripts, command-line tools or credentials: Write User Guide is instructions for the agent only. Our summary lists: Python 3. Compatibility (from SKILL.md): Requires Great Docs >=0.8, Quarto CLI installed..

Does Write User Guide access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Write User Guide safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Write User Guide use?

Write User Guide is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Write User Guide use?

About 2.3k tokens (SKILL.md is roughly 9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.1k tokens, read only when the agent opens those files.

What are the alternatives to Write User Guide?

Skills that share tags, products or a category with Write User Guide: Docs Website (kurotu/VRCQuestTools, 373 stars), Doc Writer (microsoft/aspire.dev, 196 stars), JavaScript Concept Fact Checker (leonardomso/33-js-concepts, 67k stars) and Beads Documentation Style Guide (gastownhall/beads, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Write User Guide?

pymc-labs (a GitHub organization) maintains it in pymc-labs/pathmc, which has 132 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 2, 2026.

Source: pymc-labs/pathmc on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.