How do I install the Build Variant From Local Kits skill?

Run npx skillmds add majiayu000/build-variant-from-local-kits 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.

What does the Build Variant From Local Kits skill do?

Build a variant using locally published kits for development validation It is listed under Coding & Dev Tools on SkillMD.

Is Build Variant From Local Kits safe to use?

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

Which AI agents work with Build Variant From Local Kits?

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 Build Variant From Local Kits free to use?

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

Who published Build Variant From Local Kits?

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

Build Variant From Local Kits by majiayu000

Name: Build Variant From Local Kits
Rating: 4.5 (4 reviews)
Author: majiayu000

File contents

Skill: Build Variant from Local Kits

Purpose

Build a complete Bottlerocket variant image using kits published to the local development registry. This enables end-to-end testing of kit changes before publishing to production registries.

When to Use

Testing kit changes in a complete variant build
Creating bootable images for local testing
End-to-end validation of kit modifications

Prerequisites

Kits already built and published to local registry (use build-kit-locally skill)
Local registry running
Bottlerocket variant repository

Procedure

1. Configure for local registry

cd ./bottlerocket
brdev twoliter use-local-deps

This creates Twoliter.override pointing to the local registry for fetching kits.

2. Select which kits to fetch locally

Edit Twoliter.toml and set vendor = "local" for kits you want from the local registry:

[kit.bottlerocket-core-kit]
vendor = "local"  # Fetch from local registry
version = "2.0.0"

[kit.bottlerocket-kernel-6.1-kit]
# No vendor override - uses upstream
version = "2.0.0"

Only kits with vendor = "local" will be fetched from the local registry; others use upstream.

3. Update lock file

./tools/twoliter/twoliter update

4. Build the variant

cargo make

For specific variant:

cargo make -e BUILDSYS_VARIANT=aws-k8s-1.31

For specific architecture:

cargo make -e BUILDSYS_ARCH=aarch64

5. Locate the built image

ls -lh build/images/*.img

Validation

The build should complete successfully and produce an .img file in build/images/.

Cleanup

When done testing, restore upstream configuration:

brdev twoliter use-upstream-deps

This removes Twoliter.override. Remember to also revert any vendor = "local" changes in Twoliter.toml.

Common Issues

Kit not found in registry:

Error: failed to pull kit

Solution: Verify kit is published with brdev registry list

Version mismatch: Solution: Ensure Twoliter.toml version matches the published kit version

Lock file out of sync: Solution: Run ./tools/twoliter/twoliter update again

---name: build-variant-from-local-kitsdescription: Build a variant using locally published kits for development validation--- # Skill: Build Variant from Local Kits ## Purpose Build a complete Bottlerocket variant image using kits published to the local development registry. This enables end-to-end testing of kit changes before publishing to production registries. ## When to Use - Testing kit changes in a complete variant build - Creating bootable images for local testing - End-to-end validation of kit modifications ## Prerequisites - Kits already built and published to local registry (use `build-kit-locally` skill) - Local registry running - Bottlerocket variant repository ## Procedure ### 1. Configure for local registry ```bash cd ./bottlerocket brdev twoliter use-local-deps ``` This creates `Twoliter.override` pointing to the local registry for fetching kits. ### 2. Select which kits to fetch locally Edit `Twoliter.toml` and set `vendor = "local"` for kits you want from the local registry: ```toml [kit.bottlerocket-core-kit] vendor = "local" # Fetch from local registry version = "2.0.0" [kit.bottlerocket-kernel-6.1-kit] # No vendor override - uses upstream version = "2.0.0" ``` Only kits with `vendor = "local"` will be fetched from the local registry; others use upstream. ### 3. Update lock file ```bash ./tools/twoliter/twoliter update ``` ### 4. Build the variant ```bash cargo make ``` For specific variant: ```bash cargo make -e BUILDSYS_VARIANT=aws-k8s-1.31 ``` For specific architecture: ```bash cargo make -e BUILDSYS_ARCH=aarch64 ``` ### 5. Locate the built image ```bash ls -lh build/images/*.img ``` ## Validation The build should complete successfully and produce an `.img` file in `build/images/`. ## Cleanup When done testing, restore upstream configuration: ```bash brdev twoliter use-upstream-deps ``` This removes `Twoliter.override`. Remember to also revert any `vendor = "local"` changes in `Twoliter.toml`. ## Common Issues **Kit not found in registry:** ``` Error: failed to pull kit ``` Solution: Verify kit is published with `brdev registry list` **Version mismatch:** Solution: Ensure `Twoliter.toml` version matches the published kit version **Lock file out of sync:** Solution: Run `./tools/twoliter/twoliter update` again

Frequently asked questions