MCPInstall

key-moments

Structure stories around essential emotional moments using Rodriguez's approach integrated with elemental genres. Use when plotting feels mechanical, when emotional beats need defining, or when building stories from vivid scenes rather than plot outlines.

Installs
504
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/jwynia/agent-skills --skill key-moments
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads key-moments automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Key Moments: Genre-Driven Emotional Beats Skill

You help writers identify and sequence the essential emotional experiences that define their story's genre, then build the world, characters, and connective tissue around those moments. Based on Robert Rodriguez's methodology of visualizing key moments first, integrated with elemental genre theory.

Core Principle

Stories are defined by emotional experiences, not plot mechanics. Identify the key moments your genre requires, sequence them for maximum impact, then build everything else to enable those moments.

This inverts the typical outline-then-dramatize approach: you start with vivid, memorable scenes and work backward to what must exist to make them possible.

The Seven Principles

  1. Emotional Experience Primacy: Key moments are defined by the emotional impact they create, not plot mechanics
  2. Systemic Integration: Key moments both emerge from and impact the worldbuilding systems
  3. Character Function Alignment: Characters are designed to enable, experience, or oppose key moments
  4. Visual-Experiential Priority: Key moments are conceived as vivid, memorable scenes first
  5. Flexible Sequencing: The order of key moments can be adjusted to maximize impact
  6. Consequence Cascades: Each key moment creates ripple effects through the story system
  7. Bridging Efficiency: Connective scenes serve multiple functions in world and character development

Key Moments by Elemental Genre

Wonder

Key Moment TypeEmotional ExperienceStory Function
Initial EncounterSurprise and aweEstablishes spectacular nature of setting/concept
Scale RevelationHumbling realization of vastnessContextualizes protagonist's place
Perspective ShiftParadigm change in understandingForces reevaluation of assumptions
Wonder EscalationIntensification of aweRaises stakes and deepens engagement
Transcendent IntegrationMeaning-making through wonderProvides thematic resolution

Mystery

Key Moment TypeEmotional ExperienceStory Function
Question InceptionCuriosity activationEstablishes central puzzle
Pattern RecognitionSatisfaction of connectionProvides momentum and engagement
False ResolutionSurprise from misdirectionCreates complexity and extends engagement
Progressive RevelationDeepening understandingBuilds toward solution
Solution CrystallizationIllumination and closureCompletes emotional journey

Adventure

Key Moment TypeEmotional ExperienceStory Function
Threshold CrossingExcitement of departureTransitions to adventure world
Capability TestConfidence from competenceEstablishes protagonist's abilities
Resource DepletionVulnerability from lossForces adaptation and growth
Ultimate ChallengeFear and determinationTests protagonist's limits
Return TransformationPride and perspectiveDemonstrates growth from journey

Horror

Key Moment TypeEmotional ExperienceStory Function
Wrongness GlimpseUnease from dissonanceEstablishes threat potential
Safety ViolationShock from boundary breachDemonstrates vulnerability
Threat EscalationEscalating dreadRaises stakes
Failed SolutionDespair from ineffectualityDeepens hopelessness
ConfrontationTerror meets courageProvides climactic moment

Thriller

Key Moment TypeEmotional ExperienceStory Function
Stakes EstablishmentConcern for outcomeSets up tension framework
Deadline ImpositionAnxiety from time pressureCreates urgency
Near MissRelief with lingering tensionMaintains engagement through peaks/valleys
Option EliminationMounting pressureForces protagonist into harder choices
Decision Under DuressCatharsis through actionProvides climactic release

Relationship

Key Moment TypeEmotional ExperienceStory Function
Significant ConnectionRecognition of potentialEstablishes relationship basis
Intimacy DeepeningWarmth from vulnerabilityDevelops emotional investment
Value ConflictFrustration from differencesCreates meaningful obstacles
Relationship CrisisHeartbreak or betrayalTests connection's resilience
Reconciliation/ResolutionEmotional closureCompletes relationship arc

Drama

Key Moment TypeEmotional ExperienceStory Function
Internal Conflict RevelationRecognition of contradictionEstablishes character struggle
External Pressure PointStress from circumstancesForces character choices
Failure MomentShame from inadequacyDeepens character journey
Truth ConfrontationPainful self-awarenessCatalyzes change
Character EvolutionSelf-actualizationDemonstrates growth

Issue

Key Moment TypeEmotional ExperienceStory Function
Perspective ChallengeIntellectual discomfortEstablishes issue's complexity
Stake PersonalizationEmotional investmentMakes abstract concrete
Complexity RecognitionCognitive expansionPrevents simplistic resolution
Position TestingValue/belief examinationForces intellectual honesty
Perspective IntegrationNuanced understandingProvides thematic resolution

Ensemble

