Skill instructions
company-snapshot1.56 KB
View saved version →
---
name: company-snapshot
description: Build a financial snapshot of one Japanese listed company from its EDINET filings using Kabuken tools.
disable-model-invocation: true
---
# Company snapshot
Input: one company name, ticker, or EDINET entity code, given by the user
(in Claude Code, the command argument).
1. Resolve the company to an EDINET entity code (for example `E02144`):
- name: call `search_companies` with `query`; matches are in
`companies`. If several companies match, ask the user to pick one before continuing;
- ticker: call `get_company` with `id` and `id_type: "ticker"`;
- entity code: call `get_company` with `id` (`id_type` defaults to
`entity_code`).
2. Call `get_company_financials` with `entity_code` (optional
`period_type`: `ANNUAL` default, `INTERIM` or `ALL`; optional `periods`,
default 3). If a tool says a feature is not available for this account,
tell the user that plainly and continue with the tools that work. Do
not suggest plans, prices or links. Do not guess figures.
3. Call `get_risk_context` with `entity_code` for BOJ rate-sensitivity and
METI export-control notes.
4. Present a short snapshot: company name, industry, and for the
latest period revenue, operating income, net income, total assets and
equity, plus any risk-context notes. State the period and source filing
for every figure.
5. If the user asks about risks, outlook or the business, follow the
`filing-text` skill (`get_filing_text`) and quote the filed text.
6. Do not add a stock price, market cap or P/E. Kabuken has no price data.
filing-text2.09 KB
View saved version →
---
name: filing-text
description: Read the narrative sections of a Japanese company's annual securities report as filed, using get_filing_text. Use when the user asks for risk factors, 事業等のリスク, MD&A, management discussion, outlook narrative, or the original or as-filed text.
---
# Filing text
Input: one company name, ticker, EDINET entity code, or a filing `doc_id`,
given by the user.
1. Identify the filing:
- `doc_id` given: use it;
- otherwise resolve the company to an entity code with `search_companies`
(`query`) or `get_company` (`id`, `id_type: "ticker"`). If several
companies match, ask the user to pick one.
2. Call `get_filing_text` with `doc_id` or `entity_code` (the entity code
reads the newest annual report that has XBRL data). Set `sections`:
`business_risks` for 事業等のリスク (default) or `md_and_a` for management discussion and
outlook. Optional `max_chars` limits the size of each page.
3. Each item in `sections` has `section`, `source_element`, `label_ja`,
`label_en` and `text`. The text is the filer's own Japanese wording,
verbatim, with no AI summary from Kabuken. State the company, the filing
and the period for what you show.
4. Present the text as filed, in Japanese. If `next_cursor` is set and the
user wants more, call again with `cursor` set to `next_cursor` and the
same `doc_id` or `entity_code` and `sections`. Name every entry in
`missing_sections`.
5. Translate or summarise only if the user asks. Say that the translation
or summary is your own work, not part of the filing, and quote the
original Japanese for each key sentence.
6. If the tool returns `not_found`, say that no narrative text is stored for
that filing. Do not guess or fill in from memory.
7. Keep the attribution notice from the response (EDINET / FSA, PDL1.0, and
the note that the text is the filer's).
8. Kabuken has no stock prices and gives no investment advice. If a tool
says a feature is not available for this account, tell the user that
plainly and continue with the tools that work. Do not suggest plans,
prices or links.
get-started1.55 KB
View saved version →
---
name: get-started
description: Look up a Japanese listed company in Kabuken and get figures from its official EDINET filings. Use when the user first asks about a Japanese company's financials, filings or segments.
---
# Get started with Kabuken
1. Call `search_companies` with `query` set to the company name (English or
Japanese). Matches are in `companies`. Note the company's EDINET entity
code (`company_entity_code`, for example `E02144` for Toyota). If
several companies match, ask the user to pick one.
2. Call `get_company_financials` with `entity_code` for revenue, profit,
assets, equity and cash flow from recent annual reports.
3. For other questions, use the entity code with:
- `list_documents` (`entity_code`) to find a filing and its `doc_id`
in `documents`;
- `get_segment_breakdown` (`doc_id`) for figures by segment or region;
- `compare_companies` (`entity_codes`, 2 to 5 codes) for peers;
- `get_filing_text` (`entity_code` or `doc_id`) to read the risk factors
(`business_risks`) or management discussion (`md_and_a`) of an annual
report as filed (see the `filing-text` skill). It returns the filer's
own Japanese text, not a summary.
4. State the period and the source filing for every figure.
5. Kabuken has no stock prices and gives no investment advice. Do not add
a price, market cap or valuation ratio.
6. If a tool says a feature is not available for this account, tell the
user that plainly and continue with the tools that work. Do not suggest
plans, prices or links. Do not estimate the figure.
peer-comparison1.69 KB
View saved version →
---
name: peer-comparison
description: Compare 2-5 Japanese listed companies side by side from their latest annual reports using Kabuken tools.
disable-model-invocation: true
---
# Peer comparison
Input: 2 to 5 company names, tickers, or EDINET entity codes, separated by
commas, given by the user (in Claude Code, the command argument).
1. Split the input into individual companies. If there are fewer than 2 or
more than 5, ask the user to adjust before continuing.
2. Resolve each company to an EDINET entity code (for example `E02144`):
`search_companies` with `query` for a name, or `get_company` with `id`
and `id_type: "ticker"` for a ticker. Ask the user if a name is
ambiguous.
3. Call `compare_companies` with `entity_codes` set to the list of entity
codes (not names or tickers). It returns revenue, net income, total
assets, equity, operating income and the period-end date from each
company's latest annual securities report (有価証券報告書).
4. If a tool says a feature is not available for this account, tell the
user that plainly and continue with the tools that work. Do not suggest
plans, prices or links. Do not approximate the comparison from other
tools.
5. Present a table, one row per metric and one column per company. Show the
period-end date for each company, because fiscal year-ends can differ.
If a metric is null, show its `omission_reason` instead of a number.
6. If the user asks how the risks differ, follow the `filing-text` skill
(`get_filing_text`, `business_risks`) for each company and quote the
filed passages side by side.
7. Do not rank companies by a price-based metric (P/E, market cap, dividend
yield). Kabuken has no price data.
segment-breakdown1.54 KB
View saved version →
---
name: segment-breakdown
description: Show the business-segment or geographic breakdown from a Japanese listed company's EDINET filing using Kabuken tools.
disable-model-invocation: true
---
# Segment breakdown
Input: a company name, ticker, or EDINET entity code, optionally followed
by a fiscal period, given by the user (in Claude Code, the command
argument).
1. Resolve the company to an EDINET entity code (for example `E02144`):
`search_companies` with `query` for a name, or `get_company` with `id`
and `id_type: "ticker"` for a ticker. If a name is ambiguous, ask the
user to pick one.
2. Call `list_documents` with `entity_code` to list the filings. The
filings are in `documents`; if `truncated` is true, call again with a
higher `limit` (up to 100). If the user named a period, pick the
matching filing. Otherwise use the most recent annual securities
report (有価証券報告書). Note its `doc_id`.
3. Call `get_segment_breakdown` with that `doc_id` (optional `fact_name`
to filter to one axis, optional `limit`, default 100). If a tool
says a feature is not available for this account, tell the user that
plainly and continue with the tools that work. Do not suggest plans,
prices or links.
4. Present the breakdown grouped by axis (business segment, geographic
segment, or consolidation scope), with member labels and the
reported figures. State the source filing and period for every number.
Segment labels come from the EDINET Taxonomy, which has its own
copyright notice; keep the notice the tool returns.