Finance Analysis
This is a Hermes-native finance-analysis workflow skill.
Why This Exists
finance-analysis prepares a source-bounded decision brief without claiming an authoritative financial action.
Do Not Use When
- The request is for a current quote, exchange rate, crypto price, or other live market lookup; use
live-info-operator.
- The user wants generic exploration of a supplied CSV or table without accounting periods, controls, or finance decision framing; use
data-analysis.
- The user asks to post journal entries, reconcile accounts, approve payments, submit tax filings, or configure an accounting system; use
connector-operator for an explicit observed action path.
- The user wants pipeline coverage, deal health, or a seller forecast scenario rather than authoritative revenue or close reporting; use
sales-pipeline-review.
- The user needs an enterprise or product direction decision after analysis; route that decision to
strategy-brief.
Examples
Good example:
- Prompt: Compare Q2 actuals against budget, explain the biggest expense variances, and flag cash risks for the CFO.
- Expected behavior: Prepare the period boundary, actual-versus-plan narrative, cash-risk register, and decision questions.
- Why: The supplied finance framing needs a bounded decision brief rather than an external accounting action.
Bad example:
- Prompt: What is the USD/KRW exchange rate right now?
- Expected behavior: Route to
live-info-operator, not finance-analysis.
- Why: A live exchange rate needs observed provider data rather than a finance analysis brief.
Completion Checklist
- Confirm the workflow target, evidence boundary, and stop condition are named.
- Report which outputs are prepared, observed, blocked, or missing.
- Name the smallest next verification or handoff instead of claiming completion from narration.
Recovery Notes
- If required context is missing, ask one blocking question or route back to the narrower workflow.
- If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
Workflow Lane
- Current lane: Research and company ops (
product-docs, source-finder, web-research, research, best-practice-research, autoresearch-goal, model-optimization, inference-serving, +19 more) - research, signals, ops, and briefings.
- If intent belongs to another lane, hand back to
oh-my-hermes or name the adjacent workflow.
- Shared product, routing, compatibility, and evidence rules:
omh-routing/references/skill-common-rail.md.
Use When
Use when supplied ledger, budget, forecast, revenue, expense, cash-flow, or close context needs a bounded analysis and decision brief.
Strong routing signals: `finance analysis`, `budget variance`, `budget vs actual`, `month-end close`, `재무 분석`, `예산 대비 실적`, `월마감`
Catalog Metadata
Category: operations
Phase: finance-analysis
Hermes role: operator
Quality tier: evidence-gated
Reasoning demand: light
Quality bar:
- Separate supplied numbers, assumptions, and missing finance evidence.
- Keep decision and escalation questions explicit.
Handoff policy:
Keep domain framing, clarification, source/evidence synthesis, draft outputs, and next-work routing in Hermes. A prepared brief, review, reply, or plan is not an external action, approval, filing, send, publish, data mutation, implementation, review, CI, or merge claim. Prepare a connector, file, coding, or human-review handoff only when the user explicitly accepts that next step; report it only from observed evidence. Calculations are only as authoritative as supplied or observed sources and methods; no ERP, bank, ledger, tax, payment, or filing action is implied.
Required inputs:
- period
- supplied finance source
- decision question
- calculation assumptions
Expert clarification questions:
period
- English: What period, cutoff, reporting entity/perimeter, currency/units, accounting basis, comparator version, and close status apply?
- Korean: 어떤 기간, 마감 기준일, 보고 법인과 범위, 통화와 단위, 회계 기준, 비교 버전, 마감 상태를 적용해야 하나요?
Expected outputs:
- finance_scope_source_record/v1
- finance_reconciliation_analysis_schedule/v1
- finance_risk_register/v1
- finance_decision_brief/v1
Artifact expectations:
- prepared finance analysis brief when a wrapper captures it
Safety rules:
- State source and calculation assumptions before presenting a variance.
- Do not imply an ERP, bank, ledger, tax, payment, or filing action occurred.
Procedure: load references/procedure.md.
Runtime Evidence
Preferred harness for this skill: ops-review.
omh runtime record --skill finance-analysis --harness ops-review --status started
Record observed delegation results; otherwise return not_available or not_observed.
Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes.
Preserve workflow intent and stop conditions; verify before claiming completion.
Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
Shared product, compatibility, topology, memory, harness, and execution rules: omh-routing/references/skill-common-rail.md. Load it when applicable; otherwise name an unavailable capability.
1---
2name: "omh-finance-analysis"
3description: "[omh] Turn finance and accounting inputs into a decision-ready variance, cash, and close-risk brief. Use when the user says: finance analysis, budget variance, budget vs actual, month-end close, 재무 분석, 예산 대비 실적, 월마감."
4metadata:
5 hermes:
6 tags: [workflow, oh-my-hermes, operations]
7 category: operations
8 phase: finance-analysis
9 role: operator
10 quality_tier: evidence-gated
11---
12
13# Finance Analysis
14
15This is a Hermes-native `finance-analysis` workflow skill.
16
17## Why This Exists
18
19`finance-analysis` prepares a source-bounded decision brief without claiming an authoritative financial action.
20
21## Do Not Use When
22
23- The request is for a current quote, exchange rate, crypto price, or other live market lookup; use `live-info-operator`.
24- The user wants generic exploration of a supplied CSV or table without accounting periods, controls, or finance decision framing; use `data-analysis`.
25- The user asks to post journal entries, reconcile accounts, approve payments, submit tax filings, or configure an accounting system; use `connector-operator` for an explicit observed action path.
26- The user wants pipeline coverage, deal health, or a seller forecast scenario rather than authoritative revenue or close reporting; use `sales-pipeline-review`.
27- The user needs an enterprise or product direction decision after analysis; route that decision to `strategy-brief`.
28
29## Examples
30
31Good example:
32
33- Prompt: Compare Q2 actuals against budget, explain the biggest expense variances, and flag cash risks for the CFO.
34- Expected behavior: Prepare the period boundary, actual-versus-plan narrative, cash-risk register, and decision questions.
35- Why: The supplied finance framing needs a bounded decision brief rather than an external accounting action.
36
37Bad example:
38
39- Prompt: What is the USD/KRW exchange rate right now?
40- Expected behavior: Route to `live-info-operator`, not `finance-analysis`.
41- Why: A live exchange rate needs observed provider data rather than a finance analysis brief.
42
43## Completion Checklist
44
45- Confirm the workflow target, evidence boundary, and stop condition are named.
46- Report which outputs are prepared, observed, blocked, or missing.
47- Name the smallest next verification or handoff instead of claiming completion from narration.
48
49## Recovery Notes
50
51- If required context is missing, ask one blocking question or route back to the narrower workflow.
52- If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
53
54## Workflow Lane
55
56- Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `best-practice-research`, `autoresearch-goal`, `model-optimization`, `inference-serving`, `+19 more`) - research, signals, ops, and briefings.
57- If intent belongs to another lane, hand back to `oh-my-hermes` or name the adjacent workflow.
58- Shared product, routing, compatibility, and evidence rules: `omh-routing/references/skill-common-rail.md`.
59
60## Use When
61
62Use when supplied ledger, budget, forecast, revenue, expense, cash-flow, or close context needs a bounded analysis and decision brief.
63
64 Strong routing signals: `finance analysis`, `budget variance`, `budget vs actual`, `month-end close`, `재무 분석`, `예산 대비 실적`, `월마감`
65
66## Catalog Metadata
67
68Category: `operations`
69Phase: `finance-analysis`
70Hermes role: `operator`
71Quality tier: `evidence-gated`
72Reasoning demand: `light`
73
74Quality bar:
75
76- Separate supplied numbers, assumptions, and missing finance evidence.
77- Keep decision and escalation questions explicit.
78
79Handoff policy:
80
81Keep domain framing, clarification, source/evidence synthesis, draft outputs, and next-work routing in Hermes. A prepared brief, review, reply, or plan is not an external action, approval, filing, send, publish, data mutation, implementation, review, CI, or merge claim. Prepare a connector, file, coding, or human-review handoff only when the user explicitly accepts that next step; report it only from observed evidence. Calculations are only as authoritative as supplied or observed sources and methods; no ERP, bank, ledger, tax, payment, or filing action is implied.
82
83Required inputs:
84
85- period
86- supplied finance source
87- decision question
88- calculation assumptions
89
90Expert clarification questions:
91- `period`
92 - English: What period, cutoff, reporting entity/perimeter, currency/units, accounting basis, comparator version, and close status apply?
93 - Korean: 어떤 기간, 마감 기준일, 보고 법인과 범위, 통화와 단위, 회계 기준, 비교 버전, 마감 상태를 적용해야 하나요?
94
95Expected outputs:
96
97- finance_scope_source_record/v1
98- finance_reconciliation_analysis_schedule/v1
99- finance_risk_register/v1
100- finance_decision_brief/v1
101
102Artifact expectations:
103
104- prepared finance analysis brief when a wrapper captures it
105
106Safety rules:
107
108- State source and calculation assumptions before presenting a variance.
109- Do not imply an ERP, bank, ledger, tax, payment, or filing action occurred.
110
111Procedure: load `references/procedure.md`.
112
113## Runtime Evidence
114
115Preferred harness for this skill: `ops-review`.
116
117```sh
118omh runtime record --skill finance-analysis --harness ops-review --status started
119```
120
121Record observed delegation results; otherwise return `not_available` or `not_observed`.
122Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
123- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes.
124Preserve workflow intent and stop conditions; verify before claiming completion.
125
126Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
127
128Shared product, compatibility, topology, memory, harness, and execution rules: `omh-routing/references/skill-common-rail.md`. Load it when applicable; otherwise name an unavailable capability.
rlaope