agentleFS
michaelnealemichaelneale/mesh-llm/.agents/skills/kv-tool-loop-stability/SKILL.md

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
  1. Very specific:

    Use this skill when changing Skippy KV slot cleanup, prefix-cache lookup, OpenAI tool-loop behavior, agent harnesses, or any runtime path …

    line 13
  2. Very specific:

    Prefer a direct model when reproducing Skippy KV/cache issues.

    line 22
  3. Very specific:

    Run --print-plan first and confirm the models, attempts, pressure_turns, timeout, cache thresholds, output directory, and native logs.

    line 24
  4. Distinctive:

    Do not paste full prompts, auth headers, huge stable prefixes, or private endpoint data.

    line 74
  5. Distinctive:

    If no native log is available, say that native-log scanning was not run.

    line 76
  6. Distinctive:

    When changing this harness, run:

    line 80

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Attach to an existing OpenAI-compatible /v1 endpoint. This harness does not start nodes, load models, join meshes, or change routing policy.
  2. Prefer a direct model when reproducing Skippy KV/cache issues. Use auto only when intentionally validating routed behavior.
  3. Run --print-plan first and confirm the models, attempts, pressure_turns, timeout, cache thresholds, output directory, and native logs.
  4. 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.
  5. Preserve the evidence directory: manifest.json, results.jsonl, summary.json, summary.md, and the transcript paths selected by manifest.json. Each run writes a fresh transcripts/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-plan

Run 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/local

Reporting 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.md or summary.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-validate

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about michaelneale/mesh-llm

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

10 more on GitHub

On Hacker News · 1

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.