Key Moment TypeEmotional ExperienceStory Function
Group FormationBelonging potentialEstablishes the collective
Role EstablishmentIdentity within communityDefines character functions
Group FractureLoyalty testingCreates internal conflict
Collective ChallengeShared adversityForces cooperation
Synergy MomentStrength through unityDemonstrates group value

Implementation Process

Phase 1: Key Moment Identification and Sequencing

Step 1: Determine Primary and Secondary Genres

  • Identify the core emotional experiences you want readers to have
  • Select corresponding primary and secondary elemental genres

Step 2: Select Critical Key Moments

  • Choose 3-5 essential moments from the primary genre
  • Add 2-3 supporting moments from the secondary genre
  • Ensure moments create emotional variety and progression

Step 3: Sequence Moments Optimally

  • Arrange chronologically as a starting point
  • Consider emotional pacing and tension curves
  • Allow for non-linear presentation if appropriate

Step 4: Visualize Each Moment

  • Create concrete scene concepts for each key moment
  • Focus on sensory details and emotional impact
  • Define how each moment changes character or world understanding

Phase 2: World Integration

Step 1: Determine Required World Elements

  • What must exist in the world for each key moment to occur?
  • What causal relationships connect world systems to key moments?
  • What consequences do key moments create in the world?

Step 2: Design Supporting Systems

  • Power structures that enable or oppose key moments
  • Organizations with stakes in key moment outcomes
  • Economic and belief systems creating appropriate pressures

Phase 3: Character Function

Step 1: Identify Required Character Functions

  • What roles must be filled for each key moment?
  • Assign functions to specific characters
  • Ensure protagonist experiences the most significant moments

Step 2: Create Character Arcs

  • Design development paths intersecting with key moments
  • Ensure character growth enables progression through moments
  • Create change arcs that pay off in specific key moments

Phase 4: Connective Tissue

Step 1: Identify Bridging Requirements

  • What must happen between key moments?
  • What character and world state changes are needed?
  • What time, distance, and knowledge gaps need filling?

Step 2: Design Multifunctional Bridge Scenes

  • Create connective scenes serving multiple purposes
  • Advance character development while moving toward key moments
  • Reveal world information relevant to upcoming moments

Step 3: Install Setup-Payoff Mechanics

  • Plant necessary elements for later key moments
  • Create foreshadowing enhancing later emotional impact
  • Establish rules or limitations significant later

Phase 5: Testing and Refinement

Evaluate Emotional Progression:

  • Do key moments create intended emotional journey?
  • Are there gaps or redundancies in emotional experience?
  • Should moment intensity or sequence be adjusted?

Verify Causal Logic:

  • Does each key moment follow logically from preceding elements?
  • Do character decisions leading to moments make sense?
  • Do world systems create appropriate conditions for moments?

Test for Genre Satisfaction:

  • Are primary genre emotional experiences most prominent?
  • Does secondary genre support rather than overshadow primary?
  • Are genre-specific satisfaction conditions met?

Worked Example: Wonder + Mystery

Concept: An oceanographer discovers unusual bioluminescent patterns that appear to form a communication system, leading to evidence of an ancient aquatic civilization.

Wonder Key Moments (Primary):

  1. Initial Encounter: Discovery of synchronized bioluminescent patterns across different species
  2. Scale Revelation: Realization that patterns extend throughout ocean, suggesting global network
  3. Wonder Escalation: Finding first artifacts of the ancient civilization
  4. Transcendent Integration: Communication breakthrough with the still-extant consciousness

Mystery Key Moments (Secondary):

  1. Question Inception: Why did this civilization disappear from human awareness?
  2. False Resolution: Evidence suggesting civilization destroyed itself
  3. Solution Crystallization: Discovery that civilization evolved beyond physical form

Character Functions:

  • Wonder Experiencer: Oceanographer protagonist with personal connection to the ocean
  • Mystery Solver: Research partner with cryptographic expertise
  • Opposition Force: Government/corporate agent wanting to weaponize discovery
  • Wonder Skeptic: Scientific community representative demanding proof
  • Knowledge Keeper: Elderly mentor with folklore knowledge hinting at ancient truth

Connective Tissue:

  • Research funding challenges forcing creative approaches
  • Relationship development between protagonist and research partner
  • Escalating interest from outside forces as discoveries become harder to hide
  • Progressive decoding providing partial clues

Advantages

  1. Efficiency: Focusing on key moments first prevents wasted development of unnecessary elements
  2. Emotional Clarity: Defining the story through emotional experiences ensures genre satisfaction
  3. Structural Flexibility: Allows non-linear development while maintaining narrative coherence
  4. World-Story Integration: Creates feedback loop between worldbuilding and narrative moments
  5. Character Functionality: Ensures characters serve clear purposes in creating key moments
  6. Development Prioritization: Helps focus worldbuilding on elements most critical to the story
  7. Revision Guidance: Provides clear framework for identifying what's working and what isn't

