financial-narrative-brief
Guides financial-analyst through converting raw k-dart DART data into an article-ready narrative brief. Explicitly distinct from co-consult's financial-statement-analysis (which builds a 5-level ROIC/valuation driver tree) — this skill is narrative-oriented, not valuation-oriented, and produces structured data for a reporter, not a full financial model. Use when: Phase 1, immediately after an assignment names a target company.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-14
- Stars
- ★ 25
- Forks
- 9
01 前言 Front Matter
- name
- financial-narrative-brief
- owner
- financial-analyst
- scope
- co-news
- status
- active
- version
- 1.0.1
- relates_to
- [ { "type": "follows", "skill": "source-verification-ledger" } ]
- description
- Guides financial-analyst through converting raw k-dart DART data into an article-ready narrative brief. Explicitly distinct from co-consult's financial-statement-analysis (which builds a 5-level ROIC/valuation driver tree) — this skill is narrative-oriented, not valuation-oriented, and produces structured data for a reporter, not a full financial model. Use when: Phase 1, immediately after an assignment names a target company.
- last_reviewed
- 1787702400000
- prerequisites
- k-dart
03 SKILL.md 正文
Context
This skill converts raw k-dart DART data into an article-ready narrative brief. It is explicitly distinct from co-consult's financial-statement-analysis skill, which builds a 5-level ROIC/valuation driver tree for financial modeling purposes. This skill is narrative-oriented rather than valuation-oriented: it produces structured data handed off to a reporter, not a full financial model.
When to Use
- Phase 1, immediately after an assignment names a target company
Execution Steps
-
Pull DART Data: Pull the company overview plus relevant financial statements/disclosures via the
k-dartskill — specify CFS preferred, OFS fallback, matching k-dart's own convention. -
Identify the "So What": Identify the 2-3 numbers/events a business reader actually needs — an earnings surprise, a capital-structure change, an auditor-opinion change, a change in largest shareholder, etc.
-
Produce Structured Entries: For each item, produce: headline number, YoY/QoQ delta, one-sentence context, and disclosure citation (receipt number).
-
Flag Anomalies for Legal Review: Flag anomalies — auditor opinion changes, related-party transactions, CB/EB issuance, unusual related-party loans — for legal-researcher review.
-
Hand Off as Structured Data: Hand off to the reporter as a short table or bullet list, NOT prose — the reporter, not this skill, writes the narrative sentences.
Output Format
- Wire header comment per
docs/wire-format.md— slug, register, language, desk, receipt count ([NEWS-R2]) ## Headline Numberstable: metric | value | YoY/QoQ | receipt number## Context Notes: 1-2 sentences per number## Flags for Legal Review: bullet list, may be empty
Related Skills
- k-dart
- source-verification-ledger
- financial-infographic-svg
04 同仓库更多 Skills
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.