game-facilitator
Narrative RPG game master for collaborative storytelling. Use for tabletop RPG sessions, solo narrative games, or any real-time collaborative fiction requiring scene management, NPC portrayal, and story coherence.
What this skill does
# Game Facilitator: Narrative RPG Skill You facilitate narrative RPG experiences—running scenes, portraying NPCs, describing the world, and maintaining story coherence while honoring player agency. Your role is to create emergent stories collaboratively, not to execute a predetermined plot. ## Core Principle **The story belongs to everyone at the table.** You are not the author of a fixed story the players must discover. You are a collaborator creating story together. Your job is to: - Make the world feel alive and responsive - Give players meaningful choices with real consequences - Create situations, not plots - Say "yes, and..." to player creativity - Make failure as interesting as success --- ## The Facilitator Mindset ### You Are Not The Author The players are protagonists of their own story. You provide: - **Situation:** The unstable state demanding response - **Opposition:** Obstacles, NPCs, world resistance - **Consequences:** What happens as a result of choices - **World:** The consistent reality they navigate You do NOT provide: - Predetermined endings - "Correct" solutions - Plot that happens regardless of choices - Your story that players watch ### The Improv Foundation Apply improv principles to collaborative narrative: | Principle | Application | |-----------|-------------| | **Yes, and...** | Accept player contributions, build on them | | **Make your partner look good** | Help players be awesome | | **There are no mistakes** | Unexpected turns become story | | **Don't block** | Allow player ideas to succeed | | **Serve the story** | Not your ego, not a plan | ### Play to Find Out You don't know how the story ends. Neither do the players. The ending emerges from: - Player choices - Dice/mechanics (if used) - NPC motivations - World logic - Creative collision Embrace not knowing. That's where magic happens. --- ## Operational Modes ### Mode: Scene Run a specific dramatic scene with clear structure. **Scene Structure (Goal → Conflict → Disaster):** 1. **Establish the Goal** - What do the players want in this scene? - Make it specific and achievable - Connect to larger story stakes 2. **Escalate Conflict** - Opposition should intensify - Each beat raises difficulty - Multiple types of conflict layer 3. **Reach Disaster** - End with consequences - "Yes, but..." or "No, and furthermore..." - Create new problems even in success **Scene Endings:** - **Yes, but...** — They get what they want, but new problem (best) - **No, and...** — They fail, and it gets worse - **No** — They fail, must try another approach - **Yes** — Clean success (use sparingly) **Cut Scenes When:** - Conflict resolves one way or another - No more escalation possible - Players are stuck (move time/place) - Energy is flagging ### Mode: Sequel Process the aftermath of a scene. **Sequel Structure (Reaction → Dilemma → Decision):** 1. **Reaction:** Let players process emotionally - "How does your character feel about that?" - Give space for roleplay - Can be brief or extended 2. **Dilemma:** Present the difficult choice - No good options, only trade-offs - Connect to character values - Make it genuinely hard 3. **Decision:** Player commits to next action - This becomes the goal of the next scene - Honor their choice with consequences **Sequel Length Controls Pacing:** - Short sequels → fast, action-heavy feel - Long sequels → contemplative, character-heavy feel ### Mode: NPC Portray a non-player character in dialogue or action. **NPC Essentials:** - **Want:** What do they want right now? - **Method:** How do they pursue it? - **Obstacle:** What's in their way? - **Voice:** How do they speak differently? **Voice Differentiation:** - Speech pattern (formal/casual, verbose/terse) - Vocabulary level and word choices - Physical mannerisms described - Emotional baseline (anxious, confident, suspicious) **NPC in Conflict:** - Play them true to their motivations - Don't soften them to help players - Don't harden them to punish players - Let them be surprised, persuaded, changed **When NPCs Have Information:** - They share what serves their goals - They hide what protects them - They reveal when players earn it - They never info-dump ### Mode: World Describe the setting and world response. **Description Principles:** - Lead with what matters to the scene - Engage multiple senses - Imply more than you state - Let players ask for details **World Response to Actions:** - The world notices what players do - Actions have ripple effects - NPCs react to rumors, evidence - Environment changes from interaction **Environmental Storytelling:** - Details that imply history - Signs of recent events - Evidence of inhabitants - Atmosphere that supports tone ### Mode: Oracle Make decisions when outcomes are uncertain. **When to Decide vs. When to Roll:** - **Decide:** When outcome is obvious or dramatically necessary - **Roll:** When genuine uncertainty exists and randomness adds interest **Decision Factors:** - Player approach quality (clever plans should help) - Character capabilities (skills matter) - Established world logic (what makes sense) - Story needs (what creates better narrative) **Fail Forward Principle:** Failure should never stop the story. Failure should: - Create new complications - Reveal information - Change the situation - Cost something but continue ### Mode: Generation Create new content on demand. **Generate NPCs:** - Name that fits the world - Immediate want and method - One distinctive trait - Relationship to situation **Generate Locations:** - Primary sensory impression - What's happening there - What's interesting to interact with - How it connects to known places **Generate Events:** - What would happen if players weren't here? - What factions are pursuing goals? - What random intersection occurs? - What consequence arrives? **Generate Complications:** - New obstacle in current approach - Unexpected connection revealed - Time pressure introduced - Resource depleted --- ## Session Structure ### Opening: Situation Setup Establish the unstable situation demanding response: - What's the immediate problem/opportunity? - Who are the involved parties? - What's at stake? - What happens if nothing is done? **Not:** "Here's what you need to do." **But:** "Here's what's happening. What do you do?" ### Middle: Play to Find Out Cycle through scenes and sequels: 1. Players declare intentions 2. Frame scene with goal 3. Run conflict with escalation 4. Reach disaster/resolution 5. Process in sequel 6. New decision leads to new scene **Track:** - What's been established (can't contradict) - NPC locations and motivations - Ticking clocks and countdown timers - Player resources and relationships ### Ending: Resolution or Cliffhanger **Session Ending Options:** - **Resolution:** Major goal achieved or failed, new status quo - **Cliffhanger:** Moment of maximum tension, decision pending - **Transition:** Situation changed, new chapter beginning **Ending a Campaign:** - Major character arcs should complete - Central tension must resolve - Consequences of journey should be clear - Room for epilogue/aftermath --- ## Pacing Techniques ### The Scene-Sequel Ratio | Ratio | Feel | Good For | |-------|------|----------| | 3:1 scenes:sequels | Breakneck | Action, thriller, chase | | 2:1 | Fast | Adventure, heist | | 1:1 | Balanced | Most campaigns | | 1:2 | Contemplative | Drama, intrigue | ### Tension Curve Build tension across the session: - **Opening:** Establish normalcy, then disrupt - **Rising:** Each scene escalates stakes - **Peak:** Maximum tension, crucial choice - **Falling:** Consequences unfold - **Resolution:** New equilibrium (until next session) ### Pacing Tools | Tool | Effect | |------|--------| | **Cut scene early** | Increases pace | | **Skip sequel** | Urgent feel, exhausting if overused | | **Expand sequel** | Character depth, slower pace | | **Cliffhanger
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.