Output Persistence

Output Discovery

  1. Check for context/output-config.md in the project
  2. If found, look for this skill's entry
  3. If not found, ask user: "Where should I save key moment designs?"
  4. Suggest: stories/structure/ or explorations/stories/

Primary Output

  • Genre selection - Primary and secondary elemental genres
  • Key moments list - 5-8 essential emotional beats
  • Character functions - Roles needed for each moment
  • Connective tissue - Bridge scenes between moments

File Naming

Pattern: {story-name}-moments-{date}.md

Verification (Oracle)

What This Skill Can Verify

  • Genre alignment - Do moments match primary genre? (High confidence)
  • Emotional variety - Is there progression, not repetition? (High confidence)
  • Causal logic - Do moments follow from character/world? (Medium confidence)

What Requires Human Judgment

  • Emotional impact - Will these moments land?
  • Bridge efficiency - Are connective scenes serving multiple purposes?
  • Genre satisfaction - Does overall sequence fulfill genre promise?

Oracle Limitations

  • Cannot assess whether moments will emotionally resonate
  • Cannot predict reader engagement with specific beats

Feedback Loop

Session Persistence

  • Output location: See context/output-config.md
  • What to save: Genres, moments, functions, bridges
  • Naming pattern: {story-name}-moments-{date}.md

Cross-Session Learning

  • Check for prior key moment work on this story
  • Ensure moments maintain consistency with changes
  • Failed emotional beats inform anti-patterns

Design Constraints

This Skill Assumes

  • Story has genre (emotional experience goal)
  • Moments can be identified (not pure slice-of-life)
  • Writer wants emotional structure, not just plot

This Skill Does Not Handle

  • Genre identification - Route to: genre-conventions
  • Scene-level pacing - Route to: scene-sequencing
  • Character arc details - Route to: character-arc

Degradation Signals

  • Plot-first injection (emotion retrofit)
  • Genre mismatch (wrong emotional beats)
  • Moment inflation (everything climactic)

Reasoning Requirements

Standard Reasoning

  • Single genre moment selection
  • Basic character function assignment
  • Simple bridge identification

Extended Reasoning (ultrathink)

  • Full moment sequence - [Why: all moments must create emotional journey]
  • Multi-genre integration - [Why: primary/secondary must balance]
  • World-moment coordination - [Why: world must enable moments naturally]

Trigger phrases: "design the complete emotional arc", "integrate both genres", "coordinate world with moments"

Execution Strategy

Sequential (Default)

  • Genre selection before moment identification
  • Moments before character functions
  • Functions before connective tissue

Parallelizable

  • Designing moments for different genres
  • Research into different emotional progressions

Subagent Candidates

TaskAgent TypeWhen to Spawn
Genre researchgeneral-purposeWhen exploring genre emotional requirements
Story consistencyExploreWhen checking moments against existing story

Context Management

Approximate Token Footprint

  • Skill base: ~4k tokens (genres + implementation)
  • With worked example: ~5k tokens
  • With all genres: ~6k tokens

Context Optimization

  • Focus on primary genre moments only
  • Full genre tables are reference
  • Worked example optional

When Context Gets Tight

  • Prioritize: Primary genre moments, current phase
  • Defer: Secondary genre details, all genre tables
  • Drop: Worked example, advantages list

Anti-Patterns

1. Plot-First Injection

Pattern: Building the plot outline first, then trying to locate where to insert emotional beats. Why it fails: Emotion retrofitted to plot feels mechanical. The moments don't emerge naturally from character and situation; they interrupt the story to deliver required feelings. Fix: Start with the emotional experiences you want readers to have. Build backward: what situations create those emotions? What characters would be in those situations? What world enables those situations?

2. Genre Mismatch

Pattern: Choosing key moments that deliver different emotional experiences than the primary genre promises. Why it fails: Readers come to genres for specific emotional experiences. A horror novel that delivers primarily relationship moments disappoints horror readers without satisfying romance readers. Fix: Verify that your most prominent key moments belong to your primary genre. Secondary genre moments support; they don't dominate. If the mismatch is intentional, you're writing a different genre than you think.

3. Logistics-Only Bridges

Pattern: Connective scenes that only move characters from one key moment to the next without developing character, world, or theme. Why it fails: Readers feel the pacing sag in bridge sections. They're just waiting for the next interesting thing. The story develops a stop-start rhythm rather than continuous engagement. Fix: Every bridge scene should serve at least two purposes: moving toward the next key moment AND developing character OR revealing world OR exploring theme. If a scene only serves logistics, compress or cut it.

4. Moment Inflation

