Web Deploy GitHub Pages

Create and deploy single-page static websites to GitHub Pages with autonomous workflow. Use when building portfolio sites, CV pages, landing pages, or any static web project that needs GitHub Pages deployment. Handles complete workflow from project initialization to live deployment with GitHub Actions automation.

Security Scan

The skill overall matches its stated purpose (creating and deploying static sites to GitHub Pages), but the package metadata omits important operational requirements and there are small but meaningful inconsistencies you should understand before installing.

Purpose & Capability

The skill's name, description, scripts, and templates are coherent: it initializes a static site and deploys it via GitHub Actions/gh. However the registry metadata declares no required binaries or credentials even though the runtime scripts clearly require the GitHub CLI (gh) and git and depend on an authenticated GitHub session. That mismatch between claimed requirements and actual needs is noteworthy.

Instruction Scope

SKILL.md and the provided scripts stay within the stated purpose: they generate files, create a git repo, create/push a GitHub repo, configure Pages, and rely on a GitHub Actions workflow. The docs include absolute example paths (e.g., /root/clawd/...) which are only examples but could mislead an autonomous agent to use system-root locations; otherwise the instructions do not try to read unrelated system files or exfiltrate data.

Install Mechanism

This is an instruction-only skill (no package install step). Files are included in the bundle and nothing is downloaded or extracted from arbitrary URLs during install — lower install risk.

Credentials

The skill declares no required env vars or primary credential, yet its scripts call 'gh' and use 'gh api' and rely on 'gh auth status' (which uses local credentials/tokens). That means GitHub authentication (an OAuth token or local gh credential) is implicitly required but not declared. The metadata should at least list required binaries (gh, git) and note that an authenticated GitHub account with appropriate scopes is necessary.

Persistence & Privilege

The skill does not request permanent inclusion (always:false) and does not modify other skills or global agent settings. It does perform operations in the user's GitHub account (creating repos, pushing), which is consistent with its purpose but is a potentially impactful action when invoked autonomously.

What to consider before installing

This skill will run local scripts that use git and the GitHub CLI (gh) to create repositories, push code, and call the GitHub API. Before installing or running it: - Understand it requires the gh CLI and git to be installed and the gh CLI to be authenticated (it will use your gh credentials/token). The skill metadata does not list these dependencies — verify them yourself. - Review the included scripts (init_project.sh and deploy_github_pages.sh) to confirm they do what you expect (they create repos, push to origin, and call gh api to configure Pages). - If you allow autonomous invocation, the agent could create public repositories and push content in your GitHub account; consider using a throwaway/test GitHub account or verifying gh auth scopes (pages, repo) before granting access. - The documentation contains absolute example paths (/root/...), which are examples only — ensure the agent executes scripts in a safe working directory. - If you need stricter control, run the scripts manually rather than giving the agent autonomous permission, or inspect and run them yourself after confirming dependencies and desired repository visibility. If you want, I can produce a short checklist of safe steps to run this in a disposable account or help you inspect the scripts line-by-line.

Overview

This skill enables autonomous creation and deployment of static websites to GitHub Pages. It follows a complete workflow from project structure initialization through automatic deployment via GitHub Actions, optimized for single-page applications, portfolios, and landing pages.

Core Workflow

1. Project Initialization

Create the project structure:

bash scripts/init_project.sh <project-name>

This creates:

project-name/
├── index.html
├── styles.css
├── script.js
├── README.md
└── .github/
    └── workflows/
        └── deploy.yml

2. Development

Build the website following these principles:

• Single-page first: Optimize for one-page layouts unless multiple pages explicitly required
• Autonomous generation: Generate complete, production-ready code without placeholders
• Modern design: Use modern CSS (flexbox, grid), responsive design, clean aesthetics
• No dependencies: Pure HTML/CSS/JS when possible, CDN links if frameworks needed

Use templates from assets/templates/ as starting points:

• base-html/ - Minimal HTML5 boilerplate
• portfolio/ - Portfolio/CV template with sections
• landing/ - Landing page with hero and CTA

3. GitHub Repository Setup

bash scripts/deploy_github_pages.sh <project-name> <github-username>

This script:

1. Initializes git repository
2. Creates GitHub repository via GitHub CLI
3. Configures GitHub Pages settings
4. Pushes initial commit
5. Triggers first deployment

4. Deployment

GitHub Actions automatically deploys on push to main branch. The workflow:

• Checks out code
• Deploys to gh-pages branch
• Makes site live at https://<username>.github.io/<project-name>/

Architecture Guidelines

HTML Structure

• Semantic HTML5 elements
• Meta tags for SEO and social sharing
• Responsive viewport configuration
• Favicon and icons

CSS Design

• Mobile-first responsive design
• CSS variables for theming
• Flexbox/Grid for layouts
• Smooth transitions and animations
• Dark mode support when appropriate

JavaScript

• Vanilla JS preferred
• Progressive enhancement
• Event delegation
• No console errors

Performance

• Optimized images
• Minified assets for production
• Lazy loading where appropriate
• Fast initial load time

Quick Examples

Example 1: Portfolio CV Site

User request: "Crée-moi un site portfolio CV"

Action:

1. Run init_project.sh portfolio-cv
2. Use assets/templates/portfolio/ as base
3. Generate complete HTML with sections: Hero, About, Skills, Projects, Contact
4. Deploy with deploy_github_pages.sh portfolio-cv username

Example 2: Landing Page

User request: "Fais-moi une landing page pour mon app"

Action:

1. Run init_project.sh app-landing
2. Use assets/templates/landing/ as base
3. Generate with Hero, Features, Pricing, CTA
4. Deploy with deploy_github_pages.sh app-landing username

Troubleshooting

GitHub Pages Not Deploying

• Check repository Settings → Pages → Source is set to gh-pages branch
• Verify GitHub Actions workflow ran successfully
• Check DNS propagation (can take 5-10 minutes)

Permission Errors

• Ensure gh CLI is authenticated: gh auth status
• Check repository permissions on GitHub

Build Failures

• Review Actions logs in repository
• Verify .github/workflows/deploy.yml syntax
• Check file paths and references

Resources

scripts/

• init_project.sh - Initialize project structure
• deploy_github_pages.sh - Deploy to GitHub Pages

references/

• workflow.md - Detailed workflow documentation
• design-patterns.md - Design best practices

assets/

• templates/base-html/ - Minimal HTML5 boilerplate
• templates/portfolio/ - Portfolio/CV template
• templates/landing/ - Landing page template
• .github/workflows/deploy.yml - GitHub Actions workflow template