blocker-min-input

Capture exact blocker text, attempts, and minimum unblock input from tool outputs.

3|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Dalomeve/bot-output --skill blocker-min-input
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blocker-min-input
Source: https://github.com/Dalomeve/bot-output/tree/main/skills/blocker-min-input
Command: npx skills add https://github.com/Dalomeve/bot-output --skill blocker-min-input

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When tools fail or block progress, teams struggle to pinpoint the exact blocker, number of attempts, and the minimal user action required to unblock, leading to wasted cycles. This Skill standardizes blocker reporting to accelerate resolution.

Core Features & Use Cases

  • Blocker report format captures the exact blocker text, a structured list of attempts and their outcomes, the minimum unblock input, and a defined fallback path.
  • Attempt requirements enforce a minimum of two documented attempts and retrials with corrected parameters before surfacing a blocker.
  • Minimum unblock input specifies the smallest user action needed to unblock and continue the workflow.
  • Fallback option provides an alternative path if the primary unblock steps cannot be completed.
  • Use Case in automated task workflows, when a call fails due to missing credentials or permission issues, surface a precise blocker and the fastest unblock path.

Quick Start

Provide a precise blocker, list at least two attempts, specify the minimum unblock input, and offer a fallback option to unblock quickly.

Frequently Asked Questions about blocker-min-input

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

FAQPage Schema
How do I report exact blockers in an agent workflow to unblock quickly?

To unblock quickly, a blocker report captures the exact blocker text, lists prior attempts with outcomes, specifies the minimum unblock input needed, and provides a fallback path. This standardized error-reporting format accelerates resolution by pinpointing the precise issue and fastest unblock action.

What is the minimum number of attempts required before surfacing a blocker?

The minimum requirement for surfacing a blocker is at least two documented attempts. You must list prior attempts and their outcomes, including retrials with corrected parameters, before reporting the blocker to ensure simple parameter errors are exhausted.

How do I specify the minimum unblock input when a tool fails due to missing credentials?

When a tool fails due to missing credentials, the minimum unblock input specifies the smallest user action required to proceed. The blocker report identifies the exact missing permission or credential and defines the precise input needed to resume the workflow.

Can I use a fallback path if the primary unblock steps cannot be completed?

Yes, a fallback option is included in the blocker report to provide an alternative path if the primary unblock steps cannot be completed. This ensures the agent workflow can continue by routing around the blocker using safe alternatives.

Does blocker reporting redact sensitive data from tool outputs?

Blocker reporting redacts sensitive data from tool outputs automatically. When capturing the exact blocker text and documenting prior attempts, the process ensures sensitive information is removed and provides safe alternatives to unblock quickly without exposing credentials.