dumbwaiter-mcp
Installation
SKILL.md
Dumbwaiter MCP: Wait-for-Change
Goal: give Claude a single, stable way to “wait until X happens” on a code host (GitHub now; GitLab next). This skill teaches Claude when and how to use the Dumbwaiter MCP server’s tools.
Prerequisites
- Server: this repo builds a stdio MCP server (
cargo build && target/debug/dumbwaiter-mcp). - Auth:
export GITHUB_TOKEN=…(repo read permissions are sufficient for commit statuses). - Persistence (optional):
DUMBWAITER_DBto override./state/dumbwaiter.sqlite. - Await settings (optional):
DUMBWAITER_AWAIT_TTL_SECS(default 900),DUMBWAITER_WATCHER=1to enable background polling.
When to use this skill
- You need to pause orchestration until PR checks turn green, a PR is merged, or checks fail.
- You want durable waits with a
wait_id, cancellable and recoverable after restarts. - You want progress updates visible to the host via MCP
notify_progress.
Tools overview
wait.start→ returns{ wait_id }for a condition on a selectorwait.status→ returns current state:pending|satisfied|failed|timeout|cancelled|unknownwait.cancel→ cancels a pending wait
Related skills
More from lambdamechanic/sk
rust-guidelines
Pragmatic Rust conventions to keep code readable, testable, and performant for this project.
5testing-patterns
Testing patterns and standards for this codebase, including async effects, fakes vs mocks, and property-based testing.
4bd-workflow
How to use bd (beads) for issue tracking, ready work, status updates, and comments in this repo.
4template-skill
Replace with description of the skill and when Claude should use it.
4sk
How to use the repo-scoped sk CLI to manage Claude Skills in this codebase.
1