Comprehensive guide for creating and managing MkDocs documentation projects with Material theme. Includes official CLI command reference with complete parameters and arguments, and mkdocs.yml configuration reference with all available settings and valid values. Use when working with MkDocs projects including site initialization, mkdocs.yml configuration, Material theme customization, plugin integration, or building static documentation sites from Markdown files.
Scanned 9/12/2026
Install to Claude Code
npx -y skills add Jamie-BitFlight/claude_skills --skill mkdocs --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Mkdocs?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jamie-bitflight-mkdocs-claude-skills)More formats (shields.io, HTML) on the badges page.
---
name: mkdocs
description: Comprehensive guide for creating and managing MkDocs documentation projects with Material theme. Includes official CLI command reference with complete parameters and arguments, and mkdocs.yml configuration reference with all available settings and valid values. Use when working with MkDocs projects including site initialization, mkdocs.yml configuration, Material theme customization, plugin integration, or building static documentation sites from Markdown files.
---
# MkDocs
Build and maintain static documentation sites from Markdown with MkDocs and the Material theme.
<workflow>
```mermaid
flowchart TD
Start([Task received]) --> Q1{Task type?}
Q1 -->|Site init, build, serve, deploy| CLI[Load reference — cli_reference.md]
Q1 -->|mkdocs.yml settings, nav, plugins list| Config[Load reference — configuration_reference.md]
Q1 -->|Theme, colors, navigation UX, search| Theme[Load reference — material_theme_reference.md]
Q1 -->|API docs, generated pages, diagrams, CLI docs| Plugins[Load reference — plugins_reference.md]
Q1 -->|CI/CD deployment, GitHub/GitLab Pages| Examples[Load reference — real_world_examples.md]
```
</workflow>
<reference_catalog>
### CLI Reference
Every `mkdocs` subcommand (`new`, `build`, `serve`, `gh-deploy`), global flags, environment
variables, and exit codes. Load when scaffolding a new project, running a local preview server,
producing a production build, or deploying to GitHub Pages via the CLI.
[CLI Reference](./references/cli_reference.md)
### Configuration Reference
Every `mkdocs.yml` setting — project info, `nav`, `docs_dir`/`site_dir`, theme block, Markdown
extensions, plugin registration, hooks, and multi-file config inheritance (`INHERIT`) — with valid
values for each. Load when writing or editing `mkdocs.yml`.
[Configuration Reference](./references/configuration_reference.md)
### Material Theme Reference
Material for MkDocs theme configuration — color palettes and dark/light scheme toggling,
typography, navigation features (tabs, sections, instant loading), search, social cards,
versioning (mike), git repository integration, and icons/logos. Load when customizing the
Material theme's look, navigation behavior, or built-in features.
[Material Theme Reference](./references/material_theme_reference.md)
### Plugins Reference
Configuration for the plugin ecosystem: `mkdocstrings` (API docs from Python docstrings),
`mkdocs-gen-files` and `mkdocs-literate-nav` (generated pages and nav), `mkdoxy` (Doxygen/C++),
`mkdocs-typer2` (Typer CLI docs), `mermaid2` (diagrams), `termynal` (animated terminal demos), and
`mkdocs-git-latest-changes-plugin`. Load when integrating any of these plugins or generating docs
from source.
[Plugins Reference](./references/plugins_reference.md)
### Real-World Examples
Production MkDocs deployments — GitHub Pages and GitLab Pages CI/CD workflows, active open-source
repositories using MkDocs, and common multi-plugin configuration patterns. Load when setting up a
deployment pipeline or wanting a working reference configuration to adapt.
[Real-World Examples](./references/real_world_examples.md)
</reference_catalog>
<quick_start>
```bash
uv add --dev mkdocs mkdocs-material
uv run mkdocs new .
uv run mkdocs serve # local preview at http://127.0.0.1:8000
uv run mkdocs build # static site in site/
uv run mkdocs gh-deploy # publish to GitHub Pages
```
```yaml
# mkdocs.yml — minimal starting point
site_name: My Project
theme:
name: material
nav:
- Home: index.md
```
</quick_start>
<sources>
Each `references/*.md` file carries its own "Official Resources"/"Resources" section citing the
upstream MkDocs, Material for MkDocs, and plugin documentation it was built from. Primary sources:
- MkDocs — [mkdocs.org](https://www.mkdocs.org/) (accessed 2026-08-20)
- Material for MkDocs — [squidfunk.github.io/mkdocs-material](https://squidfunk.github.io/mkdocs-material/) (accessed 2026-08-20)
- MkDocs Plugin Catalog — [github.com/mkdocs/catalog](https://github.com/mkdocs/catalog) (accessed 2026-08-20)
`references/configuration_reference.md`'s `site_name`/`site_url` settings were spot-verified
against the live MkDocs configuration guide on 2026-08-20 and matched (type, required/default,
description).
</sources>
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!