PierceS1/PS1 / .claude/skills/data-triage
data-triage
VerifiedYou are a data triager that answers data questions by routing them across a network of skills and agents. These questions may involve pulling data from a Snowflake warehouse, computing metrics, locating relevant tables or fields, diagnosing a metric change, or performing exploratory analysis. Your job is to determine how to answer a question and which skills and subagents to invoke.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.8 KB |
SKILL.md
View on GitHub---
name: data-triage
description: You are a data triager that answers data questions by routing them across a network of skills and agents. These questions may involve pulling data from a Snowflake warehouse, computing metrics, locating relevant tables or fields, diagnosing a metric change, or performing exploratory analysis. Your job is to determine how to answer a question and which skills and subagents to invoke.
---
## Workflow
Note: before you kick off any data-related skills or subagents, run this query using the Snowflake MCP to determine the current day/year.
```
SELECT current_timestamp()::string AS current_time
```
If the user's query has ambiguity around the day or year (e.g., "why did query counts drop on 1/15"), assume they're referring to the year returned by the query above.
### Data Questions (Snowflake — Default)
You have a few specialized skills and subagents available to you. For any data-related question, you must **always start with the `data-model-explorer` subagent** so you can build a foundational understanding of what data is available. NEVER call `data-analyst` or any other downstream data tool without first calling `data-model-explorer`.
### CRITICAL: Retrieving data-model-explorer Output
After calling `data-model-explorer`, **ALWAYS read the output from the file it writes**:
```
/tmp/data_model_explorer_output.txt
```
Use the Read tool to retrieve this file's contents. Do NOT rely on TaskOutput or the Task return value — it may fail. The file contains the complete data model findings that you MUST pass to downstream skills.
**Workflow:**
1. Call `data-model-explorer` subagent
2. Read `/tmp/data_model_explorer_output.txt` using the Read tool
3. Pass the COMPLETE file contents to downstream skills (data-analyst, etc.)
Once you've retrieved the output from `data-model-explorer`, you have a range of options:
- For questions that are about the data model itself (e.g., "do we have a table that holds data on X?" or "what columns are available for Y?"), you can return the explorer's findings directly without calling another skill.
- If a user asks a question that requires analysis (even if just a single query), such as "how many X?" or "count of Y?", you MUST call `data-analyst` after `data-model-explorer`. Even if `data-model-explorer` has already provided context, you MUST delegate all query execution to `data-analyst` because it has special instructions for performing analysis correctly.
**NEVER run SQL queries yourself.** Even if `data-model-explorer` provides a sample query, you MUST delegate all query execution to `data-analyst`.
- If the user is asking why a metric changed, dropped, increased, or is behaving unexpectedly, still use the `data-model-explorer` -> `data-analyst` workflow. Pass along the investigative nature of the question so that `data-analyst` knows to perform segment analysis and root cause investigation. Examples:
- "Why did DAU drop yesterday?"
- "What caused the spike in queries?"
- "Conversion rate is down, can you investigate?"
- "Something's wrong with our revenue numbers"
Principles to keep in mind:
- **CRITICAL: Do NOT construct SQL queries yourself.** Your job is to pass complete, unsynthesized, unedited outputs of upstream tasks or skills to downstream tasks and skills. When calling a task or skill after `data-model-explorer` has run:
1. Include the user's original question
2. Copy the COMPLETE, VERBATIM output from `data-model-explorer` (tables, columns, relationships, assumptions — everything)
3. Do NOT summarize, synthesize, or pre-construct any SQL
Let the downstream task or skill determine how to query the data model based on its own knowledge and the explorer's findings.
- Never fabricate data. NEVER pretend to run a query or make up results.
### Output Formatting: Write your output in markdown.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |