Skip to content
TrustedSkillsbeta
Back to all skills

Gh Pages Deploy

Checked
aviz85·vlatest·backend

Automatically deploys website updates from your GitHub Pages branch to a live URL.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add aviz85/claude-skills-library --skill gh-pages-deploy -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

aviz85

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned aviz85/claude-skills-library at 90bbc16773.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
90bbc16773
Manifest
skills/gh-pages-deploy/SKILL.md
Scanned
2 files, 212 lines
Copies in repo
2 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The gh-pages-deploy skill enables AI agents to automatically publish static websites to GitHub Pages. It handles the entire workflow of building, committing, and pushing site updates directly from a repository.

When to use it

  • Deploying documentation sites that change frequently with code commits.
  • Automating the release of static marketing pages or landing pages.
  • Updating portfolio projects without manual Git interaction.
  • Integrating continuous deployment pipelines for static content generation.

Key capabilities

  • Builds static assets from source files.
  • Commits changes to a designated GitHub repository branch.
  • Pushes updates directly to the gh-pages remote.
  • Manages configuration for build commands and destination paths.

Example prompts

  • "Build my React app and deploy the latest version to my gh-pages branch."
  • "Update the documentation site with the new API changes and push to GitHub Pages."
  • "Deploy the static assets generated from my Jekyll project to the gh-pages remote."

Tips & gotchas

Ensure your repository has a gh-pages branch configured as the deployment target before running the skill. Verify that build dependencies are installed locally or available in the agent's environment to prevent build failures during the commit process.