New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Bootstrap Feature

by openbootdotdev in openbootdotdev/openboot

A skill your agent uses when adding a new CLI subcommand or feature to openboot.

MITAuto-check passedTesting & QA

Install Bootstrap Feature

skills CLI
$ npx skills add openbootdotdev/openboot --skill bootstrap-feature -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install openbootdotdev/openboot bootstrap-feature --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/openbootdotdev/openboot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/bootstrap-feature .claude/skills/bootstrap-feature && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
bootstrap-feature
GitHub stars
275
Token cost
~1.1k tokens
SKILL.md length
365 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when adding a new CLI subcommand or feature to openboot.

  • Works in 6 steps: Where the code goes → Cobra command skeleton → Runner interface for testability → …
  • Adding a new CLI subcommand
  • SKILL.md covers Step 1 — Where the code goes, Step 2 — Cobra command skeleton, Step 3 — Runner interface for… and Step 4 — Test placement, plus 3 more sections
  • Calls go and make

What it does

Bootstrap Feature is an agent skill from openbootdotdev/openboot. Use when adding a new CLI subcommand or feature to openboot. Walks through the canonical pattern: cobra command registration, runner wiring, archtest awareness, and test placement. Trigger when the user says "add a command", "new subcommand", "implement feature X for the CLI", or starts editing under internal/cli/.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA. It works with macOS and Homebrew. The repository describes itself as: Set up your Mac dev environment in one command — CLI + Web Dashboard + Team sharing. The licence is MIT.

When your agent uses it

  • Adding a new CLI subcommand
  • Feature to openboot
  • The user says add a command
  • Implement feature X for the CLI

Example prompts

  • “add a command”
  • “new subcommand”
  • “implement feature X for the CLI”
  • “/bootstrap-feature”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Where the code goes
  2. Cobra command skeleton
  3. Runner interface for testability
  4. Test placement
  5. Verify before committing
  6. Conventional commit

What it can do on your machine

Read from SKILL.md and the folder at commit 259b119. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • go
    • make

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Bootstrap Feature loads about 1.1k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 365 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~84
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from openbootdotdev/openboot at commit 259b119, republished under its MIT licence (© openbootdotdev). 365 words, ~1,064 tokens.

