Clarify

Category: Tools & Productivity | Uploader: nikola66 | Downloads: 0 | Version: v1.0（Latest）

When intent is ambiguous, emit one structured clarification block so the UI can show choice buttons instead of guessing.

Changelog: Source: GitHub https://github.com/nikola66/web-agent

Directory Structure

Current level: tree/main/src/capabilities/skills/clarify/

📄 SKILL.md 1.3 KB

SKILL.md

---
name: Clarify
description: When intent is ambiguous, emit one structured clarification block so the UI can show choice buttons instead of guessing.
version: 1.0.0
category: bundled
tags: [ux, ambiguity, clarification, dialog]
---

## When to Use

- Requirements conflict, scope is fuzzy, or multiple valid interpretations exist.
- One sharp question resolves the fork faster than parallel tool guesses.
- UI can render options (browser host parses `<<<CLARIFY>>>` markers).

## Output Contract

Emit exactly this block **as plain assistant text** (no tool call):

```
<<<CLARIFY>>>
{"question":"Which stack should we use?","options":["React + Vite","Plain HTML/CSS","Other"],"open_ended":false}
<<<END>>>
```

Rules:

- `question`: one concise sentence ending with `?` when offering choices.
- `options`: 2–6 short strings when `open_ended` is false. Include **`Other`** only when genuinely needed.
- `open_ended`: true when typed prose is clearer than buttons — then **`options`** may be `[]`.
- JSON must parse; use double quotes. Do not wrap in markdown fences inside the markers.

Then stop and wait — the host sends the user's choice as the next user message.

## Anti-patterns

- Do **not** ask three overlapping questions — one block only.
- Do **not** use this when you can reasonably default (note the assumption briefly instead).

Comments 0

Latest | Hot

Please login before commenting.

Loading comments...

Clarify

Directory Structure

SKILL.md

Report

Notice