Agent skill

Game Facilitator

by jwynia in jwynia/agent-skills

Narrative RPG game master for collaborative storytelling. An agent skill from jwynia/agent-skills.

MITAuto-check passedWriting & Content

Install Game Facilitator

skills CLI
$ npx skills add jwynia/agent-skills --skill game-facilitator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jwynia/agent-skills game-facilitator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/creative/fiction/application/game-facilitator .claude/skills/game-facilitator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
game-facilitator
GitHub stars
170
Token cost
~4.6k tokens
SKILL.md length
2,294 words
Files
4 (incl. scripts)
Skills in repo
111
Repo updated
First seen
Licence
MIT

At a glance

Narrative RPG game master for collaborative storytelling. An agent skill from jwynia/agent-skills.

  • Works in 3 steps: Establish the Goal → Escalate Conflict → Reach Disaster
  • Tabletop RPG sessions
  • SKILL.md covers Core Principle, The Facilitator Mindset, Operational Modes and Session Structure, plus 4 more sections
  • Runs TypeScript scripts from its folder; calls deno

What it does

Game Facilitator is an agent skill from jwynia/agent-skills. 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.

Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/complication-generator.ts`, `scripts/npc-generator.ts` and `scripts/session-notes.ts`).

It sits in Writing & Content, covering Creative writing and fiction and Storytelling. The licence is MIT.

When your agent uses it

  • Tabletop RPG sessions
  • Solo narrative games
  • Any real-time collaborative fiction requiring scene management
  • Story coherence

Example prompts

  • “/game-facilitator”

Requirements

  • Node.js

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Establish the Goal
  2. Escalate Conflict
  3. Reach Disaster

What it can do on your machine

Read from SKILL.md and the folder at commit e02ec7e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (TypeScript), which the agent can run.

    Shell commands in SKILL.md call:

    • deno

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Game Facilitator loads about 4.6k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 2,294 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~4.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from jwynia/agent-skills at commit e02ec7e, republished under its MIT licence (© jwynia). 2,294 words, ~4,638 tokens.

Download SKILL.mdSave it as .claude/skills/game-facilitator/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
game-facilitator
description
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.
license
MIT
metadata.author
jwynia
metadata.version
1.0
metadata.type
utility
metadata.mode
application
metadata.domain
fiction

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:

PrincipleApplication
Yes, and...Accept player contributions, build on them
Make your partner look goodHelp players be awesome
There are no mistakesUnexpected turns become story
Don't blockAllow player ideas to succeed
Serve the storyNot 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
RatioFeelGood For
3:1 scenes:sequelsBreakneckAction, thriller, chase
2:1FastAdventure, heist
1:1BalancedMost campaigns
1:2ContemplativeDrama, 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
ToolEffect
Cut scene earlyIncreases pace
Skip sequelUrgent feel, exhausting if overused
Expand sequelCharacter depth, slower pace
Cliffhanger cutTension maintained between sessions
MontageCompress time, skip less interesting parts
FlashbackReveal backstory at moment of impact

Player Agency

Meaningful Choices

Every significant choice should:

  • Have distinct options (not false choice)
  • Have perceivable consequences
  • Express character values
  • Be irreversible (no takebacks)
When Players Surprise You

Player does something unexpected:

  1. Don't say no reflexively
  2. Ask clarifying questions
  3. Consider what would actually happen
  4. Let them try (with appropriate difficulty)
  5. Make the outcome interesting regardless

Player derails your plan:

  • You don't have a plan, you have a situation
  • NPCs adjust to new reality
  • Consequences follow actions
  • The story goes where it goes
The Spotlight

Ensure all players get:

  • Moments where their character shines
  • Scenes focused on their goals
  • NPCs who care about them specifically
  • Challenges suited to their abilities

Rotate spotlight; don't let one player dominate.


NPC Management

Active NPCs

Keep track of NPCs with ongoing presence:

Name: [Who]
Want: [Current goal]
Method: [How they pursue it]
Relationship: [To players/situation]
Next action: [What they do if players don't intervene]
NPC Factions

Groups with collective goals:

  • What do they want?
  • What resources do they have?
  • Who are their rivals?
  • What's their next move?
The Countdown

Things that happen if players don't act:

  • NPCs pursue their goals
  • Situations deteriorate
  • Opportunities close
  • Consequences arrive

Make countdowns visible when appropriate; sometimes hidden.


World Consistency

What's Been Established

Track canon from play:

  • Facts stated about the world
  • NPC names and relationships
  • Locations and their features
  • Events that have occurred

Never contradict established facts without in-world explanation.

Integration with World Bible

If using shared-world skill:

  • Check bible before introducing major elements
  • Add new canon to bible after sessions
  • Flag potential contradictions
  • Use established NPCs/locations
Improvised Canon

New facts created in play:

  • Note them immediately
  • Consider implications
  • Let them ripple outward
  • They're now as real as anything pre-planned

Tone Management

Setting Tone

Tone emerges from:

  • Description choices (gritty vs. lush)
  • NPC demeanor (serious vs. playful)
  • Consequence severity (lethal vs. forgiving)
  • Humor allowance (grimdark vs. comedy)
Reading the Table

Watch for:

  • Energy levels (tired players need simpler scenes)
  • Engagement (bored players need spotlight or change)
  • Discomfort (safety tools when needed)
  • Excitement (ride the wave when energy is high)
Show full SKILL.md (918 more words)Show less
Adjusting Mid-Session

If tone is wrong:

  • Introduce element that shifts it (comic relief, serious threat)
  • Cut to different scene type
  • Explicitly discuss with players
  • Take a break to reset

Common Situations

Players Are Stuck

Options:

  • NPC arrives with information or demand
  • Environment changes (danger, opportunity)
  • Cut away and return with new context
  • Ask "What does your character want?"
  • Offer choices explicitly
Players Are Arguing

Options:

  • Let them resolve in character
  • Apply time pressure (decide or X happens)
  • Split party temporarily (both approaches happen)
  • Ask what their characters do, not what they think should happen
Player Wants Impossible Thing

Options:

  • Clarify what's actually impossible vs. difficult
  • Offer path to eventually achieving it
  • Show consequences of attempting it
  • Ask what they actually want (goal behind goal)
Scene Is Dragging

Options:

  • Escalate conflict sharply
  • Cut to aftermath
  • Introduce complication
  • Ask "Are we done here?"

Integration with Other Skills

SkillIntegration
story-senseCore narrative principles apply
worldbuildingConsistency diagnostics for world
character-arcNPC transformation over campaign
scene-sequencingPacing structure
dialogueNPC voice and subtext
shared-worldCanon tracking across sessions
genre-conventionsGenre expectations and subversion
cliche-transcendenceAvoiding tired tropes

Available Tools

session-notes.ts

Quick session note template generator.

bash
deno run --allow-read --allow-write scripts/session-notes.ts "Session Title"
npc-generator.ts

Generate NPCs on demand.

bash
deno run --allow-read scripts/npc-generator.ts --tone dark-fantasy
deno run --allow-read scripts/npc-generator.ts --role merchant --trait suspicious
complication-generator.ts

Generate complications when stuck.

bash
deno run --allow-read scripts/complication-generator.ts --current "investigating the crime"

Anti-Patterns

The Railroad

Pattern: Pre-determined plot that happens regardless of choices. Problem: Players are audience, not participants. Fix: Create situations, not plots. Play to find out.

The Adversary

Pattern: GM "wins" when players lose. Problem: Collaboration replaced by competition. Fix: You're on the same side. You want them to succeed (eventually).

The Novelist

Pattern: Extensive narration, minimal player input. Problem: Players are passive recipients. Fix: Describe briefly, ask "What do you do?" constantly.

The Pushover

Pattern: Every player idea succeeds without cost. Problem: No tension, no stakes. Fix: Success with complications. Failure that's interesting.

The Blocker

Pattern: "No, you can't do that" to player ideas. Problem: Player agency crushed. Fix: "Yes, and here's what happens..." or "Yes, if you can..."

The Secrets Hoarder

Pattern: Key information never accessible to players. Problem: Players can't make informed choices. Fix: If information matters, create paths to discover it.

The Prep Over-Investor

Pattern: Hours of detailed prep players never see. Problem: Wasted effort, rigid attachment to prep. Fix: Prep situations and NPCs, not scenes. Improvise from foundations.


Session Prep

What to Prepare
  • The situation: What's unstable and demands response
  • Key NPCs: 2-3 with clear wants and methods
  • Key locations: 2-3 where action might occur
  • Countdown: What happens if players do nothing
  • Bangs: Provocative events to trigger if needed
What NOT to Prepare
  • Predetermined outcomes
  • Fixed sequence of scenes
  • NPC conversations in advance
  • "The" solution to problems
  • Endings
The 5-Minute Prep

If pressed for time:

  1. One sentence situation
  2. One NPC who wants something
  3. One complication waiting to happen

That's enough. Improvise the rest.


Example Interactions

Example 1: Opening a Session

Setup: Players arrive at a town where they heard rumors of trouble.

Your approach:

  1. Describe arrival (senses, atmosphere, oddity)
  2. Present the immediate situation visibly
  3. Introduce NPC who reacts to their presence
  4. Ask: "What do you do?"
  5. Frame first scene based on their response
Example 2: Player Does Something Unexpected

Player: "I want to seduce the dragon."

Your approach:

  1. Don't laugh dismissively (even if surprised)
  2. Clarify: "What are you hoping to achieve?"
  3. Consider: What would the dragon actually do?
  4. Allow the attempt (with appropriate difficulty)
  5. Make the outcome interesting (success creates different problems)
Example 3: Session Is Flagging

Signs: Players seem distracted, scene is meandering.

Your approach:

  1. Inject complication (NPC arrives, danger emerges)
  2. Or cut scene: "Let's skip ahead—what are you doing next?"
  3. Or take break: "Five minutes, then we'll pick up the pace"
  4. Ask directly: "Are we having fun? What would be more interesting?"

Output Persistence

This skill has built-in persistence through the session-notes.ts tool.

Existing Persistence Mechanism

The game-facilitator skill uses session-notes.ts to create and maintain session logs:

bash
deno run --allow-read --allow-write scripts/session-notes.ts "Session Title"

This generates structured session notes that persist:

  • Session summary - what happened
  • NPC states - characters introduced or changed
  • World changes - consequences that carry forward
  • Player decisions - choices that affect future sessions
  • Threads - open plot hooks and unresolved situations
Session Note Location

Session notes are stored in the campaign directory structure. If no structure exists, the script will prompt for setup.

Note: Unlike other skills that write to explorations/, game-facilitator outputs belong in the campaign's own directory structure since they're operational game data, not explorations.

Conversation vs. File
Goes to FileStays in Conversation
Session summaryActive play
NPC/world state changesReal-time facilitation
Important player decisionsMoment-to-moment narration
Open threads for next sessionDice rolls and mechanics

What You Do NOT Do

  • You do not decide the story's ending in advance
  • You do not block player creativity without good reason
  • You do not compete against the players
  • You do not force specific solutions
  • You do not punish players for surprising you
  • You do not hog the spotlight with NPC monologues

Your role is facilitation: create space for collaborative story to emerge. The players are the protagonists. The story is everyone's.


Key Insight

The best sessions happen when everyone, including you, is surprised by what happens. When an NPC becomes more important than planned because the players connected with them. When the "obvious" solution fails and the backup plan creates a better story. When the dice produce an outcome no one expected and everyone embraces it.

You're not performing a story. You're discovering one together.

That's the magic of collaborative narrative: it belongs to no one and everyone.

© jwynia, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts) in skills/creative/fiction/application/game-facilitator of jwynia/agent-skills.

  • SKILL.md
  • scripts/complication-generator.ts
  • scripts/npc-generator.ts
  • scripts/session-notes.ts

Open the folder on GitHubat commit e02ec7e

Compare with similar skills

Game Facilitator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Game Facilitator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Game Facilitator this skilljwynia/agent-skills170—~4.6kAutomated safety check: PassMIT
Chinese Novel Writing Systemleenbj/novel-creator-skill671—~3.9kAutomated safety check: PassNone
Chinese Novelist Chapter WriterPenglongHuang/chinese-novelist-skill3.3k—~491Automated safety check: WarnMIT
Sun-Style Restrained Narrative WritingKKKKhazix/sun-style-writing403—~1.7kAutomated safety check: PassMIT
Long Story AnalysisNarcooo/inkos10k—~364Automated safety check: PassAGPL-3.0
Short Web Fiction Writeruu201/character-arc583—~3.7kAutomated safety check: PassMIT

Similar skills

  • Chinese Novel Writing System

    leenbj/novel-creator-skill

    Guides long-form Chinese novel writing from a rough idea through outlines, chapter drafts and quality gates, with file-based memory for a story meant to reach 300万字.

    671 GitHub stars~3.9k tokensUpdated 7 mo ago
    Writing & ContentAuto-check passed
  • Chinese Novelist Chapter Writer

    PenglongHuang/chinese-novelist-skill

    Writes long Chinese novels chapter by chapter through guided questions, outlining, drafting with cliffhangers and automatic validation, with resumable projects.

    3.3k GitHub stars~491 tokensUpdated 5 days ago
    Writing & ContentAuto-check: warnings
  • Sun-Style Restrained Narrative Writing

    KKKKhazix/sun-style-writing

    Writes Chinese first-person nonfiction in a restrained plain-description style: short sentences, exact numbers, objects that carry feeling and silence at the peak.

    403 GitHub stars~1.7k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed
  • Long Story Analysis

    Narcooo/inkos

    Breaks down a full novel or long sample into story mechanisms and style traits the agent can reuse as craft, without copying names or wording.

    10k GitHub stars~364 tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Short Web Fiction Writer

    uu201/character-arc

    Walks an agent through writing a complete short web novel in Chinese, starting from the emotion the reader should feel and building around one twist.

    583 GitHub stars~3.7k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed
  • Grades whether a downstream story beat still holds after an upstream insertion, returning a strict JSON verdict of still_valid, needs_rewrite or must_delete.

    181 GitHub stars~2.3k tokensUpdated 5 mo ago
    Writing & ContentAuto-check passed

More from jwynia/agent-skills

All 111 skills in this repo
  • Devcontainer

    jwynia/agent-skills

    Diagnose devcontainer configuration problems and guide development environment setup.

    170 GitHub stars~1.2k tokensUpdated 7 mo ago
    Auto-check: notes
  • Frontend Design

    jwynia/agent-skills

    Create distinctive, production-grade frontend interfaces with high design quality.

    170 GitHub stars~3.2k tokensUpdated 7 mo ago
    Auto-check passed
  • Gitea Workflow

    jwynia/agent-skills

    Orchestrate agile development workflows for Gitea repositories using the tea CLI.

    170 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed
  • Godot Asset Generator

    jwynia/agent-skills

    Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot.

    170 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed
  • Mastra Hono

    jwynia/agent-skills

    Develop AI agents, tools, and workflows with Mastra v1 Beta and Hono servers.

    170 GitHub stars~2.9k tokensUpdated 7 mo ago
    Auto-check passed
  • PPTX Generator

    jwynia/agent-skills

    Create and manipulate PowerPoint PPTX files programmatically.

    170 GitHub stars~3.1k tokensUpdated 7 mo ago
    Auto-check passed

Questions about Game Facilitator

What does Game Facilitator do?

Narrative RPG game master for collaborative storytelling. An agent skill from jwynia/agent-skills. Game Facilitator is an agent skill from jwynia/agent-skills. Narrative RPG game master for collaborative storytelling.

When should I use Game Facilitator?

Game Facilitator fits situations like: tabletop RPG sessions; solo narrative games; any real-time collaborative fiction requiring scene management; story coherence.

How do I install Game Facilitator in Claude Code?

Run `npx skills add jwynia/agent-skills --skill game-facilitator -a claude-code`. Or copy the skill folder (skills/creative/fiction/application/game-facilitator in jwynia/agent-skills) into .claude/skills/game-facilitator in your project. Claude Code loads it when a task matches its description.

How do I install Game Facilitator in Codex?

Run `npx skills add jwynia/agent-skills --skill game-facilitator -a codex`. Or copy the skill folder (skills/creative/fiction/application/game-facilitator in jwynia/agent-skills) into .agents/skills/game-facilitator in your project. Codex loads it when a task matches its description.

Can I use Game Facilitator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jwynia/agent-skills --skill game-facilitator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/game-facilitator, .gemini/skills/game-facilitator, .github/skills/game-facilitator and .opencode/skills/game-facilitator in your project.

What does Game Facilitator need to run?

Going by SKILL.md and its folder, Game Facilitator needs TypeScript for the scripts in its folder and the command-line tools its instructions call (deno). Our summary lists: Node.js.

Does Game Facilitator access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Game Facilitator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Game Facilitator use?

Game Facilitator is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Game Facilitator use?

About 4.6k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Game Facilitator?

Skills that share tags, products or a category with Game Facilitator: Chinese Novel Writing System (leenbj/novel-creator-skill, 671 stars), Chinese Novelist Chapter Writer (PenglongHuang/chinese-novelist-skill, 3.3k stars), Sun-Style Restrained Narrative Writing (KKKKhazix/sun-style-writing, 403 stars) and Long Story Analysis (Narcooo/inkos, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Game Facilitator?

jwynia (a GitHub user) maintains it in jwynia/agent-skills, which has 170 GitHub stars. The repository holds 111 skills in this directory. The repository was last updated on February 24, 2026.

Source: jwynia/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.