gh-pages-deploy▌
aviz85/claude-skills-library · updated Apr 19, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Deploy static frontend websites to GitHub Pages using the GitHub CLI.
GitHub Pages Deployment
Deploy static frontend websites to GitHub Pages using the GitHub CLI.
Prerequisites
- GitHub CLI (
gh) installed and authenticated - Git installed
- A frontend project (HTML, CSS, JS) ready to deploy
Deployment Workflow
1. Initialize Git Repository (if needed)
git init
git add .
git commit -m "Initial commit"
2. Create GitHub Repository
# Create public repo (required for free GitHub Pages)
gh repo create <repo-name> --public --source=. --push
3. Enable GitHub Pages
# Enable GitHub Pages from main branch root
gh api repos/{owner}/{repo}/pages -X POST -f build_type=legacy -f source='{"branch":"main","path":"/"}'
Or for docs folder:
gh api repos/{owner}/{repo}/pages -X POST -f build_type=legacy -f source='{"branch":"main","path":"/docs"}'
4. Check Deployment Status
# Get pages info
gh api repos/{owner}/{repo}/pages
# View deployment status
gh api repos/{owner}/{repo}/pages/builds/latest
5. Set Homepage URL in Repo Settings
Always do this — sets the live URL in the GitHub repo's About panel (top-right on the repo page):
OWNER=$(gh api user --jq '.login')
PAGES_URL=$(gh api repos/$OWNER/$REPO_NAME/pages --jq '.html_url')
gh api --method PATCH repos/$OWNER/$REPO_NAME --field homepage="$PAGES_URL" --jq '.homepage'
6. Get Site URL
The site will be available at: https://<username>.github.io/<repo-name>/
Auto-deploy is active: every push to
maintriggers a rebuild. No GitHub Actions needed for legacy build.
Quick Deploy Script
For a complete deployment in one flow:
# Variables
REPO_NAME="my-site"
# Initialize and commit
git init
git add .
git commit -m "Initial commit"
# Create repo and push
gh repo create $REPO_NAME --public --source=. --push
# Enable pages
sleep 2
OWNER=$(gh api user --jq '.login')
gh api repos/$OWNER/$REPO_NAME/pages -X POST -f build_type=legacy -f source='{"branch":"main","path":"/"}'
# Set homepage URL in repo About panel
PAGES_URL="https://$OWNER.github.io/$REPO_NAME/"
gh api --method PATCH repos/$OWNER/$REPO_NAME --field homepage="$PAGES_URL" --jq '.homepage'
echo "✓ Site live at: $PAGES_URL"
Troubleshooting
- Pages not enabled: Ensure repo is public or you have GitHub Pro
- 404 error: Wait 1-2 minutes for deployment, check if index.html exists at root
- Build failed: Check GitHub Actions tab for errors
Updating the Site
After making changes:
git add .
git commit -m "Update site"
git push
GitHub Pages will automatically rebuild.
How to use gh-pages-deploy on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add gh-pages-deploy
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches gh-pages-deploy from GitHub repository aviz85/claude-skills-library and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate gh-pages-deploy. Access the skill through slash commands (e.g., /gh-pages-deploy) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★55 reviews- ★★★★★Yusuf Ndlovu· Dec 28, 2024
We added gh-pages-deploy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ren Shah· Dec 28, 2024
gh-pages-deploy reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Chaitanya Patil· Dec 20, 2024
Keeps context tight: gh-pages-deploy is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Alexander Patel· Dec 20, 2024
Registry listing for gh-pages-deploy matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ava Park· Dec 4, 2024
I recommend gh-pages-deploy for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★William Sanchez· Nov 23, 2024
Solid pick for teams standardizing on skills: gh-pages-deploy is focused, and the summary matches what you get after install.
- ★★★★★Anaya Ndlovu· Nov 19, 2024
gh-pages-deploy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Piyush G· Nov 11, 2024
Registry listing for gh-pages-deploy matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Fatima Wang· Nov 11, 2024
Keeps context tight: gh-pages-deploy is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Ava Gupta· Oct 14, 2024
gh-pages-deploy has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 55