菜单
Map a company's related parties — shareholders, outbound investments, brother companies, supply-chain counterparties (suppliers/customers), and funding-chain links — into a structured relationship map. Triggers on "关联方", "股权穿透", "关联企业", "supply chain map", "上下游客户供应商", "实控人", "股权结构".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/zai-org/zcode-plugins --skill related-party-map命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
A mapping between two charts of accounts — multi-book consolidation, a system migration, or a presentation change — with balance conservation proved rather than assumed, one-to-many and many-to-one relations surfaced for confirmation instead of resolved silently, and every 口径 change named. Triggers on "科目映射", "科目对照", "两个账套怎么合", "新旧科目转换", "科目表迁移", "重分类", "报表口径调整", "合并口径", "chart of accounts mapping", "account reclassification".
Audit a spreadsheet for formula accuracy, errors, and common mistakes. Scopes to a selected range, a single sheet, or the entire model (including financial-model integrity checks like BS balance, cash tie-out, and logic sanity). Triggers on "audit this sheet", "check my formulas", "find formula errors", "QA this spreadsheet", "sanity check this", "debug model", "model check", "model won't balance", "something's off in my model", "model review".
Statutory-basis financial statements and note working papers built from a trial balance — accounts mapped to the caption format the stated basis prescribes, the three statements with every tie shown as a live formula, note schedules traceable to the accounts behind them, and every accounting judgement registered for the finance lead rather than decided. Delivered as a draft pending review, unaudited. Triggers on "编制财务报表", "出一版财务报表", "法定报表", "准则报表", "资产负债表利润表现金流量表", "合并报表编制", "年报报表", "报表底稿", "附注底稿", "financial statements", "statement preparation".
正在显示 SKILL.md
| name | related-party-map |
| description | Map a company's related parties — shareholders, outbound investments, brother companies, supply-chain counterparties (suppliers/customers), and funding-chain links — into a structured relationship map. Triggers on "关联方", "股权穿透", "关联企业", "supply chain map", "上下游客户供应商", "实控人", "股权结构". |
Build the relationship graph around a target company, one hop at a time, with every edge sourced.
Exact legal entity first (see entity-resolution discipline in dd-report). All queries use the resolved full legal name / ID.
Primary tool: 天眼查 (capability-list tools via the gateway protocol). Pull each dimension separately and label it.
The tool names below are illustrative, not guaranteed. The capability list is returned per company and varies — a sample on one large listed entity (2026-08-07) offered only get_shareholder_info, get_external_investments, get_company_registration_info, get_judicial_case, get_annual_reports, get_branches, get_change_records, get_historical_registration. So: anchor with search_companies and take the candidate's id — get_company_capabilities requires company_id and will not resolve a bare name (verified 2026-08-17: passing keyword/company_name alone returns company_id is required for get_company_capabilities; call search_companies first). Then run get_company_capabilities with that id, copy tool_name verbatim from what it returns, and where a dimension below has no tool on this company's list, record that dimension as 源不可用 naming what it would have covered. Never call a name from this page that the capability list did not offer. Every dimension here is exploratory tracing, so keep each call single-step (call_tool, never call_tools_batch) and pull a fresh get_company_capabilities for each new subject the map uncovers.
get_shareholder_info); iterate up to the actual controller (实控人 — get_actual_controller returns the resolved terminal, get_equity_ratio the control path, get_beneficial_owners the UBO under 央行 rules) or a natural person/SOE terminal. Note pledge status on major holdings (get_equity_pledge_info / get_stock_pledge_info).get_external_investments; get_equity_tree for the layered structure, get_controlled_companies for the down-pierced list) with percentages; flag 100% shells and recently created vehicles.get_group_info identifies the group and its groupUUID; get_company_group_profile then returns members, group-level outbound investments and investors. get_relation_graph / get_relation_path expose the edges between two named subjects.🔴 高 finding — resolve before deciding).For listed targets, cross-check controller and major-holder data against announcements (万得 wind-docs.get_company_announcements: 权益变动、质押公告).
Short-form is Markdown in-session, per the house formatting policy. If the user asked for a document, the map goes to PDF via the report-render skill — never hand-rolled with weasyprint, wkhtmltopdf, pandoc, or a bare reportlab script, because those do not emit [n] as PDF link annotations and the citations arrive unclickable. A wide relationship roster goes to .xlsx via xlsx-author. Word is the answer only when the user asks for it or the reader will edit the file — report-render's DocxReport builds it with the same calls; unspecified long-form stays PDF (the house formatting policy). 要出 Word 就先载入 report-render 技能，再动手建。 DocxReport 与 Report 同一套调用；手搓 python-docx / docx-js 会丢掉标签配色、[n] 跳转与封面页，机制与实测记录在那个技能里，不在这里重述。
Output as a table per layer plus a compact tree for ownership:
实控人: [名称] [披露] [n]
└─ [中间层] xx%
└─ 目标公司
├─ 子公司A xx%
└─ 子公司B xx%
关联维度表:
| 关系 | 对手方 | 强度/份额 | 报告期/数据时点 | 检索于 | 源 [n] |
Every retrieved edge is [披露]. A share you summed or netted across layers (穿透持股比例) is [测算] and states the arithmetic. Percentages that cannot be retrieved stay blank with a note — never estimated.
Call out (as hypotheses, labeled [推断], each with the concrete evidence that triggered it):
Every edge carries an [n] marker naming the source system and the query date. The map closes with the coverage block — the dimensions are the check items, and the hop depth actually traversed is part of the scope:
## 覆盖范围与局限
检索于: [timestamp] · 口径/委托用途: [用途] · 股权向上穿透至第 [N] 层
| 检查项 | 结论 | 源 | 检索于 |
|---|---|---|---|
| 股权链—向上(至实控人) | 有记录(N 层) [n] / 检索范围内未发现 / 源不可用 | [系统名] | [date] |
| 股权链—向下(对外投资) | | | |
| 兄弟公司 | | | |
| 供应链(供应商/客户) | | | |
| 资金链 | | | |
| 股权质押 | | | |
本次未能覆盖: [源未覆盖或未返回的维度,以及它们本应揭示的关系]
数据滞后性: [登记变更公示滞后;供应链数据时点与更新频率]
## 来源
[n] 〔一手|二手〕发布主体 · 文档或系统名 · 日期(发布日; 检索于) · URL
A dimension the source does not cover for this entity type is 源不可用, not 检索范围内未发现 — and neither means "no such relationships exist". 〔一手|二手〕 is mandatory on every entry; a 二手 entry names what it relays. The count of distinct [n] markers equals the number of entries.