doc-publishing

Publishes documentation to GitHub Pages, Vercel, or Netlify from source docs and build outputs.

7|3|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/brainbrewlabs/brainbrew-devkit --skill doc-publishing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-publishing
Source: https://github.com/brainbrewlabs/brainbrew-devkit/tree/main/plugin/config/templates/docs/skills/doc-publishing
Command: npx skills add https://github.com/brainbrewlabs/brainbrew-devkit --skill doc-publishing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build and publish documentation to hosting platforms (GitHub Pages, Vercel, Netlify, and static-site generators) from a single workflow, reducing manual deployment steps.

Core Features & Use Cases

  • Supports publishing to GitHub Pages, Vercel, Netlify, and other static-site hosts.
  • Detects common build configurations (MkDocs, Docusaurus, Hugo, etc.) and executes appropriate deployment steps.
  • Triggers on "publish docs", "deploy docs", or "push docs live" to automatically deploy updated docs to the chosen platform.

Quick Start

Run the publish action with the target platform specified (e.g., "github-pages", "vercel", "netlify") to deploy your docs.

Frequently Asked Questions about doc-publishing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically publish docs to GitHub Pages or Netlify?

To automatically publish docs, you trigger the workflow with a target platform like "github-pages", "vercel", or "netlify" specified in the arguments to execute the deploy scripts and push your documentation live.

Can I deploy a Docusaurus or MkDocs static site using this workflow?

Yes, you can deploy Docusaurus or MkDocs static sites. The workflow detects common build configurations for these static site generators and executes the appropriate deployment steps for your chosen hosting platform.

Do I need existing deploy scripts to publish my documentation?

Yes, you need existing deploy scripts and a valid build configuration. The workflow executes these publish scripts to deploy your source docs and build outputs to the specified static-site hosting target.

What is the best way to deploy documentation from a single static-site workflow?

The best way to deploy documentation from a single workflow is specifying your hosting target in the arguments, which reduces manual deployment steps by building and publishing source docs in one automated action.

Why does my documentation deployment require a target platform argument?

Your documentation deployment requires a target platform argument to determine the destination host. Without specifying a valid target like "github-pages" or "netlify", the publish workflow cannot determine where to execute the deploy scripts.