Skip to content

BdM-15/capture-insights / skills/data-analyzer

data-analyzer

Verified

Advanced data analysis, pattern detection, and insight generation from structured and unstructured datasets. Use when the user wants to analyze data, perform statistical analysis, find insights, detect patterns, identify anomalies, compare segments, test hypotheses, or generate data-driven recommendations. Triggers on phrases like 'analyze data', 'data analysis', 'find insights', 'analyze dataset', 'statistical analysis', 'find patterns', 'compare groups', 'test hypothesis', 'correlation analysis', or 'trend analysis'.

FileKindSize
SKILL.mdskill md8.6 KB
assets/report_template.mdmarkdown1.7 KB
evals/evals.jsonconfig2.0 KB
references/pitfalls.mdmarkdown4.0 KB
references/statistical-methods.mdmarkdown4.8 KB
references/visualization-guide.mdmarkdown3.6 KB

assets/report_template.md

View on GitHub
# Data Analysis Report Template

```markdown
# Data Analysis Report: [Title]

**Date:** [Analysis Date]
**Dataset:** [Description, date range, sample size]

## Executive Summary

[2–3 sentences: key findings and top recommendation.]

## Objectives

- [Research question 1]
- [Research question 2]

## Data Overview

| Attribute     | Value                  |
| ------------- | ---------------------- |
| Source        | [Where data came from] |
| Time Period   | [Date range]           |
| Sample Size   | [N observations]       |
| Key Variables | [List main variables]  |

## Data Quality Assessment

- **Completeness:** X% complete (Y missing values across Z columns)
- **Issues Identified:** [List data quality problems with severity: high/medium/low]
- **Cleaning Steps:** [What was done to prepare data]

## Findings

### Finding 1: [Insight Title]

**Observation:** [What the data shows — specific numbers]
**Evidence:** [Statistics, test results, visualization reference]
**Significance:** [Statistical test result if applicable, e.g., t(87) = 3.2, p = 0.002, d = 0.68]
**Implication:** [What this means — so what?]

### Finding 2: [Insight Title]

[Repeat structure]

## Methodology

- **Statistical Tests Used:** [List tests and rationale for each]
- **Key Assumptions:** [Assumptions made and whether they were verified]
- **Limitations:** [What this analysis cannot tell us]

## Recommendations

1. **[Action]** — Expected Impact: [quantified if possible] — Owner: [role]
2. **[Action]** — Expected Impact: [quantified if possible] — Owner: [role]

## Next Steps

- [ ] Further analysis needed: [specify]
- [ ] Additional data to collect: [specify]
- [ ] Follow-up questions: [list]

## Appendix

[Detailed tables, methodology notes, raw statistical output]
```
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall