Agent skill · AI & Agents

user-input-protocol

Structured checkpoint format for requesting human input. When an agent needs a decision, it must stop, present context, show options, and wait. Activate when delegating to subagents, running background tasks, or hitting any decision point that requires human judgment.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill user-input-protocol --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Version: 1.0
Declared author: jwilger
Path: skills/agent/user-input-protocol/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# User Input Protocol **Value:** Respect -- the developer's judgment governs all consequential decisions. The agent never assumes when it should ask. ## Purpose Defines a structured format for agents to request human input at decision points. Prevents agents from making assumptions on the developer's behalf, ensures questions include enough context for informed decisions, and provides a pause-and-resume pattern for subagents that cannot directly prompt the user. ## Practices ### Stop and Present, Never Assume When you encounter a decision that requires human judgment, stop working immediately. Do not guess. Do not pick the "most likely" option. Present the decision clearly and wait. Decisions that require human input: - Business rule ambiguities (two valid interpretations exist) - Architecture trade-offs (performance vs. simplicity, etc.) - Scope questions (should this feature include X?) - Destructive actions (deleting files, force-pushing, dropping data) Decisions that do NOT require human input: - Implementation details with one clearly correct answer - Formatting, naming, or style choices covered by project conventions - Test structure when requirements are unambiguous ### Use

What's inside
Steps it walks through
  1. Purpose
  2. Practices
  3. Stop and Present, Never Assume
  4. Use the AWAITINGUSERINPUT Format
  5. Save State Before Pausing (Subagents)
  6. Resume Without Redoing Work
  7. Handle Multi-Question Checkpoints
  8. Enforcement Note
  9. Verification
  10. Dependencies
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the user-input-protocol skill do?

Structured checkpoint format for requesting human input. When an agent needs a decision, it must stop, present context, show options, and wait. Activate when delegating to subagents, running background tasks, or hitting any decision point that requires human judgment.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill user-input-protocol --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going