# Ose Rules Access

> Query JoelClaw docs/PDF Brain for Old School Essentials rules while preserving Referee-only access and avoiding public corpus leakage.

- Skill: `joelhooks/ose-rules-access` (Agent Skill)
- Install (CLI): `npx skillmds@latest add joelhooks/ose-rules-access`
- Raw SKILL.md: https://api.skillmd.com/api/skills/joelhooks/ose-rules-access/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: joelhooks (https://skillmd.com/u/joelhooks)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/joelhooks/ose-rules-access

---


# OSE Rules Access

Use when implementing or reviewing Old School Essentials rules lookup, Referee adjudication, `consultRules`, source citations, or public monitor output involving rules/source material.

## Policy

- RefereeAgent may consult rules/source.
- PlayerAgents must not access global rules/source unless the Referee deliberately exposes a bounded safe artifact.
- Public monitor output must never include raw private/copyrighted rules chunks.
- Prefer safe summaries, doc IDs, chunk IDs, and short citations over source text.
- Internal events may store doc/chunk IDs for audit and replay.

## Public docs API first

Start with JoelClaw docs/PDF Brain:

```bash
curl -sS https://joelclaw.com/api/docs
curl -sS "https://joelclaw.com/api/docs/search?q=Old%20School%20Essentials&perPage=5&semantic=false"
curl -sS "https://joelclaw.com/api/docs/search?q=Old-School%20Essentials%20referee&perPage=5&semantic=false"
```

Search narrow phrases. Keep `perPage` small. Use `semantic=false` first when checking exact terminology.

## Tool shape

A first `consultRules` tool should:

1. Accept a bounded query and optional adjudication context.
2. Call JoelClaw docs search.
3. Return small referee-facing excerpts or summaries plus doc IDs/chunk IDs.
4. Mark returned data as referee-private unless explicitly transformed into a player-safe/public artifact.
5. Never pass full book chunks into public monitor events.

## Output discipline

When reporting findings:

- Say what was searched.
- Include doc IDs/chunk IDs when available.
- Distinguish source-backed facts from Referee judgment.
- If evidence is thin, say so instead of filling gaps from model memory.

