Names the domain (framing documents from transcripts) and describes the output (frame capturing problem and alternatives), but doesn't list multiple concrete actions beyond 'create'. Could specify steps like 'extract key insights, identify problem statements, synthesize alternatives discussed'.

Clearly answers both what ('Create a framing document from conversation transcripts') and when ('Use when the user has transcripts (VTT, call notes, etc.) and wants to produce a frame'). Has explicit 'Use when...' clause with specific trigger conditions.

Includes natural keywords users would say: 'transcripts', 'VTT', 'call notes', 'framing document', 'frame', 'problem worth solving'. Good coverage of input formats and output types.

Clear niche combining transcript input with framing document output. The specific mention of VTT files, call notes, and the unique output format (problem framing with alternatives) makes it unlikely to conflict with general document or transcript skills.

The skill is mostly efficient but includes some unnecessary explanation. Sections like 'Common traps to avoid' and the detailed explanation of 'Less about / More about' could be tightened. Some guidance is repeated (evidence tracing appears in multiple places).

Provides concrete, specific guidance throughout. The document format template is copy-paste ready, the review checklist is explicit, and the 'Before You Start' questions give exact steps. Each section has clear deliverables.

Clear sequence from gathering transcripts → drafting sections → reviewing with explicit validation. The review section provides a concrete feedback loop (read bullet → ask for evidence → cite or drop). Steps are well-ordered and checkpoints are explicit.

Content is well-organized with clear headers, but this is a long monolithic document (~200 lines) that could benefit from splitting detailed guidance (e.g., 'Common traps' or the full template) into separate reference files. No external references are provided.