Data analysis workflow: ingest, validate quality, explore, analyze, report. Use when the user provides or references datasets (CSV, JSON, SQL, spreadsheets) or asks for statistics, aggregation, correlation, or chart generation.
Scanned 8/31/2026
Install via CLI
openskills install spytensor/openmozi---
name: data-analysis
description: "Data analysis workflow: ingest, validate quality, explore, analyze, report. Use when the user provides or references datasets (CSV, JSON, SQL, spreadsheets) or asks for statistics, aggregation, correlation, or chart generation."
version: "1.0.0"
category: utility
user-invocable: true
requires:
bins: []
env: []
install:
# pandas ships with the managed document runtime; matplotlib does not, and this
# skill's guidance below tells the model to use it. Declaring it here makes the
# claim true through the managed provisioning path (architecture-keyed overlay,
# binary wheels only, verified by import) instead of leaving the model to
# discover the gap at runtime and pip-install it itself. Declared rather than
# bundled so the App payload does not grow.
- kind: pip
package: matplotlib
imports: ["matplotlib"]
label: "Install matplotlib for chart generation"
metadata:
priority: 60
---
# Data Analysis Workflow
## How to Execute
1. **Ingest**: Read the data source (CSV, JSON, database, API). Confirm format and size.
2. **Validate**: Check for missing values, outliers, type mismatches. Report data quality issues.
3. **Explore**: Compute basic statistics (count, mean, median, distribution). Identify patterns.
4. **Analyze**: Apply the requested analysis (correlation, aggregation, filtering, comparison).
5. **Report**: Present findings with clear summaries. Generate charts/visualizations if requested.
## Rules
- Always inspect the data before analyzing — never assume structure.
- Report data quality issues (nulls, duplicates, outliers) before drawing conclusions.
- Use shell_exec with Python (pandas, matplotlib) for large datasets or complex analysis.
- Show your methodology: what you computed, which columns, what filters.
- Present numbers with appropriate precision (don't show 15 decimal places).
## Pitfalls
- Analyzing without first inspecting the data shape and quality
- Drawing conclusions from data with unaddressed quality issues
- Showing raw numbers without context or interpretation
- Not specifying units or time periods for metrics
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.