Adk Agent Builder
google/adk-python
Builds ADK (Agent Development Kit) Python agents: LLM agents with tools, graph workflows of function and agent nodes, conditional routing, fan-out and join, schema-validated delegation between…
Asks the user mid-run from inside an FSM action or Python type: user agent via the elicitation tools — requesttoolaccess for allowlist approvals and requesthumaninput for HITL (human-in-the-loop)…
Install Using Elicitations
$ npx skills add friday-platform/friday-studio --skill using-elicitations -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install friday-platform/friday-studio using-elicitations --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/system/skills/using-elicitations .claude/skills/using-elicitations && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "using-elicitations" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/using-elicitations into .claude/skills/using-elicitations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-elicitations", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/using-elicitationsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add friday-platform/friday-studio --skill using-elicitations -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install friday-platform/friday-studio using-elicitations --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/system/skills/using-elicitations .agents/skills/using-elicitations && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "using-elicitations" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/using-elicitations into .agents/skills/using-elicitations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-elicitations", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add friday-platform/friday-studio --skill using-elicitations -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install friday-platform/friday-studio using-elicitations --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/system/skills/using-elicitations .cursor/skills/using-elicitations && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "using-elicitations" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/using-elicitations into .cursor/skills/using-elicitations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-elicitations", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/friday-platform/friday-studio.git --path packages/system/skills/using-elicitations--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add friday-platform/friday-studio --skill using-elicitations -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install friday-platform/friday-studio using-elicitations --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/system/skills/using-elicitations .gemini/skills/using-elicitations && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "using-elicitations" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/using-elicitations into .gemini/skills/using-elicitations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-elicitations", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install friday-platform/friday-studio using-elicitationsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add friday-platform/friday-studio --skill using-elicitations -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/system/skills/using-elicitations .github/skills/using-elicitations && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "using-elicitations" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/using-elicitations into .github/skills/using-elicitations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-elicitations", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add friday-platform/friday-studio --skill using-elicitations -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install friday-platform/friday-studio using-elicitations --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/system/skills/using-elicitations .opencode/skills/using-elicitations && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "using-elicitations" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/using-elicitations into .opencode/skills/using-elicitations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-elicitations", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
using-elicitations- GitHub stars
- 104
- Token cost
- ~2.4k tokens
- SKILL.md length
- 1,070 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Asks the user mid-run from inside an FSM action or Python type: user agent via the elicitation tools — requesttoolaccess for allowlist approvals and requesthumaninput for HITL (human-in-the-loop)…
- A job needs the user to choose
- SKILL.md covers Choosing between them, Formatting the question, Simple multiple choice and Nested multiple choice — one…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Supply input before the action can continue
What it does
Using Elicitations is an agent skill from friday-platform/friday-studio. Asks the user mid-run from inside an FSM action or Python type: user agent via the elicitation tools — requesttoolaccess for allowlist approvals and requesthumaninput for HITL (human-in-the-loop) decisions, approvals, confirmations, and disambiguation. Use when a job needs the user to choose, approve, or supply input before the action can continue. Covers simple multiple choice, nested per-item choice, prompt formatting, and how to consume the answer.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Quizzes and assessments and Human-in-the-loop approvals. It works with Python. The repository describes itself as: Agent Harness Platform — shareable workspaces, MCP tools, skills, memory, and cron/webhook automations. Self-hosted and transparent.
When your agent uses it
- A job needs the user to choose
- Supply input before the action can continue
Example prompts
- “/using-elicitations”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit fb3069a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json and typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Using Elicitations loads about 2.4k tokens when it runs. Until then it costs about 121 tokens; SKILL.md has 1,070 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,070 words (~2,410 tokens).
“Elicitations pause a running FSM action (or Python type: user agent), surface a prompt to the user in the Activity feed, and resume the same tool call with the user's answer. Two tools, one mechanism.”
- name
- using-elicitations
Files
Just SKILL.md in packages/system/skills/using-elicitations of friday-platform/friday-studio.
Open the folder on GitHubat commit fb3069a
Compare with similar skills
Using Elicitations next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Using Elicitations this skillfriday-platform/friday-studio | 104 | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Adk Agent Buildergoogle/adk-python | 22k | — | ~879 | Automated safety check: Pass | Apache-2.0 | |
| Nucleus Delivery Evidence Finalizerprotect-my-hair/nucleus-marketplace | 164 | — | ~454 | Automated safety check: Pass | MIT | |
| Clawpathy AutoresearchClawBio/ClawBio | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Jarvis Setupethanplusai/jarvis | 838 | — | ~2.5k | Automated safety check: Notes | Custom licence | |
| Langgraph Human In The Looplangchain-ai/langchain-skills | 1.3k | 2 repos | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Nucleus Delivery Evidence Finalizer
protect-my-hair/nucleus-marketplace
Combines the evidence from completed Nucleus workflow steps into a final evidence report and result package, without scheduling steps, updating trackers or opening pull requests.
Clawpathy Autoresearch
ClawBio/ClawBio
Eval-driven skill tuning. An agent skill from ClawBio/ClawBio.
Jarvis Setup
ethanplusai/jarvis
A skill your agent uses when helping someone install, configure, or debug a fresh clone of JARVIS (this repo) — especially "the mic doesn't work", "JARVIS says his language systems are down", any…
- Official
Langgraph Human In The Loop
langchain-ai/langchain-skills
INVOKE THIS SKILL when implementing human-in-the-loop patterns, pausing for approval, or handling errors in LangGraph.
Auto Improve
crimeacs/auto-improve
GAN-style iterative improvement loop for any text artifact. An agent skill from crimeacs/auto-improve.
More from friday-platform/friday-studio
All 20 skills in this repoAuthoring Skills
friday-platform/friday-studio
Authors new agent skills that follow the Anthropic + agentskills.io specification.
Friday CLI
friday-platform/friday-studio
Interacts with a running Friday daemon via CLI and HTTP — lists/creates/modifies workspaces, triggers signals, watches sessions, publishes skills and agents.
Workspace API
friday-platform/friday-studio
Create, list, update, delete, and clean up workspaces via the daemon HTTP API at $FRIDAYDURL.
Writing Workspace Signals
friday-platform/friday-studio
Authors Friday workspace signals with correct provider configs, payload schemas, and runtime wiring.
Composing Emails
friday-platform/friday-studio
General styling and tone guidelines for composing HTML emails.
Repairing Workspaces Agents
friday-platform/friday-studio
Repairs and upgrades existing Friday workspaces, jobs, user agents, and generated agents to current runtime contracts.
Related
Works with
Categories
Questions about Using Elicitations
What does Using Elicitations do?
Asks the user mid-run from inside an FSM action or Python type: user agent via the elicitation tools — requesttoolaccess for allowlist approvals and requesthumaninput for HITL (human-in-the-loop)…. Using Elicitations is an agent skill from friday-platform/friday-studio. Asks the user mid-run from inside an FSM action or Python type: user agent via the elicitation tools — requesttoolaccess for allowlist approvals and requesthumaninput for HITL (human-in-the-loop) decisions, approvals, confirmations, and disambiguation.
When should I use Using Elicitations?
Using Elicitations fits situations like: A job needs the user to choose; supply input before the action can continue.
How do I install Using Elicitations in Claude Code?
Run `npx skills add friday-platform/friday-studio --skill using-elicitations -a claude-code`. Or copy the skill folder (packages/system/skills/using-elicitations in friday-platform/friday-studio) into .claude/skills/using-elicitations in your project. Claude Code loads it when a task matches its description.
How do I install Using Elicitations in Codex?
Run `npx skills add friday-platform/friday-studio --skill using-elicitations -a codex`. Or copy the skill folder (packages/system/skills/using-elicitations in friday-platform/friday-studio) into .agents/skills/using-elicitations in your project. Codex loads it when a task matches its description.
Can I use Using Elicitations in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add friday-platform/friday-studio --skill using-elicitations -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/using-elicitations, .gemini/skills/using-elicitations, .github/skills/using-elicitations and .opencode/skills/using-elicitations in your project.
What does Using Elicitations need to run?
SKILL.md names no scripts, command-line tools or credentials: Using Elicitations is instructions for the agent only. Our summary lists: Python 3.
Does Using Elicitations access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Using Elicitations safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Using Elicitations use?
Using Elicitations has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Using Elicitations use?
About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Using Elicitations?
Skills that share tags, products or a category with Using Elicitations: Adk Agent Builder (google/adk-python, 22k stars), Nucleus Delivery Evidence Finalizer (protect-my-hair/nucleus-marketplace, 164 stars), Clawpathy Autoresearch (ClawBio/ClawBio, 1.2k stars) and Jarvis Setup (ethanplusai/jarvis, 838 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Using Elicitations?
friday-platform (a GitHub organization) maintains it in friday-platform/friday-studio, which has 104 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on September 5, 2026.
Source: friday-platform/friday-studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.