data-analysis
starsforks
How to install data-analysis?
rlaope/oh-my-hermes/data-analysis
$npx -y skills add rlaope/oh-my-hermes --skill data-analysis[omh] Hermes data analysis workflow: scope supplied data with provenance, causal-claim, and hallucination guards.
SKILL.md
| 1 | # Data Analysis |
| 2 | |
| 3 | This is a Hermes-native `data-analysis` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `data-analysis` exists so Hermes users can ask for this workflow in chat and receive a structured, evidence-bounded OMH operating surface instead of ad hoc narration. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The request is already handled by a narrower explicit skill with stronger evidence. |
| 12 | - The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents. |
| 13 | - The only safe answer is to ask for missing authority, credentials, target, or observed evidence first. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: data-analysis analyze this CSV and summarize anomalies by segment. |
| 20 | - Expected behavior: Produce `prepare_data_analysis_card` with required context, wrapper actions, and not-evidence boundaries. |
| 21 | - Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: data-analysis invent trends from an unavailable spreadsheet. |
| 26 | - Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened. |
| 27 | - Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence. |
| 28 | |
| 29 | ## Completion Checklist |
| 30 | |
| 31 | - Dataset or corpus source, record scope, schema or extraction method, join assumptions, analysis question, method, and stop condition are explicit. |
| 32 | - Numeric claims, anomalies, trends, segments, and log patterns are reported only from observed data or supplied evidence. |
| 33 | - Causal claims require observed identification evidence. |
| 34 | - Source acquisition, file conversion, report generation, and code fixes are routed to the narrower workflow when stronger. |
| 35 | |
| 36 | ## Recovery Notes |
| 37 | |
| 38 | - If the data itself is missing, ask for the smallest dataset sample, schema, or query output needed. |
| 39 | - If the user wants datasets found online, route to source-finder before analysis. |
| 40 | - If the user wants a PPT/PDF/XLSX report generated from data, route to materials-package or deliverable-package after analysis scope is clear. |
| 41 | |
| 42 | ## OMH Context Rail |
| 43 | |
| 44 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 45 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 46 | - Current lane: **Research and company ops** (`source-finder`, `web-research`, `best-practice-research`, `autoresearch-goal`, `research-brief`, `strategy-brief`, `feedback-triage`, `research-department`, `+6 more`) - research, signals, ops, and briefings. |
| 47 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 48 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 49 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 50 | - Coverage: Every generated workflow skill carries this rail. |
| 51 | - Normal users talk to Hermes; OMH CLI is infra. |
| 52 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 53 | |
| 54 | ## Use When |
| 55 | |
| 56 | Use when Hermes should prepare supplied structured, unstructured, or mixed data analysis without unsupported numeric or causal claims. |
| 57 | |
| 58 | Strong routing signals: `data-analysis`, `data analysis`, `dataset analysis`, `csv analysis`, `json analysis`, `log analysis`, `table analysis`, `analyze csv`, `analyze this csv`, `analyze json`, `analyze logs`, `summarize anomalies`, `anomaly analysis`, `trend analysis`, `segment analysis`, `column analysis`, `schema check`, `table to chart`, `chart with an executive summary`, `spreadsheet delta analysis`, `cohort analysis`, `retention analysis`, `correlation analysis`, `causal analysis`, `causality check`, `데이터 분석`, `csv 분석`, `json 분석`, `로그 분석`, `이상치 분석`, `추세 분석`, `오류 패턴`, `컬럼 분석`, `전환율 델타`, `차트 요약`, `상관관계 분석`, `인과 분석`, `인과관계` |
| 59 | |
| 60 | ## Catalog Metadata |
| 61 | |
| 62 | Category: `analysis` |
| 63 | Phase: `data-task` |
| 64 | Hermes role: `guide` |
| 65 | Quality tier: `workflow-surface-gated` |
| 66 | |
| 67 | Quality bar: |
| 68 | |
| 69 | - Name the user-facing workflow objective, required context, next action, and stop condition. |
| 70 | - Separate prepared guidance from observed platform, runtime, connector, file, memory, or delivery evidence. |
| 71 | - Expose missing tools, credentials, targets, or observations as user-visible gaps. |
| 72 | |
| 73 | Handoff policy: |
People who liked this also viewed
6 picksType
- azure-kustoQuery and analyze data in Azure Data Explorer (Kusto/ADX) using KQL for log analytics, telemetry, and time series analysis. WHEN: KQL queries, Kusto database queries, Azure Data Explorer, ADX clustersSkillsJul 2026
- lark-base飞书多维表格（Base）操作：建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、workflow、角色权限；遇到 Base/多维表格/bitable 或 /base/ 链接时使用。文件导入转 lark-drive，认证/授权转 lark-shared。SkillsJul 2026
- lark-calendar飞书日历：管理日历日程和会议室。查看/搜索日程、创建/更新日程、管理参会人、查询忙闲和推荐时段、预定会议室。当用户需要查看日程安排、创建/修改会议、查询/预定会议室时使用。不负责：查询过去的视频会议记录（走 lark-vc）、待办任务（走 lark-task）。SkillsJul 2026
- shadcnManages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. AppliSkillsJul 2026
- xlsxUse 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.SkillsJul 2026
- firebase-data-connectAgent Skills for FirebaseSkillsJul 2026
