How do I install the Toad Bootstrap Project skill?

Run npx skillmds@latest add delorenj/toad-bootstrap-project 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 Toad Bootstrap Project safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Toad Bootstrap Project?

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 Toad Bootstrap Project free to use?

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

Who published Toad Bootstrap Project?

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

Toad Bootstrap Project by delorenj — Agent Skill

Name: Toad Bootstrap Project
Author: delorenj

Toad Bootstrap Project

Choreograph Toad's end-to-end new-project flow — create a GitHub repo, link the local dir, scaffold with pjangler, and provision the Plane board + Hermes PM. Dry-run first, one explicit go-live gate. Use when creating and wiring a brand-new 33GOD project.

delorenj 7514dcc 2.2 KB Updated Sep 17, 2026 1 repo stars

File contents

Toad — Bootstrap a Project

Choreographs Toad's marquee flow. Each step dry-runs first; nothing with a blast radius runs until the operator opts into live (TOAD_ALLOW_LIVE=1) and confirms. The tools do the work; this skill sequences them and narrates.

Inputs to gather

org — one of AutomaticAI-io, delorenj, IntelliForia.
name — kebab-case repo/project name.
visibility — public or private (default private).
description — one line.
dir — local directory (defaults to ~/code/<name>).

Flow

Preview everything (dry-run). Call each tool with defaults (no live):
1. git_repo_create { org, name, visibility, description } → prints the gh repo create … plan. (net-new; pjangler cannot do this.)
2. project_link { dir, repoUrl } → prints the git init/remote/commit/push plan. (net-new.)
3. project_init { name, dir } → dry-runs pjangler init (registry + CommonProject scaffold + .project.json); writes nothing.
4. hermes_deploy { dir } → prints the pjangler hermes-agent plan (creates the Plane board + canonical Hermes PM + Ticket Sentinel). Sprint-2 / heavy.
Confirm. Show the operator the full ordered plan and the blast radius (a real repo, a real board, a running agent). Get an explicit "go".
Go live (only after confirmation): re-run steps 1–3 with live:true / apply:true in a shell where TOAD_ALLOW_LIVE=1. Run hermes_deploy with live:true last, as its own decision.
Verify. project_audit { repo: dir } should show improved parity; the .project.json should show a linked board.

Safety

Never pass live:true/apply:true before the operator confirms.
If TOAD_ALLOW_LIVE is unset, the tools refuse live and return the plan — that is expected, not an error.
Prefer pjangler for anything it already does; only git_repo_create and project_link are Toad-native.

---name: toad-bootstrap-projectdescription: Choreograph Toad's end-to-end new-project flow — create a GitHub repo, link the local dir, scaffold with pjangler, and provision the Plane board + Hermes PM. Dry-run first, one explicit go-live gate. Use when creating and wiring a brand-new 33GOD project.---# Toad — Bootstrap a ProjectChoreographs Toad's marquee flow. Each step **dry-runs first**; nothing with ablast radius runs until the operator opts into live (`TOAD_ALLOW_LIVE=1`) andconfirms. The tools do the work; this skill sequences them and narrates.## Inputs to gather- **org** — one of `AutomaticAI-io`, `delorenj`, `IntelliForia`.- **name** — kebab-case repo/project name.- **visibility** — `public` or `private` (default `private`).- **description** — one line.- **dir** — local directory (defaults to `~/code/<name>`).## Flow1. **Preview everything (dry-run).** Call each tool with defaults (no `live`): 1. `git_repo_create { org, name, visibility, description }` → prints the `gh repo create …` plan. *(net-new; pjangler cannot do this.)* 2. `project_link { dir, repoUrl }` → prints the git init/remote/commit/push plan. *(net-new.)* 3. `project_init { name, dir }` → dry-runs `pjangler init` (registry + CommonProject scaffold + `.project.json`); writes nothing. 4. `hermes_deploy { dir }` → prints the `pjangler hermes-agent` plan (creates the Plane board + canonical Hermes PM + Ticket Sentinel). **Sprint-2 / heavy.**2. **Confirm.** Show the operator the full ordered plan and the blast radius (a real repo, a real board, a running agent). Get an explicit "go".3. **Go live** (only after confirmation): re-run steps 1–3 with `live:true` / `apply:true` in a shell where `TOAD_ALLOW_LIVE=1`. Run `hermes_deploy` with `live:true` last, as its own decision.4. **Verify.** `project_audit { repo: dir }` should show improved parity; the `.project.json` should show a linked board.## Safety- Never pass `live:true`/`apply:true` before the operator confirms.- If `TOAD_ALLOW_LIVE` is unset, the tools refuse live and return the plan — that is expected, not an error.- Prefer `pjangler` for anything it already does; only `git_repo_create` and `project_link` are Toad-native.

Frequently asked questions