answers-ask-user-input

$npx mdskill add openai/role-specific-plugins/answers-ask-user-input

Gathers user input efficiently

  • Solves unclear user preferences
  • Depends on interactive buttons
  • Decides using user feedback
  • Delivers results via text

SKILL.md

.github/skills/answers-ask-user-inputView on GitHub ↗
---
name: answers-ask-user-input
description: "Use when a small amount of missing context would materially improve the answer and tappable options plus a free-text answer can gather it efficiently."
---

# Ask User Input

## `ask_user_input`

purpose: present tappable options plus a free-text option to gather user preferences before providing advice. display interactive buttons that users can tap to answer, and include a concise placeholder for the free-text answer row.

when to use this tool:
- use for elicitation -- when you need to understand the user's preferences, constraints, or goals to give useful advice
- examples:
  - "help me plan a workout routine": ask about goals (strength/cardio/weight loss), time available, equipment access
  - "help me find a book to read": ask about genres, mood, recent favorites
  - "I'm thinking about getting a pet": ask about lifestyle, living situation, time commitment
  - "help me pick a gift for my friend": ask about occasion, budget, friend's interests

question quality requirements:
- each question should uncover a concrete preference, constraint, or tradeoff that would actually change your recommendation. If the answer would only restate which option the user already seems to prefer, the question is not useful enough.
- do NOT ask proxy questions whose options map directly onto the candidate recommendations the user is already comparing. Ask about decision factors beneath those labels instead: daily tasks, budget, timeline, schedule, risk tolerance, social setting, maintenance burden, or dealbreakers.
- avoid vague umbrella axes that bundle multiple dimensions into one abstract tradeoff. Prefer one concrete dimension per question so the user's tap gives you an interpretable signal.
- examples:
  - bad: user asks "Should I be an EMT or a firefighter?" and you ask "How do you feel about physical intensity vs medical focus?" with options that correspond to firefighter vs EMT.
  - better: ask "Which day-to-day work sounds more appealing?" with options about patient care, rescue/fire response, shift/station environment, or training timeline.

free-text placeholder requirements:
- every question MUST include free_text_placeholder
- make the placeholder short, concrete, and specific to the question, such as "Add another constraint" or "Describe your ideal pace"
- do not use generic placeholders like "Type your answer" unless the question truly has no more specific hint

when NOT to use this tool:
- user asks "A or B": they want your analysis and recommendation, not the options repeated back as buttons
- user is venting or processing emotions (e.g. "I'm having a bad day"): just listen and respond supportively
- user asks for your opinion (e.g. "what do you think of eggs?"): give your perspective directly
- factual questions (e.g. "what's the capital of France?"): just answer
- user needs prose feedback (e.g. "review my email"): provide written analysis
- user already gave you a detailed prompt with specific constraints: they've already done the narrowing themselves; asking for more second-guesses them. Proceed with their constraints and state any assumption you make inline

key instructions:
- always include a brief conversational message before presenting options -- don't show options silently
- you can ask up to 3 questions. Three is a ceiling, not a target.
- use 2-4 short, distinct options per question. You can use up to 10, but prefer 2-4.
- after calling this tool, your turn is done. Don't keep writing.
- prefer asking questions that can be multi-select. Most questions aren't mutually exclusive.

Invocation:
// Insert directly:
genui{"ask_user_input": {"questions": {...}}}
// This widget is not eligible for UUID Mode.

Example:
genui{"ask_user_input":{"questions":[{"question":"What matters most for this recommendation?","options":["Lower cost","Less effort","Best quality"],"type":"multi_select","free_text_placeholder":"Add another priority"}]}}

Args schema:
```text
// AskUserInputWidgetData
{
// Questions
//
// Ordered list of one-question pages to render.
// minItems: 1
questions: Array<
// AskUserInputQuestion
{
// Question
//
// Question shown to the user on this page.
question: string,
// Options
//
// Short answer options rendered as tappable choices.
options: string[], // minItems: 2, maxItems: 10
// Type
//
// Whether the user should pick one option or any number of options. Prefer wording questions as multi_select unless the answer is clearly only one choice.
type: "single_select" | "multi_select",
// Free Text Placeholder
//
// Short placeholder label for the free-text answer option shown below the tappable choices. Make it specific to this question.
free_text_placeholder: string,
}
>,
}
```

More from openai/role-specific-plugins

SkillDescription
analyze-account-signalsUse when the user wants to know what changed with one account, monitor an owner portfolio or watchlist, or rank accounts needing attention from recent evidence. Produce an evidence-backed account brief or bounded watchlist summary with recommended actions.
apolloUse only when a focused Sales workflow has selected a present and connected Apollo connector, or the user explicitly asks for Apollo prospecting, enrichment, Company Details, records, sequences, or outbound planning. Apply Apollo v2-specific behavior only after verifying app version 2.0.0 or later.
build-business-caseReview commercial proposals and build customer-led business cases, ROI or value models, pricing or investment rationales, executive summaries, and customer-ready value stories tied to a customer, workflow, initiative, or decision.
build-competitive-briefUse when the user wants a competitor or vendor comparison, market-landscape analysis, battlecard, objection package, positioning brief, or account-specific competitive view. Produce an evidence-backed comparison, guidance, and brief, using supplied materials, connected research, and public evidence when appropriate.
enrich-company-and-contact-dataUse for data-first company, contact, lead, and prospect discovery or enrichment, including firmographic or technographic completion, named-company profiling, entity resolution, ICP matching, prospect-list building, segmentation, trigger or sales-signal analysis, market and territory scans, and enrichment-backed comparisons. Exclude meeting preparation, outreach-led company research, and prioritization of an already established account book.
find-customer-quotesUse when the user wants verbatim customer or prospect quotes, voice-of-customer evidence, theme validation, objection evidence, product-friction examples, or support for a product area, use case, or sales narrative. Retrieve from transcripts, call notes, supplied transcript-like recordings or exports, and other grounded call material using explicit speaker-confidence and provenance rules.
find-key-internal-sourcesUse when a seller needs to find the best internal experts, owners, approvers, documents, channels, source-of-truth materials, or escalation routes for a customer question, product topic, competitive objection, implementation issue, account task, or other sales-support need. Route questions such as 'who knows about this?', 'what should I read?', 'where is the source of truth?', and 'which internal channel or document should I use?' here.
follow-up-after-callUse after a completed customer, prospect, partner, or important internal sales call, discovery session, demo, or conversation, including when the user supplies or uploads a transcript, notes, recording summary, or other grounded evidence. Advise on, assess, qualify, recap, and produce seller-ready follow-up actions and drafts.
get-rep-call-feedbackUse when the user wants evidence-backed coaching for one rep's calls, especially by comparing the rep with peer examples to identify repeatable best practices, specific upgrade moments, and practical next-call language.
hubspotUse only when a focused Sales workflow has selected a connected HubSpot CRM, or the user explicitly asks for HubSpot guidance, reads, drafts, notes, or reviewed record changes. Do not use when another CRM is authoritative.