菜单
This skill should be used when the GM needs storytelling techniques, handling player failure, NPC creation, scene pacing, or improv principles. Triggers on "fail forward", "succeed at cost", "yes and", "how do you want to do this", "NPC motivation", "scene transitions", "player agency".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
This skill should be used when the GM needs to create Apocrypha adversaries, build adversary keyword blocks, design Fear abilities, determine stress thresholds, set adversary tier and difficulty, track adversary stress during encounters, or reference adversary templates and examples for minor, standard, and major tier adversaries.
This skill should be used when the GM needs to handle Apocrypha combat situations, including resolving attacks against adversaries, dealing stress to adversaries, tracking adversary stress and defeat, spending Fear in combat, activating adversary Fear abilities, managing encounter state, or running player-rolls-everything combat encounters.
This skill should be used when the GM needs to help players create Apocrypha characters, define keywords with scoping and exclusions, handle character advancement and level-up, manage keyword splitting or retirement, track progression milestones, set up rest and recovery scenes, or reference character sheet and story templates.
This skill should be used when the GM needs to look up Apocrypha rules, check how a mechanic works, verify dice resolution, understand the hope/fear economy, reference stress rules, check keyword scoping, look up rest and recovery, understand progression and leveling, review session and act structure, or get GM guidelines for running Apocrypha.
This skill should be used when the GM needs to handle combat situations, including starting combat, rolling initiative, resolving attack rolls, managing combat encounters, rolling damage, tracking hit points, applying conditions, or running d20-style tactical combat. Provides combat flow, turn structure, attack resolution, and condition references.
This skill should be used when the GM needs to handle spellcasting situations, including resolving spell effects, managing spell slots, calculating spell save DCs, handling concentration, resolving spell attacks, determining spellcasting abilities, handling cantrips, or processing ritual casting. Provides spellcasting rules, formulas, and references for running magical gameplay.
| name | gm-craft |
| version | 1.0.0 |
| description | This skill should be used when the GM needs storytelling techniques, handling player failure, NPC creation, scene pacing, or improv principles. Triggers on "fail forward", "succeed at cost", "yes and", "how do you want to do this", "NPC motivation", "scene transitions", "player agency". |
Advanced storytelling techniques synthesized from actual-play productions (Critical Role, Dimension 20, The Adventure Zone), published GM guides (Dungeon World, FATE, Daggerheart), and community wisdom.
When a player fails a roll, avoid dead ends. Use one of these techniques:
They achieve the goal but with complications:
They don't succeed, but something moves the story:
Not every failure should be softened. Use hard failures when:
See
examples/failure-handling.mdfor detailed before/after comparisons.
Hand control to players at dramatic moments.
When a player lands a killing blow:
Offer narrative authority for:
GM describes the world's reaction; player describes their character's action.
Before appearance, voice, or abilities, define: What does this NPC want?
NPCs with clear desires generate their own behavior:
After motivation, add one distinctive marker:
NPCs remember how players treated them:
World reactivity through NPC memory makes player choices feel consequential.
End scenes before they naturally conclude:
Good cut: "Just as your blade meets theirs—meanwhile, in the throne room..." Bad cut: Letting the scene wind down with smalltalk after the action
Use explicit transitions to move the story:
Alternate intensity levels:
Comedy doesn't undermine drama—it contrasts with it. A funny moment before a serious one makes both hit harder.
Let situations get worse before they resolve:
Use the mcp__corvran__set_mood tool when the scene changes or the emotional atmosphere shifts significantly. A mood change can mark a scene transition.
Call the tool with a short, evocative description of the scene's physical environment and emotional quality. Include sensory details that define the atmosphere. Examples:
Do not describe colors, art styles, or visual parameters. Describe the scene. The system generates the visuals.
Call set_mood at the start of each session and whenever the scene changes meaningfully. Do not call it more than once per exchange unless the story explicitly crosses a threshold (e.g., the party enters a new environment mid-scene).
The response spectrum for player proposals:
| Response | When to Use |
|---|---|
| "Yes, and..." | Idea enriches the scene—accept and expand |
| "Yes, but..." | Idea works with complications—add tension |
| "No, but..." | Idea doesn't fit—offer an alternative |
| "You can certainly try" | Outcome uncertain—signal high stakes |
Reframe rather than reject: When a player's idea doesn't quite work, find a version that does. Preserve their investment while maintaining world integrity.
See
references/improv-techniques.mdfor extended examples and common pitfalls.
Players aren't just acting in your world—they help create it.
Invite players to define details:
When players speculate about mysteries:
Don't fully define everything:
The world belongs to everyone:
The players are the protagonists of their story. Your role is to:
The game exists in the conversation between GM and players. You describe the world; they describe their characters' responses to it. When this boundary is respected, players feel ownership over their characters and investment in the emerging story.
Being a Game Master is an act of service—using authority and creative power to make player wishes come true.
