Skip to content
TrustedSkillsbeta
Back to all skills

Configure Github Pages

Checked
laurigates·vlatest·backend·MIT

Automates GitHub Pages setup, including repository configuration, branch selection, and theme deployment.

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 laurigates/claude-plugins --skill configure-github-pages -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

laurigates

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 laurigates/claude-plugins at 45d1d7dcf6.

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

Scanned
2 files, 455 lines
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

What it does

This skill enables AI agents to automatically configure GitHub Pages for static website hosting directly from a repository. It handles the necessary settings adjustments to ensure your site is live and accessible via a custom domain or default URL.

When to use it

  • You have built a static site (HTML, CSS, JS) in a GitHub repository and need immediate deployment without manual CLI access.
  • Your team requires automated CI/CD workflows that trigger page updates whenever code is pushed to the main branch.
  • You want to quickly switch a project from local development to a live URL for client demos or testing.

Key capabilities

  • Activates GitHub Pages source settings within a repository.
  • Configures custom domains and CNAME files automatically.
  • Sets build contexts (e.g., gh-pages branch) for proper routing.
  • Manages privacy settings to ensure public access.

Example prompts

  • "Configure GitHub Pages for my 'portfolio-2024' repository using the main branch as the source."
  • "Set up GitHub Pages for this repo and add 'myname.com' as the custom domain."
  • "Enable GitHub Pages hosting on the docs branch for our documentation site."

Tips & gotchas

Ensure your repository contains valid static files before configuring, or the agent may fail to generate a preview. If you use a custom domain, verify that DNS records are correctly pointed to GitHub's nameservers after configuration completes.