Run

Template Types

Phase 1: Collaboration Setup (MANDATORY)

Step 1-1: Get Current Account Identifier

Identify the current account to determine LOCAL vs EXTERNAL data mapping:

SELECT CURRENT_ORGANIZATION_NAME(), CURRENT_ACCOUNT_NAME();

Result format: 'MYORG', 'MY_ACCOUNT' → Combine as MYORG.MY_ACCOUNT

Store this identifier for table mapping in sub-skills (used to match against SHARED_WITH values).

Step 1-2: View Available Collaborations

CALL {DB}.COLLABORATION.VIEW_COLLABORATIONS();

Display collaborations to user (name, status, owner).

Step 1-3: User Selects Collaboration

STOPPING POINT: Ask user which collaboration to use.

Step 1-4: Validate Collaboration Status

Inform user: "Collecting details for <collaboration_name>..."

CALL {DB}.COLLABORATION.GET_STATUS('<collaboration_name>');

Check:

• Current account's status = JOINED
• At least 2 parties are JOINED

If NOT ready: STOP — do NOT attempt to run any analysis or activation. The operation will fail. Inform the user why (which parties are not yet JOINED) and return to Step 1-3 to pick another collaboration.

Step 1-5: Get Templates and Data Offerings

ONLY proceed if Step 1-4 confirmed collaboration is ready:

CALL {DB}.COLLABORATION.VIEW_TEMPLATES('<collaboration_name>');
CALL {DB}.COLLABORATION.VIEW_DATA_OFFERINGS('<collaboration_name>');

Store these results - sub-skills will reference them.

Phase 2: Template Selection & Routing

Step 2-1: Categorize Templates

Group templates by type:

• Standard Audience Overlap: Names matching standard_audience_overlap_v*
• Standard Activation: Names matching standard_audience_overlap_activation_v*
• Custom Analysis: Type = sql_analysis in TEMPLATE_SPEC
• Custom Activation: Type = sql_activation in TEMPLATE_SPEC

Present categorized list to user.

Step 2-2: User Selects Template

STOPPING POINT: Ask user which template to run.

Step 2-3: Route to Sub-Skill (MANDATORY)

CRITICAL: You MUST load the appropriate sub-skill BEFORE attempting to build any ANALYSIS_SPEC or ACTIVATION_SPEC. Use the read tool to load the sub-skill file; the spec format is complex and varies by template type.

Based on selection, use the read tool to load the matching sub-skill and continue executing its workflow (no user confirmation needed here):

If template is standard_audience_overlap_activation_v* OR type = sql_activation: → Load activation/SKILL.md and continue with its workflow

Else (standard_audience_overlap_v OR sql_analysis OR other):* → Load analysis/SKILL.md and continue with its workflow

Note: This is NOT a stopping point. After loading the sub-skill, proceed directly with its instructions.

Policy Requirements

Some parameters require specific policies on data offerings:

If analysis fails with policy errors, user must update data offering with appropriate policies.

Stopping Points

• Step 1-3: User selects collaboration — STOP and ask
• Step 2-2: User selects template — STOP and ask
• Sub-skill stopping points: Each sub-skill (analysis, activation) has its own mandatory stopping points for table selection, parameter configuration, and execution confirmation

Resume rule: Upon user approval, proceed directly without re-asking.

Common Errors

Required Privileges

See the parent data-cleanrooms SKILL.md "Required Privileges" section for how to grant privileges using {DB}.ADMIN.GRANT_PRIVILEGE_ON_ACCOUNT_TO_ROLE or {DB}.ADMIN.GRANT_PRIVILEGE_ON_OBJECT_TO_ROLE.