# Omh Data Analysis

[omh] Dataset or table to analyze: scope supplied data with provenance, causal-claim...

- Repository: https://github.com/rlaope/oh-my-hermes (5004 stars)
- Category: Data and ML
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rlaope/oh-my-hermes --skill omh-data-analysis -g -a claude-code -y`
Codex: `npx skills add rlaope/oh-my-hermes --skill omh-data-analysis -g -a codex -y`
Cursor: `npx skills add rlaope/oh-my-hermes --skill omh-data-analysis -g -a cursor -y`
Gemini CLI: `npx skills add rlaope/oh-my-hermes --skill omh-data-analysis -g -a gemini-cli -y`

## Description

[omh] Dataset or table to analyze: scope supplied data with provenance, causal-claim, and hallucination guards. Use when the user says: data-analysis, data analysis, dataset analysis, csv analysis, json analysis, log analysis, table analysis, analyze csv.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Data Analysis

This is an OMH `data-analysis` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

## Why This Exists

`data-analysis` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.

## Do Not Use When

- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.

## Examples

Good example:

- Prompt: data-analysis analyze this CSV and summarize anomalies by segment.
- Expected behavior: Produce `prepare_data_analysis_card` with required context, wrapper actions, and not-evidence boundaries.
- Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution.

Bad example:

- Prompt: data-analysis invent trends from an unavailable spreadsheet.
- Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened.
- Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence.

## Completion Checklist

- Dataset or corpus source, record scope, schema or extraction method, join assumptions, analysis question, method, and stop condition are explicit.
- Numeric claims, anomalies, trends, segments, and log patterns are reported only from observed data or supplied evidence.
- Causal claims require observed identification evidence.
- Source acquisition, file conversion, report generation, and code fixes are routed to the narrower workflow when stronger.

## Recovery Notes

The rest: https://github.com/rlaope/oh-my-hermes/blob/HEAD/agent-skills/omh-data-analysis/SKILL.md