Guided Conversation

Minimize user friction by asking up to 4 clarifying questions before executing actions.

Security Scan

This is an instruction-only skill that only changes conversational behavior (asking up to 4 clarifying questions) and requests no credentials, installs, or filesystem access—its requirements and instructions are internally consistent with its stated purpose.

Purpose & Capability

Name/description (guided clarification) match the SKILL.md: no extra binaries, env vars, or installs are requested and nothing outside conversational guidance is required.

Instruction Scope

Instructions are limited to pre-action clarification and summarization, which is in-scope. Note: the policy 'if still ambiguous after 4 questions, make best-effort interpretation and proceed' increases risk of unintended actions; this is a design choice (usability vs safety) rather than an incoherence. Recommend enforcing requireConfirmationHighRisk and explicit safeguards for destructive or external-facing operations.

Install Mechanism

No install spec and no code files — lowest-risk form (instruction-only). Nothing will be written to disk or downloaded by the skill itself.

Credentials

The skill requests no environment variables, credentials, or config paths. Declared configuration options (maxQuestions, autoProceedAfterClarity, requireConfirmationHighRisk) are appropriate and proportional to the purpose.

Persistence & Privilege

always:false (default) and no persistent modifications or system-wide config changes are requested. Autonomous invocation is allowed by platform default but is not unusually privileged for this skill.

Assessment

This skill is coherent and low-risk because it only provides conversational instructions and asks for no secrets or installs. Before enabling: (1) enable requireConfirmationHighRisk (or set autoProceedAfterClarity=false) so high-impact actions always require explicit user consent; (2) consider lowering auto-proceed behavior or increasing maxQuestions if you prefer safety over convenience; (3) test the skill in a safe environment to ensure its 'best-effort' behavior doesn't perform unwanted actions; (4) verify it does not prompt for or transmit sensitive info (passwords, keys) and that it respects existing context/memory as promised; (5) review how it interacts with other skills (e.g., tools that perform external actions) to ensure confirmations are honored.

Guided Conversation Skill

Purpose

Minimize user friction by asking up to 4 clarifying questions before executing actions. Ensures the agent understands ambiguous tasks without over-interrogating.

When to Use

• User request is ambiguous or missing critical details
• Action is high-impact (file delete, payment, external API call)
• User has not provided enough context for safe execution

Constraints

• Max 4 questions per task
• Stop asking once sufficient clarity is reached
• Never ask for information already available in context/memory
• If still ambiguous after 4 questions, make best-effort interpretation and proceed (with user notification)

Output

After clarification:

1. Summarize understood task in 1 sentence
2. List assumptions made
3. Proceed to execution (or ask for confirmation if required by risk profile)

Integration

• Hook: pre-action phase (before tool calls)
• Risk-based: high-risk actions always require confirmation regardless of clarity
• Low-risk: can proceed automatically after clarification

Examples

User: "Zrób backup" Agent: "Which folder? Where to store? Full or incremental?" (3 questions)

User: "Wyślij maila do klienta" Agent: "Who is the client? What content? Any attachments?" (3 questions)

Configuration

• maxQuestions: 4 (default)
• autoProceedAfterClarity: true (default)
• requireConfirmationHighRisk: true (default)

Related Skills

• interaction-pipeline (status updates)
• adaptive-execution-profile (risk tolerance)