Github Pages Publisher
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.
Install
/plugin marketplace add artwist-polyakov/polyakov-claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add artwist-polyakov/polyakov-claude-skills --skill github-pages-publishergit clone --depth 1 https://github.com/artwist-polyakov/polyakov-claude-skills.git /tmp/polyakov-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/polyakov-claude-skills/plugins/github-pages-publisher/skills/github-pages-publisher ~/.claude/skills/github-pages-publisherPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# GitHub Pages Publisher Publish already-built static artifacts to a GitHub Pages repository. This skill is the **deployment/output layer** for page artifacts created by other skills. ## Required repository layout Every published artifact must go into this path shape inside the target repo: `<year>/<year>-<month>/<page-slug>/` Example: - `2026/2026-03/my-landing-page/` Never publish flat at repo root. Never skip the year or year-month nesting. ## What this skill expects Input should already exist as one of these: - a folder of built static files - a single HTML artifact plus local assets - a small static site ready to serve from a subdirectory This skill should not do major frontend design work. It should package and publish what already exists. ## Default publishing rules - preserve relative asset paths when possible - prefer `index.html` as entrypoint inside the target page directory - keep the output self-contained inside the page folder - avoid breaking existing published pages - if the same slug is republished, update the existing folder contents deliberately ## URL contract Always return the final public URL of the artifact. Assume GitHub Pages serves from the repo's configured Pages base URL. The final URL should be: `<pages-base-url>/<year>/<year>-<month>/<page-slug>/` or, if needed explicitly: `.../<page-slug>/index.html` Prefer the clean directory URL when it resolves correctly. ## Workflow 1. Determine the publish date bucket:
Details
- Skill name
github-pages-publisher- Repository
- artwist-polyakov/polyakov-claude-skills
- Path
plugins/github-pages-publisher/skills/github-pages-publisher/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Github Pages Publisher skill do?
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.
How do I install the Github Pages Publisher skill?
Claude Code plugin: /plugin marketplace add artwist-polyakov/polyakov-claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Github Pages Publisher popular?
It lives in artwist-polyakov/polyakov-claude-skills, which has 236 GitHub stars and 59 forks.
Related skills
Agent Deck
236artwist-polyakov/polyakov-claude-skills
Управление сессиями AI агентов через agent-deck CLI. Триггеры (RU): "запусти агента", "запусти саб-агента", "создай сессию", "проверь сессию", "проверь статус", "покажи вывод агента", "что агент ответил". Triggers (EN): "launch sub-agent", "create sub-agent", "start session", "check session", "show agent output".
Blogger Ads Skill
236artwist-polyakov/polyakov-claude-skills
Сопровождает рекламную сделку в Telegram на стороне блогера, рекламодателя или агентства: условия, отдельные DOCX договора и приложений, счёт, печатный и XML УПД, маркировка, сроки и завершение. Используй при подготовке или ведении конкретного рекламного размещения, проверке пакета документов либо готовности к публикации.
Codex Review
236artwist-polyakov/polyakov-claude-skills
Workflow кросс-агентного ревью с Codex. Triggers (RU): "кодекс ревью". Triggers (EN): "with codex review", "codex review workflow", "start codex review". ВАЖНО: при срабатывании триггера прочитай SKILL.md до любых других шагов.
Here Be Git
302intellectronica/agent-skills
Initialise a git repository with optional agent commit instructions and .gitignore. Use when users say "here be git", "init git", "initialise git", or otherwise indicate they want to set up version control in the current directory.
Yeet
398JetBrains/skills
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
Conventional Changelog
423mizchi/skills
Reference for Conventional Commits and automatic CHANGELOG generation. Compares release-please / changesets / git-cliff / towncrier and covers commit format, Keep a Changelog, and semver tag practices. Use when setting up or unifying a release flow.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.