The body is lean and assumes Claude's competence — no basic concept explanations, just directives, a concrete command, named outputs, and tool calls; it is above the 'mostly efficient but includes some unnecessary explanation' level because every line carries operational weight.

Provides a copy-paste bash command invoking the real helper, named output artifacts (deck.pptx, manifest.json, preflight_checks.json), concrete verification commands ('unzip -t'), and exact MCP tool names with parameters (upload_mode="native_google_slides", _get_presentation_outline, _get_slide_thumbnail), matching the 'fully executable code/commands; copy-paste ready' anchor.

A six-step numbered sequence with explicit validation checkpoints ('Do not import the PPTX until preflight_checks.json has status: passed', then unzip -t) and a repair feedback loop in step 5, matching the 'clear sequence with explicit validation steps; feedback loops for error recovery' anchor.

The body is a concise overview pointing one level deep to the real scripts/report_to_google_slides.py bundle (which exists), with no nested references and clear Workflow/Standards/Visual System sections; per the guideline to score against the actual bundle structure, this matches the 'clear overview with well-signaled one-level-deep references' anchor.

Quotes 'convert an existing HTML analytics report into a native Google Slides deck' name the domain and one concrete action (convert), but only a single action is stated rather than multiple specific concrete actions, matching the 'names domain and some actions' anchor rather than the 'lists multiple specific concrete actions' level above.

'Invoke only when the user explicitly asks to convert...' is an explicit trigger answering 'when', and 'convert an existing HTML analytics report into a native Google Slides deck' answers 'what', so both are clearly addressed; it is above the 'has what, but when is missing or only implied' level.

Natural user terms 'convert', 'HTML analytics report', 'Google Slides', and 'deck' are all present and are words a user would naturally say, matching the 'good coverage of natural terms users would say' anchor; it is above the 'some relevant keywords but missing common variations' level because the core triggering vocabulary is complete.

'Narrow conversion skill' tied to the specific HTML analytics report to native Google Slides deck niche is a clear, distinct trigger unlikely to fire for other skills, matching the 'clear niche with distinct triggers; unlikely to conflict' anchor.