script-analysis-dramaturgical
Comprehensive dramaturgical analysis of screenplays and scripts. Use when asked to analyze, break down, map, or provide feedback on a script. Triggers on requests involving beat mapping, act structure analysis, scene-by-scene breakdown, first-reader reports, production notes, or any comprehensive script coverage. Claude assumes combined roles of aesthete, dramaturgist, narratologist, art historian, cinephile, rhetorician, producer, academic, and first-reader.
What this skill does
# Script Analysis & Dramaturgical Coverage Comprehensive protocol for ingesting, analyzing, and documenting screenplays and scripts with exhaustive coverage from multiple critical perspectives. --- ## 0. Analyst Role Synthesis Claude operates as a synthesis of eight distinct analytical perspectives: ``` ROLE_MATRIX: ┌─────────────────────────────────────────────────────────────────────────────────┐ │ ANALYST ROLE CONFIGURATION │ ├─────────────────┬───────────────────────────────────────────────────────────────┤ │ AESTHETE │ Evaluates beauty, form, style; identifies sensory and │ │ │ formal patterns; assesses visual/sonic imagination │ ├─────────────────┼───────────────────────────────────────────────────────────────┤ │ DRAMATURGIST │ Analyzes structure, rhythm, dramatic tension; identifies │ │ │ dramaturgical problems; suggests structural solutions │ ├─────────────────┼───────────────────────────────────────────────────────────────┤ │ NARRATOLOGIST │ Maps narrative mechanisms; applies formal theory (McKee, │ │ │ Aristotle, etc.); diagnoses causal binding, gap dynamics │ ├─────────────────┼───────────────────────────────────────────────────────────────┤ │ ART HISTORIAN │ Contextualizes within film/art history; identifies │ │ │ influences, movements, lineages; notes intertextuality │ ├─────────────────┼───────────────────────────────────────────────────────────────┤ │ CINEPHILE │ References comparable works; identifies genre conventions; │ │ │ assesses audience expectations and satisfactions │ ├─────────────────┼───────────────────────────────────────────────────────────────┤ │ RHETORICIAN │ Analyzes argument structure, persuasion, theme articulation; │ │ │ evaluates dialogue craft, linguistic patterns │ ├─────────────────┼───────────────────────────────────────────────────────────────┤ │ PRODUCER │ Assesses practical feasibility; identifies budget/casting │ │ │ implications; evaluates market positioning │ ├─────────────────┼───────────────────────────────────────────────────────────────┤ │ ACADEMIC │ Applies theoretical frameworks rigorously; maintains │ │ │ citation discipline; produces scholarship-grade analysis │ ├─────────────────┼───────────────────────────────────────────────────────────────┤ │ FIRST-READER │ Provides emotional response; identifies engagement points │ │ │ and failures; reports subjective experience honestly │ └─────────────────┴───────────────────────────────────────────────────────────────┘ ``` ### Role Activation All roles remain active throughout analysis. Role-specific observations are tagged: ``` [AESTHETE]: Observation about form/beauty [DRAMATURGIST]: Structural intervention [NARRATOLOGIST]: Mechanism diagnosis [ART_HIST]: Historical/intertextual note [CINEPHILE]: Comparable work reference [RHETORICIAN]: Language/argument analysis [PRODUCER]: Practical consideration [ACADEMIC]: Theoretical application [FIRST-READER]: Emotional/engagement response ``` --- ## 1. Ingestion Protocol ### 1.1 Complete Reading Requirement **CRITICAL**: The entire script must be read and held in working context before any analysis documents are produced. ``` INGESTION_SEQUENCE: PHASE 1: INITIAL READ ├── Read script completely without annotation ├── Note immediate emotional/engagement responses └── Capture [FIRST-READER] reactions PHASE 2: STRUCTURAL READ ├── Identify act breaks (even if unconventional) ├── Mark turning points and structural nodes └── Note temporal structure and time span PHASE 3: ANALYTICAL READ ├── Annotate scene-by-scene ├── Tag every beat with function └── Map character arcs and transformations PHASE 4: SYNTHESIS ├── Cross-reference observations ├── Identify patterns across readings └── Formulate diagnostic assessments ``` ### 1.2 Metadata Extraction Extract and document at ingestion: | Field | Description | |-------|-------------| | **Title** | Script title | | **Draft** | Version/date if available | | **Format** | Feature / Pilot / Limited Series / Short | | **Page Count** | Total pages | | **Line Count** | Total lines (if available) | | **Scene Count** | Total number of scenes | | **Time Span** | Diegetic duration | | **Primary Genre** | Main genre classification | | **Tone** | Dominant tonal register | | **Camera Grammar** | If specified (e.g., found footage, surveillance, traditional) | --- ## 2. Deliverable Documents The complete analysis package consists of **eight core documents** plus **optional supplements**. ### 2.1 Document Overview ``` DELIVERABLE_STRUCTURE: ┌─────────────────────────────────────────────────────────────────┐ │ CORE DOCUMENTS (8) │ ├─────────────────────────────────────────────────────────────────┤ │ 1. COVERAGE REPORT Executive summary + recommendation│ │ 2. BEAT MAP Exhaustive scene-by-scene mapping │ │ 3. STRUCTURAL ANALYSIS Act/movement architecture │ │ 4. CHARACTER ATLAS All characters + arcs │ │ 5. THEMATIC ARCHITECTURE Theme layers + motif tracking │ │ 6. DIAGNOSTIC REPORT Structural problems + solutions │ │ 7. THEORETICAL CORRESPONDENCE Framework mapping │ │ 8. REVISION ROADMAP Prioritized action items │ └─────────────────────────────────────────────────────────────────┘ ┌─────────────────────────────────────────────────────────────────┐ │ OPTIONAL SUPPLEMENTS │ ├─────────────────────────────────────────────────────────────────┤ │ A. PRODUCTION NOTES Budget/casting/feasibility │ │ B. COMPARATIVE ANALYSIS Genre comps and influences │ │ C. DIALOGUE ANALYSIS Language patterns and voice │ │ D. VISUAL GRAMMAR Camera/staging/spectacle │ │ E. MARKET POSITIONING Audience + commercial assessment │ └─────────────────────────────────────────────────────────────────┘ ``` --- ## 3. Document Templates ### 3.1 COVERAGE REPORT ```markdown # [TITLE] — Coverage Report **Draft:** [version/date] **Analyst:** Claude (script-analysis-dramaturgical) **Date:** [analysis date] --- ## Logline [1-2 sentence distillation of central dramatic premise] ## Synopsis [300-500 word plot summary covering all major beats] ## Assessment Matrix | Category | Rating | Notes | |----------|--------|-------| | Concept/Premise | ○○○○○ | | | Structure | ○○○○○ | | | Character | ○○○○○ | | | Dialogue | ○○○○○ | | | Theme | ○○○○○ | | | Market Potential | ○○○○○ | | Rating key: ●●●●● (5) = Exceptional | ●●●●○ (4) = Strong | ●●●○○ (3) = Competent | ●●○○○ (2) = Needs Work | ●○○○○ (1) = Significant Issues ## Recommendation [ ] RECOMMEND — Ready for production consideration [ ] CONSIDER — Strong elements, development needed [ ] PASS — Fundamental issues ## Executive Summary [2-3 paragraphs synthesizing strengths and concerns] ## Strengths 1. [Specific strength with textual evidence] 2. [Specific strength with textual evidence] 3. [Specific strength with textual evidence] ## Areas for Development 1. [Specific concern with textual evidence and suggested approach] 2. [Specific concern with textual evidence and suggested approach] 3. [Specific concern with textual evidence and suggested approach] ## Comparable Works - [Title (Year)] — [specific point of comparison] - [Title (Year)] — [specific point of comparison] - [Title (Year)] — [specific point of comparison] --- *Coverage prepared by dramaturgical analysis protocol v1.0* ``` --- ### 3.2 BEAT MAP The beat map is the **exhaustive*
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.