Web Deploy Github
ListedHelps with web development, deployment, GitHub as part of agent workflows workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add cjhfff/cjh-skills --skill web-deploy-github -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
cjhfff
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.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 2 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: clawhub.ai, cli.github.com.
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.
Hosts contacted
clawhub.aiundeclaredcli.github.comundeclaredgithub.comsource hostWhat it found
- skills/web-deploy-github/.clawhub/origin.json:3contacts clawhub.ai
"registry": "https://clawhub.ai", - skills/web-deploy-github/scripts/deploy_github_pages.sh:19contacts cli.github.com
echo "Install: https://cli.github.com/"
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 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 cjhfff/cjh-skills at c8e155fe61.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- c8e155fe61
- Scanned
- 16 files, 1,071 lines
About this skill
What it does
This skill automates deployments to GitHub Pages. It handles building a static site and pushing the resulting files to the gh-pages branch, which is then published by GitHub Pages. This allows users to easily deploy websites directly from their repositories without manual configuration of deployment pipelines.
When to use it
- You have a static website (e.g., built with Jekyll, Hugo, or similar) hosted in a Git repository.
- You want to automatically publish your website to GitHub Pages whenever changes are pushed to the main branch.
- You need to deploy a simple landing page or documentation site without complex CI/CD setup.
- You're looking for a streamlined way to manage deployments compared to manual processes.
Key capabilities
- Builds static websites from source code.
- Pushes built files to the
gh-pagesbranch of a GitHub repository. - Automates deployment to GitHub Pages.
Example prompts
- "Deploy my website located at
/path/to/websiteto GitHub Pages." - "Build and deploy the static site in this directory."
- “Publish the contents of
publicfolder to GitHub pages.”
Tips & gotchas
- Requires a valid GitHub repository with appropriate permissions for deployment.
- The skill assumes you have a build process defined within your project that generates the static website files.