How do I install the Gh Bootstrap skill?

Run npx skillmds@latest add bahayonghang/gh-bootstrap in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gh Bootstrap safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gh Bootstrap?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gh Bootstrap free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gh Bootstrap?

bahayonghang (@bahayonghang) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gh Bootstrap by bahayonghang — Agent Skill

Name: Gh Bootstrap
Rating: 4.5 (4 reviews)
Author: bahayonghang

Gh Bootstrap

Initialize GitHub repository configuration from vetted upstream templates. Use when setting up repository automation, issue and PR templates, CI workflows, or baseline GitHub project files for a new or existing repo.

bahayonghang ae81b8e 5 files · 50.7 KB Updated Sep 10, 2026

File contents

In the commands below, <skill-dir> is this skill's base directory, announced when the skill loads. Substitute the literal path; it is not an environment variable. The runtime script gh_bootstrap_runtime.py is the only execution engine — never hand-roll the detect / fetch / render / validate steps.

Ask the user for communication language and template language preference, plus the desired mode: quick (sensible defaults, minimal interaction), custom (choose specific templates), or full (all available templates).
Detect languages, frameworks, and existing GitHub files with python "<skill-dir>/scripts/gh_bootstrap_runtime.py" detect "$ARGUMENTS" before planning. If detection returns no languages (empty project or unrecognized stack), ask the user to specify the primary language manually instead of guessing.
Call AskUserQuestion to collect necessary configuration variables (project name, GitHub owner/repo, author, license, and any component-specific values).
Scan for existing config files and plan conflict resolution. Never overwrite existing files without explicit user approval.
Read specs/template-catalog.md to map required files to repository URLs, then use python "<skill-dir>/scripts/gh_bootstrap_runtime.py" fetch-template ... to download the chosen template sources. If a template download fails (network error, 404, timeout), report which template failed and offer to skip it or retry.
Render files with python "<skill-dir>/scripts/gh_bootstrap_runtime.py" render-template ... so placeholder replacement is deterministic.
Validate the generated tree with python "<skill-dir>/scripts/gh_bootstrap_runtime.py" validate-tree <target-root> and refuse completion if unreplaced {{placeholders}} remain.

Mandatory Rules

NEVER write config files from memory; MUST render from downloaded templates.
ALWAYS replace {{variable}} placeholders (e.g. {{projectName}}); NEVER alter GitHub Actions expressions (${{ github.* }}, ${{ secrets.* }}) or action version pins (e.g. @v4). The renderer only substitutes {{...}}.
Output targets .github/workflows/, issue templates, PR templates, and baseline community files.

---name: gh-bootstrapdescription: Initialize GitHub repository configuration from vetted upstream templates. Use when setting up repository automation, issue and PR templates, CI workflows, or baseline GitHub project files for a new or existing repo.---> In the commands below, `<skill-dir>` is this skill's base directory, announced when the skill loads. Substitute the literal path; it is not an environment variable. The runtime script `gh_bootstrap_runtime.py` is the only execution engine — never hand-roll the detect / fetch / render / validate steps.1. Ask the user for communication language and template language preference, plus the desired mode: **quick** (sensible defaults, minimal interaction), **custom** (choose specific templates), or **full** (all available templates).2. Detect languages, frameworks, and existing GitHub files with `python "<skill-dir>/scripts/gh_bootstrap_runtime.py" detect "$ARGUMENTS"` before planning. If detection returns no languages (empty project or unrecognized stack), ask the user to specify the primary language manually instead of guessing.3. Call `AskUserQuestion` to collect necessary configuration variables (project name, GitHub owner/repo, author, license, and any component-specific values).4. Scan for existing config files and plan conflict resolution. Never overwrite existing files without explicit user approval.5. Read `specs/template-catalog.md` to map required files to repository URLs, then use `python "<skill-dir>/scripts/gh_bootstrap_runtime.py" fetch-template ...` to download the chosen template sources. If a template download fails (network error, 404, timeout), report which template failed and offer to skip it or retry.6. Render files with `python "<skill-dir>/scripts/gh_bootstrap_runtime.py" render-template ...` so placeholder replacement is deterministic.7. Validate the generated tree with `python "<skill-dir>/scripts/gh_bootstrap_runtime.py" validate-tree <target-root>` and refuse completion if unreplaced `{{placeholders}}` remain.## Mandatory Rules- **NEVER** write config files from memory; **MUST** render from downloaded templates.- **ALWAYS** replace `{{variable}}` placeholders (e.g. `{{projectName}}`); **NEVER** alter GitHub Actions expressions (`${{ github.* }}`, `${{ secrets.* }}`) or action version pins (e.g. `@v4`). The renderer only substitutes `{{...}}`.- Output targets `.github/workflows/`, issue templates, PR templates, and baseline community files.

Frequently asked questions