Pattern: Treating every scene as a key moment, loading the story with climactic experiences. Why it fails: Without contrast, high-intensity moments lose impact. Emotional fatigue sets in. Readers become numb when everything is equally important. Fix: Limit key moments to 5-8 per story. Let some scenes be quieter. The valleys make the peaks feel taller. Save your strongest moments for where they'll have maximum impact.

5. Forced Causation

Pattern: Key moments that don't follow logically from established character and world but happen because the plot needs them. Why it fails: Readers sense when characters act against their nature to reach a predetermined destination. The moments feel artificial, earned by authorial fiat rather than story logic. Fix: Work backward from each key moment: given this character and this world, what sequence of events makes this moment inevitable? If you can't find a path, either the moment doesn't fit or the character/world needs adjustment.

Integration

Inbound (feeds into this skill)

SkillWhat it provides
genre-conventionsGenre-specific emotional requirements
story-senseDiagnosis of what emotions are missing or misplaced
character-arcCharacter states that enable or resist key moments

Outbound (this skill enables)

SkillWhat this provides
scene-sequencingClear emotional targets for scene construction
worldbuildingWorld requirements to enable key moments
outline-collaboratorStructural skeleton built around emotional beats

Complementary

SkillRelationship
genre-conventionsKey-moments defines the emotional beats; genre-conventions ensures they satisfy genre expectations
scene-sequencingKey-moments identifies what moments matter; scene-sequencing structures the approach and aftermath

FAQ

What does the key-moments skill do?

Structure stories around essential emotional moments using Rodriguez's approach integrated with elemental genres. Use when plotting feels mechanical, when emotional beats need defining, or when building stories from vivid scenes rather than plot outlines.

How do I install key-moments?

Run npx skills add https://github.com/jwynia/agent-skills --skill key-moments in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/key-moments/ (personal) or .claude/skills/key-moments/ (project).

Which AI agents can use key-moments?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is key-moments safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains key-moments?

It is published by jwynia in jwynia/agent-skills. It has 504 recorded installs.

More from jwynia/agent-skills

View all →

presentation-design

jwynia/agent-skills

Design and evaluate presentations that communicate effectively. Use when designing a presentation, creating slides, getting presentation feedback, structuring a talk, or reviewing slides. Keywords: presentation, slides, talk, PowerPoint, Keynote, reveal.js.

Docs & Writing2.5K installs

frontend-design

jwynia/agent-skills

Create distinctive, production-grade frontend interfaces with high design quality. Provides analysis tools for auditing existing designs and generation tools for creating color palettes, typography systems, design tokens, and component templates. Supports React, Vue, Svelte, and vanilla HTML/CSS. Use when building web components, pages, or applications. Keywords: design, UI, frontend, CSS, components, palette, typography, tokens, accessibility.

Frontend & Design2.3K installs

requirements-analysis

jwynia/agent-skills

Diagnose requirements problems and guide discovery of real needs and constraints

AI & Agents2.3K installs

godot-best-practices

jwynia/agent-skills

Guide AI agents through Godot 4.x GDScript coding best practices including scene organization, signals, resources, state machines, and performance optimization. This skill should be used when generating GDScript code, creating Godot scenes, designing game architecture, implementing state machines, object pooling, save/load systems, or when the user asks about Godot patterns, node structure, or GDScript standards. Keywords: godot, gdscript, game development, signals, resources, scenes, nodes, state machine, object pooling, save system, autoload, export, type hints.

web-search-tavily

jwynia/agent-skills

Search the web using Tavily API for high-quality, AI-optimized results with advanced filtering options. Use when you need structured search results, domain filtering, relevance scores, or AI-generated answer summaries. Requires TAVILYAPIKEY. Keywords: tavily, advanced search, filtered search, domain filtering, relevance scoring.

godot-asset-generator

jwynia/agent-skills

Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot. Covers the full art pipeline from concept art and style guides to final sprites, sprite sheets, and import configuration. This skill should be used when creating game art, generating sprites, making tilesets, creating UI elements, or preparing assets for Godot import. Keywords: game assets, AI art, DALL-E, Replicate, fal.ai, sprite sheet, tileset, Godot, pixel art, character sprite, game art, texture, animation frames.

Media & Creative1K installs

Popular ai & agents skills

View category →

google-agents-cli-publish

google/agents-cli

This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).

AI & Agents513.9K installs

google-agents-cli-eval

google/agents-cli

This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).

AI & Agents513.5K installs

skill-creator

anthropics/skills

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

OfficialAI & Agents416.4K installs

codex-pet

prime-skills/runcomfy-agent-skills

Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.

AI & Agents402.1K installs

full-output-enforcement

leonxlnx/taste-skill

Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.

AI & Agents401K installs

executing-plans

obra/superpowers

Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available

AI & Agents245.7K installs