documentation-style

A set of instructions for checking project documentation against a defined writing and markup style guide. MyST and reST are text formats commonly used for structured technical documentation.

In plain words
What is it for?
Use it when reviewing or validating project documentation and reporting specific style-guide violations.
Why use it?
It helps find inconsistent tone, terminology, punctuation, formatting, or invalid documentation syntax.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/canonical/workshop/documentation-style
Any agent
npx skills add canonical/workshop --skill documentation-style
Clone the repo
git clone --depth 1 https://github.com/canonical/workshop

Made for: Claude Code, Codex.

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 599 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00042 $0.00599
Opus 5 $0.00021 $0.00300
Sonnet 5 $0.00008 $0.00120
Haiku 4.5 $0.00004 $0.00060

Measured 2d ago against content hash 53910266335e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

documentation-style scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/skills/documentation-style/SKILL.md · 75 lines

The source is not reproduced here

Licensed GPL-3.0

The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 75 lines · 42 tokens per session scan A 53910266335e

Subscribe to this mod's changes

documentation-style is a skill published in the GitHub repository canonical/workshop (105 stars, last pushed 5d ago), licensed GPL-3.0. It adds 42 tokens to every session and 599 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

toolset-design

Design and validate new MCP toolsets, tools, and tool changes. Use when planning a new toolset, adding tools to an existing toolset, reviewing a toolset PR, or deciding whether a new tool is warranted. Covers the full lifecycle: eval-first validation, tool design methodology, consolidation patterns, and review…

containers/kubernetes-mcp-server · 69 tokens

gf_agent

Specialized agent for automating Google Workspace tasks locally using gas-fakes. Generates and executes Google Apps Script code on Node.js.

brucemcpherson/gas-fakes · 29 tokens

gas-fakes-dev

Develop and implement the 'gas-fakes' project, emulating Google Apps Script (GAS) functionality using Node.js.

brucemcpherson/gas-fakes · 30 tokens

gassypedia-database

Comprehensive schema reference and natural language query guide for the Gassypedia BigQuery dataset (scrmin.gassypedia) and its central view 'bigjoin'. Use this to translate user questions into optimized SQL queries or test scripts.

brucemcpherson/gas-fakes · 55 tokens

neon-postgres

Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related…

brucemcpherson/gas-fakes · 76 tokens

gf-agent-contributor

Guide for creating or contributing modular knowledge to the gfagent skill. Use this when a user wants to teach gfagent a new trick or document an Apps Script parity oddity.

brucemcpherson/gas-fakes · 40 tokens