human-in-the-loop-design
Design the human approval surface for an agent system — which actions gate, how approvals batch without becoming rubber stamps, and what the audit trail must hold. Use when asked to add human oversight to an agent, design approval workflows for AI actions, decide what an agent may do autonomously, or fix approval fatigue in an existing loop. Produces an action-tier policy, approval UX spec, escalation rules, and audit-trail requirements. For specifying the whole agent use agent-spec; for the per-skill execution gates see the Execution-block pattern in SKILLSPEC §5.
npx skills add mohitagw15856/pm-claude-skills --skill human-in-the-loop-design --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Human-in-the-Loop Design Skill The failure mode of agent oversight isn't too little review — it's review that decays into a rubber stamp. Forty approval prompts a day trains the human to click yes; then the one that mattered goes through with the rest. This skill designs the loop so human attention lands exactly where it changes the outcome, and nowhere else. ## What This Skill Produces - An **action-tier policy**: every agent action classified auto / notify / approve / forbidden - An **approval UX spec**: what the human sees, batching rules, and the anti-rubber-stamp mechanics - **Escalation & fallback rules**: timeouts, absent approvers, disagreement - **Audit-trail requirements**: what gets recorded so any decision is reconstructable ## Required Inputs Ask for (if not already provided): - **The agent and its action inventory** — everything it *can* do (from its tool list, not its marketing) - **Blast radius per action**: reversible? outward-facing? money/data/permissions involved? - **Volume estimates**: how many times per day each action fires (approval load is a design constraint, not an afterthought) - **Who approves** — role, how many people, what else competes for their a
- What This Skill Produces
- Required Inputs
- Design Method
- Output Format
- HITL Design: [agent system]
- Quality Checks
- Anti-Patterns
What does the human-in-the-loop-design skill do?
Design the human approval surface for an agent system — which actions gate, how approvals batch without becoming rubber stamps, and what the audit trail must hold. Use when asked to add human oversight to an agent, design approval workflows for AI actions, decide what an agent may do autonomously, or fix approval fatigue in an existing loop. Produces an action-tier policy, approval UX spec, escalation rules, and audit-trail requirements. For specifying the whole agent use agent-spec; for the per-skill execution gates see the Execution-block pattern in SKILLSPEC §5.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill human-in-the-loop-design --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 mohitagw15856/pm-claude-skills, a repository with 1,255 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.