narratological-algorithms
Distill artist/theorist narrative principles into formal, implementable algorithmic frameworks. Use when asked to extract, formalize, or systematize narrative techniques from any storytelling source—filmmakers, writers, theorists, game designers, showrunners. Triggers on requests involving narrative principle extraction, story structure analysis, craft methodology formalization, or creating implementable storytelling protocols.
What this skill does
# Narratological Algorithm Distillation Transform narrative principles from artists, theorists, and practitioners into formal, implementable algorithmic frameworks. ## Workflow ### 1. Source Classification Identify source type to calibrate extraction approach: | Type | Characteristics | Extraction Focus | |------|-----------------|------------------| | **Theorist** | Prescriptive texts (McKee, Aristotle) | Direct principle extraction | | **Practitioner** | Interviews, commentary, production docs | Reverse-engineering from stated methods | | **Classical** | Ancient/foundational texts (Poetics, Natyasastra) | Translation of archaic terminology | | **Analyst** | Secondary analysis of creator's work | Validation against primary sources | ### 2. Primary Source Prioritization Always prioritize **primary sources** over secondary analysis: - Direct quotes from the creator - Production documents, interviews, lectures - The creator's own articulated methodology - Documented working processes When using secondary sources, validate principles against primary evidence. Flag where principles are inferred vs. directly stated. ### 3. Principle Extraction Protocol For each identified principle: ``` EXTRACT: 1. Locate source statement (direct quote when available) 2. Identify underlying mechanism (why it works) 3. Formulate as rule or constraint 4. Determine scope (universal vs. context-specific) 5. Map to existing narrative theory where applicable ``` ### 4. Document Structure Generate output following the canonical structure. See [references/output-template.md](references/output-template.md) for the full template. **Required sections:** 1. Meta-Principles (Axioms) 2. Structural Hierarchy 3. Core Algorithms/Protocols 4. Diagnostic Questions/Tests 5. Quick Reference Card **Optional sections (as warranted):** - Episode/Scene Templates - Theoretical Correspondence Tables - Source Cross-Reference Appendix ### 5. Formalization Patterns Convert principles to implementable forms: | Source Form | Target Form | |-------------|-------------| | Conceptual statement | Constraint rule | | Process description | Pseudocode function | | Best practice | Validity test | | Comparison | Decision table | | Taxonomy | Classification tree | See [references/formalization-patterns.md](references/formalization-patterns.md) for detailed examples. ### 6. Axiom Identification Identify 3-7 meta-principles that underpin the creator's entire approach: ``` AXIOM_CRITERIA: - Foundational (other principles derive from it) - Non-negotiable in the creator's worldview - Distinguishes this approach from alternatives - Stated explicitly or demonstrated consistently ``` Format axioms with unique identifiers: `[CREATOR_INITIALS]-A[N]` ### 7. Validation Checks Before finalizing, verify: - [ ] All principles traceable to source material - [ ] Pseudocode is syntactically coherent - [ ] Decision tables have complete coverage - [ ] Quick reference captures essential operations - [ ] Diagnostic questions are answerable yes/no - [ ] Theoretical correspondences are accurate ### 8. Cross-Medium Adaptation Notes When source material is medium-specific, include adaptation guidance for: - Film → Television (serialization, episode structure) - Literature → Interactive (agency, branching) - Single creator → Collaborative (writers' room dynamics) - Western → Non-Western theoretical traditions ## Reference Files - **[references/output-template.md](references/output-template.md)** — Full document structure template - **[references/formalization-patterns.md](references/formalization-patterns.md)** — Examples of converting prose to algorithms - **[references/theoretical-correspondences.md](references/theoretical-correspondences.md)** — Mapping table across narrative traditions
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.