How do I install the Test Local Twoliter skill?

Run npx skillmds@latest add majiayu000/test-local-twoliter 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 Test Local Twoliter skill do?

Build and test local changes to twoliter before releasing It is listed under Coding & Dev Tools on SkillMD.

Is Test Local Twoliter safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Test Local Twoliter?

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 Test Local Twoliter free to use?

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

Who published Test Local Twoliter?

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

Test Local Twoliter by majiayu000 — Agent Skill

Name: Test Local Twoliter
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Skill: Test Local Twoliter Changes

Purpose

Build twoliter from local source and configure kits to use the locally-built binary for testing changes before release.

When to Use

Making changes to twoliter source code
Testing twoliter modifications before creating a PR
Debugging twoliter behavior
Validating fixes to twoliter

Prerequisites

Twoliter repository cloned in the forest
Rust toolchain installed
At least one kit repository to test with

Procedure

1. Make changes to twoliter source

Edit files in twoliter/twoliter/src/ or twoliter/twoliter/embedded/.

2. Build twoliter

cd twoliter
cargo build --release

The binary will be at target/release/twoliter.

3. Test the changes

Override TWOLITER_DIR to point to your local build directory:

cd kits/bottlerocket-core-kit
make build TWOLITER_DIR=./twoliter/target/release

4. Iterate

After making more changes:

# Rebuild twoliter
cd ./twoliter
cargo build --release

# Test again
cd kits/bottlerocket-core-kit
make build TWOLITER_DIR=./twoliter/target/release

Validation

Verify the local twoliter is being used by checking the path:

cd kits/bottlerocket-core-kit
make build TWOLITER_DIR=./twoliter/target/release 2>&1 | head -5

You should see your modified twoliter being invoked.

Common Issues

Changes not taking effect:

Ensure you ran cargo build --release after making changes
Verify the path in TWOLITER_DIR is correct
Check that the binary exists: ls -lh ./twoliter/target/release/twoliter

Build errors in twoliter:

Run cargo check to see detailed error messages
Run cargo clippy to catch common issues
Run cargo test to verify tests pass

Kit build fails with local twoliter:

Check twoliter output for error messages
Add --log-level debug by modifying the Makefile temporarily or using the twoliter binary directly

Reverting to Released Version

To go back to using the released version, simply omit the TWOLITER_DIR override:

cd kits/bottlerocket-core-kit
make build

This uses the default tools/twoliter/twoliter from the released version.

Related Skills

---name: test-local-twoliterdescription: Build and test local changes to twoliter before releasing--- # Skill: Test Local Twoliter Changes ## Purpose Build twoliter from local source and configure kits to use the locally-built binary for testing changes before release. ## When to Use - Making changes to twoliter source code - Testing twoliter modifications before creating a PR - Debugging twoliter behavior - Validating fixes to twoliter ## Prerequisites - Twoliter repository cloned in the forest - Rust toolchain installed - At least one kit repository to test with ## Procedure ### 1. Make changes to twoliter source Edit files in `twoliter/twoliter/src/` or `twoliter/twoliter/embedded/`. ### 2. Build twoliter ```bash cd twoliter cargo build --release ``` The binary will be at `target/release/twoliter`. ### 3. Test the changes Override `TWOLITER_DIR` to point to your local build directory: ```bash cd kits/bottlerocket-core-kit make build TWOLITER_DIR=./twoliter/target/release ``` ### 4. Iterate After making more changes: ```bash # Rebuild twoliter cd ./twoliter cargo build --release # Test again cd kits/bottlerocket-core-kit make build TWOLITER_DIR=./twoliter/target/release ``` ## Validation Verify the local twoliter is being used by checking the path: ```bash cd kits/bottlerocket-core-kit make build TWOLITER_DIR=./twoliter/target/release 2>&1 | head -5 ``` You should see your modified twoliter being invoked. ## Common Issues **Changes not taking effect:** - Ensure you ran `cargo build --release` after making changes - Verify the path in `TWOLITER_DIR` is correct - Check that the binary exists: `ls -lh ./twoliter/target/release/twoliter` **Build errors in twoliter:** - Run `cargo check` to see detailed error messages - Run `cargo clippy` to catch common issues - Run `cargo test` to verify tests pass **Kit build fails with local twoliter:** - Check twoliter output for error messages - Add `--log-level debug` by modifying the Makefile temporarily or using the twoliter binary directly ## Reverting to Released Version To go back to using the released version, simply omit the `TWOLITER_DIR` override: ```bash cd kits/bottlerocket-core-kit make build ``` This uses the default `tools/twoliter/twoliter` from the released version. ## Related Skills

Frequently asked questions

Test Local Twoliter