github-pages-deployer

Name: github-pages-deployer
Author: Affitor

3installs184forks

How to install github-pages-deployer?

affitor/affiliate-skills/github-pages-deployer

$npx -y skills add Affitor/affiliate-skills --skill github-pages-deployer

Installs into the current project.

Summary

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 af

Files · 1

View on GitHub

SKILL.md

1	# GitHub Pages Deployer
2
3	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.
4
5	## Stage
6
7	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.
8
9	## When to Use
10
11	- User wants to deploy a landing page (from S4) to a free host
12	- User wants to deploy a bio link page (from S5 bio-link-deployer) to a free host
13	- User wants free static hosting with a custom domain and SSL
14	- User already has HTML files and wants to publish them without paying for hosting
15	- User wants automated deploys so pushing to main branch auto-updates the live site
16	- User wants to host a simple affiliate blog or resource page for free
17
18	## Input Schema
19
20	```yaml
21	site:
22	type: string # REQUIRED — "landing-page" \| "bio-link" \| "blog" \| "resource-page"
23	html_content: string # REQUIRED — the HTML content to deploy (full file or description)
24	# If S4 or bio-link-deployer was run, use that output automatically
25	title: string # REQUIRED — site title (used in repo name and meta)
26	description: string # OPTIONAL — meta description for SEO
27
28	repo:
29	name: string # OPTIONAL — GitHub repo name (auto-generated from title if omitted)
30	# e.g., "heygen-review" or "alex-bio-links"
31	username: string # OPTIONAL — GitHub username. Used in generated URLs.
32	# If not provided, use "[your-username]" as placeholder.
33	visibility: string # OPTIONAL — "public" \| "private". Default: "public"
34	# Note: private repos require GitHub Pro for Pages
35
36	domain:
37	custom: string # OPTIONAL — custom domain (e.g., "links.yourdomain.com")
38	subdomain: string # OPTIONAL — subdomain type: "apex" \| "subdomain"
39	# Apex = yourdomain.com, Subdomain = www.yourdomain.com
40
41	deploy:
42	method: string # OPTIONAL — "github-actions" \| "manual". Default: "github-actions"
43	branch: string # OPTIONAL — source branch. Default: "main"
44	```
45
46	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.
47
48	## Workflow
49
50	### Step 1: Gather Inputs
51
52	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?"
53
54	If no prior HTML exists:
55	- Ask for HTML content or page description
56	- Offer to call S4 or bio-link-deployer first: "Want me to create the page first, then set up the deploy?"
57
58	### Step 2: Generate Repo Structure
59
60	Create the complete file and folder structure for the GitHub Pages repo.
61
62	Standard structure for a single-page site:
63
64	```
65	[repo-name]/
66	├── index.html # Main page (the affiliate landing page or bio link)
67	├── assets/
68	│ ├── css/
69	│ │ └── style.css # External CSS if extracted from HTML (optional)
70	│ └── images/
71	│ └── .gitkeep # Placeholder — add images here
72	├── CNAME # Only if custom domain is set
73	├── .github/
74	│ └── workflows/
75	│ └── deploy.yml # GitHub Actions workflow
76	├── .gitignore
77	└── README.md
78	```
79
80	For multi-page blog/resource site, add:
81
82	```
83	├── blog/
84	│ ├── index.html # Blog listing page
85	│ └── [post-slug]/
86	│ └── index.html # Individual post pages
87	├── about/
88	│ └── index.html
89	└── sitemap.xml
90	```
91
92	### Step 3: Generate the GitHub Actions Workflow
93
94	Write the `deploy.yml` file that automatically deploys to GitHub Pages on every push to `main`.
95
96	`

People who liked this also viewed

6 picks

Type

github-pages-deployer

3installs184forks

View on GitHub

How to install github-pages-deployer?

affitor/affiliate-skills/github-pages-deployer

$npx -y skills add Affitor/affiliate-skills --skill github-pages-deployer

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# GitHub Pages Deployer
2
3	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.
4
5	## Stage
6
7	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.
8
9	## When to Use
10
11	- User wants to deploy a landing page (from S4) to a free host
12	- User wants to deploy a bio link page (from S5 bio-link-deployer) to a free host
13	- User wants free static hosting with a custom domain and SSL
14	- User already has HTML files and wants to publish them without paying for hosting
15	- User wants automated deploys so pushing to main branch auto-updates the live site
16	- User wants to host a simple affiliate blog or resource page for free
17
18	## Input Schema
19
20	```yaml
21	site:
22	type: string # REQUIRED — "landing-page" \| "bio-link" \| "blog" \| "resource-page"
23	html_content: string # REQUIRED — the HTML content to deploy (full file or description)
24	# If S4 or bio-link-deployer was run, use that output automatically
25	title: string # REQUIRED — site title (used in repo name and meta)
26	description: string # OPTIONAL — meta description for SEO
27
28	repo:
29	name: string # OPTIONAL — GitHub repo name (auto-generated from title if omitted)
30	# e.g., "heygen-review" or "alex-bio-links"
31	username: string # OPTIONAL — GitHub username. Used in generated URLs.
32	# If not provided, use "[your-username]" as placeholder.
33	visibility: string # OPTIONAL — "public" \| "private". Default: "public"
34	# Note: private repos require GitHub Pro for Pages
35
36	domain:
37	custom: string # OPTIONAL — custom domain (e.g., "links.yourdomain.com")
38	subdomain: string # OPTIONAL — subdomain type: "apex" \| "subdomain"
39	# Apex = yourdomain.com, Subdomain = www.yourdomain.com
40
41	deploy:
42	method: string # OPTIONAL — "github-actions" \| "manual". Default: "github-actions"
43	branch: string # OPTIONAL — source branch. Default: "main"
44	```
45
46	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.
47
48	## Workflow
49
50	### Step 1: Gather Inputs
51
52	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?"
53
54	If no prior HTML exists:
55	- Ask for HTML content or page description
56	- Offer to call S4 or bio-link-deployer first: "Want me to create the page first, then set up the deploy?"
57
58	### Step 2: Generate Repo Structure
59
60	Create the complete file and folder structure for the GitHub Pages repo.
61
62	Standard structure for a single-page site:
63
64	```
65	[repo-name]/
66	├── index.html # Main page (the affiliate landing page or bio link)
67	├── assets/
68	│ ├── css/
69	│ │ └── style.css # External CSS if extracted from HTML (optional)
70	│ └── images/
71	│ └── .gitkeep # Placeholder — add images here
72	├── CNAME # Only if custom domain is set
73	├── .github/
74	│ └── workflows/
75	│ └── deploy.yml # GitHub Actions workflow
76	├── .gitignore
77	└── README.md
78	```
79
80	For multi-page blog/resource site, add:
81
82	```
83	├── blog/
84	│ ├── index.html # Blog listing page
85	│ └── [post-slug]/
86	│ └── index.html # Individual post pages
87	├── about/
88	│ └── index.html
89	└── sitemap.xml
90	```
91
92	### Step 3: Generate the GitHub Actions Workflow
93
94	Write the `deploy.yml` file that automatically deploys to GitHub Pages on every push to `main`.
95
96	`

People who liked this also viewed

6 picks

Type