[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79ERP7YCFB2R7ZQ18PXVG4M":3,"skill-same:01M79ERP7YCFB2R7ZQ18PXVG4M":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M79ERP7YCFB2R7ZQ18PXVG4M","moody-s-sector-brief",null,"Produce a Sector Brief HTML report for any industry sector using Moody's GenAI MCP tools and web research. Use this skill whenever the user asks to analyze a sector, write a sector report, do an industry analysis, create a sector overview, or generate a sector deep-dive. Trigger even if they just name a sector and mention \"analysis\", \"overview\", \"outlook\", \"report\", or \"deep-dive\". Also trigger for phrases like \"what's happening in the retail sector\" or \"give me a sector breakdown for aerospace\".","zfifteen\u002Fskills-catalog","zfifteen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F221906715?v=4","01M79CQFXDZM5J5CJTCECPFA66","Dionisio Alberto Lopez III","01M79CQFY4C62PN8A2T5KDAHGA",1,"MIT","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fmoody-s-sector-brief\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: moody-s-sector-brief\ndescription: >\n  Produce a Sector Brief HTML report for any industry sector using Moody's GenAI MCP tools\n  and web research. Use this skill whenever the user asks to analyze a sector, write a sector\n  report, do an industry analysis, create a sector overview, or generate a sector deep-dive.\n  Trigger even if they just name a sector and mention \"analysis\", \"overview\", \"outlook\", \"report\",\n  or \"deep-dive\". Also trigger for phrases like \"what's happening in the retail sector\" or\n  \"give me a sector breakdown for aerospace\".\n---\n\n# Sector Brief Skill\n\nGenerates a professional HTML report (styled like a Moody's sector brief document) for a\nspecified industry sector. The report is research-heavy and text-driven, combining Moody's\ninternal research with supplemental web data across six structured sections plus an executive\nsummary and citations.\n\nThe workflow is **single-artifact streaming**: gather all data, then stream the entire filled\nHTML document back to the user as one ` ```html ` fenced code block in the final assistant\nmessage. No file copy, no `open` step, no progressive `StrReplace` edits, no JSON payload, and no\nclient-side render logic. The fenced code block is the deliverable.\n\n> ## ⚠️ CRITICAL — NON-NEGOTIABLE OUTPUT CONTRACT\n>\n> **The LLM MUST deliver the report as a single HTML artifact in the assistant response.** Specifically:\n>\n> - The final message **MUST** contain exactly one ` ```html ` fenced code block holding the **complete, standalone HTML document** (`\u003C!doctype html>` → `\u003C\u002Fhtml>`), every section populated inline.\n> - The LLM **MUST NOT** write to disk, split across messages\u002Fblocks, or substitute prose, Markdown, JSON, or links for the artifact.\n> - If data partially fails, emit the artifact with `\"Data unavailable\"` placeholders — never skip it.\n>\n> Treat any other output shape as a hard failure of the skill.\n\n## Required MCP server\n\n`Moodys MCP server` — tools used: `searchEntityDocuments` (sector research), `getEntitySectorOutlook`,\n`searchNews`, `findEntity`\n\nWeb research is also required via `searchNews` or general web search tools.\n\nIf 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:\u002F\u002Fwww.moodys.com\u002Fweb\u002Fen\u002Fus\u002Fcapabilities\u002Fgen-ai\u002Fai-ready-data.html with us to learn more.\n\n## Bundled files\n\n- `assets\u002Ftemplate.html` — pre-styled scaffold with the Moody's cover, a baked-in static 6-item\n  table of contents, and empty fill-in targets (cover title, date, section-content divs, sources\n  container). Treat this file as the **read-only structural reference**: read it, fill it in\n  mentally, and emit the complete filled document in the final response.\n\n## Template (shared)\n\nBefore emitting the HTML report, **read both**:\n1. [`skills\u002Fshared\u002Ftemplate\u002FSKILL.md`](..\u002Fshared\u002Ftemplate\u002FSKILL.md) — authoring rules (which\n   classes \u002F snippets are owned by the shared layer, allowed per-skill overrides, outlook-badge\n   usage).\n2. [`skills\u002Fshared\u002Ftemplate\u002Fassets\u002Ftemplate.html`](..\u002Fshared\u002Ftemplate\u002Fassets\u002Ftemplate.html) —\n   canonical CSS (inside `\u003Cstyle id=\"shared-template-css\">`) and literal HTML markup snippets\n   (inside `\u003Ctemplate>` tags) for the document head, cover, TOC, section block, sources-section\n   wrapper, footer, and outlook-badge.\n\n**Always check the shared template before inventing** any class, token, scaffold, or design element. Do not restyle anything the shared skill owns. At emit time, copy the **contents** of `\u003Cstyle id=\"shared-template-css\">` into the marker region `\u002F* BEGIN shared-template-css ... *\u002F` … `\u002F* END shared-template-css *\u002F`. Use literal markup from the matching `\u003Ctemplate>` snippets for all HTML chrome.\n\nThis skill uses the **`cover-simple`** variant with no skill-specific CSS overrides (inherits `body { font-size: 13px }` and `.page { max-width: 900px }`). Outlook-badge usage must use canonical pastel variants (`stable` \u002F `positive` \u002F `negative` \u002F `review` \u002F `na`) — no solid-fill or inline-color overrides.\n\n## Citations (shared)\n\nBefore emitting any `[n]` reference inline or the end-of-document Citations block, **read both**:\n1. [`skills\u002Fshared\u002Fcitations\u002FSKILL.md`](..\u002Fshared\u002Fcitations\u002FSKILL.md) — authoring rules\n   (numbering, hyperlinking, source data shape, carve-outs).\n2. [`skills\u002Fshared\u002Fcitations\u002Fassets\u002Ftemplate.html`](..\u002Fshared\u002Fcitations\u002Fassets\u002Ftemplate.html) —\n   canonical CSS (inside `\u003Cstyle id=\"shared-citations-css\">`) and literal HTML markup snippets\n   (inside `\u003Ctemplate>` tags) for inline references and the end-of-document Citations block.\n\nAt emit time, copy the **contents** of `\u003Cstyle id=\"shared-citations-css\">` into the marker region `\u002F* BEGIN shared-citations-css … *\u002F` … `\u002F* END shared-citations-css *\u002F`.\n\nThe prefix used for the end-of-document container in this skill is `sa`, so the container id\nis `#sa-sources`. This skill does not use the optional per-section `.section-citations` recap\ncomponent.\n\n## Parameters\n\nThe user should provide:\n- **Sector** (required — e.g., \"Retail & Apparel\", \"Aerospace\u002FDefense\", \"Banking\")\n\nIf the user specifies a sub-sector like \"Luxury Retail\", use it as-is for focused analysis.\n\n---\n\n## Step 0 — Sector Picker (run before anything else)\n\nIf the user has not named a specific sector in their message, **stop** and call\n`ask_user_input_v0` with a single `single_select` question before proceeding. Do **not**\nbegin any research or template reading until the sector is confirmed.\n\n**Preamble:** \"Which Moody's-covered sector would you like to analyze? Select one below\nand I'll generate the full report.\"\n\n**Options:**\n\n- Aerospace & Defense\n- Automotive Manufacturing\n- Banking — Global\n- Building Materials & Construction\n- Chemicals\n- Commercial Real Estate & REITs\n- Consumer Products\n- Diversified Manufacturing\n- Food & Beverage\n- Forest Products & Paper\n- Gaming & Lodging\n- Healthcare — Hospitals & Health Systems\n- Healthcare — Medical Devices & Technology\n- Healthcare — Pharmaceuticals\n- Infrastructure & Project Finance\n- Insurance\n- Media & Entertainment\n- Metals & Mining\n- Oil & Gas — E&P\n- Oil & Gas — Integrated & Refining\n- Oil & Gas — Midstream & Pipeline\n- Packaging\n- Retail & Apparel\n- Shipping & Ports\n- Steel\n- Structured Finance — ABS\u002FRMBS\u002FCMBS\n- Technology — Hardware & Semiconductors\n- Technology — Software & Services\n- Telecommunications\n- Transportation & Logistics\n- Utilities — Electric\n- Utilities — Gas Distribution\n- Utilities — Water\n\nOnce the user selects, treat their choice exactly as if they had typed\n`Run a sector brief for {selected sector}` and continue from Step 1.\n\nIf the user already named a sector, **skip this step entirely** and go straight to Step 1.\n\n---\n\n## Step 1 — Read the template\n\nRead `assets\u002Ftemplate.html` (relative to this skill directory) once. Keep its exact structure —\nCSS, `\u003Chead>`, cover, hardcoded TOC, section order, and element IDs — as the scaffold for the\nfinal artifact. Do **not** copy it to the workspace and do **not** open it.\n\n---\n\n## Step 2 — Research phase (parallel)\n\nFire ALL of the following searches in a **single parallel batch**:\n\n### Moody's internal research (via MCP)\n\n| Search | Purpose |\n|--------|---------|\n| `searchEntityDocuments` with criteria: \"{Sector} Sector Overview\" | Sector definition, methodology, key activities |\n| `searchEntityDocuments` with criteria: \"Economic factors impact on {Sector} Sector\" | Macro-economic context |\n| `searchEntityDocuments` with criteria: \"{Sector} Sector, industry\" | Financial performance data |\n| `searchEntityDocuments` with criteria: \"{Sector} Sector Risk and challenges\" | Risk analysis |\n| `searchEntityDocuments` with criteria: \"{Sector} sector Outlook\" | Sector outlook |\n| `getEntitySectorOutlook` for a major company in the sector | Formal Moody's outlook |\n\n### Web research (via searchNews or web tools)\n\n| Search | Purpose |\n|--------|---------|\n| \"Key players from {Sector} industry, market share, roles\" | Key players for overview |\n| \"Key regions of activity and growth markets for {Sector} sector\" | Geographic scope |\n| \"{Sector} sector aggregate revenue, profit margins, return on equity\" | Financial metrics |\n| \"Major companies from {Sector} sector benchmark comparison\" | Industry structure and dynamics |\n\n---\n\n## Step 3 — Synthesize all sections\n\nUse Moody's internal research as the **primary foundation** for every section. Web sources\nserve only to supplement gaps or validate findings. When conflicts arise, prioritize Moody's\nunless external data provides substantial evidence for reconsideration.\n\nWrite in professional credit-research language. Always attribute sources with numbered citation\nreferences inline. The exact inline markup, the URL-less fallback, and the rule that `n`\nmatches the row position of the source inside `#sa-sources` are defined in\n[skills\u002Fshared\u002Fcitations\u002FSKILL.md](..\u002Fshared\u002Fcitations\u002FSKILL.md).\n\n### Executive Summary\n\nWrite after all other sections are complete. Half-page maximum. Highlight the most relevant\ndata from each section. No bullet points — flowing paragraphs only.\n\n### Section 1: Sector Overview\n\nFour subsections:\n1. **Description of the Sector** — Define the industry, key activities, product\u002Fservice\n   categories, and business-model differences\n2. **Market Size and Growth Trends** — Current market size (revenue, volume), historical\n   growth rates, regional growth data\n3. **Key Players** — Major companies, market share, roles within the sector\n4. **Geographic Scope** — Key regions of activity, potential growth markets,\n   region-specific trends\n\n### Section 2: Macro-Economic Context\n\nThree subsections:\n1. **Economic Indicators** — How GDP growth, inflation, interest rates, consumer\n   spending\u002Fconfidence impact the sector\n2. **Regulatory Environment** — Laws, regulations, compliance risks, tariff\u002Ftrade policy\n3. **Global Trends and External Factors** — Geopolitical issues, trade policies,\n   technological disruptions, channel evolution\n\n### Section 3: Financial Performance Analysis\n\nThree subsections with **mandatory quantitative data**:\n1. **Sector-Level Financial Metrics** — Aggregate revenue, profit margins, return on\n   equity, other key metrics. Every metric must include the actual number (e.g., \"Aggregate\n   revenue of $35.2 trillion in 2025\") followed by analytical commentary\n2. **Historical Trends** — Past performance trends, demand\u002Fearnings trajectories,\n   recent growth rates\n3. **Projected Financial Outlook** — Forecast key metrics, earnings outlook, key drivers\n   shaping the near-term, structural offsets and strategic responses\n\n### Section 4: Industry Structure and Dynamics\n\nFour subsections:\n1. **Main Participants** — Benchmark major companies, roles, market share, significance\n2. **Supply Chain Analysis** — Suppliers, manufacturers, distributors, customers,\n   key pressure points\n3. **Competitive Landscape** — Porter's Five Forces analysis with Moody's-grounded\n   commentary for each force (use ratings High \u002F Moderate \u002F Low for each force)\n4. **Barriers to Entry** — Capital requirements, regulatory hurdles, technology\n   requirements, market saturation\n\n### Section 5: Risks and Challenges\n\nFive subsections:\n1. **Operational Risks** — Supply chain disruptions, labor shortages, working capital\n2. **Regulatory Risks** — Compliance requirements, policy changes, tariff exposure\n3. **Market Risks** — Demand volatility, competition, pricing, category weakness\n4. **Financial Performance and Capital Structure** — Refinancing risk, default outlook,\n   margin pressure, deleveraging\n5. **Environmental and Social Risks** — ESG considerations, climate risk, social\u002Fgovernance\n   pressures\n\n### Section 6: Sector Outlook\n\nState the Moody's outlook (Positive, Stable, Negative) and date. Then provide 2-3\nwell-developed paragraphs explaining the rationale — primary drivers, regional nuances,\nkey factors and considerations. All paragraph form, no bullet points.\n\n### Sources\n\nCollect all sources. The source data shape (`id`, `title`, `source`, `date`, `url`) and the\nend-of-document Citations row markup are defined in\n[skills\u002Fshared\u002Fcitations\u002FSKILL.md](..\u002Fshared\u002Fcitations\u002FSKILL.md).\n\n---\n\n## Inline SVG Charts — Section Instructions\n\nAfter synthesizing each of the following sections, embed one inline SVG chart directly in the section content at the position indicated. All charts must be self-contained (no external scripts or stylesheets), include a `\u003Ctitle>` element for accessibility, and use `font-family: 'Source Sans Pro', Arial, sans-serif` inside an embedded `\u003Cstyle>` block.\n\n### Section 3 — Financial Performance Analysis\n\nInsert **Chart A** immediately after the Historical Trends subsection prose:\n\n- Type: grouped bar chart (revenue) with a right-axis line series (EBITDA margin %)\n- X-axis: fiscal years (last 3–5 years); left Y-axis: revenue ($B or $T); right Y-axis: margin (%)\n- Bar color: `#003087`; line color: `#0073CF`\n- `viewBox=\"0 0 700 320\"`\n\n### Section 4 — Industry Structure and Dynamics\n\nInsert **Chart C** immediately after the Porter's Five Forces prose:\n\n- Type: horizontal scored bar chart, one bar per force (5 bars)\n- Map ratings to scores: High = 3, Moderate = 2, Low = 1; scale bar lengths to a 1–3 axis\n- Bar colors: High = `#C0392B`, Moderate = `#E67E22`, Low = `#27AE60`\n- `viewBox=\"0 0 700 220\"`\n\n### Section 6 — Sector Outlook\n\nInsert **Chart D** immediately after the outlook paragraphs:\n\n- Type: horizontal three-zone sentiment track (Negative | Stable | Positive) with a triangular marker at the current outlook position\n- Zone colors: Negative = `#C0392B`, Stable = `#2980B9`, Positive = `#27AE60`; marker color matches active zone\n- Label the current outlook and date below the track\n- `viewBox=\"0 0 700 120\"`\n\n### Pre-computation requirement — mandatory, no exceptions\n\nBefore writing any SVG `x`, `y`, `width`, `height`, or `points` attribute, compute every value via bash or Python — do not calculate mentally. Record and verify computed values, then substitute into the SVG markup.\n\nIf source data for any chart is unavailable, emit a `\u003Cp>Chart data unavailable\u003C\u002Fp>` placeholder — never omit silently.\n\n---\n\n## Step 4 — Stream the complete HTML artifact\n\nAfter all sections are synthesized, produce **one** final assistant message. The message contains:\n\n1. A one-line summary sentence (e.g. `Sector Brief for {Sector}:`).\n2. A single fenced ` ```html ` code block containing the **entire filled `template.html`\n   document** — with every element from the streaming protocol populated in place. No partial\n   documents, no separate code blocks per section.\n\nThe code block **must**:\n\n- Start at column 0 with ` ```html ` and end with a closing ` ``` ` on its own line.\n- Contain a complete, standalone HTML document (doctype → `\u003C\u002Fhtml>`) that renders without\n  external dependencies.\n- Preserve the template's `\u003Chead>` (CSS, fonts), cover, hardcoded TOC, section order, and\n  element IDs exactly. Only the empty targets defined below are populated.\n\n### Cover + footer\n\n1. `#sa-cover-title` — `\u003Cstrong>{Sector}\u003C\u002Fstrong>\u003Cbr>Analysis` (HTML, not plain text).\n2. `#sa-date` — report date string, e.g. `April 15, 2026`.\n3. `#sa-footer-date` — same date string.\n\n### Section headings\n\n4. `#sa-overview-title` — override the default \"Sector Overview\" with\n   `{Sector} — Sector Overview`.\n\n### Section content targets\n\nEach of the following divs takes fully-authored HTML (`\u003Cp>`, `\u003Cul>\u003Cli>`, and\n`\u003Cstrong class=\"subsection-title\">…\u003C\u002Fstrong>` only — no other block tags):\n\n5. `#sa-exec` — Executive Summary. Flowing paragraphs only, no bullets.\n6. `#sa-overview` — Section 1 body with four `\u003Cstrong class=\"subsection-title\">` subheaders.\n7. `#sa-macro` — Section 2 body with three subheaders.\n8. `#sa-financial` — Section 3 body with three subheaders. Every metric must include a\n   concrete number.\n9. `#sa-structure` — Section 4 body with four subheaders. Porter's Five Forces must use\n   High \u002F Moderate \u002F Low ratings per force.\n10. `#sa-risks` — Section 5 body with five subheaders.\n11. `#sa-outlook` — Section 6 body. Lead with the Moody's outlook (Positive \u002F Stable \u002F\n    Negative) and date, then 2–3 paragraphs. Paragraph form only.\n\n### Sources container\n\n12. `#sa-sources` — end-of-document Citations rows. One `\u003Cdiv class=\"source-item\">` per\n    source, in ascending `id` order, using the canonical row markup defined in\n    [skills\u002Fshared\u002Fcitations\u002FSKILL.md](..\u002Fshared\u002Fcitations\u002FSKILL.md). Apply that file's rules\n    for URL-less rows and missing `source`\u002F`date` fields.\n\n### HTML conventions\n\n- Use `\u003Cp>` for paragraphs.\n- Use `\u003Cul>\u003Cli>…\u003C\u002Fli>\u003C\u002Ful>` for bullet points (nested `\u003Cul>` for sub-bullets).\n- Use `\u003Cstrong class=\"subsection-title\">Subheader\u003C\u002Fstrong>` for subsection headers within\n  each section. Do not repeat the top-level section title — the template already renders it.\n- Emit inline citations per\n  [skills\u002Fshared\u002Fcitations\u002FSKILL.md](..\u002Fshared\u002Fcitations\u002FSKILL.md).\n- Escape any `&`, `\u003C`, `>` that appear in the narrative (`&amp;`, `&lt;`, `&gt;`).\n\n---\n\n## Tips\n\n- Run ALL research searches in a single parallel batch.\n- Moody's data is the foundation — web data supplements. Attribute external sources explicitly.\n- The executive summary should be written last, after all other sections are synthesized.\n- Citations follow the shared citations skill — read\n  [skills\u002Fshared\u002Fcitations\u002FSKILL.md](..\u002Fshared\u002Fcitations\u002FSKILL.md) before authoring any `[n]`\n  reference or the Citations block.\n\n---\n\n## Negative number formatting\n\nUse `(-X)` for ALL negatives: `(-9%)`, `(-1.2pp)`, `(-$3.4B)`, `(-250 bps)`. Never use bare minus (`-9%`), en-dash (`–9%`), or parentheses without minus (`(9%)`). Apply to growth rates, margin changes, YoY deltas, and negative monetary values.\n\n---\n\n## Output and presentation (required final steps)\n\nAfter assembling the report, you MUST follow this exact delivery sequence. Do not skip steps\nand do not substitute alternatives. When updating this skill, do not delete or modify any\nother file in the `skills\u002Fsector-brief\u002F` folder.\n\n1. **Write the HTML file in a single call.** Call `create_file` to write the entire HTML to\n   `\u002Fmnt\u002Fuser-data\u002Foutputs\u002F{sector_slug}_sector_analysis.html` in **one** call.\n   `{sector_slug}` is the lowercased, hyphenated sector name (e.g. `retail-apparel`,\n   `oil-gas`).\n2. **Preview the file.** Immediately after, 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.\n3. **Show the widget.** Call `visualize:show_widget` to surface the rendered report visually\n   to the user.\n4. **One short follow-up sentence in chat.** Write a single brief sentence acknowledging the\n   report is ready. Nothing more.\n\n**Strict prohibitions:**\n\n- **Never** emit the HTML as a fenced code block in the chat response.\n- **Never** inline the HTML, JSON payload, or large excerpts of the report body in the chat\n  message.\n","# Sector Brief Skill\n\nGenerates a professional HTML report (styled like a Moody's sector brief document) for a\nspecified industry sector. The report is research-heavy and text-driven, combining Moody's\ninternal research with supplemental web data across six structured sections plus an executive\nsummary and citations.\n\nThe workflow is **single-artifact streaming**: gather all data, then stream the entire filled\nHTML document back to the user as one ` ```html ` fenced code block in the final assistant\nmessage. No file copy, no `open` step, no progressive `StrReplace` edits, no JSON payload, and no\nclient-side render logic. The fenced code block is the deliverable.\n\n> ## ⚠️ CRITICAL — NON-NEGOTIABLE OUTPUT CONTRACT\n>\n> **The LLM MUST deliver the report as a single HTML artifact in the assistant response.** Specifically:\n>\n> - The final message **MUST** contain exactly one ` ```html ` fenced code block holding the **complete, standalone HTML document** (`\u003C!doctype html>` → `\u003C\u002Fhtml>`), every section populated inline.\n> - The LLM **MUST NOT** write to disk, split across messages\u002Fblocks, or substitute prose, Markdown, JSON, or links for the artifact.\n> - If data partially fails, emit the artifact with `\"Data unavailable\"` placeholders — never skip it.\n>\n> Treat any other output shape as a hard failure of the skill.\n\n## Required MCP server\n\n`Moodys MCP server` — tools used: `searchEntityDocuments` (sector research), `getEntitySectorOutlook`,\n`searchNews`, `findEntity`\n\nWeb research is also required via `searchNews` or general web search tools.\n\nIf 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:\u002F\u002Fwww.moodys.com\u002Fweb\u002Fen\u002Fus\u002Fcapabilities\u002Fgen-ai\u002Fai-ready-data.html with us to learn more.\n\n## Bundled files\n\n- `assets\u002Ftemplate.html` — pre-styled scaffold with the Moody's cover, a baked-in static 6-item\n  table of contents, and empty fill-in targets (cover title, date, section-content divs, sources\n  container). Treat this file as the **read-only structural reference**: read it, fill it in\n  mentally, and emit the complete filled document in the final response.\n\n## Template (shared)\n\nBefore emitting the HTML report, **read both**:\n1. [`skills\u002Fshared\u002Ftemplate\u002FSKILL.md`](..\u002Fshared\u002Ftemplate\u002FSKILL.md) — authoring rules (which\n   classes \u002F snippets are owned by the shared layer, allowed per-skill overrides, outlook-badge\n   usage).\n2. [`skills\u002Fshared\u002Ftemplate\u002Fassets\u002Ftemplate.html`](..\u002Fshared\u002Ftemplate\u002Fassets\u002Ftemplate.html) —\n   canonical CSS (inside `\u003Cstyle id=\"shared-template-css\">`) and literal HTML markup snippets\n   (inside `\u003Ctemplate>` tags) for the document head, cover, TOC, section block, sources-section\n   wrapper, footer, and outlook-badge.\n\n**Always check the shared template before inventing** any class, token, scaffold, or design element. Do not restyle anything the shared skill owns. At emit time, copy the **contents** of `\u003Cstyle id=\"shared-template-css\">` into the marker region `\u002F* BEGIN shared-template-css ... *\u002F` … `\u002F* END shared-template-css *\u002F`. Use literal markup from the matching `\u003Ctemplate>` snippets for all HTML chrome.\n\nThis skill uses the **`cover-simple`** variant with no skill-specific CSS overrides (inherits `body { font-size: 13px }` and `.page { max-width: 900px }`). Outlook-badge usage must use canonical pastel variants (`stable` \u002F `positive` \u002F `negative` \u002F `review` \u002F `na`) — no solid-fill or inline-color overrides.\n\n## Citations (shared)\n\nBefore emitting any `[n]` reference inline or the end-of-document Citations block, **read both**:\n1. [`skills\u002Fshared\u002Fcitations\u002FSKILL.md`](..\u002Fshared\u002Fcitations\u002FSKILL.md) — authoring rules\n   (numbering, hyperlinking, source data shape, carve-outs).\n2. [`skills\u002Fshared\u002Fcitations\u002Fassets\u002Ftemplate.html`](..\u002Fshared\u002Fcitations\u002Fassets\u002Ftemplate.html) —\n   canonical CSS (inside `\u003Cstyle id=\"shared-citations-css\">`) and literal HTML markup snippets\n   (inside `\u003Ctemplate>` tags) for inline references and the end-of-document Citations block.\n\nAt emit time, copy the **contents** of `\u003Cstyle id=\"shared-citations-css\">` into the marker region `\u002F* BEGIN shared-citations-css … *\u002F` … `\u002F* END shared-citations-css *\u002F`.\n\nThe prefix used for the end-of-document container in this skill is `sa`, so the container id\nis `#sa-sources`. This skill does not use the optional per-section `.section-citations` recap\ncomponent.\n\n## Parameters\n\nThe user should provide:\n- **Sector** (required — e.g., \"Retail & Apparel\", \"Aerospace\u002FDefense\", \"Banking\")\n\nIf the user specifies a sub-sector like \"Luxury Retail\", use it as-is for focused analysis.\n\n---\n\n## Step 0 — Sector Picker (run before anything else)\n\nIf the user has not named a specific sector in their message, **stop** and call\n`ask_user_input_v0` with a single `single_select` question before proceeding. Do **not**\nbegin any research or template reading until the sector is confirmed.\n\n**Preamble:** \"Which Moody's-covered sector would you like to analyze? Select one below\nand I'll generate the full report.\"\n\n**Options:**\n\n- Aerospace & Defense\n- Automotive Manufacturing\n- Banking — Global\n- Building Materials & Construction\n- Chemicals\n- Commercial Real Estate & REITs\n- Consumer Products\n- Diversified Manufacturing\n- Food & Beverage\n- Forest Products & Paper\n- Gaming & Lodging\n- Healthcare — Hospitals & Health Systems\n- Healthcare — Medical Devices & Technology\n- Healthcare — Pharmaceuticals\n- Infrastructure & Project Finance\n- Insurance\n- Media & Entertainment\n- Metals & Mining\n- Oil & Gas — E&P\n- Oil & Gas — Integrated & Refining\n- Oil & Gas — Midstream & Pipeline\n- Packaging\n- Retail & Apparel\n- Shipping & Ports\n- Steel\n- Structured Finance — ABS\u002FRMBS\u002FCMBS\n- Technology — Hardware & Semiconductors\n- Technology — Software & Services\n- Telecommunications\n- Transportation & Logistics\n- Utilities — Electric\n- Utilities — Gas Distribution\n- Utilities — Water\n\nOnce the user selects, treat their choice exactly as if they had typed\n`Run a sector brief for {selected sector}` and continue from Step 1.\n\nIf the user already named a sector, **skip this step entirely** and go straight to Step 1.\n\n---\n\n## Step 1 — Read the template\n\nRead `assets\u002Ftemplate.html` (relative to this skill directory) once. Keep its exact structure —\nCSS, `\u003Chead>`, cover, hardcoded TOC, section order, and element IDs — as the scaffold for the\nfinal artifact. Do **not** copy it to the workspace and do **not** open it.\n\n---\n\n## Step 2 — Research phase (parallel)\n\nFire ALL of the following searches in a **single parallel batch**:\n\n### Moody's internal research (via MCP)\n\n| Search | Purpose |\n|--------|---------|\n| `searchEntityDocuments` with criteria: \"{Sector} Sector Overview\" | Sector definition, methodology, key activities |\n| `searchEntityDocuments` with criteria: \"Economic factors impact on {Sector} Sector\" | Macro-economic context |\n| `searchEntityDocuments` with criteria: \"{Sector} Sector, industry\" | Financial performance data |\n| `searchEntityDocuments` with criteria: \"{Sector} Sector Risk and challenges\" | Risk analysis |\n| `searchEntityDocuments` with criteria: \"{Sector} sector Outlook\" | Sector outlook |\n| `getEntitySectorOutlook` for a major company in the sector | Formal Moody's outlook |\n\n### Web research (via searchNews or web tools)\n\n| Search | Purpose |\n|--------|---------|\n| \"Key players from {Sector} industry, market share, roles\" | Key players for overview |\n| \"Key regions of activity and growth markets for {Sector} sector\" | Geographic scope |\n| \"{Sector} sector aggregate revenue, profit margins, return on equity\" | Financial metrics |\n| \"Major companies from {Sector} sector benchmark comparison\" | Industry structure and dynamics |\n\n---\n\n## Step 3 — Synthesize all sections\n\nUse Moody's internal research as the **primary foundation** for every section. Web sources\nserve only to supplement gaps or validate findings. When conflicts arise, prioritize Moody's\nunless external data provides substantial evidence for reconsideration.\n\nWrite in professional credit-research language. Always attribute sources with numbered citation\nreferences inline. The exact inline markup, the URL-less fallback, and the rule that `n`\nmatches the row position of the source inside `#sa-sources` are defined in\n[skills\u002Fshared\u002Fcitations\u002FSKILL.md](..\u002Fshared\u002Fcitations\u002FSKILL.md).\n\n### Executive Summary\n\nWrite after all other sections are complete. Half-page maximum. Highlight the most relevant\ndata from each section. No bullet points — flowing paragraphs only.\n\n### Section 1: Sector Overview\n\nFour subsections:\n1. **Description of the Sector** — Define the industry, key activities, product\u002Fservice\n   categories, and business-model differences\n2. **Market Size and Growth Trends** — Current market size (revenue, volume), historical\n   growth rates, regional growth data\n3. **Key Players** — Major companies, market share, roles within the sector\n4. **Geographic Scope** — Key regions of activity, potential growth markets,\n   region-specific trends\n\n### Section 2: Macro-Economic Context\n\nThree subsections:\n1. **Economic Indicators** — How GDP growth, inflation, interest rates, consumer\n   spending\u002Fconfidence impact the sector\n2. **Regulatory Environment** — Laws, regulations, compliance risks, tariff\u002Ftrade policy\n3. **Global Trends and External Factors** — Geopolitical issues, trade policies,\n   technological disruptions, channel evolution\n\n### Section 3: Financial Performance Analysis\n\nThree subsections with **mandatory quantitative data**:\n1. **Sector-Level Financial Metrics** — Aggregate revenue, profit margins, return on\n   equity, other key metrics. Every metric must include the actual number (e.g., \"Aggregate\n   revenue of $35.2 trillion in 2025\") followed by analytical commentary\n2. **Historical Trends** — Past performance trends, demand\u002Fearnings trajectories,\n   recent growth rates\n3. **Projected Financial Outlook** — Forecast key metrics, earnings outlook, key drivers\n   shaping the near-term, structural offsets and strategic responses\n\n### Section 4: Industry Structure and Dynamics\n\nFour subsections:\n1. **Main Participants** — Benchmark major companies, roles, market share, significance\n2. **Supply Chain Analysis** — Suppliers, manufacturers, distributors, customers,\n   key pressure points\n3. **Competitive Landscape** — Porter's Five Forces analysis with Moody's-grounded\n   commentary for each force (use ratings High \u002F Moderate \u002F Low for each force)\n4. **Barriers to Entry** — Capital requirements, regulatory hurdles, technology\n   requirements, market saturation\n\n### Section 5: Risks and Challenges\n\nFive subsections:\n1. **Operational Risks** — Supply chain disruptions, labor shortages, working capital\n2. **Regulatory Risks** — Compliance requirements, policy changes, tariff exposure\n3. **Market Risks** — Demand volatility, competition, pricing, category weakness\n4. **Financial Performance and Capital Structure** — Refinancing risk, default outlook,\n   margin pressure, deleveraging\n5. **Environmental and Social Risks** — ESG considerations, climate risk, social\u002Fgovernance\n   pressures\n\n### Section 6: Sector Outlook\n\nState the Moody's outlook (Positive, Stable, Negative) and date. Then provide 2-3\nwell-developed paragraphs explaining the rationale — primary drivers, regional nuances,\nkey factors and considerations. All paragraph form, no bullet points.\n\n### Sources\n\nCollect all sources. The source data shape (`id`, `title`, `source`, `date`, `url`) and the\nend-of-document Citations row markup are defined in\n[skills\u002Fshared\u002Fcitations\u002FSKILL.md](..\u002Fshared\u002Fcitations\u002FSKILL.md).\n\n---\n\n## Inline SVG Charts — Section Instructions\n\nAfter synthesizing each of the following sections, embed one inline SVG chart directly in the section content at the position indicated. All charts must be self-contained (no external scripts or stylesheets), include a `\u003Ctitle>` element for accessibility, and use `font-family: 'Source Sans Pro', Arial, sans-serif` inside an embedded `\u003Cstyle>` block.\n\n### Section 3 — Financial Performance Analysis\n\nInsert **Chart A** immediately after the Historical Trends subsection prose:\n\n- Type: grouped bar chart (revenue) with a right-axis line series (EBITDA margin %)\n- X-axis: fiscal years (last 3–5 years); left Y-axis: revenue ($B or $T); right Y-axis: margin (%)\n- Bar color: `#003087`; line color: `#0073CF`\n- `viewBox=\"0 0 700 320\"`\n\n### Section 4 — Industry Structure and Dynamics\n\nInsert **Chart C** immediately after the Porter's Five Forces prose:\n\n- Type: horizontal scored bar chart, one bar per force (5 bars)\n- Map ratings to scores: High = 3, Moderate = 2, Low = 1; scale bar lengths to a 1–3 axis\n- Bar colors: High = `#C0392B`, Moderate = `#E67E22`, Low = `#27AE60`\n- `viewBox=\"0 0 700 220\"`\n\n### Section 6 — Sector Outlook\n\nInsert **Chart D** immediately after the outlook paragraphs:\n\n- Type: horizontal three-zone sentiment track (Negative | Stable | Positive) with a triangular marker at the current outlook position\n- Zone colors: Negative = `#C0392B`, Stable = `#2980B9`, Positive = `#27AE60`; marker color matches active zone\n- Label the current outlook and date below the track\n- `viewBox=\"0 0 700 120\"`\n\n### Pre-computation requirement — mandatory, no exceptions\n\nBefore writing any SVG `x`, `y`, `width`, `height`, or `points` attribute, compute every value via bash or Python — do not calculate mentally. Record and verify computed values, then substitute into the SVG markup.\n\nIf source data for any chart is unavailable, emit a `\u003Cp>Chart data unavailable\u003C\u002Fp>` placeholder — never omit silently.\n\n---\n\n## Step 4 — Stream the complete HTML artifact\n\nAfter all sections are synthesized, produce **one** final assistant message. The message contains:\n\n1. A one-line summary sentence (e.g. `Sector Brief for {Sector}:`).\n2. A single fenced ` ```html ` code block containing the **entire filled `template.html`\n   document** — with every element from the streaming protocol populated in place. No partial\n   documents, no separate code blocks per section.\n\nThe code block **must**:\n\n- Start at column 0 with ` ```html ` and end with a closing ` ``` ` on its own line.\n- Contain a complete, standalone HTML document (doctype → `\u003C\u002Fhtml>`) that renders without\n  external dependencies.\n- Preserve the template's `\u003Chead>` (CSS, fonts), cover, hardcoded TOC, section order, and\n  element IDs exactly. Only the empty targets defined below are populated.\n\n### Cover + footer\n\n1. `#sa-cover-title` — `\u003Cstrong>{Sector}\u003C\u002Fstrong>\u003Cbr>Analysis` (HTML, not plain text).\n2. `#sa-date` — report date string, e.g. `April 15, 2026`.\n3. `#sa-footer-date` — same date string.\n\n### Section headings\n\n4. `#sa-overview-title` — override the default \"Sector Overview\" with\n   `{Sector} — Sector Overview`.\n\n### Section content targets\n\nEach of the following divs takes fully-authored HTML (`\u003Cp>`, `\u003Cul>\u003Cli>`, and\n`\u003Cstrong class=\"subsection-title\">…\u003C\u002Fstrong>` only — no other block tags):\n\n5. `#sa-exec` — Executive Summary. Flowing paragraphs only, no bullets.\n6. `#sa-overview` — Section 1 body with four `\u003Cstrong class=\"subsection-title\">` subheaders.\n7. `#sa-macro` — Section 2 body with three subheaders.\n8. `#sa-financial` — Section 3 body with three subheaders. Every metric must include a\n   concrete number.\n9. `#sa-structure` — Section 4 body with four subheaders. Porter's Five Forces must use\n   High \u002F Moderate \u002F Low ratings per force.\n10. `#sa-risks` — Section 5 body with five subheaders.\n11. `#sa-outlook` — Section 6 body. Lead with the Moody's outlook (Positive \u002F Stable \u002F\n    Negative) and date, then 2–3 paragraphs. Paragraph form only.\n\n### Sources container\n\n12. `#sa-sources` — end-of-document Citations rows. One `\u003Cdiv class=\"source-item\">` per\n    source, in ascending `id` order, using the canonical row markup defined in\n    [skills\u002Fshared\u002Fcitations\u002FSKILL.md](..\u002Fshared\u002Fcitations\u002FSKILL.md). Apply that file's rules\n    for URL-less rows and missing `source`\u002F`date` fields.\n\n### HTML conventions\n\n- Use `\u003Cp>` for paragraphs.\n- Use `\u003Cul>\u003Cli>…\u003C\u002Fli>\u003C\u002Ful>` for bullet points (nested `\u003Cul>` for sub-bullets).\n- Use `\u003Cstrong class=\"subsection-title\">Subheader\u003C\u002Fstrong>` for subsection headers within\n  each section. Do not repeat the top-level section title — the template already renders it.\n- Emit inline citations per\n  [skills\u002Fshared\u002Fcitations\u002FSKILL.md](..\u002Fshared\u002Fcitations\u002FSKILL.md).\n- Escape any `&`, `\u003C`, `>` that appear in the narrative (`&amp;`, `&lt;`, `&gt;`).\n\n---\n\n## Tips\n\n- Run ALL research searches in a single parallel batch.\n- Moody's data is the foundation — web data supplements. Attribute external sources explicitly.\n- The executive summary should be written last, after all other sections are synthesized.\n- Citations follow the shared citations skill — read\n  [skills\u002Fshared\u002Fcitations\u002FSKILL.md](..\u002Fshared\u002Fcitations\u002FSKILL.md) before authoring any `[n]`\n  reference or the Citations block.\n\n---\n\n## Negative number formatting\n\nUse `(-X)` for ALL negatives: `(-9%)`, `(-1.2pp)`, `(-$3.4B)`, `(-250 bps)`. Never use bare minus (`-9%`), en-dash (`–9%`), or parentheses without minus (`(9%)`). Apply to growth rates, margin changes, YoY deltas, and negative monetary values.\n\n---\n\n## Output and presentation (required final steps)\n\nAfter assembling the report, you MUST follow this exact delivery sequence. Do not skip steps\nand do not substitute alternatives. When updating this skill, do not delete or modify any\nother file in the `skills\u002Fsector-brief\u002F` folder.\n\n1. **Write the HTML file in a single call.** Call `create_file` to write the entire HTML to\n   `\u002Fmnt\u002Fuser-data\u002Foutputs\u002F{sector_slug}_sector_analysis.html` in **one** call.\n   `{sector_slug}` is the lowercased, hyphenated sector name (e.g. `retail-apparel`,\n   `oil-gas`).\n2. **Preview the file.** Immediately after, 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.\n3. **Show the widget.** Call `visualize:show_widget` to surface the rendered report visually\n   to the user.\n4. **One short follow-up sentence in chat.** Write a single brief sentence acknowledging the\n   report is ready. Nothing more.\n\n**Strict prohibitions:**\n\n- **Never** emit the HTML as a fenced code block in the chat response.\n- **Never** inline the HTML, JSON payload, or large excerpts of the report body in the chat\n  message.\n",{"name":5,"description":7},"main","d9535210da9af28aa76bca80de80355197e1b6d6","skills\u002Fmoody-s-sector-brief","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog","https:\u002F\u002Fgithub.com\u002Fzfifteen","I like to measure things.","2026-07-19 23:41:54",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add zfifteen\u002Fskills-catalog --skill moody-s-sector-brief",{"tool":37,"command":38},"bunx","bunx skills add zfifteen\u002Fskills-catalog --skill moody-s-sector-brief",{"tool":40,"command":41},"pnpm","pnpm dlx skills add zfifteen\u002Fskills-catalog --skill moody-s-sector-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fmoody-s-sector-brief\u002FSKILL.md",true,[45,51,57],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",380,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fmoody-s-sector-brief\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"assets\u002Ftemplate.html","ASSET","资产文件",3530,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fmoody-s-sector-brief\u002Fassets\u002Ftemplate.html",{"path":58,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":59,"sourceHtmlUrl":60},"evals\u002Fevals.json",5352,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fmoody-s-sector-brief\u002Fevals\u002Fevals.json",[62,69,76,83,92,99],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M79GXQ2PWPT2E4CJYHXVJ0YE","Zotero","Use Zotero Desktop from Codex to enable\u002Fprobe the local API, search a local Zotero library, list items\u002Fcollections\u002Ftags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX\u002FRIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzotero\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M79GXN85NETKBE06865CWK6Z","zoom-apps-sdk","Use when using Apps SDK.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M79GXCYD7FGYS932J9N9RFFY","youtube","Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript.  Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or \"what does this video actually say\".  The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content.  Triggers: \"youtube transcript\", \"get the transcript of this video\", \"summarize this youtube video\", \"what did they say in https:\u002F\u002Fyoutube.com\u002F...\", \"key claims from this talk\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M79GX8EXHHYM566BKR7MS778","yeet","Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M79GX2HFJPX84NMRE5VBTYX9","x-post-creator","Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, \u002Fx-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs\u002Fx-posts\u002F[story-name]\u002F.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-post-creator\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M79GWXQT4HBT6QME6QSBZJFA","x-api","Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X\u002Fx.com, reading threads and replies, creating lists, staging\u002Fpublishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions \u002Fx-api or \"search X\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]