github-pages-deployer skill
✓ 인증됨정적 제휴 랜딩 페이지를 GitHub Pages에 배포하기 위한 전체 리포지토리 구조와 GitHub Actions 워크플로우를 생성합니다.
- GitHub 스타
- 779
- 파일
- 2
- 마지막 커밋
- 2026년 10월 19일
- 라이선스
- MIT
- 허용된 도구
- —
github-pages-deployer skill은 무엇을 하나요?
정적 제휴 랜딩 페이지를 GitHub Pages에 배포하기 위한 전체 리포지토리 구조와 GitHub Actions 워크플로우를 생성합니다.
skill의 SKILL.md에서 생성된 요약입니다.
github-pages-deployer skill 정보
이 SKILL은 제휴 랜딩 페이지, 바이오 링크 허브 또는 간단한 블로그를 무료 호스팅 서비스에 배포할 수 있게 해줍니다. 호스팅 비용을 지불하지 않고 정적 HTML 콘텐츠를 호스팅해야 하는 제휴 마케터와 개발자를 위해 설계되었습니다. HTML 콘텐츠를 제공하거나 이전에 생성된 페이지를 참조하면 index.html 파일, assets 폴더, README.md를 포함한 전체 리포지토리 구조를 생성합니다.
사용자가 콘텐츠 제작 단계에서 실제 배포 단계로 넘어가고자 할 때 에이전트가 이 SKILL을 로드해야 합니다. GitHub Actions CI/CD 워크플로우 생성을 자동화하여, 향후 main 브랜치에 푸시할 때마다 라이브 웹사이트가 자동으로 업데이트되도록 보장합니다. 또한 필요한 CNAME 파일을 생성하고 apex 또는 서브도메인 설정을 위한 특정 DNS 레코드를 제공함으로써 커스텀 도메인 구성의 기술적 복잡성을 처리합니다. 이 도구는 GitHub Pages를 호스팅 제공업체로 사용하며, 무료 SSL 및 월 100GB의 대역폭과 같은 기능을 제공합니다.
agent가 수행할 수 있는 작업
- 1랜딩 페이지 배포개발자가 기존 HTML 랜딩 페이지를 사용하여 호스팅을 위한 전체 GitHub 리포지토리를 구축할 수 있습니다.
- 2자동 배포 설정사용자가 GitHub Actions 워크플로우를 구성하여 main 브랜치에 코드를 푸시하면 라이브 사이트가 자동으로 업데이트되도록 설정할 수 있습니다.
- 3커스텀 도메인 구성에이전트가 개인 도메인을 GitHub Pages에 연결하는 데 필요한 정확한 DNS 레코드와 CNAME 파일을 제공할 수 있습니다.
skill의 SKILL.md를 기반으로 작성되었습니다. 모든 사용 사례는 해당 문서의 인용구와 대조 확인되었습니다.
github-pages-deployer skill 설치 방법
각 명령은 skill 폴더를 클라이언트의 skills 디렉터리에 복사합니다. 클라이언트를 재시작하거나 새 세션을 시작하여 로드하세요.플러그인에 github-pages-deployer skill 설치
/plugin marketplace add Affitor/affiliate-skills /plugin install distribution-skills@affiliate-skills
Claude Code에 github-pages-deployer skill 설치
~/.claude/skills/github-pages-deployer/SKILL.md
$ npx degit Affitor/affiliate-skills/skills/distribution/github-pages-deployer ~/.claude/skills/github-pages-deployerClaude Code (project)에 github-pages-deployer skill 설치
.claude/skills/github-pages-deployer/SKILL.md
$ npx degit Affitor/affiliate-skills/skills/distribution/github-pages-deployer .claude/skills/github-pages-deployerCodex에 github-pages-deployer skill 설치
~/.agents/skills/github-pages-deployer/SKILL.md
$ npx degit Affitor/affiliate-skills/skills/distribution/github-pages-deployer ~/.agents/skills/github-pages-deployerGemini CLI에 github-pages-deployer skill 설치
~/.gemini/skills/github-pages-deployer/SKILL.md
$ npx degit Affitor/affiliate-skills/skills/distribution/github-pages-deployer ~/.gemini/skills/github-pages-deployerClaude.ai에 github-pages-deployer skill 설치
npx degit Affitor/affiliate-skills/skills/distribution/github-pages-deployer github-pages-deployer && zip -r github-pages-deployer.zip github-pages-deployer # claude.ai → Customize → Skills → + → Create skill → Upload a skill → github-pages-deployer.zip
자동 검사
2026년 11월 15일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 보안 감사는 아닙니다. 에이전트가 실행하기 전에 스크립트를 읽어 보세요. 검사 방식
- 소스 저장소 연결 및 접근 가능affitor/affiliate-skills/skills/distribution/github-pages-deployer is public and reachablegithub.com/affitor/affiliate-skills/tree/HEAD/skills/distrib ↗통과
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit 2026-10-19github.com/affitor/affiliate-skills/commits ↗통과
- 스크립트에 다운로드 후 실행이나 자격 증명 탈취가 없음No scripts in the skill folder통과
- SKILL.md에 숨겨진 지침 없음No override phrases, safeguard switches, credential requests or hidden charactersgithub.com/affitor/affiliate-skills/blob/HEAD/skills/distrib ↗통과
- 사전 허용 도구가 제한됨No pre-approved tools; the agent asks before using onegithub.com/affitor/affiliate-skills/blob/HEAD/skills/distrib ↗통과
- SKILL.md가 Agent Skills 형식을 따름Valid name and description; says when to use it; 372 linesgithub.com/affitor/affiliate-skills/blob/HEAD/skills/distrib ↗통과
SKILL.md
GitHub에서 보기GitHub Pages Deployer
Generate a complete, ready-to-deploy GitHub Pages setup for affiliate landing pages, bio link hubs, and blog posts. Outputs the full repo file structure, a GitHub Actions CI/CD workflow for automatic deploys, and step-by-step instructions for custom domain configuration with SSL. Free hosting, no credit card required.
Stage
S5: Distribution — GitHub Pages is the most underused free hosting platform in affiliate marketing. 100GB bandwidth/month, free SSL, custom domains, and automatic deploys from Git. This skill takes any HTML output from S4 (landing page) or S5 (bio-link) and gets it live on the internet in under 10 minutes.
When to Use
- User wants to deploy a landing page (from S4) to a free host
- User wants to deploy a bio link page (from S5 bio-link-deployer) to a free host
- User wants free static hosting with a custom domain and SSL
- User already has HTML files and wants to publish them without paying for hosting
- User wants automated deploys so pushing to main branch auto-updates the live site
- User wants to host a simple affiliate blog or resource page for free
Input Schema
site:
type: string # REQUIRED — "landing-page" | "bio-link" | "blog" | "resource-page"
html_content: string # REQUIRED — the HTML content to deploy (full file or description)
# If S4 or bio-link-deployer was run, use that output automatically
title: string # REQUIRED — site title (used in repo name and meta)
description: string # OPTIONAL — meta description for SEO
repo:
name: string # OPTIONAL — GitHub repo name (auto-generated from title if omitted)
# e.g., "heygen-review" or "alex-bio-links"
username: string # OPTIONAL — GitHub username. Used in generated URLs.
# If not provided, use "[your-username]" as placeholder.
visibility: string # OPTIONAL — "public" | "private". Default: "public"
# Note: private repos require GitHub Pro for Pages
domain:
custom: string # OPTIONAL — custom domain (e.g., "links.yourdomain.com")
subdomain: string # OPTIONAL — subdomain type: "apex" | "subdomain"
# Apex = yourdomain.com, Subdomain = www.yourdomain.com
deploy:
method: string # OPTIONAL — "github-actions" | "manual". Default: "github-actions"
branch: string # OPTIONAL — source branch. Default: "main"
Chaining context: If S4 (landing-page-creator) or S5 (bio-link-deployer) was run earlier in the conversation, automatically use that HTML output as site.html_content. Do not ask the user to paste it again.
Workflow
Step 1: Gather Inputs
Check if an HTML page was generated earlier in the conversation (S4 landing page or bio-link page). If yes, confirm: "I'll deploy the [page type] we built earlier. What's your GitHub username?"
If no prior HTML exists:
- Ask for HTML content or page description
- Offer to call S4 or bio-link-deployer first: "Want me to create the page first, then set up the deploy?"
Step 2: Generate Repo Structure
Create the complete file and folder structure for the GitHub Pages repo.
Standard structure for a single-page site:
[repo-name]/
├── index.html # Main page (the affiliate landing page or bio link)
├── assets/
│ ├── css/
│ │ └── style.css # External CSS if extracted from HTML (optional)
│ └── images/
│ └── .gitkeep # Placeholder — add images here
├── CNAME # Only if custom domain is set
├── .github/
│ └── workflows/
│ └── deploy.yml # GitHub Actions workflow
├── .gitignore
└── README.md
For multi-page blog/resource site, add:
├── blog/
│ ├── index.html # Blog listing page
│ └── [post-slug]/
│ └── index.html # Individual post pages
├── about/
│ └── index.html
└── sitemap.xml
Step 3: Generate the GitHub Actions Workflow
Write the deploy.yml file that automatically deploys to GitHub Pages on every push to main.
# .github/workflows/deploy.yml
name: Deploy to GitHub Pages
on:
push:
branches: [ main ]
workflow_dispatch: # Allow manual trigger from GitHub UI
permissions:
contents: read
pages: write
id-token: write
concurrency:
group: "pages"
cancel-in-progress: false
jobs:
deploy:
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Setup Pages
uses: actions/configure-pages@v5
- name: Upload artifact
uses: actions/upload-pages-artifact@v3
with:
path: '.' # Deploy from repo root
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v4
This workflow uses the official GitHub Pages Actions (no third-party dependencies, no tokens needed).
Step 4: Generate the CNAME File (if custom domain)
If domain.custom is provided, create a CNAME file with just the domain:
links.yourdomain.com
For apex domains (yourdomain.com), the CNAME file contains the bare domain. GitHub Pages handles the redirect from www to apex automatically when configured correctly.
Step 5: Generate DNS Configuration Instructions
Provide exact DNS records to add in the user's domain registrar (Cloudflare, Namecheap, GoDaddy, etc.).
For subdomain (e.g., links.yourdomain.com):
Type: CNAME
Name: links
Value: [username].github.io
TTL: Auto or 3600
For apex domain (yourdomain.com):
Type: A Name: @ Value: 185.199.108.153
Type: A Name: @ Value: 185.199.109.153
Type: A Name: @ Value: 185.199.110.153
Type: A Name: @ Value: 185.199.111.153
Type: AAAA Name: @ Value: 2606:50c0:8000::153
Type: AAAA Name: @ Value: 2606:50c0:8001::153
Type: AAAA Name: @ Value: 2606:50c0:8002::153
Type: AAAA Name: @ Value: 2606:50c0:8003::153
Note: GitHub's IP addresses above are current as of 2026. Always verify at https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site
Step 6: Generate README.md
Write a clean README for the repo:
# [Site Title]
Affiliate landing page hosted on GitHub Pages.
## Live Site
[Live URL]
## Deploy
Automatic via GitHub Actions — push to `main` triggers a deploy.
## Powered By
[Affitor](https://affitor.com/?utm_source=affiliate-skills)
Step 7: Output the Complete Setup
Present all outputs in numbered sections with clear file labels.
Step 8: Self-Validation
Before presenting output, verify:
- GitHub Actions YAML is valid syntax
- CNAME file is correct format if custom domain configured
- All file paths are valid and consistent
- Deployment commands are copy-paste ready
- README.md is included in the repository files
If any check fails, fix the output before delivering. Do not flag the checklist to the user — just ensure the output passes.
Output Schema
output_schema_version: "1.0.0" # Semver — bump major on breaking changes
repo:
name: string # e.g., "heygen-review-2026"
url: string # e.g., "https://github.com/[username]/[repo-name]"
pages_url: string # e.g., "https://[username].github.io/[repo-name]"
custom_domain_url: string | null
files:
- path: string # e.g., "index.html"
content: string # full file content
- path: ".github/workflows/deploy.yml"
content: string
- path: "CNAME" # null if no custom domain
content: string | null
- path: ".gitignore"
content: string
- path: "README.md"
content: string
setup_steps:
- step: number
action: string # e.g., "Create GitHub repo"
command: string | null # CLI command if applicable
dns_records: object | null # DNS config if custom domain provided
estimated_time: string # e.g., "8-10 minutes"
Output Format
Present in five clearly labeled sections:
Section 1: Summary
- Repo name, live URL, custom domain URL (if applicable)
- Estimated time to go live: X minutes
Section 2: Files to Create Each file in its own fenced code block with the file path as the label. User can copy-paste each file's content directly.
Section 3: GitHub Setup Steps Numbered instructions:
- Create the repo on GitHub (link to github.com/new)
- Initialize and push (CLI commands provided)
- Enable GitHub Pages in repo Settings
- Set source to "GitHub Actions"
Section 4: DNS Setup (only if custom domain) Exact records to add, formatted as a table. Provider-specific notes for Cloudflare users (Proxy OFF for GitHub Pages).
Section 5: Verification How to confirm the deploy worked and SSL is active (usually 5-15 minutes for DNS propagation).
Error Handling
- No HTML content and no prior skill output: "I don't see a page to deploy yet. Want me to create a landing page first (S4), a bio link page, or do you have HTML to paste?"
- Private repo for free GitHub account: "Private repos require GitHub Pro ($4/mo) for GitHub Pages. Your options: (1) make the repo public, (2) upgrade to Pro, (3) use Netlify Drop for free private deploys."
- Custom domain not propagating: "DNS changes can take 1-48 hours. If it's been over 24 hours, double-check: CNAME file contains exactly the domain, no
https://prefix; DNS record value is[username].github.io(with no trailing slash). Enable Cloudflare proxy OFF (grey cloud) for GitHub Pages to work." - GitHub Actions failing: Common causes: Pages not enabled in repo Settings, branch name mismatch (use
mainnotmaster), orpages: writepermission missing on older repos. Provide troubleshooting checklist. - User wants WordPress or dynamic site: "GitHub Pages only hosts static HTML/CSS/JS — no PHP, no databases. For WordPress or dynamic content, use Cloudflare Pages, Netlify, or a VPS. For a simple affiliate site, static is faster and better for SEO anyway."
- Repo name taken: Suggest appending year (
heygen-review-2026) or niche (heygen-review-for-creators).
Examples
Example 1: Deploy landing page from S4
Context: S4 generated a HeyGen landing page HTML.
User: "Deploy this to GitHub Pages. My username is alexmarketer."
Action: Auto-use S4 HTML. Repo name: heygen-landing. Pages URL: https://alexmarketer.github.io/heygen-landing. Generate all files + deploy instructions.
Example 2: Deploy bio link with custom domain
Context: Bio-link-deployer generated a bio page.
User: "Put this on GitHub Pages at links.mysite.com."
Action: Repo + CNAME file with links.mysite.com. DNS: CNAME record pointing to [username].github.io. Cloudflare note: proxy must be disabled (grey cloud icon).
Example 3: Multi-page resource site User: "I want to host an affiliate resource site on GitHub Pages with a homepage, about page, and 3 blog posts." Action: Generate multi-page structure. Scaffold all index.html files with placeholder content. Deploy workflow. Note: for a blog with 10+ posts, suggest Jekyll or Eleventy for templating.
References
shared/references/ftc-compliance.md— FTC affiliate disclosure. Ensure the deployed HTML includes disclosure language.shared/references/affitor-branding.md— Affitor footer. Include in HTML before deploy.- GitHub Pages documentation: https://docs.github.com/en/pages
- GitHub Pages IP addresses (A records): https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site
shared/references/flywheel-connections.md— master flywheel connection map
Revenue & Action Plan
Expected Outcomes
- Revenue potential: A deployed landing page or bio link earns 24/7 — it's your always-on salesperson. Free hosting means 100% of revenue is profit. A single landing page can generate $200-1,000/month with consistent traffic
- Benchmark: Deployed affiliate pages indexed by Google start ranking within 2-4 weeks. Organic traffic from Google is the highest-converting free traffic source (4-5% conversion vs 1-2% from social)
- Key metric to track: Page visits → affiliate link clicks → conversions. Set up
conversion-trackerimmediately after deploying
Do This Right Now (15 min)
- Create the repo and push — follow the Setup Steps exactly (copy-paste commands)
- Verify the deploy — visit your GitHub Pages URL, confirm the page loads
- Submit to Google Search Console — add
https://[username].github.io/[repo]so Google indexes it faster - Share the live URL — post it on social media, add it to your bio link, and send it to your email list
Track Your Results
After deploying: set up conversion-tracker to monitor clicks and conversions. After 30 days, run seo-audit to optimize for search rankings. A page that ranks #1 for a buyer-intent keyword can earn $500-2,000/month passively.
Next step — copy-paste this prompt: "Set up conversion tracking for my deployed page at [URL]" → runs
conversion-tracker
Flywheel Connections
Feeds Into
conversion-tracker(S6) — deployed site URL to trackseo-audit(S6) — deployed site to audit
Fed By
landing-page-creator(S4) — HTML file to deploybio-link-deployer(S5) — bio link HTML to deploysqueeze-page-builder(S4) — squeeze page HTML to deploy
Feedback Loop
seo-audit(S6) checks deployed site health → identify deployment issues affecting SEO
Quality Gate
Before delivering output, verify:
- Would I share this on MY personal social?
- Contains specific, surprising detail? (not generic)
- Respects reader's intelligence?
- Remarkable enough to share? (Purple Cow test)
- Irresistible offer framing? (if S4 offer skills ran)
Any NO → rewrite before delivering.
chain_metadata:
skill_slug: "github-pages-deployer"
stage: "distribution"
timestamp: string
suggested_next:
- "conversion-tracker"
- "seo-audit"
이 스킬의 파일
2github-pages-deployer skill 질문
Claude Code에 github-pages-deployer skill을 어떻게 설치하나요?
npx degit Affitor/affiliate-skills/skills/distribution/github-pages-deployer ~/.claude/skills/github-pages-deployer를 실행합니다. Claude Code는 ~/.claude/skills(모든 프로젝트) 또는 .claude/skills(한 프로젝트)에서 skills를 로드하며, 설명이 작업과 일치할 때 skill을 사용합니다.
github-pages-deployer skill을 사용할 수 있는 클라이언트는 무엇인가요?
Agent Skills 형식을 읽는 모든 클라이언트(Claude Code, Codex, Gemini CLI, claude.ai(ZIP으로 업로드))가 사용할 수 있습니다. skill 내 스크립트는 클라이언트가 코드 실행을 허용하는 경우에만 실행됩니다.
WordPress와 같은 동적 웹사이트도 지원하나요?
아니요, GitHub Pages는 정적 HTML, CSS, JavaScript만 호스팅할 수 있습니다. PHP나 데이터베이스는 지원하지 않습니다.
배포를 어떻게 자동화하나요?
이 SKILL은 main 브랜치에 변경 사항을 푸시할 때마다 사이트를 자동으로 배포하는 GitHub Actions 워크플로우 파일(deploy.yml)을 생성합니다.