github-pages-deployer
Deploy affiliate content to GitHub Pages for free hosting. Triggers on: "deploy to GitHub Pages", "host on GitHub Pages", "free hosting for my affiliate site", "push to GitHub Pages", "GitHub Pages setup", "deploy my landing page to GitHub", "host my bio link on GitHub", "free affiliate website hosting", "github pages affiliate", "set up GitHub Pages for my site", "deploy HTML to GitHub", "free static hosting", "publish my affiliate page for free", "github pages custom domain".
affitor · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Affitor/affiliate-skills --skill github-pages-deployerAbout this skill
name: github-pages-deployer description: > Deploy affiliate content to GitHub Pages for free hosting. Triggers on: "deploy to GitHub Pages", "host on GitHub Pages", "free hosting for my affiliate site", "push to GitHub Pages", "GitHub Pages setup", "deploy my landing page to GitHub", "host my bio link on GitHub", "free affiliate website hosting", "github pages affiliate", "set up GitHub Pages for my site", "deploy HTML to GitHub", "free static hosting", "publish my affiliate page for free", "github pages custom domain". license: MIT version: "1.0.0" tags: ["affiliate-marketing", "distribution", "deployment", "email-marketing", "github-pages", "static-site"] compatibility: "Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent" metadata: author: affitor version: "1.0" stage: S5-Distribution
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 provid