Release
sol4k/sol4k
Bump the sol4k library version everywhere, open a release PR, and draft GitHub release notes.
MkDocs documentation project reference covering CLI commands, mkdocs.yml configuration, Material theme setup, and plugin integration.
$ npx skills add jeka-dev/jeka --skill mkdocs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeka-dev/jeka mkdocs --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/jeka-dev/jeka.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/mkdocs .claude/skills/mkdocs && 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 "mkdocs" agent skill from https://github.com/jeka-dev/jeka/tree/master/.claude/skills/mkdocs into .claude/skills/mkdocs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mkdocs", 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/jeka-dev/jeka/tree/master/.claude/skills/mkdocsType 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 jeka-dev/jeka --skill mkdocs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeka-dev/jeka mkdocs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeka-dev/jeka.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/mkdocs .agents/skills/mkdocs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mkdocs" agent skill from https://github.com/jeka-dev/jeka/tree/master/.claude/skills/mkdocs into .agents/skills/mkdocs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mkdocs", 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 jeka-dev/jeka --skill mkdocs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeka-dev/jeka mkdocs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeka-dev/jeka.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/mkdocs .cursor/skills/mkdocs && 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 "mkdocs" agent skill from https://github.com/jeka-dev/jeka/tree/master/.claude/skills/mkdocs into .cursor/skills/mkdocs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mkdocs", 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/jeka-dev/jeka.git --path .claude/skills/mkdocs--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 jeka-dev/jeka --skill mkdocs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeka-dev/jeka mkdocs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeka-dev/jeka.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/mkdocs .gemini/skills/mkdocs && 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 "mkdocs" agent skill from https://github.com/jeka-dev/jeka/tree/master/.claude/skills/mkdocs into .gemini/skills/mkdocs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mkdocs", 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 jeka-dev/jeka mkdocsInstalls 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 jeka-dev/jeka --skill mkdocs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeka-dev/jeka.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/mkdocs .github/skills/mkdocs && 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 "mkdocs" agent skill from https://github.com/jeka-dev/jeka/tree/master/.claude/skills/mkdocs into .github/skills/mkdocs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mkdocs", 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 jeka-dev/jeka --skill mkdocs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeka-dev/jeka mkdocs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeka-dev/jeka.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/mkdocs .opencode/skills/mkdocs && 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 "mkdocs" agent skill from https://github.com/jeka-dev/jeka/tree/master/.claude/skills/mkdocs into .opencode/skills/mkdocs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mkdocs", 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.
mkdocsMkDocs documentation project reference covering CLI commands, mkdocs.yml configuration, Material theme setup, and plugin integration.
Mkdocs is an agent skill from jeka-dev/jeka. MkDocs documentation project reference covering CLI commands, mkdocs.yml configuration, Material theme setup, and plugin integration. Bundled references include complete CLI parameters, all mkdocs.yml settings with valid values, Material theme customization options, and plugin configs for mkdocstrings, mermaid2, mkdocs-gen-files, mkdocs-literate-nav, and mkdocs-typer2. Use when initializing a MkDocs site, configuring mkdocs.yml, customizing the Material theme, integrating plugins, building static docs from…
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including scripts, reference files and assets (for example `.skillfish.json`, `references/cli_reference.md` and `references/configuration_reference.md`).
It sits in Development, covering Technical documentation. It works with Python, Java and Kotlin. The repository describes itself as: Next-Gen Build Tool for Java & Co. The licence is Apache-2.0.
Read from SKILL.md and the folder at commit b463563. 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.
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pipFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comunpkg.comFrom 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.
Mkdocs loads about 2k tokens when it runs, and up to ~24k if it reads all its reference files. Until then it costs about 146 tokens; SKILL.md has 366 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); the scripts in this folder are not scanned.
The full file from jeka-dev/jeka at commit b463563, republished under its Apache-2.0 licence (© jeka-dev). 366 words, ~1,980 tokens.
.claude/skills/mkdocs/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.This skill provides reference material and guidance for working with MkDocs documentation sites — including mkdocs.yml configuration, the Material theme, plugins, and CLI usage.
Loaded references (read them before acting):
references/configuration_reference.md — all mkdocs.yml keys with valid valuesreferences/material_theme_reference.md — Material theme features, palette, features flags, fontsreferences/cli_reference.md — mkdocs build/serve/gh-deploy optionsreferences/plugins_reference.md — mkdocstrings, mermaid2, gen-files, literate-nav, typer2references/real_world_examples.md — production-grade mkdocs.yml patternsWhat do you need to do?
│
├── Initialize a new site ──────────────────→ [Init]
├── Fix / improve mkdocs.yml ───────────────→ [Configure]
├── Customize the Material theme ───────────→ [Theme]
├── Add or configure plugins ───────────────→ [Plugins]
├── Improve doc content / structure ────────→ [Content]
└── Deploy (GitHub Pages, CI) ──────────────→ [Deploy]pip install mkdocs-material
mkdocs new my-project
cd my-project
mkdocs serve # preview at http://127.0.0.1:8000Minimal mkdocs.yml to start with Material:
site_name: My Project
theme:
name: material
font:
text: Roboto
code: Roboto Mono
features:
- navigation.instant
- navigation.tracking
- content.code.copy
repo_url: https://github.com/org/repo
edit_uri: edit/main/docs/Font note: Code font must be a valid Google Font. Common choices:
Roboto Mono,Fira Code,JetBrains Mono,Source Code Pro.Fire Codeis NOT a valid font name.
edit_uri (not edit_url)The correct top-level key is edit_uri. It must NOT be placed under theme:.
# ✅ Correct
repo_url: https://github.com/org/repo
edit_uri: edit/main/docs/
# ❌ Wrong — edit_url under theme: is ignored
theme:
edit_url: https://github.com/org/repo/main/docs/The edit_uri value is appended to repo_url, so for GitHub the path should include edit/<branch>/:
edit/main/docs/ → produces https://github.com/org/repo/edit/main/docs/page.mdFiles present in docs/ but absent from nav: produce warnings and are unreachable from the site.
Always keep nav: in sync with the actual files.
nav:
- Home: index.md
- Installation: installation.md
- Tutorials:
- Basics: tutorials/basics.md
- Migration Guide: migration-guide.md # don't forget orphan filesUse not_in_nav for files intentionally excluded from nav (e.g. auto-generated API pages):
not_in_nav: |
api/**
tags.mdEnable in CI to catch broken links and missing pages:
strict: truetheme:
name: material
palette:
- scheme: default
primary: deep purple
accent: purple
toggle:
icon: material/brightness-7
name: Switch to dark mode
- scheme: slate
primary: deep purple
accent: purple
toggle:
icon: material/brightness-4
name: Switch to light modetheme:
font:
text: Inter # body text — any Google Font
code: Fira Code # monospace — must be a valid Google Font nameTo disable Google Fonts (privacy / offline):
theme:
font: falsetheme:
features:
- navigation.instant # SPA-style instant loading
- navigation.tracking # anchor tracking in URL
- navigation.tabs # top-level sections as tabs
- navigation.sections # render sections in sidebar
- navigation.expand # expand all sections by default
- navigation.top # back-to-top button
- navigation.footer # prev/next links in footer
- toc.follow # sidebar TOC follows scroll
- content.code.copy # copy button on code blocks
- content.action.edit # "Edit this page" button (requires edit_uri)
- search.suggest # search autocomplete
- search.highlight # highlight search terms on pagetheme:
logo: images/logo.svg
favicon: images/favicon.png
icon:
repo: fontawesome/brands/githubNo extra plugin needed — use pymdownx.superfences:
markdown_extensions:
- pymdownx.superfences:
custom_fences:
- name: mermaid
class: mermaid
format: !!python/name:pymdownx.superfences.fence_code_format
extra_javascript:
- https://unpkg.com/mermaid@10/dist/mermaid.min.jsplugins:
- search:
separator: '[\s\-\.]+'
lang: enplugins:
- git-revision-date-localized:
enable_creation_date: true
type: timeagoplugins:
- mkdocstrings:
handlers:
python:
options:
docstring_style: google
show_source: true!!! note
Use for supplementary information.
!!! tip
Use for helpful hints.
!!! warning
Use for potential pitfalls.
??? example "Collapsible example"
Hidden by default, click to expand.Requires admonition and pymdownx.details extensions.
```python title="my_module.py" hl_lines="2 3"
def hello():
name = "world"
print(f"Hello {name}")
```Requires pymdownx.highlight and pymdownx.superfences.
=== "Python"
```python
print("hello")
```
=== "Java"
```java
System.out.println("hello");
```Requires pymdownx.tabbed with alternate_style: true.
# .github/workflows/docs.yml
name: Deploy docs
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0 # needed for git-revision-date plugin
- uses: actions/setup-python@v5
with:
python-version: '3.x'
- run: pip install mkdocs-material
- run: mkdocs gh-deploy --forceBefore reporting an mkdocs.yml as correct, check:
site_name is settheme.name is material (or another installed theme)theme.font.code is a real Google Font name (not Fire Code — it's Fira Code)edit_uri is at top level, not under theme:, and includes edit/<branch>/docs/ referenced by nav: actually exists.md file in docs/ is reachable via nav: or listed under not_in_nav:pymdownx.superfences is not listed twice (it's a common dupe)G-XXXXXXXX format (UA- is legacy)strict: true is set (or recommended) for CI builds© jeka-dev, Apache-2.0. 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 8 other files (scripts, references, assets) in .claude/skills/mkdocs of jeka-dev/jeka.
Open the folder on GitHubat commit b463563
Mkdocs 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 |
|---|---|---|---|---|---|---|
| Mkdocs this skilljeka-dev/jeka | 176 | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Releasesol4k/sol4k | 135 | — | ~949 | Automated safety check: Pass | Apache-2.0 | |
| Code Revieweralirezarezvani/claude-skills | 28k | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Lc Javayennanliu/CS_basics | 142 | — | ~5.2k | Automated safety check: Notes | None | |
| Lc Pythonyennanliu/CS_basics | 142 | — | ~4.4k | Automated safety check: Notes | None | |
| Code Comment GeneratorArabelaTso/Skills-4-SE | 253 | — | ~4.6k | Automated safety check: Pass | Apache-2.0 |
sol4k/sol4k
Bump the sol4k library version everywhere, open a release PR, and draft GitHub release notes.
alirezarezvani/claude-skills
Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin, C, .NET, Java, C, C++, Rust, Ruby, PHP, and Dart/Flutter.
yennanliu/CS_basics
File a LeetCode Java solution into this repo the way the existing ones are filed — put it in the package its pattern owns, write the file-level javadoc header (<number.
yennanliu/CS_basics
File a LeetCode Python solution into this repo the way the existing ones are filed — find the problem's real slug, write the Python file in the house layout (problem docstring, V0 with an IDEA block…
ArabelaTso/Skills-4-SE
Generates meaningful comments and documentation for code to improve maintenance and readability.
afkT/DevUtils
新增或修改 DevUtils DevEngine 第三方框架解耦实现:读取 DevAssist Engine 接口、DevEngine core 实现、 extensions 调用入口、默认初始化和 README,实现 JSON、Log、Image、Permission、Toast 等 Engine; 在用户要求创建某个功能 Engine、新增 Engine 实现、替换第三方库或扩展…
Categories
MkDocs documentation project reference covering CLI commands, mkdocs.yml configuration, Material theme setup, and plugin integration. Mkdocs is an agent skill from jeka-dev/jeka.yml configuration, Material theme setup, and plugin integration.
Mkdocs fits situations like: initializing a MkDocs site; configuring mkdocs.yml; customizing the Material theme; integrating plugins.
Run `npx skills add jeka-dev/jeka --skill mkdocs -a claude-code`. Or copy the skill folder (.claude/skills/mkdocs in jeka-dev/jeka) into .claude/skills/mkdocs in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jeka-dev/jeka --skill mkdocs -a codex`. Or copy the skill folder (.claude/skills/mkdocs in jeka-dev/jeka) into .agents/skills/mkdocs 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 jeka-dev/jeka --skill mkdocs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mkdocs, .gemini/skills/mkdocs, .github/skills/mkdocs and .opencode/skills/mkdocs in your project.
Going by SKILL.md and its folder, Mkdocs needs Python for the scripts in its folder and the command-line tools its instructions call (pip). Our summary lists: Python 3.
SKILL.md names 2 domains. In commands or code: github.com and unpkg.com; the agent is likely to contact these when it follows the instructions. 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Mkdocs is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2k tokens (SKILL.md is roughly 7.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 22k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Mkdocs: Release (sol4k/sol4k, 135 stars), Code Reviewer (alirezarezvani/claude-skills, 28k stars), Lc Java (yennanliu/CS_basics, 142 stars) and Lc Python (yennanliu/CS_basics, 142 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jeka-dev (a GitHub organization) maintains it in jeka-dev/jeka, which has 176 GitHub stars. The repository was last updated on July 17, 2026.
Source: jeka-dev/jeka on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.