.claude/skills/compare-datasets/SKILL.md
# Skill: Compare Datasets ## Purpose Compare metrics, findings, and patterns across two or more connected datasets. Helps identify cross-dataset patterns (e.g., "conversion funnel behavior is similar across both product lines") and dataset-specific anomalies. ## When to Use - User says `/compare-datasets` or "compare across datasets" - After analyzing multiple datasets, to find commonalities - When the user asks "is this pattern unique to this dataset?" ## Invocation `/compare-datasets` — com
npx skillsauth add ai-analyst-lab/ai-analyst .claude/skills/compare-datasetsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Compare metrics, findings, and patterns across two or more connected datasets. Helps identify cross-dataset patterns (e.g., "conversion funnel behavior is similar across both product lines") and dataset-specific anomalies.
/compare-datasets or "compare across datasets"/compare-datasets — compare active dataset with all others
/compare-datasets {id1} {id2} — compare two specific datasets
/compare-datasets metric={name} — compare a specific metric across datasets
.knowledge/datasets/ to enumerate all connected datasets./connect-data to add another."For each dataset:
.knowledge/datasets/{id}/metrics/index.yamlFor each metric that exists in 2+ datasets:
For each dataset:
.knowledge/analyses/index.yamlWrite findings to .knowledge/global/cross_dataset_observations.yaml:
Display a comparison table:
Cross-Dataset Comparison: {dataset_a} vs {dataset_b}
Shared Metrics: {N} ({M} with matching definitions)
Metric Discrepancies: {list}
Shared Patterns:
- {pattern description} (seen in both datasets)
Divergences:
- {metric} is {direction} in {dataset_a} but {direction} in {dataset_b}
Suggested Next:
- "Investigate why {pattern} differs between datasets"
- "Align {metric} definitions across datasets"
testing
# Skill: {{BLANK_1_SKILL_NAME}} ## Purpose {{BLANK_2_WHEN_TO_FIRE}} ## When to Use Fires automatically when the user asks Claude to do something that matches the trigger condition above. ## Instructions 1. Detect the trigger condition 2. Execute your guardrail check 3. If the check matters, print a clear, visible warning with "{{BLANK_3_SIGNATURE_PHRASE}}" as the first line 4. Continue with the analysis, incorporating the warning into the output ## Anti-Patterns - Do not fire when the condit
development
# Skill: Visualization Patterns ## Purpose Ensure every chart Claude Code produces follows high-quality design standards with named themes, consistent styling, and clear data communication. ## When to Use Apply this skill whenever generating a chart, graph, or data visualization. Always apply the active theme unless the user specifies otherwise. Default theme: `minimal`. ## Instructions ### Pre-flight: Load Learnings Before executing, check `.knowledge/learnings/index.md` for relevant entrie
development
# Skill: Triangulation / Sanity Check ## Purpose Cross-reference analytical findings against multiple data sources, external benchmarks, and common sense to catch errors before they become bad decisions. ## When to Use Apply this skill after every analysis, before presenting findings to stakeholders, and whenever a result seems surprising. If a finding would change a decision, it MUST be triangulated first. ## Instructions ### Triangulation Framework Every finding gets checked through four
data-ai
# Skill: Tracking Gap Identification ## Purpose Assess whether the data needed for an analysis actually exists, identify what's missing, and produce prioritized instrumentation requests for engineering when gaps are found. ## When to Use Apply this skill after the Data Explorer agent inventories available data, when an analysis requires data that might not exist, or when initial query results suggest incomplete tracking. Run before committing to an analysis approach. ## Instructions ### Gap