--- name: moody-s-sector-brief description: > 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". --- # Sector Brief Skill Generates a professional HTML report (styled like a Moody's sector brief document) for a specified industry sector. The report is research-heavy and text-driven, combining Moody's internal research with supplemental web data across six structured sections plus an executive summary and citations. 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** (`` → ``), 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 brief `"Data unavailable"` placeholders for missing > sections — never skip the artifact. > > Treat any other output shape as a hard failure of the skill. ## Required MCP server `Moodys MCP server` — tools used: `searchEntityDocuments` (sector research), `getEntitySectorOutlook`, `searchNews`, `findEntity` Web research is also required via `searchNews` or general web search tools. 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. ## Bundled files - `assets/template.html` — pre-styled scaffold with the Moody's cover, a baked-in static 6-item table of contents, and empty fill-in targets (cover title, date, section-content divs, sources container). 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**: 1. [`skills/shared/template/SKILL.md`](../shared/template/SKILL.md) — authoring rules (which classes / snippets are owned by the shared layer, allowed per-skill overrides, outlook-badge usage). 2. [`skills/shared/template/assets/template.html`](../shared/template/assets/template.html) — canonical CSS (inside `