release-unclaim

Releases or force-revokes component claims in the Marshall coordination store.

Updated Jul 15, 2026
One-click install
npx skills add https://github.com/builtbyberry/marshall-claude-plugin --skill release-unclaim-builtbyberry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-unclaim
Source: https://github.com/builtbyberry/marshall-claude-plugin/tree/main/marshall/skills/release-unclaim
Command: npx skills add https://github.com/builtbyberry/marshall-claude-plugin --skill release-unclaim-builtbyberry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a release component is locked by a claim, other contributors are blocked from working on it. This Skill hands a claim back to the shared Marshall store when work is done or paused, and recovers stuck or dead holds left behind by machines that went away. ## Core Features & Use Cases - Graceful claim release: Return your own claim via the Marshall MCP release_claim tool so the component becomes free for others. - Force revocation: Recover stuck or stale holds with revoke_claim, with a confirmation step before pulling a lock from another holder. - Fence advancement: Both paths advance the component's fence so a superseded worker's next write fails loudly instead of silently clobbering state. - Use Case: A teammate's laptop died mid-release while holding the billing component. You run /marshall:release-status to find the claim id, confirm with the team, then revoke the claim so work can resume. ## Quick Start Ask the agent to release the claim on the billing component, or to revoke a stuck hold after confirming with you first.

Frequently Asked Questions about release-unclaim

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I release a component claim in Marshall?

Call the Marshall MCP release_claim tool with the claim id to hand your own claim back to the shared store. If you do not know the claim id, run /marshall:release-status first to list current holds and their ids.

How do I recover a stuck or dead claim hold?

Use the Marshall revoke_claim tool with the claim id to force a stuck hold off the component. Confirm with the user first, since revoking pulls the lock out from under whoever held it.

What is the difference between release_claim and revoke_claim?

release_claim is the graceful path for handing back your own claim when work is done or paused. revoke_claim is a recovery operation for stuck or dead holds and can be used by any workspace member after confirmation.

Does releasing a claim mark the component as done?

No. Releasing only frees the coordination lock and leaves the component open, so its dependents stay blocked. If the work merged, also call set_component_state with state merged.

What happens to a superseded worker after a claim is revoked?

Both release and revoke advance the component's fence, so the superseded worker's next write fails loudly instead of silently clobbering newer state.