Use when a meta-agent request is too ambiguous to safely generate, package, publish, or adapt without one to five targeted questions.
70%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/clarify-question-loop/SKILL.mdAsk only questions that change the generated package, runtime adapter, safety boundary, or public/private release decision.
For /hep-build creation or behavior-changing packaging, this is not a
substitute for the Builder Interview and Research Gate in
contracts/builder-interview-research-gate.md. Run that gate first: assess the
supplied context and ask only material gaps, including zero questions when
sufficient (8-12 only if that many gaps remain); research similar agent repositories or comparables and
academic/professional theory, then use this clarify loop only for the remaining
narrow ambiguities.
This loop shares the briefing interview engine's contract
(agentlas_cloud/interview/): a question is only worth asking if the answer
would change execution, not just its phrasing. Respect the surface budget
(chat 3-5 in one batch, stormbreaker <= 8 across two batches; build asks only
the material gaps). 'decide later' is always a valid answer — record it as
deferred, never re-ask. Outside build, when answers you auto-confirmed from
code/memory reach three in a row, the next question must go to the human.
Never ask non-technical users to choose internal labels such as
single-agent, team-builder, ownership boundary, memory/context, synthesis,
or produces/consumes. Translate them before asking:
If a question still sounds technical, split it into two shorter everyday questions and give examples such as 조사, 분석, 검토, 승인.
See docs/clarify-question-loop.md.
agentlas-ai/Agentlas-OS
fdcd97a
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.