Agent skill · software engineering · aiskillstore
docusaurus-deployer
This skill should be used when deploying a Docusaurus site to GitHub Pages. It automates the configuration, building, and deployment process, handling GitHub Pages setup, environment configuration, and CI/CD automation. Includes local validation before GitHub Actions triggering.
Why this skill is useful
Adds executable scripts and automation for deploying Docusaurus sites to GitHub Pages, including CI/CD setup and local validation processes.
What it needs
Requires npm installed locally. Requires github account access. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Docusaurus GitHub Pages Deployer Automate building and deploying Docusaurus documentation sites to GitHub Pages with local validation before CI/CD triggering. Constitution Alignment: This skill implements production deployment standards defined in Constitution v4.0.1 (Pillar 9: Universal Cloud-Native Deployment from Section I). All deployments must meet project quality gates before publication. What This Skill Does 1. Project Analysis - Examine Docusaurus structure and dependencies 2. Local Configuration Validation - Verify Docusaurus config and sidebars 3. Local Build & Testing - Build site locally and validate output 4. Content Verification - Check for broken links and syntax errors 5. GitHub Pages Setup - Configure repository and deployment settings 6. CI/CD Automation - Set up GitHub Actions workflows 7. Deployment Verification - Validate successful deployment When to Use This Skill Deploy Docusaurus to GitHub Pages when: Setting up documentation deployment for the first time Making updates to documentation before publishing Updating deployment configuration Troubleshooting deployment issues Managing multiple documentation sites Ensuring documentation quality before production How to Use This Skill Follow the validate-locally-then-publish workflow: Step 1: Prepare Repository Configuration Gather GitHub organization/username, repository name, deployment target (user/project pages), and custom domain (optional). Step 2: Analyze Project Structure Examine Docusaurus project: Verify docusaurus.config.ts, sidebars.js/ts, package.json engines field, and dependencies exist. For detailed configuration guidance, see references/configuration-guide.md. Step 3: Update Docusaurus Configuration Update docusaurus.config.ts with GitHub Pages settings. See references/configuration-guide.md for complete configuration examples and guidelines based on deployment target (user vs. project pages). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/docusaurus-deployer