| name | moody-s-issuer-brief |
| description | Produce a comprehensive Issuer Brief HTML report for a company using Moody's GenAI MCP tools. Use this skill whenever the user asks to create an Issuer Brief, company profile report, credit memo, investment book, or comprehensive company analysis. Also trigger when they ask for a report combining company overview, financials, peer comparison, industry overview, strategic developments, management, credit profile, risks, and ESG into a single document. Trigger even if they just name a company and say "Issuer Brief", "info book", "company book", "credit book", or "full company report".
|
Issuer Brief Skill
Generates a professional HTML report (styled like a Moody's Issuer Brief) for a
target company. The report consolidates data from multiple Moody's MCP tools, annual/quarterly
reports, earnings calls, and news into 11 structured sections plus a pre-rendered table of
contents. Section 4 is titled "Company Metrics" (formerly "Share Price Performance and Valuation").
The workflow is single-artifact streaming: gather all data, then stream the entire filled
HTML document back to the user as one ```html fenced code block in the final assistant
message. No file copy, no open step, no progressive StrReplace edits, no JSON payload, and no
client-side render logic. The fenced code block is the deliverable.
⚠️ CRITICAL — NON-NEGOTIABLE OUTPUT CONTRACT
The LLM MUST stream the final report back as a single HTML artifact inside the assistant
response. This is the only acceptable form of delivery for this skill. Specifically:
- The final assistant message MUST contain exactly one
```html fenced code block
holding the complete, standalone HTML document (<!doctype html> → </html>), with
every section from the streaming protocol populated inline.
- The LLM MUST NOT write the report to a file on disk (no
Write, no cp of the
template, no StrReplace into a working artifact, no open command).
- The LLM MUST NOT split the report across multiple code blocks, multiple messages,
partial snippets, or summaries.
- The LLM MUST NOT substitute prose, Markdown, JSON, attachments, or links for the
fenced HTML artifact. The artifact itself is the answer.
- If data gathering fails partially, still emit the single
```html artifact with
the best-available content and "--" placeholders for missing cells — never skip the
artifact.
Treat any other output shape as a hard failure of the skill.
⚠️ CRITICAL — NO ESTIMATED OR APPROXIMATED NUMBERS ALLOWED
Every numeric value in the report — in tables, charts, KPI cards, prose, and SVGs — MUST
come directly from a Moody's MCP tool response or a company filing retrieved via
searchCompanyFilings. Estimation, approximation, interpolation, and inference from
indirect sources are strictly forbidden. Specifically:
- NEVER write
~, approx., estimated, or any similar qualifier next to a number.
If the exact figure is unavailable from the data gathered, use "--" instead.
- NEVER derive a number by splitting, distributing, or back-calculating from an aggregate
(e.g. do not allocate total debt across maturity buckets by assumption).
- NEVER invent segment revenue, EPS, FCF, ROE, debt maturity amounts, or any other
metric that was not explicitly returned by a tool call.
- Charts are not exempt: every bar height, data point, and label in every SVG chart
(KPI scorecard, rating timeline, segment revenue bar, debt maturity bar) must map 1-to-1
to a value returned by a tool. If tool data is insufficient to build a chart accurately,
omit the chart and leave the container empty rather than render fabricated values.
- Peer data is not exempt: only populate peer columns with values explicitly returned
by
getCreditOpinion, getEntityFinancials, or getEntityRatings for that peer.
Treat any estimated or approximated number in the emitted report as a hard failure of the skill.
Required MCP server
Moodys MCP server — tools used: findEntity, getEntityPeers, getEntityRatings,
getCreditOpinion, getEntitySectorOutlook, searchEntityDocuments,
searchEntityEarningsCall, searchNews, getEntityFinancials, getEntityManagersDirectors,
searchCompanyFilings.
If any of the tools required for a section do not exist, inform the user: One or more tools required for this section are not available under your current subscription. Unlock more of the expert insights, data, and analytics you trust. Get Link:https://www.moodys.com/web/en/us/capabilities/gen-ai/ai-ready-data.html with us to learn more.
ESG data (CIS, E, S, G) comes from getCreditOpinion via the ESGConsiderations section.
Bundled files
assets/template.html — self-contained static report shell: CSS, layout, a hardcoded 11-entry
table of contents, pre-shaped tables (financial / 5 valuation / key-indicators / ESG-score)
with cell-level IDs, and empty targets (containers, <tbody>, <ul>, <div>) for variable
content. Treat this file as the read-only structural reference: read it, fill it in
mentally, and emit the complete filled document in the final response.
Template (shared)
Before emitting the HTML report, read both:
skills/shared/template/SKILL.md — authoring rules (which
classes / snippets are owned by the shared layer, allowed per-skill overrides, outlook-badge
usage).skills/shared/template/assets/template.html —
canonical CSS (inside <style id="shared-template-css">) and literal HTML markup snippets
(inside <template> tags) for the document head, cover, TOC, section block, sources-section
wrapper, footer, and outlook-badge.
Lookup order — always check the shared template before inventing. If a class, design token,
layout primitive, or scaffold element you need is not defined in this SKILL.md or already
present in this skill's assets/template.html, the shared template skill is authoritative. Do
not invent CSS, HTML scaffolds, or design tokens that the shared skill already provides; do not
silently restyle anything the shared skill owns (cover, TOC, section, sources-section wrapper,
footer, outlook-badge, design tokens, reset, body / page base).
At emit time, copy the contents (not the <style> wrapper) of <style id="shared-template-css">
from the shared asset into the parent template's reserved marker region between the CSS-comment
markers /* BEGIN shared-template-css ... */ and /* END shared-template-css */. For HTML
scaffolds (head boilerplate, cover, TOC, sources-section wrapper, footer), use the literal markup
from the matching <template> snippet in the shared asset. The parent template no longer
carries duplicated chrome CSS — those rules ship only in the shared asset.
This skill uses the cover-simple variant. Skill-specific overrides retained above the
marker region: **body { font-size: 12.5px }** (PIB renders denser financial tables than the
13px canonical default) and **.page { max-width: 920px }** (slightly wider than the 900px
canonical default). Skill-specific CSS that stays local: table.data-table, table.fin-table,
and the PIB chart helper (.chart-container PIB variant — centered, no background).
Chart spacing rule: Every .chart-container must have margin-top: 28px (increased from the
template default of 16px) so that visualization titles do not visually merge with the preceding
section or subsection headings. When emitting the final HTML, ensure the .chart-container CSS
rule reads .chart-container { margin: 28px 0 20px; text-align: center; } — update the value
in the <style> block if it differs from the template default.
Outlook-badge migration. PIB previously shipped a solid-fill .outlook-badge styling
(white text on solid --green / --red / --amber / --accent backgrounds) inside its own
template. That carve-out has been removed. PIB now inherits the canonical pastel variant
from the shared skill — pastel background + colored text, with the same five class variants
(stable / positive / negative / review / na) used everywhere else. Do not re-define
.outlook-badge rules locally and do not emit inline style="..." overrides on outlook
badges. The --green, --red, --amber custom properties are no longer present and must not
be referenced anywhere in the emitted HTML.
Citations (shared)
Before emitting any [n] reference inline, any per-section recap block, or the end-of-document
Citations block, read both:
skills/shared/citations/SKILL.md — authoring rules
(numbering, hyperlinking, source data shape, carve-outs).skills/shared/citations/assets/template.html —
canonical CSS (inside <style id="shared-citations-css">) and literal HTML markup snippets
(inside <template> tags) for inline references, the end-of-document Citations block, and
the optional .section-citations recap.
At emit time, copy the contents (not the wrapper) of <style id="shared-citations-css">
from the shared asset into the parent template's reserved marker region, located inside
assets/template.html between the CSS-comment markers
/* BEGIN shared-citations-css … */ and /* END shared-citations-css */. The parent
template no longer carries duplicated citation CSS — those rules ship only in the shared
asset.
Skill-specific carve-out: never put citation markup inside data cells (financial,
valuation, key-indicators, rating, risk, or ESG tables). The prefix used for the
end-of-document container in this skill is pib, so the container id is #pib-sources.
Per-section recap blocks live in #pib-cite-a … #pib-cite-k, mapped one-to-one to the
eleven report sections in document order:
| Letter | Section |
|---|
a | 1. Company Overview |
b | 2. Business Segments and Operations |
c | 3. Historical Financials |
d | 4. Company Metrics |
e | 5. Peer Comparison and Competitive Landscape |
f | 6. Industry Overview and Trends |
g | 7. Strategic Developments |
h | 8. Management and Governance |
i | 9. Credit Profile |
j | 10. Risks and Challenges |
k | 11. ESG Profile |
Each #pib-cite-{x} should be filled with a single <div class="section-citations">…</div>
recap as defined in the shared skill (.cite-label "Citations" pill plus one .cite-item per
source referenced in that section). The recap re-uses the same global [n] numbering as the
inline references and #pib-sources — it never starts a new sequence. If a section has no
inline citations, leave the corresponding #pib-cite-{x} empty.
Parameters
The user should provide:
- Company Name (required)
- Currency (optional, defaults to USD)
Step 1 — Resolve the target company and peers
Call findEntity with the company name. Store the canonical entity name and ID.
Then call getEntityPeers for the target to get up to 3 peers. Call findEntity
for each peer to resolve their entity IDs.
Step 2 — Read the template
Read assets/template.html (relative to this skill directory) once. Keep its exact structure —
CSS, <head>, hardcoded TOC, section order, table skeletons, row labels, and element IDs — as
the scaffold for the final artifact. Do not copy it to the workspace and do not open it.
Step 3 — Gather all data in parallel
Fire ALL of the following in a single parallel batch. This is the heaviest step — launch
everything at once.
For the target company
| Tool Call | Purpose |
|---|
getCreditOpinion (sections: Profile, Summary, CreditStrengths, CreditChallenges, FactorsLeadingToUpgrade, FactorsLeadingToDowngrade, KeyIndicatorsTable, ScorecardTable, ESGConsiderations) | Credit profile, strengths/challenges, financials, ESG |
getEntityFinancials | Primary source for historical financials (3 full fiscal years + LTM) and valuation table data |
getEntityRatings | Current rating, outlook, historical ratings |
getEntitySectorOutlook | Sector outlook |
searchEntityDocuments with "Credit Opinion" | Credit opinion documents |
searchEntityDocuments with "Business units, Segment Revenue, Profile, Segments, Revenue Drivers" | Business segment data |
searchCompanyFilings with "segment revenue, business segments, revenue by segment" | Per-segment revenue from annual/quarterly filings to populate Business Segments and Operations section |
searchEntityDocuments with "Risk factors, competitive pressures, market volatility, regulatory compliance, litigation" | Risk analysis |
searchEntityDocuments with "Leverage, Debt, Liquidity, Credit Facilities, Coverage, Ratings, Outlook" | Credit profile data |
searchEntityEarningsCall with "Target Market, Services, Products, Mission, Vision, Markets, Geographies, Revenue" | Company overview from earnings call |
searchEntityEarningsCall with "Business units, Segment Revenue, Drivers, Revenue Drivers, Earnings" | Business segments from earnings call |
searchEntityEarningsCall with "Market Size, Growth Rate, Demand, Competition, Market Share, Regulation, Trends" | Industry analysis |
searchEntityEarningsCall with "Share, Stock, Price, Market capitalization, Earnings per share, Dividend, Valuation" | Share price data |
searchEntityEarningsCall with "Risk factors, competitive pressures, market volatility, economic uncertainty" | Risks from earnings call |
searchEntityEarningsCall with "merger, acquisitions, strategic developments, alliances, partnerships" |
For each peer (up to 3 peers)
| Tool Call | Purpose |
|---|
getCreditOpinion (Profile, KeyIndicatorsTable, CreditStrengths, CreditChallenges, FactorsLeadingToUpgrade, FactorsLeadingToDowngrade, ScorecardTable, ESGConsiderations) | Peer comparison data + ESG |
getEntityFinancials | Peer valuation and financial data for Share Price Performance and Valuation section |
getEntityRatings | Peer ratings |
Step 4 — Synthesize + emit the complete artifact
Use Moody's internal research as the primary foundation. Earnings call data and news
supplement. Write in professional credit-research language with numbered citation references
inline in narrative text. The exact inline markup, the URL-less fallback, and the rule that
n matches the row position of the source inside #pib-sources are defined in
skills/shared/citations/SKILL.md — read it before authoring
any [n] reference.
After data is gathered, produce one final assistant message. The message contains:
- A one-line summary sentence (e.g.
Issuer Brief for {Target Company}:).
- A single fenced
```html code block containing the entire filled
template.html document — with every element from the streaming protocol populated in
place. No partial documents, no separate code blocks per section.
The code block must:
- Start at column 0 with
```html and end with a closing ``` on its own line.
- Contain a complete, standalone HTML document (doctype →
</html>) that renders without
external dependencies.
- Preserve the template's
<head> (CSS, fonts), hardcoded TOC, section order, table
skeletons, row labels, and element IDs exactly. Only the empty targets defined below are
populated.
Render order of content inside the code block follows the page top-to-bottom so the artifact
is human-readable as well as browser-renderable.
Cover + footer
#pib-cover-company — plain text, canonical target name.#pib-company — plain text target name.#pib-date — report date, e.g. April 15, 2026.#pib-footer-date — same date string.
Section 1 — Company Overview
-
#pib-overview-kpi — KPI scorecard strip: a row of exactly 4 metric cards rendered as an
inline SVG (width="780" height="90"). Each card shows a metric name (top, small caps) and
value (bottom, bold). Source the four metrics from getEntityFinancials and getEntityRatings:
(1) Revenue (LTM, in billions, e.g. $412.3B), (2) EBITDA Margin (LTM, e.g. 31.2%),
(3) Net Debt / EBITDA (LTM, e.g. 1.8×), (4) Moody's Rating (current long-term rating,
e.g. Aa1). Cards are evenly spaced; use a light #f4f6f9 fill with a #0066cc left-border
accent (4 px). Render inside <div class="chart-container">…</div>.
SVG layout constants: W=780, H=90, 4 cards each cardW=170, gap=16,
total cards span = 4×170 + 3×16 = 728, left offset ox = (780−728)/2 = 26.
Card x for card i (0-indexed) = ox + i×(170+16).
Per card: background <rect> at card x, y=10, w=170, h=70, fill #f4f6f9, rx=4;
accent <rect> at card x, y=10, w=4, h=70, fill #0066cc, rx=2;
label <text> at card x+14, y=32, font-size=10, fill=#6b7280, font-weight=600 (metric name);
value <text> at card x+14, y=58, font-size=20, fill=#00205b, font-weight=700 (metric value).
-
#pib-overview-rating-timeline — Rating upgrade timeline showing Moody's rating history as a
horizontal step-line SVG. Source rating history from getEntityRatings. Constants:
W=780, H=160; padding {top:30, right:30, bottom:50, left:70}; plot area cW=680, cH=80.
X-axis = dates of rating changes (oldest left, most recent right). Y-axis = ordinal rating scale
(map ratings to numeric rank: Aaa=1, Aa1=2, Aa2=3, Aa3=4, A1=5, A2=6, A3=7, Baa1=8, Baa2=9,
Baa3=10, Ba1=11, Ba2=12, Ba3=13, B1=14, B2=15, B3=16, Caa1=17 … show only ratings present
in history on the y-axis). Draw as a step-line: horizontal segment at rating level, then
vertical drop/rise at the change date. Stroke #0066cc, stroke-width=2, fill=none.
Place a filled circle (, fill=) at each rating-change point and a label above
(font-size=10, fill=, font-weight=600) showing the rating symbol.
X-axis labels: year of each change, rotated . Y-axis labels: rating symbols at each
tick. Title: . Render inside .
Section 2 — Business Segments and Operations
Revenue per segment must be sourced exclusively from searchCompanyFilings (annual or
quarterly company filings) to ensure consistency with reported company data. Do not use
earnings call data or Moody's estimates for segment revenue figures.
#pib-segments-intro — one introductory paragraph in <p>…</p>.#pib-segments-pie — revenue-by-segment bar chart rendered as an inline SVG. Constants:
W=600, H=320; padding {top:40, right:20, bottom:80, left:80}; plot area cW=500, cH=200.
Let N = number of segments. bw = min(cW / N × 0.6, 60); gap = (cW − bw × N) / (N + 1).
mx = max(revenue values); yPos(v) = 40 + 200 − (v / mx) × 200.
Bar x for segment i (0-indexed) = 80 + gap × (i + 1) + bw × i.
If you do not have a calculator tool, use bash or Python to compute all of the above values before emitting any SVG — do not attempt to calculate them mentally.
Fill each bar with the palette in index order: #0066cc, #e74c3c, #27ae60, #f39c12, #8e44ad, #16a085.
Emit the revenue value (in the same unit as the pie, e.g. $12.3B or XX%) above each bar,
centred on the bar (text-anchor="middle", font-size=10, fill=#444c58).
Emit the segment name below the x-axis baseline, centred on the bar, rotated -30°
(font-size=10, fill=#444c58).
Draw the x-axis baseline: <line x1="80" y1="240" x2="580" y2="240" stroke="#9aa0ab"/>.
Title: <text x="300" y="24" text-anchor="middle" font-size="12" fill="#00205b" font-weight="700">Revenue by Segment</text>.
Render inside <div class="chart-container">.#pib-segments-list — one <li> per segment. Each <li> must contain a
<strong>Segment Name</strong> header followed by one paragraph of prose describing the
segment's business activities, key products/services, end markets, and revenue contribution.
Revenue figures cited must match those sourced from company filings used in the pie chart.
Structure: <li><strong>Segment Name</strong><p>Description paragraph with revenue context…</p></li>.#pib-segments-outro — one closing paragraph in <p>…</p>.
Section 3 — Historical Financials
ALL numeric values in the financial table MUST be populated exclusively from data returned by
the getEntityFinancials MCP tool. Do not supplement or override table cells with figures
from earnings calls, credit opinions, news, or any other source. If a value is not available in
getEntityFinancials, write "--" in that cell. This ensures every number is factual and
verifiable from Moody's MCP data. Annual columns are limited to exactly 3 full fiscal years (oldest → most recent). Include a single YoY% column calculated only between the last two fully completed years (FY−1 vs FY), and an LTM column. Remove all quarterly columns. The table layout runs left to right as: line items | FY−2 | FY−1 | FY | YoY% (FY vs FY−1) | LTM.
-
#pib-fin-col-1 … #pib-fin-col-5 — period labels. Canonical order: FY−2, FY−1, FY, YoY% (FY vs FY−1), LTM (adapt labels to actual fiscal years, e.g. 2022, 2023, 2024, YoY%, LTM). Do not populate #pib-fin-col-6, #pib-fin-col-7, or #pib-fin-col-8 — leave them empty.
-
#pib-fin-r{1..19}-c{1..5} — per-cell numeric values in millions for columns 1–5. The YoY% column (c4) is computed as (FY value − FY−1 value) / |FY−1 value| × 100, formatted as e.g. +4.2% or −3.1%. Write "--" when the value is zero or unavailable. Never touch the row-label <td> cells. Leave c6, c7, and c8 cells empty.
The financial table must include the following line items in this exact order (map to row IDs r1–r14; leave r15–r19 empty if not applicable):
r1 = Revenue, r2 = Gross Profit, r3 = Operating Profit (EBIT), r4 = Interest Expense,
r5 = Net Income, r6 = Cash & Cash Equivalents, r7 = Total Assets, r8 = Total Liabilities,
r9 = Total Equity, r10 = Cash Flow from Operations, r11 = Capital Expenditures,
r12 = Depreciation & Amortization, r13 = Net Cash from Investing, r14 = Net Cash from Financing.
Leave rows r15–r19 (including the EPS row at r19) empty — do not populate them.
-
#pib-fin-summary — one dense 6–8 sentence paragraph in <p>…</p> integrating revenue,
EBITDA margin, leverage, cash flow, and key operational metrics.
-
#pib-fin-highlights — <ul><li>…</li></ul> bullet points covering headline results vs
guidance, performance drivers, updated guidance, and strategic commentary.
-
#pib-fin-analysis — HTML with subsection headers and dense analytical bullets organised by
Revenue & End-Market Performance, Profitability & Margins, Leverage & Liquidity. Use
<strong class="subsection-title">…</strong> for each sub-heading, followed by
<ul><li>…</li></ul>.
Section 4 — Company Metrics
Note: This section was formerly "Share Price Performance and Valuation." The Monthly Share
Price chart and its analysis, the Peer Share Price chart and its analysis, and the first
valuation table (Market & Price Data) and its analysis have been removed. Do not emit
#pib-shareprice-monthly-chart, #pib-shareprice-monthly-analysis, #pib-shareprice-peer-chart,
#pib-shareprice-peer-analysis, or #pib-val-1-* elements. Leave those IDs empty.
#pib-val-col-1 … #pib-val-col-4 — shared company headers starting from valuation
table 2 (the first remaining table). Target company in column 1. Leave unused columns empty
if fewer than 3 peers.#pib-val-2-col-*, #pib-val-3-col-*, #pib-val-4-col-*, #pib-val-5-col-* — repeat the
same company names across all five valuation tables.#pib-val-{1..5}-r{i}-c{1..4} — per-cell values for the five valuation tables (row labels
are pre-filled). Source valuation data from getEntityFinancials for both the target company
and peer companies to ensure data availability. Use "--" for missing values.#pib-val-{1..5}-analysis — one paragraph each in <p>…</p> comparing target vs peers for
that table. No citation numbers inside the table cells.
Section 5 — Peer Comparison and Competitive Landscape
#pib-peers-intro — one short intro paragraph in <p>…</p>.#pib-peers-table — one <tr> per company (target first):
<tr><td>Target Co</td><td>Description from Credit Opinion Profile…</td></tr>.#pib-peers-rating — one <tr> per company:
<tr><td>Target Co</td><td>Aaa</td><td><span class="outlook-badge stable">Stable</span></td></tr>.#pib-ki-col-1 … #pib-ki-col-4 — reuse the valuation-table company labels.#pib-ki-r{1..8}-c{1..4} — per-cell values (8 metrics × up to 4 companies).
Row labels pre-filled.#pib-peers-conclusion — 1–2 paragraphs in <p>…</p> summarising the target company's quantitative and business-risk differentiation relative to peers and its relative competitive positioning.
Section 6 — Industry Overview and Trends
-
#pib-industry — exactly 3 paragraphs in <p>…</p>, one per subsection, with the subsection title rendered as <strong class="subsection-title">…</strong> before the paragraph text. Cover only these three subsections in order:
(1) Macroeconomic Context — macro conditions affecting the sector;
(2) Industry Size and Growth — market size, growth rates, and key demand drivers;
(3) Industry Outlook and Trends — forward-looking view, emerging trends, and regulatory considerations.
Do not include Sub-Sector and Regional Performance or a standalone Competitive Landscape prose subsection; those are replaced by the Porter's diagram below.
-
#pib-industry-porters — Porter's Five Forces diagram rendered as an inline SVG. Layout: hub-and-spoke with a central box connected by horizontal/vertical lines to four surrounding boxes. Positions:
- Centre:
cx=370, cy=200 — Competitive Rivalry (assessed intensity)
- Top:
cx=370, cy=40 — New Entrants
- Bottom:
cx=370, cy=360 — Substitutes
- Left:
cx=100, cy=200 — Supplier Power
- Right:
cx=640, cy=200 — Buyer Power
Each box is w=180, h=60, centred on its cx/cy. Draw connector lines from the edge of the centre box to the nearest edge of each surrounding box (straight horizontal or vertical lines, stroke=#9aa0ab, stroke-width=1.5).
Colour-code each box by assessed intensity based on gathered data:
- High → fill=
#ffe4e6, stroke=#e74c3c, title-color=#b91c1c
- Medium → fill=
#fef9c3, stroke=#f39c12, title-color=#92400e
- Low → fill=
#dcfce7, stroke=#27ae60, title-color=#166534
Each box contains two <text> lines: (1) force name, font-size=11, font-weight=700, fill=title-color; (2) intensity label (e.g. "High", "Medium", "Low"), font-size=10, fill=#444c58.
Section 7 — Strategic Developments
28b. #pib-strategy-timeline — horizontal timeline SVG rendered inline, listing all strategic events from the past 12 months in chronological order (oldest left → most recent right). Constants: W=740, H=120. Draw a horizontal baseline at y=60 from x=40 to x=700 (stroke=#9aa0ab, stroke-width=1.5). For each event place a filled circle (r=5, fill=#0066cc) on the baseline at its proportional date position; a short vertical stem (stroke=#0066cc, stroke-width=1) rising to y=36; and a <text> label above the stem (text-anchor="middle", font-size=9, fill=#00205b, font-weight=600) showing a 2–3 word title on one line and the date (YYYY-MM-DD) on the next line (dy=+11). Below the baseline add a <text> at y=80 per event showing the year tick mark if space permits. Title: <text x="370" y="14" text-anchor="middle" font-size="11" fill="#00205b" font-weight="700">Strategic Developments Timeline</text>. Render inside <div class="chart-container">.
#pib-strategy-list — one <li> per development from the past 12 months (same events as the timeline):
<li><strong>Title</strong>: 2026-01-15 — description with citation <a href="…" target="_blank" class="cite-ref">[3]</a>.</li>.
Cover M&A, partnerships, strategic shifts, capital allocation.
Section 8 — Management and Governance
-
#pib-mgmt-cards — a row of name cards rendered as an inline SVG showing key executives and directors from getEntityManagersDirectors. Each card is w=160, h=70, spaced 12px apart, with fill=#f4f6f9, stroke=#d1d5db, rx=4. Each card shows: (1) person's name (font-size=11, font-weight=700, fill=#00205b); (2) their position/title (font-size=9, fill=#6b7280). Lay out cards in rows of up to 4; compute SVG height dynamically (rows × 82 + 20). SVG width=700. Render inside <div class="chart-container">.
-
#pib-mgmt — 1–2 paragraphs in <p>…</p> summarising the leadership team's experience and strategic focus, board governance structure, and any notable recent governance changes or leadership transitions. Normal text only; no subsection headers.
Section 9 — Credit Profile
#pib-credit-analysis — 1–2 paragraphs in <p>…</p> covering the key aspects of the debt profile, leverage trends, maturity schedule, liquidity position, and credit ratings.#pib-credit-chart — one inline <svg> (see Debt Maturity template). Data for this
chart must come from searchCompanyFilings; use the actual future calendar-year debt
obligation periods as reported in the filing's maturity schedule.#pib-rating-table — one <tr> per rating class:
<tr><td>Senior Unsecured - Fgn Curr</td><td>Aaa</td><td><span class="outlook-badge stable">Stable</span></td><td>2024-11-20</td></tr>.
Section 10 — Risks and Challenges
#pib-risks-narrative — 1–2 paragraphs in <p>…</p> summarising the current key risks and challenges facing the company, spanning market/competitive, operational, regulatory, and technology dimensions.#pib-risk-table — 5–7 <tr>s:
<tr><td>Market & Competitive</td><td>Description…</td><td>Impact…</td><td>Mitigation…</td></tr>.
No citation numbers inside cells.
Section 11 — ESG Profile
-
#pib-esg-kpi — a row of exactly 4 metric cards rendered as an inline SVG (width="780" height="90"). The four cards are: (1) Overall CIS Score, (2) Environmental (E) Score, (3) Social (S) Score, (4) Governance (G) Score. Source all four scores from getCreditOpinion (ESGConsiderations section). Use the same card layout as the KPI scorecard strip in Section 1 (same SVG layout constants: cardW=170, gap=16, ox=26; #f4f6f9 fill, #0066cc left-border accent). Render inside <div class="chart-container">.
-
#pib-esg-narrative — three short paragraphs in <p>…</p>, one per ESG dimension:
(1) Environmental — key environmental initiatives, risks, and performance;
(2) Social — social policies, workforce practices, and community impact;
(3) Governance — governance structure, board practices, and oversight quality.
Use <strong class="subsection-title">…</strong> before each paragraph.
-
#pib-esg-r{1..3}-focus / #pib-esg-r{1..3}-score — category-row cells (Environmental,
Social, Governance rows are pre-labelled). Focus is a short text; score is the Moody's
ESG score (e.g. E-3). No citations inside cells.
Citations
#pib-sources — end-of-document Citations rows. One <div class="source-item"> per
source, in [1], [2], … order. Use the canonical row markup defined in
skills/shared/citations/SKILL.md. Numbering must match
inline [n] references.
Step 5 — Present the report to the user
⚠️ CRITICAL — THIS STEP MUST NEVER BE SKIPPED
After the ```html code block, add a single short sentence confirming the artifact is
complete (e.g. Artifact rendered above — the report is fully self-contained HTML.). Do not
write the artifact to disk and do not suggest shell commands. The code block itself is the
deliverable.
Use whatever tool is available in your current environment to present or display the final report to the user (e.g. a file presenter, inline renderer, or widget) at the end of running the skill.
Streaming protocol (element → content)
| Element ID | Content type |
|---|
#pib-cover-company, #pib-company, #pib-date, #pib-footer-date | Plain text |
#pib-overview-kpi | One inline <svg> — KPI scorecard strip (4 metric cards) |
#pib-overview-rating-timeline | One inline <svg> — Moody's rating history step-line |
#pib-overview, #pib-mgmt | <p>…</p> paragraphs (with subsection titles where noted) |
#pib-segments-intro, #pib-segments-outro, #pib-peers-intro, #pib-peers-conclusion, #pib-fin-summary, #pib-fin-analysis, #pib-val-{2..5}-analysis, #pib-credit-analysis, #pib-risks-narrative, #pib-esg-narrative, #pib-industry | <p>…</p> paragraphs |
#pib-fin-highlights | <ul><li>…</li></ul> |
#pib-segments-list | One <li> per segment (with <strong> header + prose paragraph) |
#pib-strategy-list | One <li> per development |
#pib-strategy-timeline | One inline <svg> — horizontal event timeline |
#pib-mgmt-cards | One inline <svg> — name cards grid |
#pib-esg-kpi | One inline <svg> — 4 ESG metric cards |
#pib-industry-porters | One inline <svg> — Porter's Five Forces hub-and-spoke diagram |
#pib-fin-col-{1..5} | Plain text period label (FY−2, FY−1, FY, YoY%, LTM) |
Fixed 4-company layout: valuation tables and the key-indicators table assume target + up to
3 peers (4 columns). If fewer than 3 peers are available, leave unused column header / cell IDs
empty — do not collapse or restructure the tables.
Reference markup snippets
Pre-filled row-label cells are never changed from the template. Only the empty data cells are
populated:
<tr><td class="row-label">Total debt</td><td id="pib-fin-r14-c1"></td>…</tr>
<tr><td>Target Co</td><td>Description from Credit Opinion Profile…</td></tr>
<tr><td>Target Co</td><td>Aaa</td><td><span class="outlook-badge stable">Stable</span></td></tr>
<tr><td>Senior Unsecured - Fgn Curr</td><td>AaaStable2024-11-20
Market CompetitiveDescription…Impact…Mitigation…
iPhoneThe iPhone segment encompasses Apple's line of smartphones running iOS. It is the company's largest revenue contributor, generating $209,586.0m (50.4% of total revenue) in FY2024 as reported in the annual filing. The segment benefits from strong brand loyalty, a growing services attach rate, and continued premium pricing power across global markets.
Title: 2026-01-15 — description of the development with citation [3].
For #pib-sources source-item rows, use the canonical row markup defined in
skills/shared/citations/SKILL.md.
SVG chart templates
Palette (indexed, target = first): #0066cc, #e74c3c, #27ae60, #f39c12, #8e44ad, #16a085.
Every chart is wrapped in <div class="chart-container">…</div> so the existing CSS applies.
KPI Scorecard Strip (#pib-overview-kpi)
See layout constants defined in Section 1, item 5 above. Four metric cards rendered inline.
Rating History Step-line (#pib-overview-rating-timeline)
See layout constants defined in Section 1, item 6 above. Horizontal step-line chart sourced
from getEntityRatings.
Revenue by Segment Bar Chart (#pib-segments-pie)
See layout constants defined in Section 2, item 9 above. Data sourced exclusively from
searchCompanyFilings.
Debt Maturity (#pib-credit-chart)
⚠️ MANDATORY DATA REQUIREMENT — NO ESTIMATION PERMITTED
searchCompanyFilings MUST be called with a query targeting the debt maturity schedule
(e.g. "long-term debt maturities schedule obligations") before this chart can be emitted.
This is a required tool call — it cannot be skipped, inferred from total debt figures, or
substituted with data from any other source.
- NEVER estimate, split, distribute, or approximate maturity amounts from aggregate debt.
- NEVER construct buckets from total debt divided by assumed years.
- If
searchCompanyFilings does not return an explicit per-year maturity schedule, leave
#pib-credit-chart empty and omit the chart entirely. Do not render a chart with
fabricated values.
Source data exclusively from searchCompanyFilings (annual reports, 10-K, or debt/liquidity
footnotes) — do not use Moody's estimates or earnings call figures for maturity amounts.
Build the chart using future debt obligation periods as reported in the filing's debt
maturity schedule. Use the actual future years (e.g. 2025, 2026, 2027, 2028, 2029, Thereafter)
rather than generic buckets; drop any year with zero obligations before computing layout.
Bar chart. Constants:
W=700, H=250; padding {top:20, right:20, bottom:60, left:70}; plot area cW=610, cH=170.- Buckets: use the actual future calendar years from the filing's debt maturity schedule (e.g.
2025, 2026, 2027, 2028, 2029, Thereafter). Drop any year whose value is 0 before
computing layout. Let N = remaining bucket count.
bw = min(cW / N × 0.6, 50); gap = (cW − bw × N) / (N + 1).mx = max(values); yPos(v) = 20 + 170 − (v / mx) × 170.- Bar
x for bucket i = 70 + gap × (i + 1) + bw × i.
- Fill bars with
#0066cc. Emit the value above each bar as {v}B (right-aligned to the bar
centre) and the label below rotated -25°.
- Title
<text x="350" y="14" text-anchor="middle" font-size="12" fill="#00205b" font-weight="700">Debt Maturity Profile (USD-Billion)</text>.
<div class="chart-container">
<svg width="700" height="250" viewBox="0 0 700 250" xmlns="http://www.w3.org/2000/svg">
<text x="350" y="14" text-anchor="middle" font-size="12" fill="#00205b" font-weight="700">Debt Maturity Profile (USD-Billion)</text>
<line x1="70" y1="190" x2="680" y2="190" stroke="#9aa0ab"/>
<rect x="{bx}" y="{yPos(v)}" width="{bw}" height="{190 − yPos(v)}" fill="#0066cc"/>
<text x="{bx + bw/2}" = = = =>{v}B
{label}
Class-selection rules
outlook-badge variants: stable / positive / negative / review / na (canonical
pastel set defined by the shared template skill). Map by outlook text:
Stable → stable, Positive → positive, Negative → negative,
Review for Upgrade / Review for Downgrade / RUR → review. If the outlook is missing
or unknown, use na (renders as muted gray) — do not default to stable.subsection-title on a <strong> is the canonical way to render a sub-heading inside a
section-content block.
Tips
- Run ALL research searches in a single parallel batch to minimize latency.
- No estimated or approximated numbers anywhere in the report. Every figure in tables,
charts, KPI cards, and prose must come directly from a tool response. If a value is not
available from the data gathered, use
"--". Never use ~, approx., or any similar
qualifier. See the CRITICAL no-estimation block above for full rules.
searchCompanyFilings is a required call for the debt-maturity chart and the segment
revenue bar chart. These charts must not be rendered without it. If the filing search does
not return the required per-year schedule or segment breakdown, leave the chart container
empty rather than fabricate values.- Target company appears first in every table and comparison; across valuation / key-indicators
tables, reuse the same company labels in columns 1–4.
- Financial table values are in millions; use
"--" for zero or unavailable. Never hide a row.
- Historical-financials analysis must include specific numbers for every claim.
- Emit each chart SVG directly into its container inside the artifact — the template does not
render charts at load time. Use the reference templates + palette above.
- KPI scorecard and rating timeline SVGs go in
#pib-overview-kpi and
#pib-overview-rating-timeline before #pib-overview prose in Section 1.
- The segment pie chart (
#pib-segments-pie) goes between #pib-segments-intro and
#pib-segments-list in Section 2. Revenue data must match filings.
- For the debt-maturity chart, source future obligation amounts from
searchCompanyFilings and
use actual calendar years as x-axis labels. Drop any year whose value is 0 (do not emit a
<rect> for it). Filter buckets before computing bar positions.
- Section 4 is now "Company Metrics". Do not emit
#pib-shareprice-monthly-chart,
#pib-shareprice-monthly-analysis, #pib-shareprice-peer-chart, #pib-shareprice-peer-analysis,
or #pib-val-1-* elements. Start valuation tables from #pib-val-2-*.
- If fewer than 3 peers are returned, leave unused valuation / key-indicators column headers
and cells blank. Do not attempt to collapse the tables.
- Citation references
[n] are used inline throughout narrative text per
. Never put citation markup
inside table cells (financial / valuation / key-indicators / rating / risk / ESG).
