← ClaudeAtlas

pinboard-deliverlisted

Deliver exactly one active pinboard attempt from its accepted brief, current definition identity, and renewable lease. Use when the item, checkout, definition, acceptance criteria, and verification are already recorded. Do not use for intake, portfolio selection, broad audits, design exploration, or acceptance review.
valsteen/pinboard · ★ 4 · AI & Automation · score 77
Install: claude install-skill valsteen/pinboard
# Deliver from the pinboard Deliver the accepted checkpoint of one active attempt: implement its complete scope, verify it, leave a durable result, and return it accurately for review. Do not initialize delivery for a request that only asks to read named context, get oriented, or wait. Read only that bounded context and leave lifecycle, authority, source planning, dispatch, and review untouched until the human requests revision or implementation. Use [the shared runtime adapters](../pinboard/references/runtime-adapters.md) for identity, checkout isolation, worker and reviewer launch, permission declarations, and waiting. This skill continues to own delivery semantics. Direct human invocation to start a named Pinboard item is not an attempt-establishment failure. When no already prepared active attempt was supplied, follow the main skill's [human task-start route](../pinboard/SKILL.md#route-human-task-starts-through-pinboard): give its one gentle clarification, suggest ordinary Pinboard wording, and continue through Pinboard when the item and outcome are clear. Do not enter the worker checks merely to surface missing internal preparation, and do not stop after explaining the route when Pinboard can continue. ## Establish the attempt Follow the [current MCP request contract](../pinboard/references/runtime-adapters.md#current-mcp-request-shapes) when executing native launch acquisition and continuation inputs. Do not reuse historical flat inputs as a current call shape. B