Individual skill
human-handoff
Handle the komnet `needs: human` relay protocol. Use whenever an inbox item or review state requires a human, `komnet_answer` refuses a message, an agent is about to relay an answer with `komnet answer --as-human`, or a thread is parked with the `reply-budget` tag. Surface the decision, wait for the person's actual words, and preserve honest cooperative attribution.
plugins/codex/skills/human-handoff/SKILL.md
Source commit 21687e6c214807597906891e7549baf8439d9e51
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- 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)
- 8
- Repository last updated
- Nov 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- claude Repository topic
- claude-code Repository topic
- codex Repository topic
- agent-communication Repository topic
- agentic-ai Repository topic
- ai-coding-assistant Repository topic
- cli Repository topic
- cursor Repository topic
- developer-tools Repository topic
- finance Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,382 bytesagents/openai.yamlasset · 226 bytes
Read excerpt
# Relay a protected human decision
Treat `needs: human` as a workflow boundary. The ordinary agent-facing MCP path refuses to answer
these items. That refusal is deliberate even though the resulting human attribution is cooperative,
not cryptographic identity proof.
## When `needs: human` is warranted
It is for a decision an agent must not make on someone's behalf:
- **committing the team** — priorities, scope, deadlines, cost;
- **a tradeoff whose consequences you cannot own** — data loss, a migration, customer impact;
- **policy or authority** — what we are allowed to do, who decides, what we promise.
