Rust Rebuild

VerifiedCaution

Safely modify Allbert's Rust source in an isolated worktree, run Tier A validation, and produce a patch.

Sby Skills Guide Bot
DevelopmentAdvanced
7/23/2026
Claude Code
#rust#git-worktree#patch-review#validation#self-modification

Recommended for

Automated summary

Changes Allbert's Rust source inside an isolated rebuild worktree, runs the Tier A validation chain, and produces an operator-reviewed patch.

Strengths

  • Enforces a clear safety contract: no edits to the source checkout or to skills/rust-rebuild
  • Confines all reads, writes, and validation commands to the kernel-created self-improvement worktree
  • Runs Tier A validation before proposing anything and records the failing command plus output tail
  • Explicitly separates patch generation from installation, which stays an operator decision

Limitations

  • Depends on `allbert-cli self-improvement config show` resolving a source checkout with a pinned Rust toolchain
  • Covers only Tier A validation, not full or end-to-end testing
  • Handles only Rust source changes and yields a patch artifact rather than applying it
When to use it

Use it when the operator explicitly asks Allbert to change its own Rust source and wants a validated patch to review.

When not to use it

Do not use it for non-Rust changes, for editing the source checkout directly, or when Tier A validation cannot be run.

Security analysis

Caution
Quality score88/100

The skill is for controlled self-modification and includes clear safety constraints, but it uses powerful tools (process_exec, write_file) inside a worktree without specifying command allowlisting. That warrants caution rather than risky.

Findings
  • •process_exec allows arbitrary command execution; safety relies on operator discipline and the kernel-created worktree rather than a command allowlist.
  • •write_file can modify Rust source; the skill restricts edits to the worktree, but this boundary is policy-level rather than mechanically enforced by the tool schema.
  • •The self-modification workflow could produce unreviewed changes if the required operator approval and install step are skipped, although the skill explicitly requires review.
How this analysis is made

Examples

Add a CLI flag
Use the rust-rebuild skill to add a --verbose flag to the allbert-cli config subcommand, run Tier A validation, and give me the patch path plus a summary.
Fix a panic
Rebuild: fix the panic in the worktree cleanup code inside the self-improvement worktree, validate it, and propose a patch for my review.
Refactor a module
Use rust-rebuild to extract the validation command runner into its own module, run Tier A validation, and report any failing output instead of installing.

name: rust-rebuild description: "Modify Allbert in an isolated rebuild worktree, run Tier A validation, and produce an operator-reviewed patch." intents: meta allowed-tools: process_exec read_file write_file

Rust Rebuild

Use this skill only when the operator explicitly asks Allbert to change its own Rust source.

Safety Contract

  • Never edit the source checkout directly.
  • Never edit skills/rust-rebuild/ in the source checkout.
  • Work only inside the active self-improvement worktree.
  • Run the Tier A validation chain before proposing a patch.
  • Treat failures as needs-review, not as permission to bypass review.
  • Produce a concise summary plus the patch artifact path; do not inline large diffs in chat.

Operating Ritual

  1. Confirm that allbert-cli self-improvement config show resolves a source checkout and reports a pinned Rust toolchain.
  2. Use the kernel-created worktree path from the self-improvement workflow.
  3. Inspect files with read_file and make edits with write_file only inside that worktree.
  4. Use process_exec inside the worktree for validation commands.
  5. If validation fails, capture the failing command and the relevant output tail.
  6. Hand the operator a patch summary and next-step hint for approval.

The rebuild output is a review artifact, not an install action. The operator must explicitly approve and install any patch in a later step.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/rust-rebuild-mrx3xxn7/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/rust-rebuild-mrx3xxn7' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/rust-rebuild-mrx3xxn7/download' --output '.skill-downloads/rust-rebuild-mrx3xxn7/SKILL.md.part' && mv '.skill-downloads/rust-rebuild-mrx3xxn7/SKILL.md.part' '.skill-downloads/rust-rebuild-mrx3xxn7/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): process_exec read_file write_file

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/rust-rebuild-mrx3xxn7/SKILL.md' && test -s '.skill-downloads/rust-rebuild-mrx3xxn7/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/rust-rebuild' && cp -R '.skill-downloads/rust-rebuild-mrx3xxn7' '.claude/skills/rust-rebuild'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/rust-rebuild-mrx3xxn7'

openskills read 'rust-rebuild-mrx3xxn7'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/rust-rebuild-mrx3xxn7/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills