Skip to main content

b2b-document

外贸文档分析 — 读取报价单/合同/PI/装箱单等贸易单据,提取报价、条款、规格等关键数据

跳到安装

来源信息

仓库
chefroger/smart-trade-ai
最近来源活动
2026年8月11日 06:52
检测到的 SKILL.md 语言
中文
星标
77
分支
10

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

文件资源管理器
9 个文件

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
b2b-document
description
外贸文档分析 — 读取报价单/合同/PI/装箱单等贸易单据,提取报价、条款、规格等关键数据
when_to_use
["用户提供了外贸单据(报价单 / 合同 / PI / 装箱单 / 产品规格书)要求提取关键信息","需要对比多份报价单的价格差异","从合同或 PI 中提取付款条件、交期、贸易术语","让 Hermes 内置 read_file 读文件即可,不需要本技能","不要用于:生成新文档(用 b2b-doc-generation);普通 PDF/Word 阅读(用 Hermes 内置 office skills)"]
triggers
["读报价单","对比报价","提取合同条款","分析PI","看装箱单","产品规格书","贸易单据","报价分析","invoice analysis","quotation comparison"]
category
文档管理
version
1.0.0
author
Foreign Trade Assistant
---|------|-------------|-----|------|---------|------| | [确切] | [确切] | $3.50/pc [确切] | 1000 pcs [确切] | 30天 [确切] | T/T 30/70 [确切] | 📄 报价单.xlsx R12 | 每个单元格后标注置信度标签 ## ⚠️ 数据冲突与异常 [如有] 列出所有发现的冲突/不一致/异常 ## 已查找但未找到的信息 [必须] 列出你在文件中查找了但没有找到的信息 ## 建议 [如有] 基于数据的业务建议,不要脱离数据做推测 ``` ## 置信度标签(每个关键数字后必标) | 标签 | 含义 | 示例 | |------|------|------| | [确切] | 直接从文档中读到的精确值 | "$3.50/pc [确切]" | | [计算] | 基于文档数值计算得出 | "$3,500.00 [计算:$3.50 × 1000]" | | [推断] | 合理推断,非直接读取 | "约30天 [推断:基于历史交期]" | | [不确定] | 文档模糊,用户应核实 | "TBD [不确定:单据此处空白]" | ## 引用格式 - Excel: 📄 {文件名} | Sheet: {sheet名} | Row: {行号} | Col: {列号} - PDF: 📄 {文件名} | Page: {页码} | Section: {段落标题} - Word: 📄 {文件名} | Section: {标题} | Paragraph: {段落号} --- Examples: - `📄 2024年度报价单.xlsx | Sheet: Sheet1 | Row: 12-15 | Column: C-E` - `📄 客户资料.xlsx | Sheet: 联系方式 | Row: 3` - `📄 产品规格书.pdf | Page: 4 | Section: 技术参数` For PDF files, cite page numbers. For Word documents, cite section headings. ## Domain Terminology — Universal B2B Trade ### How to Handle Industry Terms 1. **Read the documents first** — product names, model numbers, and technical parameters are defined in the spec sheets and quotes. Let the documents teach you the domain. 2. **Map Chinese ↔ English** on the fly — many B2B documents mix languages. Translate freely; the LLM's multilingual ability handles this. 3. **Respect the document's own terminology** — if the document calls something a "Model A-200", use that exact term. Don't guess synonyms. 4. **Group by SKU / model number** — product codes (e.g. `A-200`, `TYPE-B`, `Φ25×3`) are the universal key for cross-referencing across files. ### Common Cross-Industry Parameters When extracting specifications, these parameter types appear across most industries: | Parameter Category | Examples | Common Units | |---|---|---| | Dimensions | Length, width, height, diameter, thickness | mm, cm, m, inch | | Weight | Net weight, gross weight | kg, g, lb, ton | | Material | Composition, grade, finish | (varies by industry) | | Capacity / Rating | Power, flow rate, load, pressure | W, kW, L/min, kN, MPa, bar | | Quantity | MOQ, pack size, container load | pcs, sets, cartons, pallets | | Color / Finish | Color code, surface treatment | (varies by industry) | | Certification | ISO, CE, RoHS, FDA, etc. | — | ### Cross-Industry Commercial Terms (通用商务术语) | 中文 | English | 缩写 | |------|---------|------| | 报价单 | Quotation / Price List | — | | 形式发票 | Proforma Invoice | PI | | 商业发票 | Commercial Invoice | CI | | 装箱单 | Packing List | PL | | 提单 | Bill of Lading | B/L | | 成交记录 | Transaction Record | — | | 合同 / 订单 | Contract / Purchase Order | PO | | 交货期 | Delivery Time / Lead Time | — | | 付款条件 | Payment Terms | T/T, L/C, D/P, D/A | | 贸易术语 | Incoterms | FOB, CIF, EXW, DDP | | 最小订单量 | Minimum Order Quantity | MOQ | | 样品 | Sample | — | | 大货 | Bulk Order / Mass Production | — | | 尾款 | Balance Payment | — | | 订金 | Deposit | — | | 唛头 | Shipping Mark | — | ### Currencies Recognize and distinguish between: - `¥` / `CNY` / `RMB` — 人民币 - `$` / `USD` — 美元 - `€` / `EUR` — 欧元 - `£` / `GBP` — 英镑 - `¥` / `JPY` — 日元 - `₩` / `KRW` — 韩元 ### Unit Conversions - 1 英寸 (inch) = 25.4 mm - 1 英尺 (foot) = 304.8 mm - 1 磅 (lb) ≈ 0.4536 kg - 1 美吨 (short ton) ≈ 907.2 kg - 1 公吨 (metric ton) = 1000 kg - 1 加仑 (US gallon) ≈ 3.785 L - 1 MPa = 1 N/mm² = 145 psi - 1 bar = 100 kPa - °F = °C × 9/5 + 32 ## Excel Table Extraction Guide When reading Excel files, follow these rules: 1. **Multi-level headers**: If row 1 and 2 are merged/category headers, treat them as composite column names. 2. **Merged cells**: If a cell appears empty, check if it's part of a merged range — look at adjacent cells for context. 3. **Numeric precision**: Always preserve the **exact** number of decimal places as shown in the original. Do not round. 4. **Units**: Note the unit in the column header or nearby cells. Distinguish between `mm` / `cm` / `m` / `inch`. 5. **Currency**: Note the currency marker. Distinguish between `¥`, `$`, `€`, `£`. 6. **Empty rows**: Skip empty rows between data sections. Pay attention to **subtotal** and **total** rows. 7. **Multi-sheet workbooks**: Treat each sheet independently. Sheet name often indicates product category or customer. ## Cross-Reference Patterns When analyzing B2B documents, look for these cross-file relationships (applicable to any industry): - **Quote → Spec**: A quote lists a product code at a certain price; the spec sheet defines that code's full specifications. Always cross-check. - **Quote → Customer**: A quote filename or header references a customer code; the customer file maps that code to company name, contact, address. - **Transaction → Quote**: A transaction record references a quote number; cross-check the price and quantity match. - **Multiple Quotes**: Same product from different vendors → compare prices. - **Spec → Inventory**: A spec sheet defines what a product is; the inventory list tells you how many are in stock. ## Knowledge Graph Memory (Cognee) — B2B Usage Cognee stores extracted facts as entities and relationships in a knowledge graph. Use `cognee_remember` to persist key findings after each significant analysis step: ### What to Store - **Product facts extracted from docs**: model numbers, specs, prices, MOQs, lead times - **Customer requirements mentioned by user**: target markets, certification needs, budget ranges - **Cross-file linkages discovered**: which spec file defines the product in which quote - **User decisions and preferences**: preferred output language, format style, naming conventions ### When to Store - After reading a product spec sheet → store key parameters - After the user mentions a customer name or requirement → store it - After cross-referencing multiple files → store the discovered relationships - After generating a document → store what was generated and for whom ### Recall Before Analysis Use `cognee_recall` at the start of a new task to check for relevant past context. This connects new questions to previous findings without the user needing to repeat context. ## Document Generation When the user asks you to create a business document (PPTX, DOCX, XLSX, or report), follow these rules: ### Language Consistency (Critical) - **One document, one language.** If the target audience is English-speaking (Middle East, Europe, Americas, Southeast Asia), the ENTIRE document must be in English — titles, body, tables, footnotes, everything. If the audience is Chinese-speaking, use Chinese throughout. Never produce mixed-language output. - Product model numbers and SKU codes stay in their original form regardless of language. ### Presentation (PPTX) Quality 1. Plan the slide structure before writing code. 10-12 slides for a product catalog, 6-8 for a company intro. 2. Choose a color palette with 2-3 colors that fit the industry (not generic blue). 3. Every slide needs visual elements: colored accent bars, card backgrounds, tables, or icons. Never plain white slide + text only. 4. Typography: titles 36-44pt bold, section headers 18-24pt, body 12-16pt. Consistent font family throughout. 5. Tables: bold headers with dark background, alternating row fills, all columns populated with real data. 6. Vary slide layouts. Don't repeat the same layout across slides. 7. Left-align body text; center only cover text and section titles. 8. After generating, read back the file to verify content is complete and formatting is correct. ### Document (DOCX) Quality 1. Use consistent heading styles (Heading 1, 2, 3) for hierarchy. 2. Tables should have borders, bold headers, and consistent column widths. 3. Include a header/footer with company name and page numbers. 4. Use the same language policy as PPTX — no mixed-language output. ### Spreadsheet (XLSX) Quality 1. Freeze the header row. Apply auto-filter to columns where applicable. 2. Format numbers consistently: currency with symbol, percentages with % sign, dates in ISO format. 3. Use cell borders and alternating row colors for readability. 4. Include a summary sheet if the workbook has multiple data sheets. ### General Output Rules - **No placeholder text**: Never output "XXX", "Lorem ipsum", "[TBD]", or fake phone numbers. If a value is truly unknown, omit that field. - **Verify after generating**: Read back the output file to check for truncation, missing data, or layout issues. - **Cite sources**: When data comes from specific files, note the source filename. ## Privacy & Confidentiality B2B documents often contain sensitive information: - Client names and contact details - Pricing and margin information - Supplier identities When analyzing, **always** follow the active privacy mode. Do not expose raw file contents to external services unless explicitly permitted. Prefer local analysis with read_file over uploading to cloud parsers.
在 GitHub 查看