ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified

web-deploy-github

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.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/kjaylee/kj-web-deploy-github
Or

Web Deploy GitHub Pages

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

Metadata

Author@kjaylee
Stars1776
Views0
Updated2026-03-02
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-kjaylee-kj-web-deploy-github": {
      "enabled": true,
      "auto_update": true
    }
  }
}
Safety NoteClawKit audits metadata but not runtime behavior. Use with caution.

Related Skills

ui-ux-pro-max

UI/UX design intelligence and implementation guidance for building polished interfaces. Use when the user asks for UI design, UX flows, information architecture, visual style direction, design systems/tokens, component specs, copy/microcopy, accessibility, or to generate/critique/refine frontend UI (HTML/CSS/JS, React, Next.js, Vue, Svelte, Tailwind). Includes workflows for (1) generating new UI layouts and styling, (2) improving existing UI/UX, (3) producing design-system tokens and component guidelines, and (4) turning UX recommendations into concrete code changes.

kjaylee 1776

ralph-loop

AI 자율 구현 방법론. 구현/개발/코딩 요청 시 자동 적용. 메인은 마더 서브에이전트를 spawn하고, 마더가 워커들을 관리. specs/ → IMPLEMENTATION_PLAN.md → 1태스크씩 구현 → 2단계 리뷰 → 테스트 → 반복.

kjaylee 1776

game-dev-rust-godot

Game development workflow using Rust+WASM or Godot 4.x for HTML5 games. Use when creating new games, implementing game mechanics, or porting existing games. Follows TDD-based production pipeline v3.1 with asset-first approach. Covers Rust(Macroquad/Bevy), Godot HTML5 Export, asset acquisition, test case writing, and QA automation. Master directive (2026-02-06) - ONLY Rust+WASM or Godot allowed, JS/TS frameworks prohibited.

kjaylee 1776

subagent-dev

Execute implementation plans using fresh subagents per task with two-stage review (spec compliance + code quality). Use when executing multi-task plans with independent work units. Enhances ralph-loop methodology.

kjaylee 1776

systematic-debugging

Root-cause-first debugging methodology. Use when encountering any bug, test failure, or unexpected behavior BEFORE proposing fixes. Prevents random fix attempts that waste time and create new bugs.

kjaylee 1776