blocked-task-state
Authoritative protocol for signaling blocked or input-required task states. Mandates targeted A2A pings using the Task.state envelope rather than global capacity broadcasts. Triggers: Use this skill whenever your execution becomes blocked, requires explicit operator input, or encounters a failure that halts progress.
63
73%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/blocked-task-state/SKILL.mdBlocked Task-State Coordination
If you are an agent and your task transitions into a blocked, input-required, or failed state, you MUST NOT broadcast a global idle signal.
You MUST immediately use the view_file tool to read and strictly adhere to .agents/skills/blocked-task-state/references/blocked-task-state-workflow.md before sending any A2A messages.
- Repository
- neomjs/neo
- Commit
c1ce853
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.