Download SKILL.mdSave it as .claude/skills/bootstrap-feature/SKILL.md (or your agent's skills folder).
name
bootstrap-feature
description
Use when adding a new CLI subcommand or feature to openboot. Walks through the canonical pattern: cobra command registration, runner wiring, archtest awareness, and test placement. Trigger when the user says "add a command", "new subcommand", "implement feature X for the CLI", or starts editing under internal/cli/.

Bootstrap a new openboot feature

This skill gives the canonical recipe for adding a new CLI command or feature to openboot without violating project invariants.

Step 1 — Where the code goes

Kind of thingLocation
New CLI subcommandinternal/cli/<verb>.go, register in internal/cli/root.go init()
Subprocess call (any binary)internal/system.RunCommand / RunCommandSilent — do not call exec.Command directly
HTTP call (any URL)internal/httputil.Do — handles 429 + Retry-After
Path under ~os.UserHomeDir() — never os.Getenv("HOME"), never hardcode ~
User-visible outputinternal/ui.* helpers — never raw fmt.Println
Destructive actionguarded by cfg.DryRun check
Error returned to callerwrapped: fmt.Errorf("context: %w", err)

These are enforced (or planned) by internal/archtest. The rule that covers each invariant is listed in AGENTS.md.

Step 2 — Cobra command skeleton

go
// internal/cli/myverb.go
package cli

import "github.com/spf13/cobra"

func newMyVerbCmd() *cobra.Command {
	var flag string
	cmd := &cobra.Command{
		Use:   "myverb [arg]",
		Short: "One-line description",
		Long:  "Longer description if useful.",
		Args:  cobra.ExactArgs(1),
		RunE: func(cmd *cobra.Command, args []string) error {
			return runMyVerb(cmd.Context(), args[0], flag)
		},
	}
	cmd.Flags().StringVar(&flag, "flag", "", "Description of the flag")
	return cmd
}

Register it in internal/cli/root.go:

go
rootCmd.AddCommand(newMyVerbCmd())

Step 3 — Runner interface for testability

If your feature shells out, use the Runner pattern so L1 tests can fake subprocess calls. Example from internal/brew/runner.go:

go
type Runner interface {
	Output(args ...string) ([]byte, error)
	CombinedOutput(args ...string) ([]byte, error)
	// ...
}

// realRunner uses exec.Command — this file is in execAllowedPaths.
type realRunner struct{}

func New() *Brew { return &Brew{r: &realRunner{}} }

Then in tests:

go
type fakeRunner struct { ... }
func (f *fakeRunner) Output(args ...string) ([]byte, error) { ... }

This is the pattern that lets the fake-runner half of L1 stay fast and hermetic.

Step 4 — Test placement

ScopeTierBuild tagWhere
Pure logic + fakesL1none<pkg>/<feature>_test.go
Real subprocess in temp dirL1nonetest/integration/<feature>_integration_test.go
Compiled binary, no installsL3e2etest/e2e/...
Real installs on macOSL4 (VM)e2e,vmtest/e2e/...

Default to faked-runner L1 unless the thing you're testing only exists when a real brew/git/npm is on the path — then add an integration test under test/integration/ (no build tag; it runs as part of L1).

Show full SKILL.md (133 more words)Show less

Step 5 — Verify before committing

bash
go vet ./...
make test-unit                  # ~75s, includes archtest + integration

If archtest fails with a new violation, fix the code rather than baselining — the baseline is for intentional exceptions and they require justification in the commit message.

Step 6 — Conventional commit

feat: add openboot myverb command for X

One thing per commit. If you also fixed an unrelated bug along the way, split it into a separate commit.

Common mistakes

  1. Calling exec.Command from the feature file — refactor through internal/system or add a Runner. archtest will catch this.
  2. Skipping cfg.DryRun check — destructive ops must be a no-op under --dry-run. Print "[DRY-RUN] Would X" instead of doing X.
  3. Hardcoding ~/ — always os.UserHomeDir() then filepath.Join.
  4. Raw fmt.Println — use ui.Info, ui.Success, ui.Warn, ui.Error.
  5. Forgetting to register the command in root.go — cobra silently does nothing if AddCommand is missed.

© openbootdotdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/bootstrap-feature of openbootdotdev/openboot.

Open the folder on GitHubat commit 259b119

Compare with similar skills

Bootstrap Feature next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Bootstrap Feature compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bootstrap Feature this skillopenbootdotdev/openboot275—~1.1kAutomated safety check: PassMIT
Payload Snapshotopenshift-eng/ai-helpers120—~6.4kAutomated safety check: PassApache-2.0
Edge Bringupexeex/edge-cores110—~1.7kAutomated safety check: NotesApache-2.0
Mole CLI Release Flowtw93/Mole70k—~2.5kAutomated safety check: PassGPL-3.0
Reproduce macOS Python FlavorsNuitka/Nuitka15k—~1.7kAutomated safety check: PassAGPL-3.0
CodexBar macOS Releasesteipete/CodexBar22k—~1.5kAutomated safety check: PassMIT

Similar skills

  • Payload Snapshot

    openshift-eng/ai-helpers

    Snapshot OpenShift payload data (release controller, PR diffs, comments, CI jobs, JUnit results, regression tracking) to a local directory for offline analysis

    120 GitHub stars~6.4k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Edge Bringup

    exeex/edge-cores

    Prepare a macOS or Ubuntu machine for edge-e3 development, diagnose missing Verilator/LLVM/Python dependencies, initialize the public repository, and answer or act on the example prompts in the root…

    110 GitHub stars~1.7k tokensUpdated 12 days ago
    AI & LLM EngineeringAuto-check: notes

  • Mole CLI Release Flow

    tw93/Mole

    Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.

    70k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Reproduce macOS Python Flavors

    Nuitka/Nuitka

    Reproduce macOS Nuitka issues across Python distributions and GitHub Actions Python packaging.

    15k GitHub stars~1.7k tokensUpdated today
    DevOps & CloudAuto-check passed

  • CodexBar macOS Release

    steipete/CodexBar

    Releases a signed, notarized CodexBar build: confirms the changelog, resolves signing credentials from 1Password, runs the release script in tmux, and updates the Sparkle appcast and Homebrew tap.

    22k GitHub stars~1.5k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Release

    eugene1g/agent-safehouse

    Run the local Agent Safehouse release flow: inspect commits since the last published release, propose the next SemVer version and changelog, present a dry-run for confirmation, then update…

    2.1k GitHub stars~3.5k tokensUpdated 8 days ago
    DevelopmentAuto-check passed

More from openbootdotdev/openboot

  • Ship PR

    openbootdotdev/openboot

    A skill your agent uses when the user is done editing and wants to ship the current branch via a pull request — phrases like "open a PR", "ship it", "ship this", "submit the PR", "let's send it"…

    275 GitHub stars~3.6k tokensUpdated 14 days ago
    Auto-check: warnings

Works with

Categories

Questions about Bootstrap Feature

What does Bootstrap Feature do?

A skill your agent uses when adding a new CLI subcommand or feature to openboot. Bootstrap Feature is an agent skill from openbootdotdev/openboot. Use when adding a new CLI subcommand or feature to openboot.

When should I use Bootstrap Feature?

Bootstrap Feature fits situations like: adding a new CLI subcommand; feature to openboot; the user says add a command; implement feature X for the CLI.

How do I install Bootstrap Feature in Claude Code?

Run `npx skills add openbootdotdev/openboot --skill bootstrap-feature -a claude-code`. Or copy the skill folder (.agents/skills/bootstrap-feature in openbootdotdev/openboot) into .claude/skills/bootstrap-feature in your project. Claude Code loads it when a task matches its description.

How do I install Bootstrap Feature in Codex?

Run `npx skills add openbootdotdev/openboot --skill bootstrap-feature -a codex`. Or copy the skill folder (.agents/skills/bootstrap-feature in openbootdotdev/openboot) into .agents/skills/bootstrap-feature in your project. Codex loads it when a task matches its description.

Can I use Bootstrap Feature in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openbootdotdev/openboot --skill bootstrap-feature -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bootstrap-feature, .gemini/skills/bootstrap-feature, .github/skills/bootstrap-feature and .opencode/skills/bootstrap-feature in your project.

What does Bootstrap Feature need to run?

Going by SKILL.md and its folder, Bootstrap Feature needs the command-line tools its instructions call (go and make).

Does Bootstrap Feature access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Bootstrap Feature safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Bootstrap Feature use?

Bootstrap Feature is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Bootstrap Feature use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Bootstrap Feature?

Skills that share tags, products or a category with Bootstrap Feature: Payload Snapshot (openshift-eng/ai-helpers, 120 stars), Edge Bringup (exeex/edge-cores, 110 stars), Mole CLI Release Flow (tw93/Mole, 70k stars) and Reproduce macOS Python Flavors (Nuitka/Nuitka, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bootstrap Feature?

openbootdotdev (a GitHub organization) maintains it in openbootdotdev/openboot, which has 275 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 23, 2026.

Source: openbootdotdev/openboot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.