Menu

Individual skill

attribution-intent-clarification

Resolve genuinely ambiguous attribution queries by asking ONE focused clarifying question, then hand off to attribution-data-query (or another skill). Never become a wall of questions.

skills/attribution-intent-clarification/SKILL.md

Read pinned source

Source commit ef1c5166a62ffcabc8092680c339e8e424b6a1f7

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
Yes
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
9
Repository last updated
Nov 6, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## 1. Purpose

Resolve **genuinely ambiguous** attribution queries by asking **one focused clarifying question**, then hand the resolved query off to `attribution-data-query` (or another skill). Exists so we don't silently guess on multi-meaning inputs — but it must **never become a wall of questions**.

> **Shared conventions (canonical elsewhere — don't re-derive):** attribution model default + aliases and sales-platform scope + measurement identity are canonical in **`attribution-data-query`** (`references/attribution-model.md`, `references/sales-platform-scope.md`); when you state a default in an option, use those (load the `attribution-data-query` skill from this plugin if it isn't loaded). Note the default **time window is task-specific and not a contradiction**: a simple query defaults to 7 days, a model comparison to 30 days (needs signal) — state whichever you're using.

## 2. When to trigger

**Trigger** when the user's request has **≥ 2 plausible interpretations** on a dimension that materially changes the answer.

**5 ambiguity types** (detailed examples → `references/ambiguity-types.md`):

- **Granularity** — channel / campaign / creative?
- **Metric** — by ROAS / spend / orders / new customers?