Publish static page artifacts from the publisher workspace to a GitHub Pages repository using a fine-grained token, with advisory image optimization and an original-image path. Use when a React/static page artifact is already prepared and needs to be copied into the Pages repo under a strict year/year-month/page-slug directory layout, then committed and pushed, with a final public artifact URL returned.
Ask your Agent
Use this Skill: https://skilld.dev/gh/artwist-polyakov/polyakov-claude-skills/github-pages-publisher
This session only. Nothing lands on disk.
≈122 tokens on demand. Your agent reads this file only when SKILL.md points to it.
Required environment variables:
GHPAGES_TOKEN — fine-grained GitHub token with contents write access to the target repoGHPAGES_REPO — owner/repoGHPAGES_BRANCH — target branch (usually main or gh-pages)GHPAGES_PAGES_BASE_URL — public Pages base URL, for example https://example.github.io/repoThe publisher writes artifacts into:
YYYY/YYYY-MM/page-slug/The final URL is derived as:
<GHPAGES_PAGES_BASE_URL>/YYYY/YYYY-MM/page-slug/Source: SKILL.md on GitHub
The skill automates publishing static web artifacts to GitHub Pages, utilizing git for repository operations and Pillow for image optimization. It follows security best practices for secret management and input sanitization. The primary security consideration is the inherent risk of indirect prompt injection when the agent processes external artifacts during the pre-publish validation phase.
1 alert: gptAnomaly
Risk: LOW · No issues
Signed by skilld at 42bec57. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.
Last checked against GitHub last week.