Individual skill
attribution-data-query
Translate explicit data requests into Cube.dev SQL and return results. Default skill for query-type asks in the Attribution domain. No estimation, no fabrication, no proactive dashboards.
skills/attribution-data-query/SKILL.md
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.
- agent-skills Repository topic
- attribution Repository topic
- chatgpt Repository topic
- claude Repository topic
- claude-plugin Repository topic
- codex Repository topic
- cursor Repository topic
- ecommerce Repository topic
- gemini-cli-extension Repository topic
- incrementality Repository topic
- data Derived category
- data-databases Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 12,928 bytesexamples/example-A-meta-roas-last-week.mddoc · 2,676 bytesreferences/attribution-model.mddoc · 2,147 bytesreferences/edge-cases.mddoc · 2,822 bytesreferences/failure-modes.mddoc · 2,685 bytesreferences/granularity-default.mddoc · 409 bytesreferences/sales-platform-scope.mddoc · 4,499 bytesreferences/sql-examples.mddoc · 7,743 bytesreferences/time-range-resolution.mddoc · 1,692 bytestemplates/01-channel-roas.sqlasset · 705 bytestemplates/02-top-n-campaigns.sqlasset · 655 bytestemplates/03-period-over-period.sqlasset · 1,547 bytestemplates/04-creative-headlines.sqlasset · 779 bytestemplates/05-actual-store-sales.sqlasset · 718 bytes
Read excerpt
# attribution-data-query
## 1. Purpose
Translate the user's explicit data request into a precise Cube.dev SQL query and return results. **No estimation, no fabrication, no proactive dashboard creation.** This is the default skill for all query-type requests in the Attribution domain.
## 2. When to trigger
**Trigger condition**: the user's request explicitly states (or strongly implies) **most** of:
- A specific metric (ROAS, spend, new_customers, conversion_rate, etc.)
- A specific dimension (channel, campaign, creative, sales_channel)
- A time range (explicit or common phrasing like "last week", "last 30 days")
- Optional: filters, attribution model, sort order