ttrpg-writing

Writes and reviews D&D campaign wiki content using DM-facing and player-facing prose standards.

Updated May 29, 2026
One-click install
npx skills add https://github.com/Thedougler/shattered-sea-wiki --skill ttrpg-writing-thedougler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ttrpg-writing
Source: https://github.com/Thedougler/shattered-sea-wiki/tree/main/.claude/skills/ttrpg-writing
Command: npx skills add https://github.com/Thedougler/shattered-sea-wiki --skill ttrpg-writing-thedougler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? TTRPG campaign wikis mix two incompatible audiences — DMs who need scannable reference material and players who need immersive prose — and AI-generated content tends to produce atmospheric filler that fails at the table. This Skill enforces consistent writing standards so every wiki page serves its intended reader. ## Core Features & Use Cases - Dual-mode writing: Separates DM-facing reference content (terse, point-first, scannable) from player-facing prose (second-person, sensory, immersive) and applies the right technique to each section. - Anti-slop quality pass: Detects and removes banned structures like contrastive reframes, portentous withholding, negative-space writing, and invented stakes. - Callout and publish enforcement: Converts non-standard Obsidian callouts to the four allowed types and audits publish/audience frontmatter so GM secrets never leak to player-facing pages. - Use Case: Ask the agent to rewrite a flat NPC description, and it applies the Brennan voice principles, fixes wrong callout types, verifies wikilinks, and wires up paired public/DM companion pages. ## Quick Start Ask the agent to rewrite a wiki page or draft a read-aloud for your next session, and it will apply the correct mode and quality standards automatically.

Frequently Asked Questions about ttrpg-writing

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

FAQPage Schema
How do I write better DM-facing notes for D&D sessions?▼

DM-facing content uses point-first structure: lead with the core noun, state its condition, then put mechanics in parentheses. Keep paragraphs under three sentences, bold threats and NPCs, and ensure every sentence gives the DM something to say, do, or decide.

How do I write read-aloud text for tabletop RPG sessions?▼

Read-aloud text uses second-person present tense, layers at least three senses, and ends on an unresolved hook. Keep it to four sentences maximum, describe what the world does rather than what players feel, and never include conditional framing.

What Obsidian callout types should a D&D campaign wiki use?▼

This standard allows exactly four types: read-aloud for spoken narration, dm for single directives, mechanic for rules and DCs, and check for tiered skill check outcomes. Other types like secret, warning, or note are converted automatically.

How do I keep GM secrets out of player-visible wiki pages?▼

Every page sets publish and audience frontmatter fields, and entities introduced to players get paired pages: a public page plus a DM companion file with a -dm suffix. The publish-guard reference defines routing rules for extracting leaked private content.

When should I not use atmospheric prose in campaign notes?▼

Avoid atmospheric prose in mechanical reference material like stat blocks, DC tables, clock entries, and inventory lists, which the DM reads as data. Voice and prose technique apply only to read-aloud text, NPC descriptions, and narrative DM notes.