Index of every page on this site: llms.txt
All skills
antfu avatar

/antfu-query

@4a6bb39 official
by Anthony Fuantfu/skills6.1k stars
345
Run it yourself

Interview the user relentlessly about a plan, decision, or idea until reaching a shared understanding, using the agent's interactive question tool (not plain text). Use when the user wants to stress-test their thinking, clarify requirements, or says "grill me" or "query me".

Use this Skill: https://skilld.dev/gh/antfu/skills/antfu-query

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈72 tokens for metadata: the name and description. ≈661 when used: this file.

Description uses 3.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈289 characters, or 3.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Query

Interview the user relentlessly until you reach a shared understanding. Map this as a design tree: every decision branches into the decisions that hang off it.

Ask With the Question Tool

Put every question to the user through the agent's interactive question tool (for example AskUserQuestion in Claude Code, or the equivalent in other agents; load it first if it is deferred). Do not write questions as plain text in the reply.

  • Give each question 2-4 distinct, concrete options with a short description of the trade-off.
  • Put your recommended answer first and mark it (Recommended), so picking it accepts your recommendation. The tool adds an "Other" option for free-form answers; do not add one.
  • Keep headers short. Use multi-select only when the options are not mutually exclusive.
  • Batch the whole frontier into one call, up to the tool's limit per call (4 in Claude Code). If the frontier is larger, ask the most blocking questions first and the rest next round.
  • If the agent has no question tool, fall back to plain text: number the questions, list the options, and state your recommended answer for each.

Rounds

Work the tree in rounds. The frontier is every decision whose prerequisites are already settled: the questions you can ask now without guessing at answers you have not heard yet. Ask the whole frontier in one round, then wait for the answers before the next round.

  • Each answered round reshapes the tree: settled decisions push the frontier outward and unblock questions that depended on them. Recompute the frontier and ask the next round.
  • A question whose answer depends on another question still open in this round belongs to a later round.
  • Word each question so the recommended option is the natural "yes".
  • Use the user's free-form "Other" answers and notes as new input: they may add or remove branches.

Facts vs Decisions

Finding facts is your job, never the user's. When a question needs a fact from the environment (files, code, tools, docs), look it up yourself or dispatch a sub-agent with a fresh context window. Do not ask the user for anything you could look up.

Do not block on it: a running exploration is an unsettled prerequisite, so only the questions downstream of it wait. Ask the rest of the frontier now. The decisions are the user's: put each to them and wait.

Done

The session is done when the frontier is empty: every branch of the design tree visited, nothing left silently assumed. Summarize the settled decisions in a short list and do not act on them until the user confirms you have reached a shared understanding.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts21d3 checks · Risk SAFE
  • Gen Agent Trust Hub21d

    The skill is safe and facilitates a structured interviewing process to help users clarify plans or designs. It includes safety measures such as requiring user confirmation before acting on any gathered information.

  • Socket21d

    No alerts

  • Snyk21d

    Risk: LOW · No issues

Signed by skilld at 4a6bb39. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 5 days ago.

Activeupdated 3 weeks ago
Other metadata
metadata
{
  "author": "Anthony Fu",
  "version": "2026.10.31",
  "source": "Adapted from https://github.com/mattpocock/skills/blob/main/skills/productivity/grilling/SKILL.md"
}

README badge

README badge for antfu/skills/antfu-query