---
name: partners
description: "Query and analyze partner reporting data in Snowflake. Use when: analysts ask about a specific data partner, vendor datashare, or partner tables. Triggers: partner, vendor, datashare, partner data, external data source."
---

# Partner Data Skill

## Overview

This skill helps analysts query data from external partners delivered to Snowflake (via datashares, file loads, or APIs). Each partner has its own sub-skill with domain-specific context (databases, schemas, entity relationships, query patterns).

Universal query standards that apply to all partners are in `references/query-standards.md`.

## Partner Routing

**Load** `references/partner-registry.md` to get the full list of registered partners, their trigger terms, and sub-skill paths. Match the analyst's question against the trigger terms in the registry.

**Only use partner-specific terms to identify a partner** — generic terms like "streaming numbers", "sales data", or "top songs" are not sufficient. If the partner is not clear, stop and ask (see Step 1).

## Workflow

### Step 1: Identify the Partner(s)

1. **Load** `references/partner-registry.md`
2. Match the analyst's question against trigger terms in the registry
3. **If the partner is not clear** — stop immediately. Ask: *"Which partner's data are you looking for?"* and list the registered partners. Do not proceed until the analyst names a partner.
4. **If one partner is identified**: Load **only** that partner's sub-skill. **Do not load any other partner sub-skills for this query.**
5. **If multiple partners are explicitly named**: Load each named partner's sub-skill from the registry one at a time. Handle one partner at a time in the response.
   - For any named partner without a registered sub-skill, use the Snowflake catalog (`SHOW TABLES/VIEWS IN SCHEMA`, `DESCRIBE TABLE`) to discover available objects.

### Step 2: Load Universal Standards

Before building any query, **Load** `references/query-standards.md` — this contains rules that apply to all partner data (value discovery, aggregation rules, catalog usage, date-range interpretation).

### Step 3: Follow the Partner Sub-Skill

The partner sub-skill will guide:
- Data source selection (which databases/schemas)
- Table and join identification
- Partner-specific filters and caveats
- Query construction

## Adding a New Partner

1. Copy `_template/` to `partners/<partner-name>/`
2. Follow the setup checklist at the top of `_template/SKILL.md` — fill every `<!-- FILL: ... -->` marker and delete the checklist block when done
3. Delete any reference files that don't apply to this partner
4. Add a row to `references/partner-registry.md` under the appropriate category
5. Test by asking a sample question that should route to the new partner