Menu
Use when preparing, publishing, verifying, or diagnosing Firkin crates.io/GitHub releases from the standalone Firkin repository.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when verifying Firkin can be installed and used from a fresh external Rust project without local path dependencies.
Use when iterating quickly on Firkin performance, local profiling, stage timing, bottleneck attribution, smoke evidence, or benchmark-derived instrumentation in the Firkin checkout.
Use rs-hack for large Rust refactors in Firkin/Cube, especially moving the CubeAPI Firkin backend into firkin-runtime::single_node with AST-aware discovery, batch transforms, dry-run/apply/revert discipline, and compile gates.
| name | firkin-release |
| description | Use when preparing, publishing, verifying, or diagnosing Firkin crates.io/GitHub releases from the standalone Firkin repository. |
Use this skill inside the standalone Firkin repository when the task involves CI, crate packaging, crates.io publication, GitHub release drafts, or release verification.
/Users/darin/vendor/github.com/apple/containerization; it is
source evidence only.cargo publish unless the user explicitly approves publishing in
the current thread.Run these from the repo root before publishing or pushing a release commit:
cargo metadata --format-version 1
cargo fmt --check
CARGO_TARGET_DIR=/tmp/firkin-standalone-target cargo check --workspace --all-targets
CARGO_TARGET_DIR=/tmp/firkin-standalone-target cargo clippy --workspace --all-targets -- -D warnings
CARGO_TARGET_DIR=/tmp/firkin-standalone-target cargo test --workspace
scripts/check-firkin-crate-graph.sh
git diff --check
firkin-vminitd-bytes defaults to runtime-download, so normal checks and
consumer installs do not require local vminitd/vmexec binaries. Live VM proof
remains a separate, signed macOS flow.
Publish in dependency order. Crates.io rate-limits new crate creation; if a 429 response gives a retry timestamp, wait and resume from the failed crate.
firkin-types
firkin-trace
firkin-artifacts
firkin-envd
firkin-vminitd-bytes
firkin-vsock
firkin-ext4
firkin-e2b-wire
firkin-vmm
firkin-sandbox
firkin-admission
firkin-hygiene
firkin-template
firkin-evidence
firkin-oci
firkin-vminitd-client
firkin-e2b-contract
firkin-e2b-server
firkin-core
firkin-runtime
firkin-benchmark
firkin-single-node
firkin
Use:
cargo publish -p <crate>
If dependent crates fail with no matching package named firkin-* found, the
upstream crate has not propagated through the index yet. Wait and retry the
same crate; do not change dependency versions.
The repository should contain:
.github/workflows/ci.yml for macOS Rust checks..github/workflows/package.yml for package dry-runs and tarball checks..github/workflows/publish.yml for manual crates.io publication with the
crates-io environment and CRATES_IO_TOKEN secret..github/workflows/release.yml for draft prerelease artifacts on
v0.0.1* tags.After push, confirm:
gh repo view delightful-ai/firkin --json nameWithOwner,visibility,defaultBranchRef,url
gh workflow list --repo delightful-ai/firkin
Visibility must remain PRIVATE.
After crates.io publication completes, switch to the firkin-external-consumer
skill and verify from a fresh temp project using crates.io dependencies only.