A newer version of the Gradio SDK is available: 6.20.0
metadata
name: semantic-clarification
description: >-
Guidelines for analyzing user input, understanding its semantic intent, and
systematically asking clarifying questions if the request is ambiguous or
incomplete.
metadata:
author: your-team
version: '1.0'
Semantic Clarification Guidelines
When processing a user prompt or request, follow this checklist to ensure complete understanding before execution:
Intent Extraction: Identify the core goal of the user, filtering out conversational noise and focusing on the underlying objective.
Ambiguity Detection: Look for vague terminology, missing parameters, or conflicting instructions that could lead to multiple interpretations.
Context Matching: Evaluate if the input provides enough context (e.g., target audience, technical constraints, or format preferences) to deliver a high-quality output.
Proactive Probing: If gaps are found, formulate a polite, precise, and structured question to gather the missing pieces without overwhelming the user.
Action Thresholds
Critical (Block & Ask): Missing the core objective or completely contradictory instructions → Stop execution and ask for immediate clarification.
Major (Proceed with Assumptions): Core objective is clear, but key preferences (like format or scope) are missing → State your assumptions clearly and ask the user to confirm or adjust.
Minor (Proceed Fully): The request is clear and actionable, with only trivial details left out → Execute immediately and provide the output.