media-reviewer
Deep content analysis for structure, themes, narrative flow, key moments, and important quotes. Use before content-documenter.
What this skill does
# Media Reviewer Skill Expert at analyzing media content to understand structure, ideas, and narrative flow. ## What This Skill Does - Reads content materials (text, captions, transcripts) - Understands ideas and concepts being presented - Identifies narrative structure and progression - Discovers key moments, turning points, and themes - Recognizes content organization patterns ## Analysis Process Follow these 9 steps in order: ### Step 1: Read Everything - Read the complete content file - Note the metadata (title, source, date, type) - Don't skim - read thoroughly - If content is truncated, note what's missing ### Step 2: Understand Context - What is this content about? - Who created it and why? - What's the intended audience? - What's the publication context? - When was it created? ### Step 3: Identify Structure - How is the content organized? - What are the main sections/segments? - How long is each part? - What's the logical flow? - Are there chapters, timestamps, or markers? ### Step 4: Extract Core Ideas - What are the 3-7 main concepts? - How are they explained? - What examples are given? - How do ideas connect to each other? - What's the central thesis? ### Step 5: Track Narrative Flow - How does content progress? - What's the arc (intro → development → conclusion)? - Where are the key transitions? - How do ideas build on each other? - What's the pacing? ### Step 6: Find Key Moments - What are the most important points? - Where are the "aha" moments? - What would someone quote from this? - What's most memorable? - What's surprising or novel? ### Step 7: Extract Quotes + Timestamps - Find 5-20 verbatim quotes - For video/audio: note exact timestamps (HH:MM:SS or MM:SS) - Capture the most insightful statements - Include context for each quote - Never paraphrase - exact words only ### Step 8: Identify Themes - What recurring topics emerge? - What patterns appear throughout? - What's the underlying message? - What values or perspectives are expressed? ### Step 9: Documentary Angle - If making a documentary about this, how would you structure it? - What's the narrative hook that draws people in? - What makes this content unique? - What's the emotional arc? ## Output Your analysis is IMPLICIT - it stays in your thinking. The content-documenter skill will use your analysis to produce structured output. Do NOT output JSON directly from this skill. Focus on understanding deeply so content-documenter can produce rich output. ## Important Rules - Be thorough and comprehensive - Understand the material deeply - Preserve nuance and detail - Note what makes this content unique - Always include timestamps for video/audio - Read the ENTIRE content before analyzing - Don't add interpretation or opinion - Don't skip important details - Don't oversimplify complex concepts - Don't paraphrase quotes - keep verbatim - Don't rush - thoroughness over speed
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.