Menu
Use when running tooltest to validate MCP servers, interpret failures, and iterate fixes in this repo.
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
Migrate docs from bd (beads) to br (beads_rust). Use when updating AGENTS.md, converting bd commands, "bd sync" → "br sync --flush-only", or beads migration.
One lifecycle for Lambda repos: choose a br issue, start work, land the PR, and watch GitHub via Dumbwaiter MCP until it merges.
Git-backed issue tracker for multi-session work with dependencies and persistent memory across conversation compaction. Use when work spans sessions, has blockers, or needs context recovery after compaction.
Testing patterns and standards for this codebase, including async effects, fakes vs mocks, and property-based testing.
how to approach tests, types and coverage
Pragmatic Rust conventions to keep code readable, testable, and performant for this project.
| name | tooltest-fix-loop |
| description | Use when running tooltest to validate MCP servers, interpret failures, and iterate fixes in this repo. |
You have access to this repository and can run commands.
Goal: make the repository's MCP server(s) conform to the MCP spec as exercised by tooltest.
Figure out how to start the MCP server from this repo (stdio or streamable HTTP).
Select a small, related subset of tools intended to be used together. Default to testing at most 50 tools at a time, and strongly prefer a smaller group. Use --tool-allowlist (or tool_allowlist in MCP input) to enforce this.
Run tooltest against it and fix failures until it exits 0.
If you see "state-machine generator failed to reach minimum sequence length", re-run with --lenient-sourcing or seed values in --state-machine-config.
CLI usage (preferred when you can run commands):
--trace-all /tmp/tooltest-traces.jsonl.tooltest stdio --command "<command that starts the repo's MCP server>" --tool-allowlist foo --tool-allowlist bar
CLI http (allowlist example): tooltest http --url "http://127.0.0.1:9000/mcp" --tool-allowlist foo --tool-allowlist barMCP tool usage (when you must call via MCP):
tooltest tool with the shared input schema.--json and --trace-all are not supported).{
"target": { "stdio": { "command": "<command that starts the repo's MCP server>" } },
"tool_allowlist": ["foo", "bar"]
}
Don't rename tools or change schemas unless required; prefer backward-compatible fixes.
Add/adjust tests if needed.
Return a short summary of what you changed and why, plus the final passing tooltest output snippet.