Subspace Builds
dallison/subspace
Build and test Subspace across supported platforms and build systems.
Bump cmake/sdk-pin.cmake to a new published SDK C++ desktop kit (version + SHA-256 + IDL lock).
MITAuto-check passed
Install Wally Kit Pin
$ npx skills add RunanywhereAI/wally --skill wally-kit-pin -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install RunanywhereAI/wally wally-kit-pin --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/RunanywhereAI/wally.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/wally-kit-pin .claude/skills/wally-kit-pin && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "wally-kit-pin" agent skill from https://github.com/RunanywhereAI/wally/tree/main/.agents/skills/wally-kit-pin into .claude/skills/wally-kit-pin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wally-kit-pin", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/RunanywhereAI/wally/tree/main/.agents/skills/wally-kit-pinType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add RunanywhereAI/wally --skill wally-kit-pin -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install RunanywhereAI/wally wally-kit-pin --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RunanywhereAI/wally.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/wally-kit-pin .agents/skills/wally-kit-pin && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wally-kit-pin" agent skill from https://github.com/RunanywhereAI/wally/tree/main/.agents/skills/wally-kit-pin into .agents/skills/wally-kit-pin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wally-kit-pin", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add RunanywhereAI/wally --skill wally-kit-pin -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install RunanywhereAI/wally wally-kit-pin --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RunanywhereAI/wally.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/wally-kit-pin .cursor/skills/wally-kit-pin && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "wally-kit-pin" agent skill from https://github.com/RunanywhereAI/wally/tree/main/.agents/skills/wally-kit-pin into .cursor/skills/wally-kit-pin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wally-kit-pin", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/RunanywhereAI/wally.git --path .agents/skills/wally-kit-pin--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add RunanywhereAI/wally --skill wally-kit-pin -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install RunanywhereAI/wally wally-kit-pin --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RunanywhereAI/wally.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/wally-kit-pin .gemini/skills/wally-kit-pin && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "wally-kit-pin" agent skill from https://github.com/RunanywhereAI/wally/tree/main/.agents/skills/wally-kit-pin into .gemini/skills/wally-kit-pin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wally-kit-pin", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install RunanywhereAI/wally wally-kit-pinInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add RunanywhereAI/wally --skill wally-kit-pin -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/RunanywhereAI/wally.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/wally-kit-pin .github/skills/wally-kit-pin && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "wally-kit-pin" agent skill from https://github.com/RunanywhereAI/wally/tree/main/.agents/skills/wally-kit-pin into .github/skills/wally-kit-pin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wally-kit-pin", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add RunanywhereAI/wally --skill wally-kit-pin -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install RunanywhereAI/wally wally-kit-pin --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RunanywhereAI/wally.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/wally-kit-pin .opencode/skills/wally-kit-pin && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "wally-kit-pin" agent skill from https://github.com/RunanywhereAI/wally/tree/main/.agents/skills/wally-kit-pin into .opencode/skills/wally-kit-pin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wally-kit-pin", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
wally-kit-pin- GitHub stars
- 1.6k
- Token cost
- ~1k tokens
- SKILL.md length
- 379 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Bump cmake/sdk-pin.cmake to a new published SDK C++ desktop kit (version + SHA-256 + IDL lock).
- Works in 3 steps: SDK GitHub Release v$SDK is published… → Public assets exist → Do not point WALLY_SDK_DIR at SDK source…
- SKILL.md covers Preconditions, Bump together (never…, CI Swift tree and Private overlays, plus 1 more section
- Calls bash, cmake and gh; needs GITHUB_TOKEN
What it does
Wally Kit Pin is an agent skill from RunanywhereAI/wally. Bump cmake/sdk-pin.cmake to a new published SDK C++ desktop kit (version + SHA-256 + IDL lock). Use after an SDK GitHub Release is published (not draft), when fetch-kit.sh 404s, or when SCHEMALOCK mismatches.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with C++, GitHub and macOS. The repository describes itself as: Get up and running with GLM-5.3-flash, DeepSeek, Gemma and other open source frontier models. The licence is MIT.
Example prompts
- “/wally-kit-pin”
Requirements
- A credential in GITHUB_TOKEN
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- SDK GitHub Release v$SDK is published (isDraft=false). Drafts 404
- Public assets exist
- Do not point WALLY_SDK_DIR at SDK source — configure error.
What it can do on your machine
Read from SKILL.md and the folder at commit 3819f46. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bashcmakegh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
GITHUB_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Wally Kit Pin loads about 1k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 379 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from RunanywhereAI/wally at commit 3819f46, republished under its MIT licence (© RunanywhereAI). 379 words, ~1,009 tokens.
Download SKILL.mdSave it as
.claude/skills/wally-kit-pin/SKILL.md (or your agent's skills folder).- name
- wally-kit-pin
- description
- Bump cmake/sdk-pin.cmake to a new published SDK C++ desktop kit (version + SHA-256 + IDL lock). Use after an SDK GitHub Release is published (not draft), when fetch-kit.sh 404s, or when SCHEMA_LOCK mismatches.
Wally kit pin
Pin file: cmake/sdk-pin.cmake. Fetcher: scripts/build/fetch-kit.sh. Overlay:
scripts/build/fetch-private-pack.sh. CMake wrapper: cmake/RunAnywhereSDK.cmake.
Companion: cpp-desktop-kit in runanywhere-sdks (what the tarball contains).
Preconditions
- SDK GitHub Release
v$SDKis published (isDraft=false). Drafts 404 for this repo'sGITHUB_TOKEN. Prerelease is fine;latestis not required. - Public assets exist:
RunAnywhere-cpp-desktop-{macos-arm64,windows-x64}-v$SDK.tar.gz(+ windows-arm64 once that kit is on the release). - Do not point
WALLY_SDK_DIRat SDK source — configure error. Prefix is-DCMAKE_PREFIX_PATH=or-DWALLY_SDK_KIT=.
Bump together (never version-only)
# After SDK v$SDK is published:
gh release download "v$SDK" --repo RunanywhereAI/runanywhere-sdks \
--pattern 'RunAnywhere-cpp-desktop-*-v'"$SDK"'.tar.gz*' -D /tmp/kits
shasum -a 256 /tmp/kits/RunAnywhere-cpp-desktop-*.tar.gzUpdate in cmake/sdk-pin.cmake:
WALLY_PINNED_SDK_VERSIONWALLY_PINNED_KIT_SHA256_MACOS_ARM64WALLY_PINNED_KIT_SHA256_WINDOWS_X64WALLY_PINNED_KIT_SHA256_WINDOWS_ARM64(uncomment once the asset exists)- IDL triple copied from the kit's
share/runanywhere/SCHEMA_LOCK:WALLY_PINNED_IDL_VERSION,WALLY_PINNED_IDL_SCHEMA_SHA256,WALLY_PINNED_IDL_PROTOC_VERSION
fetch-kit.sh refuses SDK_VERSION != WALLY_PINNED_SDK_VERSION. Do not override
only an env var to "try" a newer kit — checksums are keyed to the pin.
Configure fails if the extracted kit's SCHEMA_LOCK does not match the IDL
pin. When the schema changes, consume a new kit and bump the pin — never
hand-write proto types locally. Wally never runs protoc: crate::io::proto::v1::*
is generated at build time by prost/protox straight from the new kit's .proto
files (build.rs), and nothing generated is committed.
src/sys/bindings.rs (the rac_* C ABI declarations) is committed and
derived from the kit's C headers by bindgen — regenerate it after a kit pin
bump with scripts/build/gen-sys-bindings.sh (--check verifies it is
current; CI runs that on macOS).
Show full SKILL.md (169 more words)Show less
CI Swift tree
.github/workflows/ci.yml and release.yml check out
RunanywhereAI/runanywhere-sdks at ref: v$SDK into .deps/runanywhere-sdks
for the Apple MLX host (WALLY_SDK_SWIFT_PATH). Bump that ref in the same
commit as the pin. macos-26 (Xcode 26 / Swift 6.2 — matches SDK
swift-tools-version: 6.2); macos-15 is Swift 6.1; macos-14 is Swift 5.10.
Private overlays
Not part of the pin. Applied after extract:
WALLY_PRIVATE_OVERLAY(local tarball)- tarball next to the kit prefix named
RunAnywhere-cpp-desktop-{macos-arm64-neurt,windows-arm64-qhexrt}-private-v*.tar.gz - skip (OSS) unless
WALLY_REQUIRE_PRIVATE=1
QHexRT is Windows ARM64 only. Public bottles must stay OSS — never bake overlay bytes into a Homebrew bottle or a public GitHub Release asset.
Windows ARM64 public kit is commons-only (no llama.cpp). Overlay apply
then rebuild product wally.exe. v0.20.28 ARM64 kits are missing
lib/libcurl.lib (packager only globbed x64-windows-static) — copy from
vcpkg arm64-windows-static until the next SDK kit train. Wally
cmake/RunAnywhereSDK.cmake links that import lib when present.
NeuRT: public mac bottle has MLX, not NeuRT. Overlay tarball +
WALLY_APPLE_MLX_HOST=ON rebuild. See wally-e2e for QAIRT / SD15 / DSP
gotchas; do not weaken public CI to require overlays.
Verify
bash scripts/build/fetch-kit.sh macos-arm64 /tmp/kit
cmake -B build -G Ninja -DCMAKE_BUILD_TYPE=Release -DCMAKE_PREFIX_PATH=/tmp/kit
cmake --build build -j "$(sysctl -n hw.logicalcpu)"
WALLY_SDK_KIT=/tmp/kit bash scripts/test/e2e.sh ./build/wally© RunanywhereAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/wally-kit-pin of RunanywhereAI/wally.
Open the folder on GitHubat commit 3819f46
Compare with similar skills
Wally Kit Pin next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Wally Kit Pin this skillRunanywhereAI/wally | 1.6k | — | ~1k | Automated safety check: Pass | MIT | |
| Subspace Buildsdallison/subspace | 104 | — | ~990 | Automated safety check: Pass | Apache-2.0 | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Release Easydicttisfeng/Easydict | 15k | — | ~810 | Automated safety check: Pass | GPL-3.0 | |
| pybind11 Release Publicationpybind/pybind11 | 18k | — | ~2.5k | Automated safety check: Pass | Custom licence | |
| Cherry Studio Regression TestsCherryHQ/cherry-studio | 53k | — | ~1.2k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
Release Easydict
tisfeng/Easydict
编排 Easydict macOS 的 draft、publish、release 和 resume，整理英文 GitHub Release 内容，并处理发布后的 Issue 跟进及本地清理。不用于一般的发布流程设计讨论。
pybind11 Release Publication
pybind/pybind11
Walks a maintainer through publishing a pybind11 release after the preparation PR merges, with preflight checks, confirmations before each push and a GitHub release.
Cherry Studio Regression Tests
CherryHQ/cherry-studio
Runs Cherry Studio's critical-path regression suite as deterministic Playwright E2E tests through a GitHub workflow on macOS and Windows runners.
JS Cpp Protocol
notepadqq/notepadqq
Reference for the communication protocol between the JavaScript editor (CodeMirror or Monaco) and the C++/Qt UI layer via QWebChannel.
More from RunanywhereAI/wally
Wally Architecture
RunanywhereAI/wally
Where Wally logic belongs — command layering, proto as SOT, kit vs CLI ownership, Apple MLX host vs wally-cxx.
Wally Device E2E
RunanywhereAI/wally
Run wally's LLM e2e on Apple Neural Engine (NeuRT) and Snapdragon Hexagon NPU (QHexRT) devices.
Wally Release
RunanywhereAI/wally
Cut an Wally product release (independent of SDK version) — version bump, release:patch label, merge, auto-tag, bottles.
Wally E2E
RunanywhereAI/wally
Verify a built wally binary against a pinned C++ desktop kit on macOS and Windows.
Related
Questions about Wally Kit Pin
What does Wally Kit Pin do?
Bump cmake/sdk-pin.cmake to a new published SDK C++ desktop kit (version + SHA-256 + IDL lock). Wally Kit Pin is an agent skill from RunanywhereAI/wally.cmake to a new published SDK C++ desktop kit (version + SHA-256 + IDL lock).
How do I install Wally Kit Pin in Claude Code?
Run `npx skills add RunanywhereAI/wally --skill wally-kit-pin -a claude-code`. Or copy the skill folder (.agents/skills/wally-kit-pin in RunanywhereAI/wally) into .claude/skills/wally-kit-pin in your project. Claude Code loads it when a task matches its description.
How do I install Wally Kit Pin in Codex?
Run `npx skills add RunanywhereAI/wally --skill wally-kit-pin -a codex`. Or copy the skill folder (.agents/skills/wally-kit-pin in RunanywhereAI/wally) into .agents/skills/wally-kit-pin in your project. Codex loads it when a task matches its description.
Can I use Wally Kit Pin in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add RunanywhereAI/wally --skill wally-kit-pin -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wally-kit-pin, .gemini/skills/wally-kit-pin, .github/skills/wally-kit-pin and .opencode/skills/wally-kit-pin in your project.
What does Wally Kit Pin need to run?
Going by SKILL.md and its folder, Wally Kit Pin needs the command-line tools its instructions call (bash, cmake and gh) and credentials named GITHUB_TOKEN. Our summary lists: A credential in GITHUB_TOKEN.
Does Wally Kit Pin access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Wally Kit Pin safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Wally Kit Pin use?
Wally Kit Pin is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Wally Kit Pin use?
About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Wally Kit Pin?
Skills that share tags, products or a category with Wally Kit Pin: Subspace Builds (dallison/subspace, 104 stars), Mole CLI Release Flow (tw93/Mole, 70k stars), Release Easydict (tisfeng/Easydict, 15k stars) and pybind11 Release Publication (pybind/pybind11, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wally Kit Pin?
RunanywhereAI (a GitHub organization) maintains it in RunanywhereAI/wally, which has 1,562 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 10, 2026.
Source: RunanywhereAI/wally on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.