Aaron Jackson avatar

Aaron Jackson

Community

@yolanother

50Followers
|
177Public Repos
|
2Published Skills

By day I'm a software engineer working for corporations, by night enjoy working on open source, building libraries, games and VR experiences.

Skills Distribution
DomainDeveloper To...Release Engineerin.. (40%)GPU Inference Engi.. (35%)Linux Systems & Di.. (25%)

Agent Skills by Aaron Jackson

Showing 2 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About Aaron Jackson

FAQPage Schema
What tasks can I accomplish with yolanother's Llama Manager skills?

You can build and publish a complete signed Llama Manager appliance release (.deb packages, APT repo, ISO) with atomic publish and download-site verification, and separately build or update the ROCm llama.cpp llama-server engine for the AMD Strix Halo iGPU, including new model architecture support.

Who are these skills designed for?

They target the maintainer and release engineers of the Llama Manager appliance—developers comfortable with Debian packaging, distrobox containers, ROCm builds, and rsync-based deployment who need to cut releases or bump the inference engine version.

How does the release build and publish process run?

The unattended release runner builds signed packages and the ISO from main, stages pinned inputs from the asset mirror, performs an atomic publish, then runs a two-pass rsync to the thromgar host and verifies public URLs. A --no-sync local loop with serve-local.sh supports iteration.

When should I use build-llama-cpp versus build-and-deploy-release?

Use build-llama-cpp to update or rebuild the ROCm llama.cpp llama-server engine itself—version bumps, new model architectures, or engine-level build fixes. Use build-and-deploy-release only to cut and publish a full appliance release; it does not rebuild llama.cpp.

What are the prerequisites and signing requirements?

The llama.cpp build requires a pinned checkout and a distrobox ROCm build environment on AMD Strix Halo hardware. The release flow stages pinned inputs from an asset mirror; signing may run unattended or require a human depending on the step, per the skill's documented gotchas.