story-state

Inspect and control mutable text-adventure run state with stable wrappers.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/lgjsd/StoryShell --skill story-state
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-state
Source: https://github.com/lgjsd/StoryShell/tree/main/openclaw/skills/story-state
Command: npx skills add https://github.com/lgjsd/StoryShell --skill story-state

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage mutable text-adventure run state with stable wrappers, enabling safe, reversible changes and clear separation between live data and canonical story data.

Core Features & Use Cases

  • Inspect the current state with lightweight wrappers and helpers.
  • Save, load, and branch runs to experiment with different narrative paths.
  • Reset to initial state or patch specific flags and relationships.
  • Keep mutable state isolated from canonical data and enforce deterministic state handling.
  • Use simple, code-driven workflows to manage state across stories and runs.

Quick Start

Show the current state with storyshell-state show <state-file> and then reset or patch as needed.

Frequently Asked Questions about story-state

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage mutable state in a text adventure safely?

Mutable state in a text adventure is managed safely through stable wrappers that keep live run data separate from canonical story data, enabling reversible changes and deterministic state handling.

Can I save and load checkpoints to branch narrative paths?

Yes, you can save and load checkpoints to branch narrative paths, allowing you to experiment with different story routes and reset to initial states without permanently losing previous run data.

How do I patch specific flags or relationships in story state?

You can patch specific flags or relationships in story state using code-driven workflows provided by deterministic state helpers, which allow targeted updates while keeping mutable data isolated from canonical data.

What is the best way to reset a text adventure run to its initial state?

Resetting a text adventure run to its initial state is best handled through lightweight wrappers that restore the original conditions, providing a safe, reversible workflow for clearing mutable data.

Why keep mutable run state separate from canonical story data?

Keeping mutable run state separate from canonical story data ensures deterministic state handling, preventing unintended permanent modifications to the core narrative while allowing safe experimentation across runs.

Are there limitations to patching mutable state across stories?

Patching mutable state across stories requires using enforced deterministic state helpers and stable wrappers, limiting direct modifications to ensure changes remain reversible and do not corrupt canonical data.