notque/vexjoy-agent / skills/analysis/data
data
VerifiedData analysis, reference enrichment, and data engineering: pipelines and warehouses, server database design and tuning, SQLite with Peewee.
references/output-templates.md
View on GitHub# Output Templates
Templates for common analysis types. Each template specifies the structure for `analysis-report.md` tailored to the analysis pattern.
---
## A/B Test Evaluation
Use when comparing two (or more) experimental variants with a defined control.
```markdown
# A/B Test Analysis Report
## Headline
[One sentence: does the test variant win, lose, or is the result inconclusive?]
## Test Design
- **Hypothesis**: [What was being tested]
- **Control (A)**: [Description]
- **Variant (B)**: [Description]
- **Primary metric**: [Metric name and definition]
- **Sample**: Control N=[X], Variant N=[Y]
- **Test duration**: [Start - End]
- **Minimum detectable effect**: [MDE used in test design]
## Results
### Primary Metric
| Group | Value | 95% CI | N |
|-------|-------|--------|---|
| Control (A) | [value] | [lower - upper] | [N] |
| Variant (B) | [value] | [lower - upper] | [N] |
| **Difference** | **[value]** | **[lower - upper]** | |
- Statistical significance: [p-value]
- Effect size: [Cohen's d or relative change]
- Practical significance: [Above/Below minimum actionable threshold]
### Secondary Metrics (if applicable)
| Metric | Control | Variant | Difference | 95% CI | Significant? |
|--------|---------|---------|------------|--------|-------------|
| [name] | [value] | [value] | [diff] | [CI] | [Yes/No] |
### Segment Breakdown (if applicable)
| Segment | Control | Variant | Difference | N (per group) |
|---------|---------|---------|------------|---------------|
| [name] | [value] | [value] | [diff] | [N] |
*Note: [N] segments tested. [Correction method] applied. [N] significant after correction.*
## Rigor Checks
- Sample adequacy: [PASS/FAIL]
- Group balance: [Ratio and assessment]
- Time window: [Complete/Gaps noted]
- Multiple testing: [Method if applicable]
## Limitations
- [Limitation 1]
- [Limitation 2]
## Recommendation
[Ship / Do not ship / Extend test -- with rationale tied to evidence thresholds]
## What Would Increase Confidence
- [Suggestion 1]
- [Suggestion 2]
```
---
## Trend Analysis
Use when examining how a metric changes over time.
```markdown
# Trend Analysis Report
## Headline
[One sentence: what is the trend and what does it mean for the decision?]
## Trend Summary
- **Metric**: [Name and definition]
- **Period**: [Start - End]
- **Granularity**: [Daily / Weekly / Monthly]
- **Overall direction**: [Increasing / Decreasing / Flat / Volatile]
- **Rate of change**: [Average period-over-period change with CI]
## Trend Data
### Overall
| Period | Value | Change | Change % |
|--------|-------|--------|----------|
| [period] | [value] | [abs change] | [pct change] |
### By Segment (if applicable)
| Segment | Start Value | End Value | Overall Change | Trend |
|---------|-------------|-----------|----------------|-------|
| [name] | [value] | [value] | [change] | [direction] |
## Pattern Detection
- **Seasonality**: [Detected / Not detected -- pattern description]
- **Structural breaks**: [Any abrupt changes in trend? When?]
- **Outliers**: [Periods that deviate significantly from trend]
## Drivers
[What is driving the trend? Segment decomposition showing which segments contribute most to the overall change.]
| Segment | Contribution to Overall Change |
|---------|-------------------------------|
| [name] | [pct of total change] |
## Limitations
- [Limitation 1: e.g., "Seasonality not fully controlled -- only 1 year of data"]
- [Limitation 2: e.g., "External factors (pricing change in March) may confound trend"]
## Recommendation
[Action tied to the decision frame from Phase 1]
## What Would Increase Confidence
- [More time periods to control for seasonality]
- [Additional segmentation to isolate drivers]
```
---
## Distribution Profiling
Use when understanding the shape and characteristics of a metric's distribution.
```markdown
# Distribution Analysis Report
## Headline
[One sentence: what does the distribution tell us about the decision?]
## Distribution Summary
- **Metric**: [Name and definition]
- **Sample**: N=[count]
- **Period**: [Time window]
## Key Statistics
| Statistic | Value |
|-----------|-------|
| Mean | [value] |
| Median | [value] |
| Std Dev | [value] |
| Min | [value] |
| Max | [value] |
| p25 | [value] |
| p75 | [value] |
| p90 | [value] |
| p95 | [value] |
| p99 | [value] |
| Skewness | [value -- interpretation] |
## Distribution Shape
- **Type**: [Normal / Right-skewed / Bimodal / Long-tailed / Uniform]
- **Key characteristic**: [What is notable about this distribution?]
- **Mean vs Median gap**: [If large, indicates skew -- report which is more appropriate]
## Percentile Analysis
[For performance/latency data, focus on tail behavior]
| Percentile | Value | Within Threshold? |
|------------|-------|-------------------|
| p50 | [value] | [Yes/No] |
| p90 | [value] | [Yes/No] |
| p95 | [value] | [Yes/No] |
| p99 | [value] | [Yes/No] |
## Segments (if applicable)
| Segment | Mean | Median | p99 | N |
|---------|------|--------|-----|---|
| [name] | [value] | [value] | [value] | [count] |
## Outlier Analysis
- **Outlier definition**: [Method: >3 std dev / IQR / domain-specific]
- **Count**: [N outliers of M total ([pct]%)]
- **Impact on mean**: [Mean with outliers vs without]
- **Investigation**: [What outliers represent -- errors? genuine extremes?]
## Limitations
- [Limitation 1]
- [Limitation 2]
## Recommendation
[Action tied to the decision frame]
```
---
## Cohort Comparison
Use when comparing groups defined by a shared characteristic (sign-up date, plan tier, geography).
```markdown
# Cohort Comparison Report
## Headline
[One sentence: how do cohorts differ and what does it mean?]
## Cohort Definitions
| Cohort | Definition | N |
|--------|-----------|---|
| [name] | [selection criteria] | [count] |
## Comparison Fairness Assessment
- Same time window: [Yes/No -- details]
- Same population base: [Yes/No -- details]
- Known confounders: [List]
- Survivorship bias: [Risk level and mitigation]
## Results
### Primary Metric
| Cohort | Value | 95% CI | N |
|--------|-------|--------|---|
| [name] | [value] | [lower - upper] | [count] |
### Pairwise Comparisons
| Comparison | Difference | 95% CI | Significant? | Practically Significant? |
|-----------|-----------|--------|-------------|------------------------|
| A vs B | [diff] | [CI] | [Yes/No] | [Yes/No -- vs threshold] |
*[N] pairwise comparisons performed. [Correction method] applied.*
## Cohort Behavior Over Time (if temporal)
| Period | Cohort A | Cohort B | Gap |
|--------|----------|----------|-----|
| [period] | [value] | [value] | [diff] |
[Is the gap widening, narrowing, or stable?]
## Limitations
- [Limitation 1]
- [Limitation 2]
## Recommendation
[Action tied to the decision frame]
```
---
## Funnel Analysis
Use when measuring drop-off through a sequence of steps.
```markdown
# Funnel Analysis Report
## Headline
[One sentence: where is the biggest drop-off and what does it mean?]
## Funnel Definition
- **Entry**: [First step and its definition]
- **Exit**: [Last step / conversion event]
- **Time window**: [Period analyzed]
- **Population**: [Who is included]
## Funnel Steps
| Step | Count | Rate from Previous | Rate from Entry | Drop-off |
|------|-------|-------------------|-----------------|----------|
| [Step 1] | [N] | -- | 100% | -- |
| [Step 2] | [N] | [pct] | [pct] | [pct dropped] |
| [Step 3] | [N] | [pct] | [pct] | [pct dropped] |
| [Final] | [N] | [pct] | [pct] | [pct dropped] |
**Overall conversion**: [Entry to Final pct]
## Biggest Drop-off
- **Step**: [Where the largest drop occurs]
- **Drop rate**: [Percentage]
- **Volume**: [Absolute number of users lost]
- **Context**: [Why this might be happening -- if data supports it]
## By Segment (if applicable)
| Segment | Entry | Final | Conversion | vs Overall |
|---------|-------|-------|------------|-----------|
| [name] | [N] | [N] | [pct] | [+/- vs overall] |
## Limitations
- [Limitation 1: e.g., "Cannot distinguish intentional exits from errors"]
- [Limitation 2]
## Recommendation
[Where to focus optimization efforts, tied to decision frame]
```
---
## Phase Artifact Templates
### analysis-frame.md (Phase 1 output)
```markdown
# Analysis Frame
## Decision
[What decision is being supported]
## Decision-Maker
[Who will act on this analysis]
## Options
- Option A: [description]
- Option B: [description]
- Default (no action): [what happens if we take no action]
## Evidence Requirements
- Favors Option A if: [condition]
- Favors Option B if: [condition]
- Minimum threshold: [what bar must be cleared]
## Deal-Breakers
- [condition that forces a specific option regardless]
```
### metric-definitions.md (Phase 2 output)
```markdown
# Metric Definitions
## Metrics
### [Metric Name]
- Formula: [exact computation]
- Population: [inclusion/exclusion criteria]
- Time window: [start - end, granularity]
- Segments: [how data is sliced]
## Comparison Groups (if applicable)
### Group A: [Name]
- Selection: [criteria]
### Group B: [Name]
- Selection: [criteria]
- Fairness: [same population? same time window?]
## Success Criteria
- Minimum meaningful effect: [threshold]
- Minimum sample per segment: [N]
- Test type: [one-tailed / two-tailed / descriptive only]
```
### data-quality-report.md (Phase 3 output)
```markdown
# Data Quality Report
## Dataset Overview
- Source: [file path / description]
- Rows: [N]
- Columns: [N]
- Date range: [start - end]
## Column Profiles
| Column | Type | Non-null | Missing % | Unique | Notes |
|--------|------|----------|-----------|--------|-------|
| [name] | [type] | [count] | [pct] | [count] | [flags] |
## Quality Assessment
- [ ] Sample adequate (N=[count], population=[est])
- [ ] Time window complete (gaps: [none / list])
- [ ] Segment minimums met ([list segments below 30])
- [ ] Missing values acceptable ([list columns above 20%])
## Quality Issues
[List any issues that affect planned analysis]
## Data Ready: [YES / NO - with reason]
```
### analysis-results.md (Phase 4 output)
```markdown
# Analysis Results
## Metrics
### [Metric Name]
- Value: [point estimate]
- 95% CI: [lower - upper]
- Sample: N=[count]
## Comparisons (if applicable)
### [Group A] vs [Group B]
- Group A: [metric] = [value] (N=[count])
- Group B: [metric] = [value] (N=[count])
- Difference: [absolute] ([relative]%)
- 95% CI of difference: [lower - upper]
- Practical significance: [above/below minimum threshold]
## Rigor Gate Results
- [ ] Sample Adequacy: [PASS / FAIL - details]
- [ ] Comparison Fairness: [PASS / FAIL / N/A - details]
- [ ] Multiple Testing: [PASS / FAIL / N/A - details]
- [ ] Practical Significance: [PASS / FAIL - details]
## Rigor Violations (if any)
[List violations and their impact on conclusions]
```
### analysis-report.md (Phase 5 output)
```markdown
# Analysis Report
## Headline
[One sentence: what the data says about the decision]
## Decision Context
[Recap from Phase 1 frame]
## Key Findings
1. [Primary finding with CI]
2. [Supporting finding]
3. [Qualifying finding or important segment variation]
## Limitations
- [Limitation 1]
- [Limitation 2]
## Recommendation
[Action recommendation with confidence level]
## What Would Increase Confidence
- [Additional data or analysis that would help]
---
## Appendix: Methodology
- Data source: [file]
- Rows analyzed: [N]
- Time window: [range]
- Tools: [pandas/stdlib]
- Metrics: See metric-definitions.md
- Quality: See data-quality-report.md
- Detailed results: See analysis-results.md
```
---
## Anomaly Investigation
Use when investigating unexpected spikes, drops, or deviations in metrics.
```markdown
# Anomaly Investigation Report
## Headline
[One sentence: what happened, when, and what caused it?]
## Anomaly Summary
- **Metric**: [Name]
- **Normal range**: [Expected value or range]
- **Anomaly value**: [Observed value]
- **Deviation**: [How far from normal -- Z-score or percentage]
- **When**: [Date/time range]
- **Duration**: [How long the anomaly lasted]
## Timeline
| Time | Value | Status |
|------|-------|--------|
| [before] | [normal value] | Normal |
| [onset] | [value] | Anomaly begins |
| [peak] | [value] | Peak deviation |
| [recovery] | [value] | Returns to normal |
## Root Cause Analysis
### Correlated Events
| Event | Timing | Correlation |
|-------|--------|-------------|
| [deployment/change/incident] | [time] | [Likely/Possible/Unlikely] |
### Segment Isolation
| Segment | Affected? | Severity |
|---------|-----------|----------|
| [name] | [Yes/No] | [Magnitude] |
[Which segments are affected narrows the possible causes.]
## Impact Assessment
- **Duration**: [How long]
- **Magnitude**: [Quantified impact -- revenue lost, users affected, etc.]
- **Scope**: [How widespread -- single endpoint vs system-wide]
## Limitations
- [Limitation 1]
## Recommendation
[Action to prevent recurrence, tied to decision frame]
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |