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).
Write and maintain narrative user-guide pages for a Great Docs site.
$ npx skills add pymc-labs/pathmc --skill write-user-guide -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pymc-labs/pathmc write-user-guide --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "write-user-guide" agent skill from https://github.com/pymc-labs/pathmc/tree/main/.agents/skills/write-user-guide into .claude/skills/write-user-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-user-guide", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pymc-labs/pathmc/tree/main/.agents/skills/write-user-guideType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pymc-labs/pathmc --skill write-user-guide -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pymc-labs/pathmc write-user-guide --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pymc-labs/pathmc.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/write-user-guide .agents/skills/write-user-guide && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-user-guide" agent skill from https://github.com/pymc-labs/pathmc/tree/main/.agents/skills/write-user-guide into .agents/skills/write-user-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-user-guide", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pymc-labs/pathmc --skill write-user-guide -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pymc-labs/pathmc write-user-guide --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pymc-labs/pathmc.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/write-user-guide .cursor/skills/write-user-guide && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "write-user-guide" agent skill from https://github.com/pymc-labs/pathmc/tree/main/.agents/skills/write-user-guide into .cursor/skills/write-user-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-user-guide", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pymc-labs/pathmc.git --path .agents/skills/write-user-guide--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pymc-labs/pathmc --skill write-user-guide -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pymc-labs/pathmc write-user-guide --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pymc-labs/pathmc.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/write-user-guide .gemini/skills/write-user-guide && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "write-user-guide" agent skill from https://github.com/pymc-labs/pathmc/tree/main/.agents/skills/write-user-guide into .gemini/skills/write-user-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-user-guide", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pymc-labs/pathmc write-user-guideInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pymc-labs/pathmc --skill write-user-guide -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pymc-labs/pathmc.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/write-user-guide .github/skills/write-user-guide && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "write-user-guide" agent skill from https://github.com/pymc-labs/pathmc/tree/main/.agents/skills/write-user-guide into .github/skills/write-user-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-user-guide", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pymc-labs/pathmc --skill write-user-guide -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pymc-labs/pathmc write-user-guide --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pymc-labs/pathmc.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/write-user-guide .opencode/skills/write-user-guide && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "write-user-guide" agent skill from https://github.com/pymc-labs/pathmc/tree/main/.agents/skills/write-user-guide into .opencode/skills/write-user-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-user-guide", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
write-user-guideWrite 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. 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.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit e3b9467. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Requires Great Docs >=0.8, Quarto CLI installed.
From compatibility in the SKILL.md frontmatter.
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.
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.
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.
The full file from pymc-labs/pathmc at commit e3b9467, republished under its MIT licence (© pymc-labs). 761 words, ~2,255 tokens.
.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.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.
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 buildskills/write-user-guide/
├── SKILL.md
└── references/
├── page-anatomy.md
└── writing-guidelines.md| Need | Action |
|---|---|
| Add a new guide page | Create user_guide/NN-topic.qmd |
| Reorder pages | Rename numeric prefixes |
| Group pages into sections | Set guide-section in frontmatter |
| Add an interactive example | Use {python} code cells in the .qmd |
| Cross-reference another page | Use [text](../user-guide/page.qmd) links |
| Embed a callout | Use :::{.callout-tip} / :::{.callout-note} |
| Add images | Place in assets/ and reference from QMD |
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.qmdGreat Docs strips the prefix for clean URLs:
00-introduction.qmd → user-guide/introduction.html.
Every user-guide page starts with YAML frontmatter:
---
title: "Writing Docstrings"
guide-section: "Getting Started"
tags: [API, Content]
---Required keys:
| Key | Description |
|---|---|
title | Page heading and sidebar label |
Optional keys:
| Key | Description |
|---|---|
guide-section | Group pages under a sidebar section header |
tags | Content tags for discoverability |
bread-crumbs | Set false to hide breadcrumb navigation |
status | Page status badge: experimental, new, stable |
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 GuidesIf no guide-section is set, the page appears at the top level.
A well-structured page follows this outline:
# 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:
# heading matching the title.## for major sections, ### for subsections.#### if possible.Quarto callouts highlight important information:
:::{.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.
Embed live Python examples that run during the build:
```{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:
#| eval: false to show code without executing it.#| echo: false to show only the output.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/):
{{< tbl-preview file="assets/data/students.csv" >}}
{{< tbl-explorer file="assets/data/students.csv" >}}Python API (for DataFrames produced in executable cells):
```{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).
Link to other pages in the site:
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.
Place images in assets/ at the project root:
Great Docs copies the assets/ directory into the build
automatically.
Task Progress:
- [ ] Step 1: Choose a filename
- [ ] Step 2: Write frontmatter
- [ ] Step 3: Write content
- [ ] Step 4: Build and previewStep 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.
guide-section values to regroup..qmd file.title and guide-section.> [!NOTE] → :::{.callout-note}).great-docs.yml.01, 03, 05) but
large jumps make it hard to insert pages later.# heading. If title: "Foo" but
the body starts with # Bar, the sidebar says "Foo" but the
page says "Bar".guide-section is case-sensitive. "Getting Started" and
"getting started" create separate sections.user_guide/, not in subdirectories.my_page.qmd becomes
my-page.html.© 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
SKILL.md and 2 other files (references) in .agents/skills/write-user-guide of pymc-labs/pathmc.
Open the folder on GitHubat commit e3b9467
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Write User Guide this skillpymc-labs/pathmc | 132 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Docs Websitekurotu/VRCQuestTools | 373 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Doc Writermicrosoft/aspire.dev | 196 | — | ~7.6k | Automated safety check: Pass | MIT | |
| JavaScript Concept Fact Checkerleonardomso/33-js-concepts | 67k | 1 repos | ~5k | Automated safety check: Pass | MIT | |
| Beads Documentation Style Guidegastownhall/beads | 28k | — | ~3.2k | Automated safety check: Pass | MIT | |
| JavaScript Concept Page Workflowleonardomso/33-js-concepts | 67k | — | ~3.9k | Automated safety check: Pass | MIT |
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).
microsoft/aspire.dev
Guidelines for producing accurate and maintainable documentation for the Aspire documentation site.
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.
gastownhall/beads
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.
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.
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.
pymc-labs/pathmc
Generate documentation sites for Python packages with Great Docs.
pymc-labs/pathmc
Author, configure, and distribute Agent Skills for a Great Docs site.
pymc-labs/pathmc
Configure a Great Docs documentation site through great-docs.yml.
pymc-labs/pathmc
Review and improve Python docstrings for Great Docs API reference generation.
pymc-labs/pathmc
Autonomous bug-fix workflow. An agent skill from pymc-labs/pathmc.
pymc-labs/pathmc
Bayesian path analysis (observed-variable SEM) in PyMC. An agent skill from pymc-labs/pathmc.
Categories
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.
Write User Guide fits situations like: improving user-guide content; tasks that involve Technical writing; tasks that involve Static sites and blogs.
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.
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.
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.
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..
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.
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.
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.
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.
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.
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.