Skills docusaurus-deployer

📦

docusaurus-deployer

Name: docusaurus-deployer
Author: 92Bilal26

v1.2 Content revision r1 Medium Risk 🌐 Network access🔑 Env variables📁 Filesystem access⚙️ External commands

Deploy Docusaurus Sites to GitHub Pages

Docusaurus deployments often fail because configuration, build output, and GitHub Pages settings do not match. This skill guides setup, validation, CI workflow creation, and troubleshooting.

Supports: Claude Codex Code(CC)

📊 67 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "docusaurus-deployer" from https://skillstore.io/skills/92bilal26-docusaurus-deployer.md and its manifest at https://skillstore.io/api/skills/92bilal26-docusaurus-deployer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/92bilal26-docusaurus-deployer.md Signed manifest GET /api/skills/92bilal26-docusaurus-deployer/manifest Signed lockfile GET /api/skills/92bilal26-docusaurus-deployer/lockfile

Test it

Using "docusaurus-deployer". Deploy a project pages site from apps/docs.

Expected outcome:

A deployment plan covering target URL, base path, workflow path changes, local validation steps, and post-deploy checks.

Using "docusaurus-deployer". A GitHub Pages site shows 404 after a successful workflow run.

Expected outcome:

Identifies likely base URL or Pages source mismatch.
Lists repository settings to verify.
Recommends local build and artifact checks before another push.

Using "docusaurus-deployer". Add deployment checks before publishing documentation updates.

Expected outcome:

A validation checklist for type checks, production build, local serving, content links, frontmatter, and responsive navigation.

Security Audit

Medium Risk

v7 • 7/5/2026 Open versioned report

Most static findings are documentation examples, Markdown backticks, placeholder URLs, or relative links, so they are false positives. Confirmed risk is limited to expected deployment commands that run npm scripts and broad git staging or pushing. No prompt injection or credential exfiltration intent was found.

Files scanned

1,728

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

Medium

SKILL.md:71-75 references/local-validation-guide.md:163-171

Broad Repository Staging Before Push

The skill recommends `git add .` followed by commit and push. This can publish unrelated local changes or secrets if the repository is dirty.

Both locations explicitly stage all files before pushing to main. This is legitimate deployment guidance, but it creates a clear accidental disclosure path.

Capability review items (2)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium

SKILL.md:60-65

Ruby/shell backtick execution

```bash

The surrounding block instructs running npm ci, typecheck, build, and serve. These are expected deployment commands, but npm scripts can execute project-controlled code.

Medium

SKILL.md:71-75

Ruby/shell backtick execution

```bash

The surrounding block instructs git add, commit, and push to main. These commands can publish repository changes and should require review before execution.

Risk Factors

🌐 Network access (8)

references/configuration-guide.md:18 references/configuration-guide.md:37 references/configuration-guide.md:57 references/configuration-guide.md:135 references/configuration-guide.md:155 references/performance-standards.md:247 references/performance-standards.md:248 references/troubleshooting.md:101

🔑 Env variables (2)

references/github-actions-guide.md:342 references/troubleshooting.md:118

📁 Filesystem access (6)

references/local-validation-guide.md:106 references/performance-standards.md:242 references/performance-standards.md:244 references/performance-standards.md:28 references/troubleshooting.md:95 references/troubleshooting.md:169

⚙️ External commands (23)

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/92bilal26-docusaurus-deployer/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/92bilal26-docusaurus-deployer/security.svg)](https://skillstore.io/skills/92bilal26-docusaurus-deployer?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/92bilal26-docusaurus-deployer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/92bilal26-docusaurus-deployer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/92bilal26-docusaurus-deployer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

92Bilal26. (2026). docusaurus-deployer security audit report (audit version 7) [Author version 1.2]. Skillstore. https://skillstore.io/skills/92bilal26-docusaurus-deployer/audits/7

BibTeX citation

@techreport{92bilal26-92bilal26-docusaurus-deployer-2026,
  author = {92Bilal26},
  title = {docusaurus-deployer security audit report (audit version 7)},
  institution = {Skillstore},
  year = {2026},
  number = {7},
  url = {https://skillstore.io/skills/92bilal26-docusaurus-deployer/audits/7},
  note = {Author version 1.2}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "docusaurus-deployer security audit report (audit version 7)"
version: "1.2"
type: report
authors:
  - name: "92Bilal26"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/92bilal26-docusaurus-deployer/audits/7"
identifiers:
  - type: other
    value: "skillstore:92bilal26-docusaurus-deployer:audit:7"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Publish a Documentation Site

Configure base URL, repository settings, and local validation before publishing a Docusaurus site to GitHub Pages.

Add CI Deployment

Create or adjust a GitHub Actions workflow that builds Docusaurus and deploys the generated static site.

Fix Failed Deployments

Diagnose 404 pages, build failures, broken links, workflow permission errors, and incorrect working directories.

Try These Prompts

Prepare Deployment

Deploy my Docusaurus site to GitHub Pages. Check the config, run local validation, and explain each required setting before changes.

Create Workflow

Set up GitHub Actions for a Docusaurus project in [directory]. Use GitHub Pages source and adjust workflow paths to this repository.

Troubleshoot Failure

Troubleshoot a failed Docusaurus GitHub Pages deployment using local build logs and GitHub Actions logs. Identify root cause and minimal fix.

Audit Release Readiness

Audit this monorepo Docusaurus deployment for baseUrl, workflow permissions, dependency scripts, build output, and safe commit scope before publishing.

Best Practices

Run type checks and production builds locally before pushing deployment changes.
Review staged files before committing, especially when workflow or configuration files changed.
Keep GitHub Actions permissions limited to the permissions required for Pages deployment.

Avoid

Do not push to main before confirming local build output and navigation.
Do not hardcode production site URLs inside documentation links when relative links work.
Do not pass repository secrets into build steps unless the deployment requires them.