using-elicitations

Pause automated AI workflows to collect user input and approvals.

97|5|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/friday-platform/friday-studio --skill using-elicitations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-elicitations
Source: https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/using-elicitations
Command: npx skills add https://github.com/friday-platform/friday-studio --skill using-elicitations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated AI workflows often require pausing execution to collect user input, approvals, or disambiguation before continuing, but there is no built-in standard mechanism to do this without breaking the workflow run. This Skill fills that gap by providing native elicitation tools that pause FSM actions or Python user agents, surface prompts to users, and resume execution automatically once a response is received.

Core Features & Use Cases

  • Tool Access Approvals: Use request_tool_access to ask users for permission to call tools outside the action's default allowlist, with clear options to allow once, allow always, or deny the request.
  • Human-in-the-Loop Input: Use request_human_input to collect user decisions, confirmations, or free-form text for approvals, disambiguation, or multi-item selection tasks.
  • Use Case: For example, when building an inbox triage workflow, you can use nested elicitations to ask the user to select an action for each incoming email mid-run, without breaking the workflow execution.

Quick Start

Use the using-elicitations skill to request user approval before sending a sensitive draft client email.

Frequently Asked Questions about using-elicitations

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

FAQPage Schema
How do I pause an AI workflow to request human input mid-execution?

You can pause AI workflows to request human input mid-execution using request_human_input primitives that surface prompts, collect user decisions, and automatically resume execution after receiving a response without breaking the workflow run.

Can I ask users for tool access approvals outside a default allowlist in Python agents?

Yes, you can use the request_tool_access primitive to ask users for permission to call tools outside a Python user-type agent's default allowlist, providing clear options to allow once, allow always, or deny the request before resuming.

What is the best way to handle per-item selection tasks in an automated inbox triage workflow?

The best way to handle per-item selection tasks in automated workflows is using nested grouped elicitations, allowing you to ask users to select an action for each incoming email mid-run without breaking the workflow execution.

Does this elicitation mechanism support timeout handling and workflow retry logic?

Yes, the elicitation mechanism supports timeout handling and idempotent retry logic to resume FSM actions and Python user-type agent workflows safely after a user response or timeout event occurs.

What are the limitations of using elicitations for human-in-the-loop decisions in FSM actions?

Elicitations are limited to FSM actions and Python user-type agents requiring human-in-the-loop decisions, and rely on the user responding to the surfaced prompt to resume execution via the built-in retry logic.