rpg-observe

Observe rpg-server state subtrees and return JSON via dot-path queries.

Updated May 2, 2026
One-click install
npx skills add https://github.com/onelittlenightmusic/skills-rpg --skill rpg-observe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rpg-observe
Source: https://github.com/onelittlenightmusic/skills-rpg/tree/main/skills/rpg-observe
Command: npx skills add https://github.com/onelittlenightmusic/skills-rpg --skill rpg-observe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables continuous observation of a specified portion of the rpg-server state, turning it into JSON for caching and downstream consumption in mywant workflows.

Core Features & Use Cases

  • Observe a subtree of the rpg-server state and return its value as JSON.
  • Target a specific path with a dot-path; omit the target to observe the full state.
  • Integrates with mywant caching to track and react to game-state changes (e.g., doors, stages, or player positions).

Quick Start

Provide a JSON argument specifying a target path to observe a substate, or omit the target to observe the entire state.

Frequently Asked Questions about rpg-observe

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

FAQPage Schema
How do I observe rpg-server state and export it as JSON?

You can observe rpg-server state by querying the observe endpoint with actor=chap. It returns a JSON snapshot containing fields like value, target, achievements_unlocked, and next_goal for downstream caching and consumption.

Can I fetch a specific value from the game state using a dot-path?

Yes, you can fetch specific game state values by providing a JSON argument with a target field set to a dot-path, such as a door's status or current stage data. Omitting the target returns the full state snapshot as JSON.

What is the best way to monitor RPG state changes for caching workflows?

Monitoring RPG state changes for caching workflows is done by continuously observing a specified subtree of the rpg-server state. This produces JSON snapshots that integrate with mywant caching to track and react to changes like player positions or door statuses.

What fields are included in the JSON response when monitoring game state snapshots?

The JSON response from monitoring game state snapshots includes value, target, achievements_unlocked, and next_goal fields. These are produced by querying the rpg-server observe endpoint using actor=chap with an optional target path.

Do I need to specify a target path to observe the full rpg-server state?

No, you do not need to specify a target path to observe the full rpg-server state. Simply omit the target field from the JSON argument, and the observe endpoint returns the entire state as a JSON snapshot.

Why does my rpg-server observation return the entire state instead of a specific subtree?

Your observation returns the entire state because the target field was omitted from the JSON argument. To observe a specific subtree, provide a dot-path in the target field to fetch only the desired portion of the game state.