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