BotCurrent↗
← Back to examples

Community recipe

Run a tabletop session with persistent campaign state

A tabletop campaign loses continuity when remembered events, character resources and saved notes disagree.

Read original recipe
Suggested result

A session record and consistent next-session state.

What you need: Source-named agent: Claude Code. Suggested inputs: Campaign copy; Table agreement. A disposable local campaign with network display and persistent hooks disabled. Workflow costs and current compatibility remain unverified.

Approve campaign scope and recoverable saves. Keep network display and persistent hooks off unless separately approved. Confirm relationship/state changes, deletions, external services and imported copyrighted material before relevant action.

Community recipe. BotCurrent has not independently tested this workflow.

Setup and access

Proposed inputs

  1. Name

    Campaign copy

    Owner

    Players or game master

    Minimum scope

    One fictional scene, characters and current resources.

    Quality check

    Agree ruleset and starting state.

  2. Name

    Table agreement

    Owner

    Players

    Minimum scope

    Tone, exclusions, roll control and save policy.

    Quality check

    All participants can correct or pause play.

Access and setup — proposed or unknown

Proposed minimum

  1. A disposable local campaign with network display and persistent hooks disabled.

Compatibility unknowns

  1. Unknown: helper compatibility, installed model access and save recovery.

External actions requiring approval

  1. Network exposure, hooks, destructive changes or external content uploads.

Detailed steps and output format

At a glance

Suggested result
A session record and consistent next-session state.Suggested; untested.
Tool
Claude CodeSource-named; check current access.
Suggested inputs
Campaign copy; Table agreementProposed; access notes below.
Human review
Approve campaign scope and recoverable saves. Keep network display and persistent hooks off unless separately approved. Confirm relationship/state changes, deletions, external…
Read full note

Approve campaign scope and recoverable saves. Keep network display and persistent hooks off unless separately approved. Confirm relationship/state changes, deletions, external services and imported copyrighted material before relevant action.

Suggested boundaries; source approvals below.
Setup notes
A disposable local campaign with network display and persistent hooks disabled.Guide notes; proposed setup untested.
Cost
Workflow cost not established. Check current tool pricing, setup and human review costs before trying it.No measured cost or time added.
Content depth
Source-linked example · suggestions untestedDepth does not establish successful execution.
Check source evidence and limits ↓

Function and scope

Personal, Creative production · Single task

Editorial classification; no execution or compatibility test is implied.

No tool mapping reviewed for this task.

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

A tabletop campaign loses continuity when remembered events, character resources and saved notes disagree.

Suggested task · untested

Support a player-directed session and prepare a checked continuation point.

What you could produce

A session record and consistent next-session state.

Where these suggestions come from
  • Core problem: Our suggestion; no result reported by the source
  • Agent job: Our suggestion; no result reported by the source
  • Expected output: Our suggestion; no result reported by the source
  • Relevant job roles: Our suggestion; no result reported by the source
  • Benefit type: Our suggestion; no result reported by the source
Suggestions and their limits

Describes the proposed purpose and review output; measured benefit and successful delivery are not established.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Before you try it · suggestions untested

Original decision guidance and synthetic first check. Source facts are reused by reference; nothing here was executed.

Read the attributed source evidence and original caveats below ↓

Why use this

  1. Returning players need to know what actually happened, which resources remain and which choices are still open. A fluent recap can conceal contradictions that later change the game.

  2. A file-backed session could make continuity inspectable. Players should be able to correct the record and retain control over their characters, tone and table boundaries.

Why an agent / simpler alternative

Useful judgment

Interpret open-ended choices and retrieve relevant story context.

Simpler alternative

Use a shared journal and manual tracker for a human-run session.

Unsuitable when

The group expects certified rules accuracy or has not agreed content boundaries.

Expected deliverable and review checks

Proposed artifact

Before/after state comparison and restart recap.

Critical checks

  1. Resources reconcile with resolved actions.

  2. The recap preserves player decisions and unresolved threads.

Missing output evidence

No session run or restart verification performed.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

One original scene with two fictional characters, a consumable item and a choice that must remain unresolved.

Acceptance checks

  1. Save/reopen preserves the item change and unresolved choice.

  2. No character decision is invented and no network listener starts.

Stop conditions

  1. An unexpected installation, permission change or irreversible write is needed.

Tasks: Campaigns & growthDocuments & filesData & analysis

Useful for: Personal and household

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.
Claude CodeIndependent testing: No
Failure handling, costs and limits

Failure signals and proposed responses

  1. Signal

    The recap changes an earlier player choice.

    Why it matters

    Future consequences rest on invented events.

    Proposed response

    Compare the scene record and ask players to resolve it.

  2. Signal

    Reopening restores different resources.

    Why it matters

    Narration and persisted mechanics have diverged.

    Proposed response

    Pause and reconcile against the last agreed checkpoint.

Effort and cost — unknown

Setup work

  1. Review helpers and agree a bounded scene.

Ongoing review

  1. Check state changes and consent during play.

Unknowns

  1. Unknown: model cost, setup time and long-session reliability.

Limits

  1. One session-management job; no extra count for story, combat or inventory phases.

Full source evidence

Community recipe · Tool workflows

Original task title: Run a tabletop session with persistent campaign state

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://github.com/neuralinitiative/claude-dnd-skill/blob/main/skills/dnd/SKILL.md ↗

Attributed to: Neural Initiative LLC

Supporting source context

Project documentation supporting the linked recipe’s scope, permissions and limits. These references do not establish an independent test or add counted jobs.

Community recipe
Original action type
tool_action
What the source reports
Loads campaign and character files, interprets player choices, calls Python helpers for mechanics, retrieves relevant narrative context, and maintains continuity across turns. Command procedures save session events and resources, update campaign files, and verify persisted replay data before closing.
Source outcome limits
A proposed assisted game session with inspectable state. No correctness, balance, player-enjoyment or faithful adaptation claim. All encounter, story and inventory phases remain one job.
Evidence attribution caveat
This community recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Source approval description
Prompts for campaign, ruleset, display and dice choices. Players retain their decisions. Save-time relationship batches need approval; the main skill also permits silent continuity autosaves. Consequential operations such as deleting campaign data require a pause.
Named tools
Claude Code Read/Write/Edit/Glob/Bash/AskUserQuestion; Python mechanics helpers; Markdown campaign files; optional display.
Model or version
Skill header v2.4.0; source routing names claude-sonnet-4-6, claude-opus-4-6 and claude-haiku-4-5-20251001.
Publication date
Unknown
Source last checked
2026-10-14
Demonstrated in Canada
Unknown
Canadian availability
Unknown
Proposed Canadian adaptation
Use consensual table boundaries, locally chosen session dates and original or lawfully usable campaign material. No Canadian service deployment or model access was checked.
Recommended approval boundaries
Approve campaign scope and recoverable saves. Keep network display and persistent hooks off unless separately approved. Confirm relationship/state changes, deletions, external services and imported copyrighted material before relevant action.