kv-tool-loop-stability
Skill3.8k starsChanged 20 days agoApache-2.0View on GitHub
Use this skill when certifying mesh-llm KV/cache stability under repeated OpenAI tool-call loops, same-prefix cache reuse, suffix-prefill limits, or native Skippy slot/decode/eviction failures.
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Use this skill when changing Skippy KV slot cleanup, prefix-cache lookup, OpenAI tool-loop behavior, agent harnesses, or any runtime path …
- Very specific: line 22
Prefer a direct model when reproducing Skippy KV/cache issues.
- Very specific: line 24
Run --print-plan first and confirm the models, attempts, pressure_turns, timeout, cache thresholds, output directory, and native logs.
- Distinctive: line 74
Do not paste full prompts, auth headers, huge stable prefixes, or private endpoint data.
- Distinctive: line 76
If no native log is available, say that native-log scanning was not run.
- Distinctive: line 80
When changing this harness, run:
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
KV Tool-Loop Stability
QA orchestration follows ../manage-ci/SKILL.md. The typed Rust command
cargo xtool automation stability kv-tool-loop owns this certification.
Use this skill when changing Skippy KV slot cleanup, prefix-cache lookup,
OpenAI tool-loop behavior, agent harnesses, or any runtime path related to
llama_decode failed, failed to find a memory slot, low same-prefix cache
reuse, or proactive eviction failures.
Workflow
- Attach to an existing OpenAI-compatible
/v1endpoint. This harness does not start nodes, load models, join meshes, or change routing policy. - Prefer a direct model when reproducing Skippy KV/cache issues. Use
autoonly when intentionally validating routed behavior. - Run
--print-planfirst and confirm the models, attempts,pressure_turns, timeout, cache thresholds, output directory, and native logs. - Pass the active Skippy native log when available. The harness checkpoints native logs at run start and scans appended bytes, rescanning a log when it is created, replaced, truncated, or rewritten after the checkpoint.
- Preserve the evidence directory:
manifest.json,results.jsonl,summary.json,summary.md, and the transcript paths selected bymanifest.json. Each run writes a freshtranscripts/run-*/directory; preexisting evidence is preserved.
Commands
Preview the run without touching the endpoint:
cargo xtool automation stability kv-tool-loop \
--base-url http://127.0.0.1:9337/v1 \
--models Qwen/Qwen2.5-3B-Instruct-GGUF:q4_k_m \
--attempts 5 \
--pressure-turns 8 \
--timeout 180 \
--min-cached-tokens 2048 \
--suffix-prefill-limit 256 \
--native-log ~/.mesh-llm/runtime/<pid>/logs/skippy-native.log \
--output-dir target/kv-tool-loop-stability/local \
--print-planRun the certification:
cargo xtool automation stability kv-tool-loop \
--base-url http://127.0.0.1:9337/v1 \
--models Qwen/Qwen2.5-3B-Instruct-GGUF:q4_k_m \
--attempts 5 \
--pressure-turns 8 \
--timeout 180 \
--min-cached-tokens 2048 \
--suffix-prefill-limit 256 \
--native-log ~/.mesh-llm/runtime/<pid>/logs/skippy-native.log \
--output-dir target/kv-tool-loop-stability/localReporting Rules
- Report the model list, attempts, pressure turns, timeout, cache thresholds, success rate, native log paths, and output directory.
- Include the summary verdict and failing phase details from
summary.mdorsummary.json. - Do not paste full prompts, auth headers, huge stable prefixes, or private endpoint data.
- If no native log is available, say that native-log scanning was not run.
Validation
When changing this harness, run:
just with-lld cargo test --locked -p xtask --bin xtask --test migration_stability stability -- --test-threads=1
just with-lld cargo clippy --locked -p xtask --all-targets -- -D warnings
just ci-validateTrending
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Who's talking about michaelneale/mesh-llm
- A Hacker News story“Pool spare GPU capacity to run LLMs at larger scale”Hacker News · Mar 24, 2026 · 11 points
- @rusttrending.bsky.social“michaelneale / mesh-llm: reference impl with llama.cpp compiled to distributed inference across machines, …”Bluesky · Apr 11, 2026 · 2 likes
- @yug1224.com“複数のLLMを連携させてタスクをこなすための分散型エージェントフレームワークらしい 複雑なワークフローを構築する際に役立ちそうかな yug1224 starred michaelneale/mesh-llm…”Bluesky · Apr 8, 2026 · 1 likes
- Mesh-LLM/mesh-llm“Add mesh-llm MoE planning, analysis, and ranking contribution commands”GitHub · Apr 11, 2026
- Mesh-LLM/mesh-llm“Simplify model for node states”GitHub · Apr 10, 2026
The biggest 5 of 18 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 18
Talked about on GitHub, Bluesky and Hacker News (18 times).
On GitHub · 15
- Apr 11, 2026Add mesh-llm MoE planning, analysis, and ranking contribution commands — Mesh-LLM/mesh-llm0 reactions · 1 comment
- Apr 10, 2026Simplify model for node states — Mesh-LLM/mesh-llm0 reactions · 2 comments
- Apr 10, 2026revise mesh publication rules — Mesh-LLM/mesh-llm0 reactions · 1 comment
- Apr 5, 2026Roll out config as local node config first, then reconcile mesh-wide desired state — Mesh-LLM/mesh-llm0 reactions · 2 comments
- Apr 3, 2026CommitLLM sumi capture: working on Apple Silicon Q8_0 — michaelneale/llama.cpp0 reactions
10 more on GitHub
- Apr 2, 2026Add hardware runtime status enrichment without changing model metadata sources — Mesh-LLM/mesh-llm0 reactions
- Apr 2, 2026Design owner identity propagation and direct verification — Mesh-LLM/mesh-llm0 reactions · 4 comments
- Apr 2, 2026Design owner keystore and Rust signed+encrypted message primitives — Mesh-LLM/mesh-llm0 reactions
- Apr 2, 2026Track splitting PR #130 into smaller rollout PRs — Mesh-LLM/mesh-llm0 reactions · 2 comments
- Apr 2, 2026research: mesh-llm integration — p2p inference mesh + model sharding under obol-stack economic layer — ObolNetwork/obol-stack0 reactions
- Apr 2, 2026[WIP] Make PR 103 mergable on top of PR 127 — Mesh-LLM/mesh-llm0 reactions
- Apr 2, 2026refactor: decompose mesh.rs and app/mod.rs into focused submodules — Mesh-LLM/mesh-llm0 reactions · 1 comment
- Mar 28, 2026Autoupdater — Mesh-LLM/mesh-llm0 reactions
- Mar 27, 2026Add a staged auto-updater for release bundles — Mesh-LLM/mesh-llm0 reactions
- Mar 27, 2026Add generic bulk transfer support to mesh plugins — Mesh-LLM/mesh-llm0 reactions
On Bluesky · 2
- Apr 11, 2026michaelneale / mesh-llm: reference impl with llama.cpp compiled to distributed inference across machines, with real end to end demo ★720… — @rusttrending.bsky.social2 likes and reposts
- Apr 8, 2026複数のLLMを連携させてタスクをこなすための分散型エージェントフレームワークらしい 複雑なワークフローを構築する際に役立ちそうかな yug1224 starred michaelneale/mesh-llm… — @yug1224.com1 likes and repost
On Hacker News · 1
- Mar 24, 2026Pool spare GPU capacity to run LLMs at larger scale11 points · 3 comments
Other versions1 project uses a version of this.
Word for word · 1
- Mesh-LLM/mesh-llm★ 3.5k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/AGENTS.mdAGENTS.md
- mesh/AGENTS.mdAGENTS.md
- skippy/AGENTS.mdAGENTS.md
- benchmark-tuneSkill
- config-settings-managementSkill
- connect-agentsSkill
- deploy-linux-gpuSkill
- deploy-macosSkill
- deploy-windowsSkill
- hf-bf16-gguf-conversion-jobsSkill
- hf-gguf-quant-jobsSkill
- hf-layer-package-jobsSkill
- hf-quant-and-layer-package-jobsSkill
- llama-patch-changesSkill
- llama-stage-patch-changesSkill
- manage-ciSkill
- mesh-joinSkill
- metrics-serverSkill
- plugin-web-ui-extensionSkill
- release-notesSkill
- release-validationSkill
- remote-observable-processSkill
- skippy-cache-family-benchSkill
- skippy-correctnessSkill
- skippy-family-certificationSkill
- skippy-metricsSkill
- skippy-model-packageSkill
- skippy-promptSkill
- skippy-servingSkill
- skippy-spec-benchSkill
- telemetry-privacy-reviewSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

