# Clarify Ambiguous User Requests

Ambiguous requests can lead to wrong assumptions and wasted work. This skill helps Claude, Codex, and Claude Code infer goals, constraints, and useful clarifying questions.

## Install

```bash
npx skillstore add dnyoussef/intent-analyzer
```

## Metadata

- Status: approved
- Slug: dnyoussef-intent-analyzer
- Skillstore revision: r1
- Version status: missing
- Tree hash: 7b3d626c835f7eda2398929c717be582a6e1cdeee14a0c652a98dbd698c6690e
- Author: DNYoussef
- GitHub username: DNYoussef
- License: MIT
- Repository: https://github.com/DNYoussef/ai-chrome-extension/tree/main/.claude/skills/intent-analyzer
- Ref: 72d5025b022c77f7a51bdf5c1637c689c80e89d1
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network
- Quality score: 75
- Public page: https://skillstore.pages.dev/skills/dnyoussef-intent-analyzer
- Manifest: https://skillstore.pages.dev/api/skills/dnyoussef-intent-analyzer/manifest

## Capabilities

- Maps vague requests to likely underlying goals and user needs.
- Identifies explicit and implicit constraints from wording and context.
- Recommends when to proceed, state assumptions, or ask clarifying questions.
- Provides pattern guidance for creative, analytical, technical, and decision requests.
- Encourages concise clarification with one to three strategic questions.

## Use Cases

- Clarify Product Requests: Turn broad product ideas into clearer goals, constraints, and next questions before planning work.
- Improve Coding Help: Distinguish between learning, debugging, production implementation, and review needs before answering technical questions.
- Guide Research Conversations: Identify decision criteria, audience needs, and missing context before producing analysis or recommendations.

## Prompt Templates

### Clarify a Vague Request

```
Use intent-analyzer on this request. Identify the likely goal, key missing context, and one clarifying question: [paste request].
```

### Choose an Interpretation

```
Analyze this request with intent-analyzer. List the top interpretations, estimate confidence, and recommend whether to proceed or clarify: [paste request].
```

### Prepare Better Technical Help

```
Use intent-analyzer before answering this technical request. Infer experience level, likely goal, missing constraints, and the best response strategy: [paste request].
```

### Resolve High-Stakes Ambiguity

```
Apply intent-analyzer deeply. Separate explicit asks, inferred goals, assumptions, risk of wrong interpretation, and the minimum clarification needed: [paste request].
```

## Limitations

- It is a reasoning framework, not an automated classifier or scoring engine.
- It depends on available conversation context and may still infer incorrectly.
- It does not verify facts, inspect systems, or access external data.
- It can slow simple tasks if applied too broadly.

## Best Practices

- Use the skill when misunderstanding the request would materially change the answer.
- Ask only the smallest number of clarifying questions needed to proceed.
- State important assumptions when proceeding without full clarification.

## Anti Patterns

- Do not use deep intent analysis for simple factual questions.
- Do not ask many broad questions when one targeted question would resolve ambiguity.
- Do not present internal reasoning as a substitute for useful output.

## Security Audit

- Audited at: 2026-07-06T12:29:39.781\+00:00
- Summary: All seven static findings are false positives in markdown guidance. The cited text discusses requests, assumptions, context clues, and efficient clarification, with no scripts, network calls, or reconnaissance behavior. No prompt injection or semantic abuse was found.

## Stats

- Views: 175
- Downloads: 12
- Favorites: 0
- Popularity score: 0