moody-s-sector-brief

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".

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/moody-s/skills/moody-s-sector-brief/SKILL.md

Quality

Content

57%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and highly actionable for research/synthesis, with good progressive disclosure via the shared template and citations skills. Its major defect is a hard self-contradiction between the CRITICAL output contract (single fenced ```html block, no disk write) and the final "Output and presentation" section (create_file to disk, never emit as a fenced block).

Suggestions

Resolve the contradiction: pick one authoritative delivery mechanism and delete the other — either keep the CRITICAL contract (single ```html block in the response, no disk write) and remove the create_file/"Never emit as fenced block" section, or vice versa, so the skill never instructs two opposite terminal actions.

Tighten the redundant output-contract restatements: the streaming/emit rules are stated in the intro, the CRITICAL block, and Step 4; consolidate into a single authoritative statement to reduce token cost and the chance of drift.

Reconcile every mention of disk output: the intro and CRITICAL block say "no file copy, no open step, MUST NOT write to disk" while Step 4.1 / "Output and presentation" require create_file and visualize:show_widget — align these so the skill's I/O behavior is internally consistent.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes competence (no explaining what a sector is), but it restates the output/streaming contract at least three times — intro "single-artifact streaming", the CRITICAL block, and Step 4 — before contradicting itself in "Output and presentation", which is redundant padding that could be tightened.	2 / 3
Actionability	Concrete guidance is strong (named MCP tools, search-criteria tables, exact element IDs like #sa-cover-title, chart specs with viewBox/colors, file path), but the two final delivery instructions directly conflict (fenced ```html block vs. create_file to disk / "Never emit the HTML as a fenced code block"), leaving the most critical step unresolved rather than copy-paste ready.	2 / 3
Workflow Clarity	Steps are clearly sequenced (Step 0 picker → Step 1 read template → Step 2 parallel research → Step 3 synthesize → Step 4 stream) with some checkpoints (mandatory SVG pre-computation, data-unavailable fallbacks), but the contradictory final delivery section creates genuine ambiguity in the workflow's terminal step, capping clarity.	2 / 3
Progressive Disclosure	Clear overview with well-signaled one-level-deep references to bundled assets/template.html (verified present) and shared skills (../shared/template/SKILL.md, ../shared/citations/SKILL.md) for CSS/markup details, keeping the SKILL.md body as an overview pointer rather than inlining everything.	3 / 3
	Total	9 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-crafted: third-person voice, concrete actions, broad natural trigger terms, and explicit what/when guidance. It is concise yet comprehensive and clearly scoped to Moody's sector briefs.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Produce a Sector Brief HTML report", "analyze a sector", "write a sector report", "do an industry analysis", "create a sector overview", "generate a sector deep-dive" — and names the tooling ("Moody's GenAI MCP tools and web research"), matching the anchor for listing multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers what ("Produce a Sector Brief HTML report for any industry sector using Moody's GenAI MCP tools and web research") and when ("Use this skill whenever the user asks to analyze a sector..."), satisfying the both-what-and-when anchor with explicit triggers.	3 / 3
Trigger Term Quality	Covers natural user terms broadly — "analysis", "overview", "outlook", "report", "deep-dive" — plus whole phrases users would say like "what's happening in the retail sector" and "give me a sector breakdown for aerospace", meeting the good-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	The Moody's-anchored sector-brief niche and sector-specific trigger phrasing give it a clear, distinct scope unlikely to fire for unrelated skills, matching the clear-niche anchor despite the somewhat generic words "report"/"outlook".	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 9 suspicious	Warning

	Total	15 / 16 Passed

Repository: openai/plugins
Path: plugins/moody-s/skills/moody-s-sector-brief/SKILL.md
Commit: 11c74d6

Reviewed: 17 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.