analysis-artifacts

Generates reproducible SQL queries, Python visualizations, and summary tables for BigQuery data analyses.

823|66|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/warpdotdev/oz-skills --skill analysis-artifacts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analysis-artifacts
Source: https://github.com/warpdotdev/oz-skills/tree/main/.agents/skills/analysis-artifacts
Command: npx skills add https://github.com/warpdotdev/oz-skills --skill analysis-artifacts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep-dive data analyses often produce one-off answers that cannot be reproduced, audited, or shared. This Skill structures BigQuery investigations into a persistent directory of artifacts so every insight is backed by a saved query, visualization, or table.

Core Features & Use Cases

  • Structured analysis scaffolding: Creates an analyses/ directory with assets/queries and assets/visualizations subdirectories plus a README as the main readable document.
  • Reproducible artifacts: Saves every material BigQuery query as a commented .sql file, generates charts via Python scripts with output images, and stores summary tables as .csv files.
  • Rigorous methodology: Enforces an explicit plan, a Problem Statement, and carefully controlled cohort definitions before querying, then produces a final README with TL;DR and Key Takeaways.
  • Use Case: When asked why paid users retain better than free users, the agent scaffolds an analysis folder, defines cohorts controlling for tenure and observation windows, saves each retention query and curve, and delivers a shareable README report.

Quick Start

Ask the agent to do a deep-dive analysis of a product question using BigQuery and produce a reproducible analysis directory with saved queries and visualizations.

Frequently Asked Questions about analysis-artifacts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make a BigQuery analysis reproducible?

Save every material query as a commented .sql file, generate charts with versioned Python scripts, and store summary tables as CSVs in a dedicated analysis directory. This Skill automates that structure with a README tying all artifacts together.

How to structure a data deep dive or exploratory analysis?

Start with a written plan mapping sub-questions, define cohorts explicitly to control for confounders like tenure and observation windows, then create artifacts as you go. Finish with a README containing a TL;DR and Key Takeaways.

What artifacts should a data analysis produce?

A reproducible analysis should produce saved SQL query files, visualization scripts with output images, CSV summary tables, and a README report. Trivial one-off lookup queries can be skipped to reduce noise.

Does this work with data warehouses other than BigQuery?

The workflow is written around BigQuery, but the artifact pattern of saved SQL files, Python visualizations, and a README applies to any SQL-based warehouse. Query syntax would need adjustment for other engines.

When should I not use a full analysis workflow?

Skip it for simple data lookups or one-off questions with obvious answers, since scaffolding directories and artifacts adds overhead. It is intended for deep dives and investigations where reproducibility and shareability matter.