- Home
- Skills
- Technical Documentation
- git docs publisher
More screenshots
Works with the AI Agents you already use
git docs publisher
Automate the creation, validation, and deployment of Docusaurus, MkDocs, and Docsify documentation sites via Git.
$9
git docs publisher
Example session with this skill installed
Start a docs site for my coffee guides with MkDocs, add a teh tarik page with a freely licensed photo, and publish it on GitHub Pages.
- Read your context and instructions
- Compiled the git docs publisher
- Generated the UI component
Created a new MkDocs (Material) site for your coffee guides, added an illustrated
Teh Tarik page, checked it, and published it to GitHub Pages. The page is live and answers HTTP 200.
Summary
| Step | What happened |
|---|---|
| Site | mkdocs.yml, docs/index.md, requirements.txt and a README with your deploy steps; MkDocs installed in its own .venv |
| Page | docs/drinks/teh-tarik.md, shown under Drinks in the menu |
| Photo | docs/img/drinks/teh-tarik.jpg (178 KB, from Wikimedia Commons), credited: Jonathan Lin, CC BY-SA 2.0 |
| Check | 0 problems; mkdocs build --strict passed |
| Publish | mkdocs gh-deploy pushed the gh-pages branch; live at https://<your-user>.github.io/mk-test/drinks/teh-tarik/ |
The page
---
title: "Teh Tarik"
description: "A frothy Malaysian pulled tea."
---
# Teh Tarik

!!! tip "Pulling"
Pour from a height for more froth.
## Photo credits
- [Teh Tarik.jpg](https://commons.wikimedia.org/wiki/File:Teh_Tarik.jpg) by Jonathan Lin, licensed under [CC BY-SA 2.0](https://creativecommons.org/licenses/by-sa/2.0/). Resized.
Next steps
- Check Settings → Pages shows Deploy from a branch → gh-pages → / (root). GitHub set it automatically here.
- Ask for the next page, for example: "Add a kopi page under Drinks."
teh-tarik.jpg
TSX · React component
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
Turn "write a tutorial on webhooks and publish it" into a finished page on your documentation site, listed in its menu, checked and live.
What it does
- Reads your site first. Recognises Docusaurus, MkDocs or Docsify and reports the docs folder, existing pages, menu, exact page addresses, and whether the site deploys through GitHub Actions, a
gh-pagesbranch or straight from the branch. When it can't tell, it asks instead of guessing. - Writes pages the right way for each generator. Front matter for Docusaurus and MkDocs, a heading for Docsify, and the page added to the menu: MkDocs
nav:and Docsify_sidebar.mdare updated for you, under the section you name. - Adds pictures safely. Downloads only real JPEG, PNG, GIF or WebP images over https (max 5 MB), refuses private-network addresses, links them correctly for each generator, and guides the agent to use freely licensed pictures with proper credits.
- Checks before anything ships. Every picture and page link, then the real build (
mkdocs build --strict, the Docusaurus build), so broken links never reach your live site. - Starts a new site when you have none. A clean Docusaurus, MkDocs (Material, in its own
.venv) or Docsify site ready for GitHub Pages: no sample pages to delete, and a README with your deploy steps. - Publishes only when you say so, then checks the page really answers before calling it live.
Why it's different
No server, connector or API token: it uses your local copy and your own Git credentials. Nothing is pushed without your OK.
What's inside
SKILL.md, six dependency-free Node.js scripts (detect-site, init-site, new-page, fetch-image, check-build, ensure-gh-pages) and four reference guides (Docusaurus, MkDocs, Docsify, picture licensing and credits).
Tested
Each generator end to end, live on GitHub Pages: a new site created, an illustrated page added to the menu, the real build or checks run, deployed, and the pages, pictures, menu and links verified in a browser.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Technical Documentation.
Does not support VitePress, Hugo, or Jekyll. Requires Node.js 18+. Cannot create GitHub repos without the gh CLI. Production builds require generator-specific local environments.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 17 days ago
- Accounts
GitHub
- Software
Node.js 18+
Git
Python 3.9+ (MkDocs sites only)docsify-cli
Permissions
Allowed Hosts
File Scopes
Reads and writes the docs site in your project. Network access is used to download pictures you ask for (https only, private addresses refused), to install the site's own dependencies when you agree, and to push and deploy when you confirm. It never asks for or stores tokens.