tear-sheet

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Financial Tear Sheet Generator

财务摘要文档生成器

Generate audience-specific company tear sheets by pulling live data from S&P Capital IQ via the S&P Global MCP tools and formatting the result as a professional Word document.
通过S&P Global MCP工具从S&P Capital IQ获取实时数据,生成针对特定受众的公司财务摘要文档,并将结果格式化为专业的Word文档。

Style Configuration

样式配置

These are sensible defaults. To customize for your firm's brand, modify this section — common changes include swapping the color palette, changing the font (Calibri is standard at many banks), and updating the disclaimer text.
Colors:
  • Primary (header banner background, section header text): #1F3864
  • Accent (signature section highlights): #2E75B6
  • Table header row fill: #D6E4F0
  • Table alternating row fill: #F2F2F2
  • Table borders: #CCCCCC
  • Header banner text: #FFFFFF
Typography (sizes in half-points for docx-js):
  • Font family: Arial
  • Company name: 18pt bold (size: 36)
  • Section headers: 11pt bold (size: 22), Primary color
  • Body text: 9pt (size: 18)
  • Table text: 8.5pt (size: 17)
  • Footer/disclaimer: 7pt italic (size: 14)
  • Per-template overrides are specified in each reference file's Formatting Notes.
Company Header Banner:
  • The header is a navy (#1F3864) banner spanning the full page width with company name in white.
  • Below the banner, key-value pairs MUST be rendered in a two-column borderless table spanning the full page width. Left column: company identifiers (ticker, HQ, founded, employees, sector). Right column: financial identifiers (market cap, EV, stock price, shares outstanding). Each cell contains a bold label and regular-weight value on the same line (e.g., "Market Cap $124.7B"). Do not left-justify all fields in a single column — this wastes horizontal space and looks unprofessional. The two-column spread is the single most important visual signal that distinguishes a professional tear sheet from a default document.
    • Implementation: Create a 2-column table with
      borders: none
      and
      shading: none
      on all cells. Set column widths to 50% each. Place left-column fields (ticker, HQ, founded, employees) as separate paragraphs in the left cell. Place right-column fields (market cap, EV, stock price, shares outstanding) in the right cell. Each field is a single paragraph: bold run for the label, regular run for the value.
    • The specific fields in each column vary by audience — see the reference file's header spec. The principle is always: spread across the page, not clumped left.
  • Do not use a bordered table for the header key-value block. Bordered tables are reserved for financial data only.
  • Key metrics in the header (market cap, EV, stock price) should be displayed as inline key-value pairs, not in a separate bordered table.
Section Headers:
  • Each section header gets a horizontal rule (thin line, #CCCCCC, 0.5pt) directly beneath it to create clean visual separation between sections.
  • Render the rule as a bottom border on the header paragraph itself — do not insert a separate paragraph element for the rule. A separate paragraph adds its own before/after spacing and causes excessive whitespace below section titles.
  • Implementation: In docx-js, apply a bottom border to the section header paragraph via
    paragraph.borders.bottom = { style: BorderStyle.SINGLE, size: 1, color: "CCCCCC" }
    . Do not use
    doc.addParagraph()
    with a separate horizontal rule element. Do not use
    thematicBreak
    . The border must be on the heading paragraph itself with 0pt spacing after, so the rule sits tight against the header text.
  • Spacing: 12pt before the header paragraph, 0pt after the header paragraph, 4pt before the next content element.
Bullet Formatting:
  • Use a single bullet character (•) for all bulleted content across all tear sheet types. Do not mix •, -, ▸, or numbered lists within or across tear sheets.
  • Synthesis/analysis bullets (Earnings Highlights, Strategic Fit, Integration Considerations, Conversation Starters): indented block-style formatting with left indent 360 DXA (0.25") and a hanging indent for the bullet character. These should be visually offset from body text — they're interpretive content and should look distinct from data tables and prose paragraphs.
  • Informational bullets within relationship sections: standard body indent (180 DXA), no hanging indent.
  • Do not apply left-border accents to any bullet sections. Left-border styling renders inconsistently in docx-js and creates visual artifacts. Use indentation and text size differentiation to distinguish signature sections instead.
Tables (financial data only):
  • Header row: Table Header Fill (#D6E4F0) with bold dark text
  • Body rows: alternating white / Table Alternating Fill (#F2F2F2)
  • Borders: Table Border color (#CCCCCC), thin (BorderStyle.SINGLE, size 1)
  • Cell padding: top/bottom 40 DXA, left/right 80 DXA
  • Right-align all numeric columns
  • Always use ShadingType.CLEAR (never SOLID — SOLID causes black backgrounds)
Layout:
  • US Letter portrait, 0.75" margins (1080 DXA all sides)
Number formatting:
  • Currency: USD. Use millions unless company revenue > $50B (then billions, one decimal). Label units in column headers (e.g., "Revenue ($M)"), not in individual cells.
  • Table cells: plain numbers with commas, no dollar signs. Example: a revenue cell shows "4,916" not "$4,916". The column header carries the unit.
  • Fiscal years: actual years (FY2022, FY2023, FY2024), never relative labels (FY-2, FY-1).
  • Negatives: parentheses, e.g., (2.3%)
  • Percentages: one decimal place
  • Large numbers: commas as thousands separators
Footer (document footer, not inline): Place the source attribution and disclaimer in the actual document footer (repeated on every page), not as inline body text at the bottom. The footer is exactly two lines, centered, on every page:
  • Line 1: "Data: S&P Capital IQ via Kensho | Analysis: AI-generated | [Month Day, Year]"
  • Line 2: "For informational purposes only. Not investment advice."
  • Style: 7pt italic, centered, #666666 text color
  • This footer text must be identical across all tear sheet types for the same company. Do not vary the wording by audience.
  • This footer is required on every tear sheet, every audience type, every page. Do not omit it.
以下是合理的默认设置。如需根据贵公司品牌进行自定义,请修改此部分——常见的修改包括更换调色板、更改字体(Calibri是许多银行的标准字体)以及更新免责声明文本。
颜色:
  • 主色调(页眉横幅背景、章节标题文本):#1F3864
  • 强调色(重点章节高亮):#2E75B6
  • 表格表头行填充色:#D6E4F0
  • 表格交替行填充色:#F2F2F2
  • 表格边框色:#CCCCCC
  • 页眉横幅文本色:#FFFFFF
排版(docx-js使用半磅为单位):
  • 字体家族:Arial
  • 公司名称:18pt 加粗(size: 36)
  • 章节标题:11pt 加粗(size: 22),主色调
  • 正文文本:9pt(size: 18)
  • 表格文本:8.5pt(size: 17)
  • 页脚/免责声明:7pt 斜体(size: 14)
  • 每个模板的覆盖设置在各参考文件的“格式说明”中指定。
公司页眉横幅:
  • 页眉为深蓝色(#1F3864)横幅,横跨整页宽度,公司名称为白色。
  • 横幅下方,键值对必须以两列无边框表格呈现,横跨整页宽度。 左列:公司标识(股票代码、总部所在地、成立年份、员工数、行业)。右列:财务标识(市值、企业价值(EV)、股价、流通股数)。每个单元格包含加粗标签和常规字体的值,位于同一行(例如:"市值 $124.7B")。不要将所有字段左对齐在单一列中——这会浪费水平空间,看起来不够专业。两列分布是区分专业财务摘要文档与默认文档的最重要视觉标志。
    • 实现方式: 创建一个
      borders: none
      且所有单元格
      shading: none
      的两列表格。将列宽设置为各占50%。将左列字段(股票代码、总部、成立年份、员工数)作为独立段落放在左单元格中。将右列字段(市值、EV、股价、流通股数)放在右单元格中。每个字段为一个单独段落:标签为加粗文本,值为常规文本。
    • 每列中的具体字段因受众而异——请参阅参考文件的页眉规范。原则始终是:跨页面分布,而非左对齐堆叠。
  • 不要为页眉键值块使用带边框的表格。 带边框的表格仅用于财务数据。
  • 页眉中的关键指标(市值、EV、股价)应以内联键值对形式显示,而非单独的带边框表格。
章节标题:
  • 每个章节标题正下方添加一条水平分隔线(细线,#CCCCCC,0.5pt),以在章节之间创建清晰的视觉分隔。
  • 将分隔线作为标题段落本身的下边框呈现——不要为分隔线插入单独的段落元素。单独的段落会添加自身的前后间距,导致章节标题下方出现过多空白。
  • 实现方式: 在docx-js中,通过
    paragraph.borders.bottom = { style: BorderStyle.SINGLE, size: 1, color: "CCCCCC" }
    为章节标题段落添加下边框。不要使用
    doc.addParagraph()
    添加单独的水平分隔线元素,也不要使用
    thematicBreak
    。边框必须直接应用于标题段落,且段落后间距设为0pt,使分隔线紧贴标题文本。
  • 间距:标题段落前12pt,标题段落后0pt,下一个内容元素前4pt。
项目符号格式:
  • 所有类型财务摘要文档中的所有项目符号内容均使用单一项目符号字符(•)。不要在同一或不同财务摘要文档中混合使用•、-、▸或编号列表。
  • 分析/综合项目符号(收益亮点、战略契合度、整合考量、对话切入点):缩进块式格式,左缩进360 DXA(0.25"),项目符号字符悬挂缩进。这些内容应与正文文本在视觉上区分开——它们是解释性内容,应与数据表和散文段落看起来不同。
  • 关系章节中的信息性项目符号:标准正文缩进(180 DXA),无悬挂缩进。
  • 不要为任何项目符号章节添加左边框强调。 左边框样式在docx-js中呈现不一致,会产生视觉伪影。改用缩进和文本大小差异来区分重点章节。
表格(仅用于财务数据):
  • 表头行:表格表头填充色(#D6E4F0)搭配深色加粗文本
  • 正文行:交替白色/表格交替行填充色(#F2F2F2)
  • 边框:表格边框色(#CCCCCC),细线(BorderStyle.SINGLE,size 1)
  • 单元格内边距:上下40 DXA,左右80 DXA
  • 所有数值列右对齐
  • 始终使用ShadingType.CLEAR(绝不要使用SOLID——SOLID会导致黑色背景)
布局:
  • US Letter纵向,0.75"边距(所有边1080 DXA)
数字格式:
  • 货币:美元(USD)。除非公司收入超过500亿美元(此时使用十亿美元,保留一位小数),否则使用百万为单位。在列标题中标注单位(例如:"收入(百万美元)"),不要在单个单元格中标注。
  • 表格单元格:带逗号的纯数字,无美元符号。 示例:收入单元格显示"4,916"而非"$4,916"。列标题承载单位信息。
  • 财年:实际年份(FY2022、FY2023、FY2024),绝不要使用相对标签(FY-2、FY-1)。
  • 负数:使用括号,例如:(2.3%)
  • 百分比:保留一位小数
  • 大数:使用逗号作为千位分隔符
页脚(文档页脚,非内联): 将来源归因和免责声明放在实际文档页脚中(每页重复),不要作为内联正文文本放在底部。页脚为恰好两行,居中,显示在每页:
  • 第一行:"数据来源:S&P Capital IQ via Kensho | 分析:AI生成 | [月 日, 年]"
  • 第二行:"仅供参考,不构成投资建议。"
  • 样式:7pt 斜体,居中,文本颜色#666666
  • 同一公司的所有类型财务摘要文档的页脚文本必须完全相同。不要因受众不同而更改措辞。
  • 此页脚要求在每个财务摘要文档、每种受众类型、每页上都存在。 请勿省略。

Component Functions

组件函数

You MUST use these exact functions to create document elements. Do NOT write custom docx-js styling code. Copy these functions into your generated Node script and call them. The Style Configuration prose above remains as documentation; these functions are the enforcement mechanism.
javascript
const docx = require("docx");
const {
  Document, Paragraph, TextRun, Table, TableRow, TableCell,
  WidthType, AlignmentType, BorderStyle, ShadingType,
  Header, Footer, PageNumber, HeadingLevel, TableLayoutType,
  convertInchesToTwip
} = docx;

// ── Color constants ──
const COLORS = {
  PRIMARY: "1F3864",
  ACCENT: "2E75B6",
  TABLE_HEADER_FILL: "D6E4F0",
  TABLE_ALT_ROW: "F2F2F2",
  TABLE_BORDER: "CCCCCC",
  HEADER_TEXT: "FFFFFF",
  FOOTER_TEXT: "666666",
};

const FONT = "Arial";

// ── 1. createHeaderBanner ──
// Returns an array of docx elements: [banner paragraph, key-value table]
function createHeaderBanner(companyName, leftFields, rightFields) {
  // leftFields / rightFields: arrays of { label: string, value: string }
  const banner = new Paragraph({
    children: [
      new TextRun({
        text: companyName,
        bold: true,
        size: 36, // 18pt
        color: COLORS.HEADER_TEXT,
        font: FONT,
      }),
    ],
    shading: { type: ShadingType.CLEAR, color: "auto", fill: COLORS.PRIMARY },
    spacing: { after: 0 },
    alignment: AlignmentType.LEFT,
  });

  function buildCellParagraphs(fields) {
    return fields.map(
      (f) =>
        new Paragraph({
          children: [
            new TextRun({ text: f.label + "  ", bold: true, size: 18, font: FONT }),
            new TextRun({ text: f.value, size: 18, font: FONT }),
          ],
          spacing: { after: 40 },
        })
    );
  }

  const noBorder = { style: BorderStyle.NONE, size: 0, color: "FFFFFF" };
  const noBorders = { top: noBorder, bottom: noBorder, left: noBorder, right: noBorder };
  const noShading = { type: ShadingType.CLEAR, color: "auto", fill: "FFFFFF" };

  const kvTable = new Table({
    rows: [
      new TableRow({
        children: [
          new TableCell({
            children: buildCellParagraphs(leftFields),
            width: { size: 50, type: WidthType.PERCENTAGE },
            borders: noBorders,
            shading: noShading,
          }),
          new TableCell({
            children: buildCellParagraphs(rightFields),
            width: { size: 50, type: WidthType.PERCENTAGE },
            borders: noBorders,
            shading: noShading,
          }),
        ],
      }),
    ],
    width: { size: 100, type: WidthType.PERCENTAGE },
  });

  return [banner, kvTable];
}

// ── 2. createSectionHeader ──
// Returns a single Paragraph with bottom border rule
function createSectionHeader(text) {
  return new Paragraph({
    children: [
      new TextRun({
        text: text,
        bold: true,
        size: 22, // 11pt
        color: COLORS.PRIMARY,
        font: FONT,
      }),
    ],
    spacing: { before: 240, after: 0 }, // 12pt before, 0pt after
    border: {
      bottom: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
    },
  });
}

// ── 3. createTable ──
// headers: string[], rows: string[][], options: { accentHeader?, fontSize? }
function createTable(headers, rows, options = {}) {
  const fontSize = options.fontSize || 17; // 8.5pt default
  const headerFill = options.accentHeader ? COLORS.ACCENT : COLORS.TABLE_HEADER_FILL;
  const headerTextColor = options.accentHeader ? COLORS.HEADER_TEXT : "000000";

  const cellBorders = {
    top: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
    bottom: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
    left: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
    right: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
  };

  const cellMargins = { top: 40, bottom: 40, left: 80, right: 80 };

  function isNumeric(val) {
    if (typeof val !== "string") return false;
    const cleaned = val.replace(/[,$%()]/g, "").trim();
    return cleaned !== "" && !isNaN(cleaned);
  }

  // Header row
  const headerRow = new TableRow({
    children: headers.map(
      (h) =>
        new TableCell({
          children: [
            new Paragraph({
              children: [
                new TextRun({
                  text: h,
                  bold: true,
                  size: fontSize,
                  color: headerTextColor,
                  font: FONT,
                }),
              ],
            }),
          ],
          shading: { type: ShadingType.CLEAR, color: "auto", fill: headerFill },
          borders: cellBorders,
          margins: cellMargins,
        })
    ),
  });

  // Data rows with alternating shading
  const dataRows = rows.map((row, rowIdx) => {
    const fill = rowIdx % 2 === 1 ? COLORS.TABLE_ALT_ROW : "FFFFFF";
    return new TableRow({
      children: row.map((cell, colIdx) => {
        const align = colIdx > 0 && isNumeric(cell)
          ? AlignmentType.RIGHT
          : AlignmentType.LEFT;
        return new TableCell({
          children: [
            new Paragraph({
              children: [
                new TextRun({ text: cell, size: fontSize, font: FONT }),
              ],
              alignment: align,
            }),
          ],
          shading: { type: ShadingType.CLEAR, color: "auto", fill: fill },
          borders: cellBorders,
          margins: cellMargins,
        });
      }),
    });
  });

  return new Table({
    rows: [headerRow, ...dataRows],
    width: { size: 100, type: WidthType.PERCENTAGE },
  });
}

// ── 4. createBulletList ──
// items: string[], style: "synthesis" | "informational"
function createBulletList(items, style = "synthesis") {
  const indent =
    style === "synthesis"
      ? { left: 360, hanging: 180 }   // 360 DXA left, hanging indent for bullet
      : { left: 180 };                 // 180 DXA, no hanging

  return items.map(
    (item) =>
      new Paragraph({
        children: [
          new TextRun({ text: "•  ", font: FONT, size: 18 }),
          new TextRun({ text: item, font: FONT, size: 18 }),
        ],
        indent: indent,
        spacing: { after: 60 },
      })
  );
}

// ── 5. createFooter ──
// date: string (e.g., "February 23, 2026")
function createFooter(date) {
  return new Footer({
    children: [
      new Paragraph({
        children: [
          new TextRun({
            text: `Data: S&P Capital IQ via Kensho | Analysis: AI-generated | ${date}`,
            italics: true,
            size: 14, // 7pt
            color: COLORS.FOOTER_TEXT,
            font: FONT,
          }),
        ],
        alignment: AlignmentType.CENTER,
      }),
      new Paragraph({
        children: [
          new TextRun({
            text: "For informational purposes only. Not investment advice.",
            italics: true,
            size: 14,
            color: COLORS.FOOTER_TEXT,
            font: FONT,
          }),
        ],
        alignment: AlignmentType.CENTER,
      }),
    ],
  });
}
Usage in generated scripts:
  1. Copy all functions and constants above into the generated Node.js script
  2. Call
    createHeaderBanner(...)
    instead of manually building banner paragraphs and tables
  3. Call
    createSectionHeader(...)
    for every section title — never manually set paragraph borders
  4. Call
    createTable(...)
    for all tabular data — financial summaries, trading comps, M&A activity, relationship tables, funding history, etc. Pass
    { accentHeader: true }
    for M&A activity tables (IB/M&A template). For non-numeric tables (e.g., relationships, ownership), the function still works correctly — it only right-aligns cells that contain numeric values.
  5. Call
    createBulletList(items, "synthesis")
    for earnings highlights, strategic fit, integration considerations, and conversation starters
  6. Call
    createBulletList(items, "informational")
    for relationship entries
  7. Pass
    createFooter(date)
    to the Document constructor's
    footers.default
    property
What these functions eliminate:
  • Black background tables (enforces
    ShadingType.CLEAR
    everywhere)
  • Separate horizontal rule paragraphs under section headers (enforces
    border.bottom
    on the paragraph itself)
  • Bordered key-value tables in headers (enforces
    borders: none
    )
  • Inconsistent bullet styles (enforces
    character only)
  • Missing footers (provides the exact footer structure)
您必须使用这些精确的函数来创建文档元素,不得编写自定义docx-js样式代码。 将这些函数复制到您生成的Node脚本中并调用它们。上面的样式配置文字作为文档保留;这些函数是执行机制。
javascript
const docx = require("docx");
const {
  Document, Paragraph, TextRun, Table, TableRow, TableCell,
  WidthType, AlignmentType, BorderStyle, ShadingType,
  Header, Footer, PageNumber, HeadingLevel, TableLayoutType,
  convertInchesToTwip
} = docx;

// ── Color constants ──
const COLORS = {
  PRIMARY: "1F3864",
  ACCENT: "2E75B6",
  TABLE_HEADER_FILL: "D6E4F0",
  TABLE_ALT_ROW: "F2F2F2",
  TABLE_BORDER: "CCCCCC",
  HEADER_TEXT: "FFFFFF",
  FOOTER_TEXT: "666666",
};

const FONT = "Arial";

// ── 1. createHeaderBanner ──
// Returns an array of docx elements: [banner paragraph, key-value table]
function createHeaderBanner(companyName, leftFields, rightFields) {
  // leftFields / rightFields: arrays of { label: string, value: string }
  const banner = new Paragraph({
    children: [
      new TextRun({
        text: companyName,
        bold: true,
        size: 36, // 18pt
        color: COLORS.HEADER_TEXT,
        font: FONT,
      }),
    ],
    shading: { type: ShadingType.CLEAR, color: "auto", fill: COLORS.PRIMARY },
    spacing: { after: 0 },
    alignment: AlignmentType.LEFT,
  });

  function buildCellParagraphs(fields) {
    return fields.map(
      (f) =>
        new Paragraph({
          children: [
            new TextRun({ text: f.label + "  ", bold: true, size: 18, font: FONT }),
            new TextRun({ text: f.value, size: 18, font: FONT }),
          ],
          spacing: { after: 40 },
        })
    );
  }

  const noBorder = { style: BorderStyle.NONE, size: 0, color: "FFFFFF" };
  const noBorders = { top: noBorder, bottom: noBorder, left: noBorder, right: noBorder };
  const noShading = { type: ShadingType.CLEAR, color: "auto", fill: "FFFFFF" };

  const kvTable = new Table({
    rows: [
      new TableRow({
        children: [
          new TableCell({
            children: buildCellParagraphs(leftFields),
            width: { size: 50, type: WidthType.PERCENTAGE },
            borders: noBorders,
            shading: noShading,
          }),
          new TableCell({
            children: buildCellParagraphs(rightFields),
            width: { size: 50, type: WidthType.PERCENTAGE },
            borders: noBorders,
            shading: noShading,
          }),
        ],
      }),
    ],
    width: { size: 100, type: WidthType.PERCENTAGE },
  });

  return [banner, kvTable];
}

// ── 2. createSectionHeader ──
// Returns a single Paragraph with bottom border rule
function createSectionHeader(text) {
  return new Paragraph({
    children: [
      new TextRun({
        text: text,
        bold: true,
        size: 22, // 11pt
        color: COLORS.PRIMARY,
        font: FONT,
      }),
    ],
    spacing: { before: 240, after: 0 }, // 12pt before, 0pt after
    border: {
      bottom: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
    },
  });
}

// ── 3. createTable ──
// headers: string[], rows: string[][], options: { accentHeader?, fontSize? }
function createTable(headers, rows, options = {}) {
  const fontSize = options.fontSize || 17; // 8.5pt default
  const headerFill = options.accentHeader ? COLORS.ACCENT : COLORS.TABLE_HEADER_FILL;
  const headerTextColor = options.accentHeader ? COLORS.HEADER_TEXT : "000000";

  const cellBorders = {
    top: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
    bottom: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
    left: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
    right: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
  };

  const cellMargins = { top: 40, bottom: 40, left: 80, right: 80 };

  function isNumeric(val) {
    if (typeof val !== "string") return false;
    const cleaned = val.replace(/[,$%()]/g, "").trim();
    return cleaned !== "" && !isNaN(cleaned);
  }

  // Header row
  const headerRow = new TableRow({
    children: headers.map(
      (h) =>
        new TableCell({
          children: [
            new Paragraph({
              children: [
                new TextRun({
                  text: h,
                  bold: true,
                  size: fontSize,
                  color: headerTextColor,
                  font: FONT,
                }),
              ],
            }),
          ],
          shading: { type: ShadingType.CLEAR, color: "auto", fill: headerFill },
          borders: cellBorders,
          margins: cellMargins,
        })
    ),
  });

  // Data rows with alternating shading
  const dataRows = rows.map((row, rowIdx) => {
    const fill = rowIdx % 2 === 1 ? COLORS.TABLE_ALT_ROW : "FFFFFF";
    return new TableRow({
      children: row.map((cell, colIdx) => {
        const align = colIdx > 0 && isNumeric(cell)
          ? AlignmentType.RIGHT
          : AlignmentType.LEFT;
        return new TableCell({
          children: [
            new Paragraph({
              children: [
                new TextRun({ text: cell, size: fontSize, font: FONT }),
              ],
              alignment: align,
            }),
          ],
          shading: { type: ShadingType.CLEAR, color: "auto", fill: fill },
          borders: cellBorders,
          margins: cellMargins,
        });
      }),
    });
  });

  return new Table({
    rows: [headerRow, ...dataRows],
    width: { size: 100, type: WidthType.PERCENTAGE },
  });
}

// ── 4. createBulletList ──
// items: string[], style: "synthesis" | "informational"
function createBulletList(items, style = "synthesis") {
  const indent =
    style === "synthesis"
      ? { left: 360, hanging: 180 }   // 360 DXA left, hanging indent for bullet
      : { left: 180 };                 // 180 DXA, no hanging

  return items.map(
    (item) =>
      new Paragraph({
        children: [
          new TextRun({ text: "•  ", font: FONT, size: 18 }),
          new TextRun({ text: item, font: FONT, size: 18 }),
        ],
        indent: indent,
        spacing: { after: 60 },
      })
  );
}

// ── 5. createFooter ──
// date: string (e.g., "February 23, 2026")
function createFooter(date) {
  return new Footer({
    children: [
      new Paragraph({
        children: [
          new TextRun({
            text: `Data: S&P Capital IQ via Kensho | Analysis: AI-generated | ${date}`,
            italics: true,
            size: 14, // 7pt
            color: COLORS.FOOTER_TEXT,
            font: FONT,
          }),
        ],
        alignment: AlignmentType.CENTER,
      }),
      new Paragraph({
        children: [
          new TextRun({
            text: "For informational purposes only. Not investment advice.",
            italics: true,
            size: 14,
            color: COLORS.FOOTER_TEXT,
            font: FONT,
          }),
        ],
        alignment: AlignmentType.CENTER,
      }),
    ],
  });
}
在生成脚本中的用法:
  1. 将上述所有函数和常量复制到生成的Node.js脚本中
  2. 调用
    createHeaderBanner(...)
    而非手动构建横幅段落和表格
  3. 为每个章节标题调用
    createSectionHeader(...)
    ——绝不要手动设置段落边框
  4. 所有表格数据调用
    createTable(...)
    ——财务摘要、交易对比、并购活动、关系表、融资历史等。对于并购活动表格(IB/M&A模板),传递
    { accentHeader: true }
    。对于非数值表格(例如关系、所有权),该函数仍能正常工作——它仅会将包含数值的单元格右对齐。
  5. 为收益亮点、战略契合度、整合考量和对话切入点调用
    createBulletList(items, "synthesis")
  6. 为关系条目调用
    createBulletList(items, "informational")
  7. createFooter(date)
    传递给Document构造函数的
    footers.default
    属性
这些函数消除的问题:
  • 黑色背景表格(在所有地方强制使用
    ShadingType.CLEAR
  • 章节标题下方的单独水平分隔线段落(强制将
    border.bottom
    应用于段落本身)
  • 页眉中的带边框键值表格(强制使用
    borders: none
  • 不一致的项目符号样式(仅强制使用
    字符)
  • 缺失页脚(提供精确的页脚结构)

Workflow

工作流程

Step 1: Identify Inputs

步骤1:确定输入信息

Gather up to four things before proceeding:
  1. Company — name or ticker. If only a ticker, resolve the full company name with an initial query (e.g., use the company info tool).
  2. Audience — one of four types:
    • Equity Research — for buy-side/sell-side analysts evaluating an investment
    • IB / M&A — for bankers profiling a company in transaction context
    • Corp Dev — for internal strategic teams evaluating an acquisition target
    • Sales / BD — for commercial teams preparing for a client meeting
  3. Comparable companies (optional) — if the user has specific comps in mind, note them. Otherwise the skill will identify peers from S&P Global data. This matters for Equity Research, IB/M&A, and Corp Dev tear sheets.
  4. Page length preference (optional) — defaults vary by audience (see below), but the user can override.
If the user doesn't specify an audience, ask.
在开始前收集最多四项内容:
  1. 公司——名称或股票代码。如果仅提供股票代码,通过初始查询解析完整公司名称(例如使用公司信息工具)。
  2. 受众——四类之一:
    • 股票研究——用于买方/卖方分析师评估投资
    • IB / 并购——用于银行家在交易背景下分析公司
    • 企业发展——用于内部战略团队评估收购目标
    • 销售 / BD——用于商务团队准备客户会议
  3. 可比公司(可选)——如果用户有特定的对比公司,请记录下来。否则,该技能将从S&P Global数据中识别同行公司。这对股票研究、IB/并购和企业发展类财务摘要文档很重要。
  4. 页面长度偏好(可选)——默认值因受众而异(见下文),但用户可以覆盖。
如果用户未指定受众,请询问。

Step 2: Read the Audience-Specific Reference

步骤2:阅读特定受众的参考文档

Read the corresponding reference file from this skill's directory:
  • Equity Research →
    references/equity-research.md
  • IB / M&A →
    references/ib-ma.md
  • Corp Dev →
    references/corp-dev.md
  • Sales / BD →
    references/sales-bd.md
Each reference defines sections, a query plan, formatting guidance, and page length defaults.
从此技能的目录中读取相应的参考文件:
  • 股票研究 →
    references/equity-research.md
  • IB / 并购 →
    references/ib-ma.md
  • 企业发展 →
    references/corp-dev.md
  • 销售 / BD →
    references/sales-bd.md
每个参考文档定义了章节、查询计划、格式指南和页面长度默认值。

Step 3: Pull Data via S&P Global MCP

步骤3:通过S&P Global MCP获取数据

First: Create the intermediate file directory:
bash
mkdir -p /tmp/tear-sheet/
Use the S&P Global MCP tools (also known as the Kensho LLM-ready API). Claude will have access to structured tools for financial data, company information, market data, consensus estimates, earnings transcripts, M&A transactions, and business relationships. The query plans in each reference file describe what data to retrieve for each section — map these to the appropriate S&P Global tools available in the conversation.
After each query step, immediately write the retrieved data to the intermediate file(s) specified in the reference file's query plan. Do not defer writes — data written to disk is protected from context degradation in long conversations.
Query strategy: Each reference file includes a query plan with 4-6 data retrieval steps. These are starting points, not rigid constraints. Prioritize data completeness over minimizing calls:
  • Always pull 4 fiscal years of financial data, even though only 3 years are displayed. The fourth (earliest) year is needed to compute YoY revenue growth for the first displayed year. Without it, the earliest year's growth rate will show "N/A" — which looks like missing data, not a design choice.
  • Execute the query plan as written, using whichever S&P Global tools match the data needed.
  • If a tool call returns incomplete results, try alternative tools or narrower queries. For example, if company summary doesn't include segment detail, try the segments tool directly.
  • If a data point isn't returned after a targeted retry, move on — label it "N/A" or "Not disclosed."
  • Never fabricate data. If the tools don't return a number, do not estimate from training knowledge.
User-specified comps: If the user provided comparable companies, query financials and multiples for each comp explicitly. If no comps were provided, use whatever peer data the tools return, or identify peers from the company's sector using the competitors tool.
Optional context from the user: Listen for additional context the user provides naturally. If they mention who the acquirer is ("we're looking at this for our platform"), what they sell ("we sell data analytics to banks"), or who the likely buyers are ("this would be interesting to Salesforce or Microsoft"), incorporate that context into the relevant synthesis sections (Strategic Fit, Conversation Starters, Deal Angle). Don't prompt for this information — just use it if offered.
Private company handling: CIQ includes private company data, so query the same way. However, expect sparser results. When generating for a private company:
  • Skip: stock price, 52-week range, beta, stock performance, consensus estimates, trading comps
  • Lean into: business overview, relationships, ownership structure, whatever financials are available
  • Note "Private Company" prominently in the header
首先: 创建中间文件目录:
bash
mkdir -p /tmp/tear-sheet/
使用S&P Global MCP工具(也称为Kensho LLM-ready API)。Claude将有权访问用于财务数据、公司信息、市场数据、共识预测、收益 transcript、并购交易和业务关系的结构化工具。每个参考文件中的查询计划描述了每个部分需要检索的数据——将这些映射到对话中可用的相应S&P Global工具。
每次查询步骤后,立即将检索到的数据写入参考文件查询计划中指定的中间文件。 不要延迟写入——写入磁盘的数据可避免长对话中的上下文退化。
查询策略: 每个参考文件包含一个4-6步的数据检索查询计划。这些是起点,而非严格约束。优先考虑数据完整性而非减少调用次数:
  • 始终获取4个财年的财务数据,即使仅显示3年。第四年(最早的年份)用于计算第一个显示年份的同比收入增长率。没有它,最早年份的增长率将显示为"N/A"——这看起来像缺失数据,而非设计选择。
  • 按编写的查询计划执行,使用与所需数据匹配的任何S&P Global工具。
  • 如果工具调用返回不完整的结果,尝试替代工具或更窄的查询。例如,如果公司摘要不包含细分市场详情,直接尝试细分市场工具。
  • 如果经过针对性重试后仍未返回数据点,请继续——将其标记为"N/A"或"未披露"。
  • 切勿编造数据。如果工具未返回数值,不要根据训练知识估算。
用户指定的对比公司: 如果用户提供了可比公司,明确查询每个对比公司的财务数据和倍数。如果未提供对比公司,使用工具返回的任何同行数据,或使用竞争对手工具从公司所在行业中识别同行。
用户提供的可选上下文: 留意用户自然提供的额外上下文。如果他们提及收购方是谁("我们正在为我们的平台评估这家公司")、他们销售什么("我们向银行销售数据分析服务")或潜在买家是谁("这对Salesforce或Microsoft来说会很有吸引力"),将这些上下文整合到相关的综合部分(战略契合度、对话切入点、交易角度)中。不要提示用户提供此信息——如果用户主动提供,直接使用即可。
私有公司处理: CIQ包含私有公司数据,因此查询方式相同。但预计结果会更稀疏。为私有公司生成文档时:
  • 跳过:股价、52周区间、贝塔系数、股票表现、共识预测、交易对比
  • 重点关注:业务概述、关系、所有权结构、任何可用的财务数据
  • 在页眉中显著标注"私有公司"

Step 3b: Calculate Derived Metrics

步骤3b:计算衍生指标

After all data collection is complete and intermediate files are written, compute all derived metrics in a single dedicated pass. This is a calculation-only step — no new MCP queries.
Read all intermediate files back into context, then compute:
  • Margins: Gross Margin %, EBITDA Margin %, FCF Margin %, Operating Margin %
  • Growth rates: YoY revenue growth, YoY segment revenue growth, YoY EPS growth
  • Efficiency ratios: FCF Conversion (FCF/EBITDA), R&D as % of Revenue, Capex as % of Revenue
  • Capital structure: Net Debt (Total Debt − Cash & Equivalents), Net Debt / EBITDA
  • Segment mix: Each segment's revenue as % of consolidated total revenue (use consolidated revenue as denominator per Data Integrity Rule 8)
Validation (moved from Arithmetic Validation): During this calculation pass, enforce all arithmetic checks:
  • Margin calculations: Verify EBITDA Margin = EBITDA / Revenue, Gross Margin = Gross Profit / Revenue, etc. If the computed margin doesn't match the raw numbers, use the computation from raw components.
  • Growth rates: Verify YoY growth = (Current − Prior) / Prior. Don't rely on pre-computed growth rates if you have the underlying values.
  • Segment totals: If showing revenue by segment, verify segments sum to total revenue (within rounding tolerance). If they don't, omit the total row rather than publishing inconsistent math.
  • Percentage columns: Verify "% of Total" columns sum to ~100%.
  • Valuation cross-checks: If you show both EV and EV/Revenue, verify EV / Revenue ≈ the stated multiple.
If a validation fails: attempt recalculation from raw data. If still inconsistent, flag the metric as "N/A" rather than publishing incorrect numbers. Quiet math errors in a tear sheet destroy credibility.
Write results to
/tmp/tear-sheet/calculations.csv
with columns:
metric,value,formula,components
Example rows:
metric,value,formula,components
gross_margin_fy2024,72.4%,gross_profit/revenue,"9524/13159"
revenue_growth_fy2024,12.3%,(current-prior)/prior,"13159/11716"
net_debt_fy2024,2150,total_debt-cash,"4200-2050"
完成所有数据收集并写入中间文件后,在单独的专用步骤中计算所有衍生指标。这仅为计算步骤——不进行新的MCP查询。
将所有中间文件读回上下文,然后计算:
  • 利润率: 毛利率%、EBITDA利润率%、自由现金流(FCF)利润率%、营业利润率%
  • 增长率: 收入同比增长率、细分市场收入同比增长率、每股收益(EPS)同比增长率
  • 效率比率: FCF转化率(FCF/EBITDA)、研发费用占收入比、资本支出占收入比
  • 资本结构: 净债务(总债务−现金及等价物)、净债务/EBITDA
  • 细分市场占比: 每个细分市场收入占合并总收入的百分比(根据数据完整性规则8,使用合并总收入作为分母)
验证(从算术验证移至此处): 在计算过程中,执行所有算术检查:
  • 利润率计算: 验证EBITDA利润率 = EBITDA / 收入,毛利率 = 毛利润 / 收入等。如果计算出的利润率与原始数据不符,使用原始组件重新计算。
  • 增长率: 验证同比增长率 = (当期−上期)/上期。如果有基础数据,不要依赖预先计算的增长率。
  • 细分市场总计: 如果显示细分市场收入,验证细分市场总和等于总收入(在四舍五入公差范围内)。如果不相等,省略总计行,而非发布不一致的数据。
  • 百分比列: 验证"占总计百分比"列总和约为100%。
  • 估值交叉检查: 如果同时显示EV和EV/收入,验证EV / 收入 ≈ 所述倍数。
如果验证失败:尝试从原始数据重新计算。如果仍然不一致,将指标标记为"N/A",而非发布错误的数值。财务摘要文档中的隐性数学错误会破坏可信度。
将结果写入
/tmp/tear-sheet/calculations.csv
,列包括:
metric,value,formula,components
示例行:
metric,value,formula,components
gross_margin_fy2024,72.4%,gross_profit/revenue,"9524/13159"
revenue_growth_fy2024,12.3%,(current-prior)/prior,"13159/11716"
net_debt_fy2024,2150,total_debt-cash,"4200-2050"

Step 3c: Verify Data Files

步骤3c:验证数据文件

Before generating the document, verify that all intermediate files are present and populated.
Read each intermediate file via separate read operations and print a verification summary:
=== Tear Sheet Data Verification ===
company-profile.txt: ✓ (12 fields)
financials.csv:      ✓ (36 rows)
segments.csv:        ✓ (8 rows)
valuation.csv:       ✓ (5 rows)
calculations.csv:    ✓ (18 rows)
earnings.txt:        ✓ (populated)
relationships.txt:   ⚠ MISSING
peer-comps.csv:      ✓ (12 rows)
================================
Soft gate: If any file expected for the current audience type is missing or empty, print a warning but continue. The tear sheet handles missing data gracefully with "N/A" and section skipping. However, the warning ensures visibility into what data was lost.
Critical rule: The files — not your memory of earlier conversation — are the single source of truth for every number in the document. When generating the DOCX in Step 4, read values from the intermediate files. Do not rely on conversation context for financial data.
在生成文档前,验证所有中间文件是否存在且已填充。
通过单独的读取操作读取每个中间文件,并打印验证摘要:
=== 财务摘要文档数据验证 ===
company-profile.txt: ✓ (12个字段)
financials.csv:      ✓ (36行)
segments.csv:        ✓ (8行)
valuation.csv:       ✓ (5行)
calculations.csv:    ✓ (18行)
earnings.txt:        ✓ (已填充)
relationships.txt:   ⚠ 缺失
peer-comps.csv:      ✓ (12行)
================================
软限制: 如果当前受众类型所需的任何文件缺失或为空,打印警告但继续。财务摘要文档会通过"N/A"和跳过章节的方式优雅处理缺失数据。但警告可确保您了解丢失的数据内容。
关键规则:文件——而非您对早期对话的记忆——是文档中每个数值的唯一真实来源。 在步骤4生成DOCX时,从中间文件读取数值。不要依赖对话上下文获取财务数据。

Step 4: Format as DOCX

步骤4:格式化为DOCX

Read
/mnt/skills/public/docx/SKILL.md
for docx creation mechanics (docx-js via Node). Apply the Style Configuration above plus the section-specific formatting in the reference file.
Page length defaults (user can override):
  • Equity Research: 1 page (density is the convention)
  • IB / M&A: 1-2 pages
  • Corp Dev: 1-2 pages
  • Sales / BD: 1-2 pages
If content exceeds the target, each reference file specifies which sections to cut first.
Output filename:
[CompanyName]_TearSheet_[Audience]_[YYYYMMDD].docx
Example:
Nvidia_TearSheet_CorpDev_20260220.docx
Save to
/mnt/user-data/outputs/
and present to the user.
阅读
/mnt/skills/public/docx/SKILL.md
了解docx创建机制(通过Node使用docx-js)。应用上述样式配置以及参考文件中的特定章节格式。
页面长度默认值(用户可覆盖):
  • 股票研究:1页(密集度是行业惯例)
  • IB / 并购:1-2页
  • 企业发展:1-2页
  • 销售 / BD:1-2页
如果内容超过目标长度,每个参考文件指定了首先删减哪些章节。
输出文件名:
[CompanyName]_TearSheet_[Audience]_[YYYYMMDD].docx
示例:
Nvidia_TearSheet_CorpDev_20260220.docx
保存到
/mnt/user-data/outputs/
并呈现给用户。

Data Integrity Rules

数据完整性规则

These override everything else:
  1. S&P Global tools are the only source for financial data. Do not fill gaps with training knowledge — it may be stale or wrong.
  2. Label what you can't find. Use "N/A" or "Not disclosed" rather than omitting a row silently.
  3. Dates matter. Note the fiscal year end or reporting period. Don't assume calendar year = fiscal year. Market data (stock prices, market cap) should include an "as of" date.
  4. Don't mix reporting periods. If you have FY2023 revenue and LTM EBITDA, label them distinctly.
  5. Prefer MCP-returned fields over manual computation. If the S&P Global tools return a pre-computed field (e.g., net debt, EBITDA, FCF), use that value directly rather than computing it from components. Only compute derived metrics manually when the tools do not return the field. This reduces discrepancies.
  6. Ensure consistency across tear sheet types. If generating multiple tear sheets for the same company (e.g., equity research and IB/M&A in the same session), the same underlying data points must produce identical values across all outputs. Net debt, revenue, EBITDA, margins, and growth rates must match exactly. Do not re-query or re-compute independently per report — reuse the same retrieved values.
  7. Never downgrade known transaction values. If the M&A tools return a deal value for a transaction, that value must appear in the output. Do not replace a known deal value with "Undisclosed." Use "Undisclosed" only when the tools genuinely return no value for a transaction.
  8. Use consolidated revenue as the denominator for segment percentages. When computing "% of Total" for segment tables, divide each segment's revenue by consolidated total revenue (as reported on the income statement), not by the sum of segment revenues. The sum of segments often exceeds consolidated revenue due to intersegment eliminations. Using consolidated revenue ensures percentages align with the total revenue figure shown elsewhere in the document.
  9. Always include forward (NTM) multiples when available. If the tools return both trailing and forward valuation multiples, both must appear in the output. Forward multiples are the primary valuation reference for equity research, IB/M&A, and corp dev audiences. Never show only trailing multiples when forward data is available.
  10. No S&P Global tool returns executive or management data. Do not populate management names, titles, or biographical details from training data — this violates Rule 1 and produces stale information. If a management section appears in a template, omit it entirely. Ownership structure (institutional holders, insider %, PE sponsor) may be included only if returned by the tools — gate with "data permitting."
这些规则优先于其他所有规则:
  1. S&P Global工具是财务数据的唯一来源。 不要用训练知识填补空白——训练知识可能过时或错误。
  2. 标注无法找到的内容。 使用"N/A"或"未披露"而非静默省略行。
  3. 日期很重要。 标注财年末或报告期。不要假设日历年=财年。市场数据(股价、市值)应包含"截至"日期。
  4. 不要混合报告期。 如果您有FY2023收入和LTM EBITDA,要明确标注它们。
  5. 优先使用MCP返回的字段而非手动计算。 如果S&P Global工具返回预先计算的字段(例如净债务、EBITDA、FCF),直接使用该值,而非从组件计算。仅当工具未返回该字段时,才手动计算衍生指标。这可减少差异。
  6. 确保不同类型财务摘要文档的一致性。 如果为同一公司生成多个财务摘要文档(例如同一会话中的股票研究和IB/并购),相同的基础数据点必须在所有输出中产生相同的值。净债务、收入、EBITDA、利润率和增长率必须完全匹配。不要为每份报告独立重新查询或重新计算——重用相同的检索值。
  7. 绝不降低已知交易价值。 如果并购工具返回交易的交易价值,该值必须出现在输出中。不要用"未披露"替换已知的交易价值。仅当工具确实未返回交易价值时,才使用"未披露"。
  8. 使用合并总收入作为细分市场百分比的分母。 在计算细分市场表格的"占总计百分比"时,将每个细分市场的收入除以合并总收入(如损益表所示),而非细分市场收入总和。由于内部细分市场抵消,细分市场总和通常超过合并总收入。使用合并总收入可确保百分比与文档中其他地方显示的总收入数字一致。
  9. 如果可用,始终包含远期(NTM)倍数。 如果工具同时返回 trailing 和远期估值倍数,两者必须都出现在输出中。远期倍数是股票研究、IB/并购和企业发展受众的主要估值参考。当有远期数据可用时,绝不要仅显示trailing倍数。
  10. 没有S&P Global工具返回高管或管理数据。 不要从训练数据中填充管理层姓名、职位或传记细节——这违反了规则1,会产生过时信息。如果模板中包含管理层部分,完全省略该部分。所有权结构(机构持有者、内部人士持股比例、私募股权赞助商)仅在工具返回时才可包含——需注明"数据允许时"。

Intermediate File Rule

中间文件规则

All data retrieved from MCP tools must be persisted to structured intermediate files before document generation. These files — not conversation context — are the single source of truth for every number in the document.
Setup: At the start of Step 3, create the working directory:
mkdir -p /tmp/tear-sheet/
Write-after-query mandate: After each MCP query step completes, immediately write the retrieved data to the appropriate intermediate file(s). Do not wait until all queries finish. Each reference file's query plan specifies which file(s) to write after each step.
File schemas:
FileFormatColumns / StructureUsed By
/tmp/tear-sheet/company-profile.txt
Key-value textname, ticker, exchange, HQ, sector, industry, founded, employees, market_cap, enterprise_value, stock_price, 52wk_high, 52wk_low, shares_outstanding, beta, ownershipAll
/tmp/tear-sheet/financials.csv
CSV
period,line_item,value,source
All
/tmp/tear-sheet/segments.csv
CSV
period,segment_name,revenue,source
ER, IB, CD
/tmp/tear-sheet/valuation.csv
CSV
metric,trailing,forward,source
ER, IB, CD
/tmp/tear-sheet/consensus.csv
CSV
metric,fy_year,value,source
ER
/tmp/tear-sheet/earnings.txt
Structured textQuarter, date, key quotes, guidance, key driversER, IB, Sales
/tmp/tear-sheet/relationships.txt
Structured textCustomers, suppliers, partners, competitors — each with descriptorsIB, CD, Sales
/tmp/tear-sheet/peer-comps.csv
CSV
ticker,metric,value,source
ER, IB, CD
/tmp/tear-sheet/ma-activity.csv
CSV
date,target,deal_value,type,rationale,source
IB, CD
/tmp/tear-sheet/calculations.csv
CSV
metric,value,formula,components
All (written in Step 3b)
Abbreviations: ER = Equity Research, IB = IB/M&A, CD = Corp Dev, Sales = Sales/BD.
Not every audience type uses every file — the reference files define which query steps apply. Files not relevant to the current audience type need not be created.
Raw values only. Intermediate files store raw values as returned by the tools. Do not pre-compute margins, growth rates, or other derived metrics in these files — that happens in Step 3b.
Page budget enforcement: Each reference file specifies a default page length and a numbered cut order. If the rendered document exceeds the target, apply cuts in the order specified — do not attempt to shrink font sizes or margins below the template minimums. The cut order is a strict priority stack: cut section 1 completely before touching section 2.
从MCP工具检索到的所有数据必须在生成文档前持久化到结构化中间文件中。这些文件——而非对话上下文——是文档中每个数值的唯一真实来源。
设置: 在步骤3开始时,创建工作目录:
mkdir -p /tmp/tear-sheet/
查询后立即写入的要求: 每次MCP查询步骤完成后,立即将检索到的数据写入相应的中间文件。不要等到所有查询完成。每个参考文件的查询计划指定了每个步骤后要写入的文件。
文件架构:
文件格式列 / 结构使用者
/tmp/tear-sheet/company-profile.txt
键值文本name, ticker, exchange, HQ, sector, industry, founded, employees, market_cap, enterprise_value, stock_price, 52wk_high, 52wk_low, shares_outstanding, beta, ownership所有受众
/tmp/tear-sheet/financials.csv
CSV
period,line_item,value,source
所有受众
/tmp/tear-sheet/segments.csv
CSV
period,segment_name,revenue,source
ER, IB, CD
/tmp/tear-sheet/valuation.csv
CSV
metric,trailing,forward,source
ER, IB, CD
/tmp/tear-sheet/consensus.csv
CSV
metric,fy_year,value,source
ER
/tmp/tear-sheet/earnings.txt
结构化文本Quarter, date, key quotes, guidance, key driversER, IB, Sales
/tmp/tear-sheet/relationships.txt
结构化文本Customers, suppliers, partners, competitors — 每个都有描述符IB, CD, Sales
/tmp/tear-sheet/peer-comps.csv
CSV
ticker,metric,value,source
ER, IB, CD
/tmp/tear-sheet/ma-activity.csv
CSV
date,target,deal_value,type,rationale,source
IB, CD
/tmp/tear-sheet/calculations.csv
CSV
metric,value,formula,components
所有受众(步骤3b中写入)
缩写: ER = 股票研究,IB = IB/并购,CD = 企业发展,Sales = 销售/BD。
并非所有受众类型都使用所有文件——参考文件定义了哪些查询步骤适用。与当前受众类型无关的文件无需创建。
仅存储原始值。 中间文件存储工具返回的原始值。不要在这些文件中预先计算利润率、增长率或其他衍生指标——这些计算在步骤3b中进行。
页面预算执行: 每个参考文件指定了默认页面长度和编号删减顺序。如果渲染后的文档超过目标长度,按指定顺序删减——不要尝试将字体大小或边距缩小到模板最小值以下。删减顺序是严格的优先级栈:完全删减第1节后再触碰第2节。

Content Quality Rules

内容质量规则

  1. Rewrite every narrative section for the audience. The CIQ company summary is an input, not an output. Each audience type needs a different description: concise and thesis-oriented for equity research, pitchbook prose for IB, product-focused for Corp Dev, plain language for Sales/BD. Never paste the CIQ summary verbatim into any tear sheet.
  2. Differentiate earnings highlights by audience. The same earnings call produces different takeaways for different readers. Equity research wants segment-level performance and consensus beat/miss. IB wants margin trajectory and strategic commentary. Sales/BD wants strategic themes that create conversation angles. Do not reuse the same bullets across tear sheet types.
  3. Synthesis sections are the differentiator. Strategic Fit Analysis, Integration Considerations, Conversation Starters, and Business Overview paragraphs are where the tear sheet earns its value. These sections require analytical reasoning that connects data points into a narrative — listing company names without context is not synthesis.
  4. Flag pending divestitures in segment tables. If a company has announced a pending divestiture of a segment or business unit, add a footnote or parenthetical to the segment table noting the pending transaction (e.g., "Mobility* — *Pending divestiture, expected mid-2026"). For Corp Dev and IB/M&A tear sheets, include a one-line note below the segment table showing pro-forma revenue and revenue mix excluding the divested segment. This helps the reader evaluate the "go-forward" business without doing the math themselves.
  1. 为每个受众重写所有叙述性章节。 CIQ公司摘要是输入,而非输出。每个受众类型需要不同的描述:股票研究需要简洁且以论点为导向,IB需要推介式 prose,企业发展需要以产品为重点,销售/BD需要直白语言。绝不要将CIQ摘要直接粘贴到任何财务摘要文档中。
  2. 按受众区分收益亮点。 同一次收益电话会议对不同读者会产生不同的要点。股票研究需要细分市场层面的表现和共识超出/未达预期情况。IB需要利润率趋势和战略评论。销售/BD需要能创造对话角度的战略主题。不要在不同类型的财务摘要文档中重复使用相同的项目符号。
  3. 综合部分是差异化所在。 战略契合度分析、整合考量、对话切入点和业务概述段落是财务摘要文档体现价值的地方。这些部分需要分析推理,将数据点连接成叙事——仅列出公司名称而无上下文不是综合。
  4. 在细分市场表格中标记待剥离业务。 如果公司宣布将剥离某个细分市场或业务单元,在细分市场表格中添加脚注或括号标注待处理交易(例如:"Mobility* — *待剥离,预计2026年年中完成")。对于企业发展和IB/并购类财务摘要文档,在细分市场表格下方添加一行说明,显示剥离该细分市场后的预计收入和收入结构。这有助于读者无需自行计算即可评估"未来业务"。

Arithmetic Validation

算术验证

→ Arithmetic validation is now enforced in Step 3b (Calculate Derived Metrics). All margin calculations, growth rates, segment totals, percentage columns, and valuation cross-checks are validated during the dedicated calculation pass, before document generation begins. See Step 3b for the full validation checklist.
→ 算术验证现在在步骤3b(计算衍生指标)中执行。 所有利润率计算、增长率、细分市场总计、百分比列和估值交叉检查都在专门的计算步骤中验证,然后才开始生成文档。有关完整的验证清单,请参阅步骤3b。