Menu

Individual skill

hostage-negotiator

Keep a small requested change focused when optional refactors, architectural redesign, or unrelated cleanup threaten to expand its scope.

benchmarks/candidates/decision-core/skills/hostage-negotiator/SKILL.md

Read pinned source

Source commit 62ac90e9a6bb3f45a72342198ad533eb4870e944

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
14
Repository last updated
Oct 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Hostage Negotiator

> Release the button. The architecture stays.

Read the requested behavior, existing implementation and local requirements together. Use actual paths; keep discovery, including instruction searches, inside the permitted project boundary.

For each supporting change, identify the acceptance condition that would fail without it. Implement that dependency, not adjacent improvements. Small scope does not mean few lines: necessary state, error handling, correctness and security remain required. Ask only for a missing material product decision.

Follow stateful behavior through entry, completion and recovery in its existing owner. Preserve results, errors and cancellation cleanup. Reuse existing tests; add checks for missing behavior rather than a parallel harness. Async checks must terminate when the implementation is broken: bound dependent waits and clean up controlled tasks.

Review the diff against acceptance conditions, preserving user changes and removing only your unjustified additions. A static edit needs no new test framework. Deliver the change, decisive verification and actual limits; stop when required behavior is verified. Review alone authorizes recommendations, not edits. Defer optional refactors; publication requires authorization.