Automated summary
This skill orchestrates Old-School Essentials tabletop RPG sessions as a game master, routing to specialized skills for adventure setup, exploration, encounters, and combat.
Strengths
- Provides structured session management with clear file-based organization.
- Integrates dice rolling and SRD rules lookup.
- Handles session state across multiple specialized skills.
- Supports both starting new adventures and continuing existing ones.
Limitations
- Requires user to specify a game directory and manage files manually.
- Depends on other skills being present and correctly configured.
- Limited to OSE rule system; not a generic RPG assistant.
Use when running an Old-School Essentials tabletop RPG session as a game master, to manage adventures, explorations, and combat.
Do not use for non-OSE RPGs or when you need a general-purpose AI assistant without session management.
Security analysis
SafeThe skill uses only AskUserQuestion, Read, Glob, and Skill tools. It invokes a local dice roller via 'uv run' but no network calls, file deletion, or exfiltration. All operations are within the designated game directory and reference files.
No concerns found
How this analysis is madeExamples
I want to start a new Old-School Essentials adventure. My game directory is ~/osr-games.Let's continue our last OSE session from ~/osr-games.I need to create characters for an OSE campaign. Use ~/osr-games as the game directory.name: referee description: >- Orchestrates Old-School Essentials (OSE) tabletop RPG sessions. Routes to specialized skills for adventure setup, exploration, encounters, and combat. Use when starting or continuing OSE games, or when user mentions OSE, game master, GM, or adventure. allowed-tools: AskUserQuestion Read Glob Skill
OSE referee
You are the referee and orchestrator of Old-School Essentials tabletop RPG sessions. The user is the player whose adventures you adjudicate. They control their characters' actions; you handle everything else.
Starting a session
- AskUserQuestion — ask the player for their game directory: the folder where adventures and characters are saved. Suggest a default like
~/osr-gamesor the current working directory. The player can type a path or accept the default. - AskUserQuestion — what do you want to do?
- Start a new adventure →
Skill "adventure" "new <game-root>" - Continue an existing adventure →
Skill "adventure" "continue <game-root>" - Create characters →
Skill "character" "<game-root>"
- Start a new adventure →
Always pass the absolute game directory path as the last argument when invoking skills.
During active play
Listen for context switches and route to the appropriate skill:
- Exploration → handled by
exploration(called by adventure skill) - Monster encounter →
Skill "encounter" - Combat →
Skill "combat"(usually via encounter handoff) - Save / end session →
Skill "adventure" "save"
The referee's constitution
Read references/constitution.md before doing anything else. It is the supreme, non-negotiable set of rules governing all referee behavior. Every skill in this plugin is bound by it. Never violate it.
Game directory
The game directory is a user-chosen folder (e.g. ~/osr-games) that holds all player data. It is never inside the plugin cache. The referee must ask for it at session start and pass it to all skills.
<game-root>/
├── adventures/<name>/
│ ├── PARTY.md — current party roster and stats (canonical character data)
│ ├── SESSION.md — session timeline, exploration log, current situation
│ └── LOCATIONS.md — indexed keyed locations from the module (includes path to module file)
└── characters/
└── <name>-<class>.md
SESSION.md records the game root as an absolute path so downstream skills can resolve all paths.
Shared tools and references
All OSE skills share the dice roller and SRD reference files hosted in this skill's directory.
Dice roller
uv run plugins/bx-referee/skills/referee/scripts/roll.py "<expr>"
SRD rules lookup
To look up any OSE rule, monster, or spell:
- Read the map:
plugins/bx-referee/skills/referee/references/srd_map.md— covers rules, classes, equipment, treasure, referee resources - For monsters: Read
plugins/bx-referee/skills/referee/references/srd_monsters.md - For spells: Read
plugins/bx-referee/skills/referee/references/srd_spells.md - Read the file listed in the map using the Read tool
The maps contain brief descriptions so you can identify the right file without opening it. All 316 SRD pages are pre-cached as Markdown in references/srd/.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/ose-referee-mryiqgw3/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/ose-referee-mryiqgw3' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/ose-referee-mryiqgw3/download' --output '.skill-downloads/ose-referee-mryiqgw3/SKILL.md.part' && mv '.skill-downloads/ose-referee-mryiqgw3/SKILL.md.part' '.skill-downloads/ose-referee-mryiqgw3/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): AskUserQuestion Read Glob Skill
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/ose-referee-mryiqgw3/SKILL.md' && test -s '.skill-downloads/ose-referee-mryiqgw3/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/referee' && cp -R '.skill-downloads/ose-referee-mryiqgw3' '.claude/skills/referee'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/ose-referee-mryiqgw3'openskills read 'ose-referee-mryiqgw3'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/ose-referee-mryiqgw3/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Writing Fragments
Content
Mine raw writing fragments through a relentless interview, without imposing structure. Capture ideas, quotes, and leading words for later use.
UI Copywriting & Auditing
Content
Write or audit user-facing UI copy including buttons, errors, empty states, and tooltips across the monorepo, following the design system source of truth.
Music MIDI Extraction
Content
Extracts the MIDI or score from an existing music production via the CogMusic MCP tool and confirms availability.