Agent skill

Create Tabletop Rpg

by FerroxLabs in FerroxLabs/wayland

End-to-end workflow for designing, playtesting, illustrating, laying out, and publishing a tabletop role-playing game.

Apache-2.0Auto-check passed

Install Create Tabletop Rpg

skills CLI
$ npx skills add FerroxLabs/wayland --skill create-tabletop-rpg -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FerroxLabs/wayland create-tabletop-rpg --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/workflows/create-tabletop-rpg .claude/skills/create-tabletop-rpg && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
create-tabletop-rpg
GitHub stars
608
Token cost
~2.6k tokens
SKILL.md length
1,224 words
Files
1
Skills in repo
1,194
Repo updated
First seen
Licence
Apache-2.0

At a glance

End-to-end workflow for designing, playtesting, illustrating, laying out, and publishing a tabletop role-playing game.

  • Works in 6 steps: A core mechanic delivers a distinctive… → Playtesting has validated that the rules… → The rulebook is written in clear,… → …
  • The user wants to create tabletop rpg
  • SKILL.md covers When to Use, Prerequisites, Steps and Decision Points, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Create Tabletop Rpg is an agent skill from FerroxLabs/wayland. End-to-end workflow for designing, playtesting, illustrating, laying out, and publishing a tabletop role-playing game. Covers core system design, character creation mechanics, setting development, playtesting methodology, art direction, layout and graphic design, and publishing on DriveThruRPG, itch.io, and through Kickstarter campaigns. Use when the user wants to create tabletop rpg or needs a structured multi-step process for this goal. Do NOT use when the request is a single-step task or requires professional…

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.

When your agent uses it

  • The user wants to create tabletop rpg
  • Needs a structured multi-step process for this goal
  • The request is a single-step task
  • Requires professional advice beyond educational guidance

Example prompts

  • “/create-tabletop-rpg”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. A core mechanic delivers a distinctive play experience
  2. Playtesting has validated that the rules are clear, balanced, and fun
  3. The rulebook is written in clear, unambiguous prose with examples
  4. Professional art and layout make the book inviting to read
  5. The game is published on digital marketplaces and available for purchase
  6. A community exists for players and GMs to share experiences

What it can do on your machine

Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Create Tabletop Rpg loads about 2.6k tokens when it runs. Until then it costs about 143 tokens; SKILL.md has 1,224 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~143
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 1,224 words, ~2,648 tokens.

Download SKILL.mdSave it as .claude/skills/create-tabletop-rpg/SKILL.md (or your agent's skills folder).
name
create-tabletop-rpg
description
End-to-end workflow for designing, playtesting, illustrating, laying out, and publishing a tabletop role-playing game. Covers core system design, character creation mechanics, setting development, playtesting methodology, art direction, layout and graphic design, and publishing on DriveThruRPG, itch.io, and through Kickstarter campaigns. Use when the user wants to create tabletop rpg or needs a structured multi-step process for this goal. Do NOT use when the request is a single-step task or requires professional advice beyond educational guidance.
license
Apache-2.0
type
workflow
skills
tabletop-rpg-designer worldbuilding-master digital-illustrator self-publishing-guide
trigger_phrases
I want to create a tabletop RPG design my own RPG system make a TTRPG publish a tabletop game create an RPG rulebook design a role-playing game TTRPG from…
metadata.author
foundry-skills
metadata.version
1.0.0
metadata.tags
tabletop-rpg game-design content-marketing step-by-step planning
metadata.category
creative-project
metadata.depends
tabletop-rpg-designer worldbuilding-master digital-illustrator self-publishing-guide

Create Tabletop Rpg

Estimated time: 4-8 months

This workflow guides you through creating a complete tabletop role-playing game from initial system concept through design, playtesting, art, layout, and publication. The indie TTRPG scene has exploded in recent years, with platforms like itch.io and DriveThruRPG making it possible for solo designers to reach thousands of players. But creating a good TTRPG requires a rare combination of game design skill, writing ability, visual presentation, and willingness to playtest relentlessly.

The workflow covers six phases: system design, worldbuilding and writing, playtesting iteration, art direction and creation, layout and graphic design, and publishing and distribution. It works for anything from a one-page micro-RPG to a full 200+ page rulebook.

By the end of this workflow you will have: a playtested game system, a written and edited rulebook, professional art and layout, and a published game available for purchase.

When to Use

  • User wants to create tabletop rpg
  • User needs a structured, step-by-step process for create tabletop rpg
  • User wants to create a tabletop RPG
  • design my own RPG system
  • make a TTRPG
  • Do NOT use when: the request is outside the scope of create tabletop rpg or requires professional advice beyond educational guidance
  • Do NOT use for single-step tasks that one atomic skill can handle independently

Prerequisites

Before starting this workflow, ensure:

  • Experience playing tabletop RPGs (understanding what makes them work)
  • A game concept or mechanical idea you want to explore
  • Access to playtest groups (in-person or online)
  • Basic writing ability (the rulebook is a technical document that must be clear)
  • Budget for art and layout (or willingness to learn these skills)

Steps

Step 1: Design Your Core System (uses: tabletop-rpg-designer)

Use the Tabletop RPG Designer and D&D Master skills to design the core mechanical framework.

  • Input: game concept and mechanical ideas, Target play experience (combat-focused, narrative-driven, investigation, horror), Complexity level (rules-light, medium-crunch, heavy-crunch)
  • Output: Resolution system, character creation, and action economy, Attributes, skills, classes/playbooks, and advancement, Combat or challenge resolution rules
  • Key focus: Defining the core resolution mechanic: what dice do players roll, what

Step 2: Build the World and Write the Rules (uses: worldbuilding-master)

Use the Worldbuilding Master and Game Narrative Writer skills to create the setting and write the complete rulebook text.

  • Input: core-mechanics from Step 1 (system that the world must serve), design-pillars from Step 1 (principles guiding world design), character-system from Step 1 (world context for character options)
  • Output: World, factions, locations, and adventure hooks, Complete first draft of all game text, Introductory scenario for new groups
  • Key focus: Building a setting that the mechanics reinforce (a horror game needs a

Step 3: Playtest and Iterate (uses: tabletop-rpg-designer)

run structured playtests and iterate.

  • Input: rulebook-draft from Step 2 (rules to test), starter-adventure from Step 2 (scenario for testing), core-mechanics from Step 1 (systems to validate)
  • Output: Structured feedback from all playtest sessions, Rules changes documented with rationale, Character options, abilities, and encounters tested for balance
  • Key focus: Running at least 3 internal playtests (you as GM, observing where players

Step 4: Commission or Create Art (uses: digital-illustrator)

plan and create (or commission) the art that brings the game to life.

  • Input: revised-rulebook from Step 3 (content that needs illustration), setting-bible from Step 2 (visual reference for the world), character-system from Step 1 (character types to depict)
  • Output: Style guide, mood boards, and visual identity document, Detailed descriptions for each illustration needed, Complete set of illustrations for the rulebook
  • Key focus: Creating an art direction document: style, mood, color palette, and reference

Step 5: Layout and Graphic Design (uses: digital-illustrator)

Use the Digital Illustrator and Self-Publishing Guide skills to create a professional layout.

  • Input: revised-rulebook from Step 3 (text to lay out), finished-artwork from Step 4 (art to integrate), art-direction from Step 4 (visual identity to maintain)
  • Output: Complete InDesign or Affinity Publisher files, Screen-optimized PDF with bookmarks and hyperlinks, Print-ready PDF with bleeds and crop marks
  • Key focus: Choosing layout software: Affinity Publisher, Adobe InDesign, or Canva for

Step 6: Publish and Distribute (uses: self-publishing-guide)

Use the Self-Publishing Guide and Community Builder skills to get the game into players' hands.

  • Input: digital-pdf and print-pdf from Step 5 (products to sell), cover-art from Step 4 (marketing asset), starter-adventure from Step 2 (free sample content)
  • Output: Active listings on DriveThruRPG and itch.io, Free sample version for marketing, Discord, forum, or social media presence for the game
  • Key focus: Publishing on DriveThruRPG (the dominant TTRPG marketplace) with optimized
Show full SKILL.md (488 more words)Show less

Decision Points

  • After each step: Evaluate output quality before proceeding. If output is insufficient, iterate on the current step before moving forward.
  • Mid-workflow: If circumstances change significantly, re-evaluate earlier steps before continuing.

Failure Handling

  • Designing in a vacuum without playtesting: Theory is not practice. A mechanic that seems elegant on paper may be clunky at the table. Playtest early, playtest often.
  • Rules ambiguity: If two playtesters interpret a rule differently, the rule is unclear. Blind playtests reveal ambiguities you cannot see because you know what you meant.
  • Feature creep: Adding more subsystems does not make a better game. Discipline yourself to the design pillars and cut mechanics that do not serve them.
  • Neglecting the GM section: Players interact with the game through mechanics. GMs interact through tools and guidance. A weak GM section means poorly run games.
  • Skipping layout and design: A beautifully designed game with ugly layout will be judged by the layout. Professional presentation signals professional content.

Expected Outcome

When this workflow is complete, the user will have:

  1. A core mechanic delivers a distinctive play experience
  2. Playtesting has validated that the rules are clear, balanced, and fun
  3. The rulebook is written in clear, unambiguous prose with examples
  4. Professional art and layout make the book inviting to read
  5. The game is published on digital marketplaces and available for purchase
  6. A community exists for players and GMs to share experiences

Output Format

CREATE TABLETOP RPG TRACKER
===========================

[ ] Step 1: Design Your Core System
    Status: [pending/in-progress/complete]
[ ] Step 2: Build the World and Write the Rules
    Status: [pending/in-progress/complete]
[ ] Step 3: Playtest and Iterate
    Status: [pending/in-progress/complete]
[ ] Step 4: Commission or Create Art
    Status: [pending/in-progress/complete]
[ ] Step 5: Layout and Graphic Design
    Status: [pending/in-progress/complete]
[ ] Step 6: Publish and Distribute
    Status: [pending/in-progress/complete]

Timeline: ______ weeks
Overall Status: [IN PROGRESS / COMPLETE]

Adaptation notes:

  • Adjust timeline based on user's availability and prior experience
  • Steps may be reordered if dependencies allow parallel execution
  • Skip optional steps if time or budget is constrained

Edge Cases

  • Designing in a vacuum without playtesting: Theory is not practice. A mechanic that seems elegant on paper may be clunky at the table. Playtest early, playtest often.
  • Rules ambiguity: If two playtesters interpret a rule differently, the rule is unclear. Blind playtests reveal ambiguities you cannot see because you know what you meant.
  • Feature creep: Adding more subsystems does not make a better game. Discipline yourself to the design pillars and cut mechanics that do not serve them.
  • Neglecting the GM section: Players interact with the game through mechanics. GMs interact through tools and guidance. A weak GM section means poorly run games.

Example

Input: "I want to create tabletop rpg and need a structured plan to follow step by step."

Output:

Step 1 (tabletop-rpg-designer-dnd-master): Design Your Core System -- produces concrete deliverables for this phase.

Step 2 (worldbuilding-master-game-narrative-writer): Build the World and Write the Rules -- produces concrete deliverables for this phase.

Step 3 (tabletop-rpg-designer): Playtest and Iterate -- produces concrete deliverables for this phase.

Step 4 (digital-illustrator): Commission or Create Art -- produces concrete deliverables for this phase.

Step 5 (digital-illustrator-self-publishing-guide): Layout and Graphic Design -- produces concrete deliverables for this phase.

Step 6 (self-publishing-guide-community-builder): Publish and Distribute -- produces concrete deliverables for this phase.

Result: User has a complete create tabletop rpg plan with all deliverables produced, validated, and ready for implementation.

© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/process/resources/skills-library/bodies/workflows/create-tabletop-rpg of FerroxLabs/wayland.

Open the folder on GitHubat commit 4c030c7

Compare with similar skills

Create Tabletop Rpg next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Create Tabletop Rpg compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create Tabletop Rpg this skillFerroxLabs/wayland608—~2.6kAutomated safety check: PassApache-2.0
Design Systemaffaan-m/ECC274k—~698Automated safety check: PassMIT
Design Guidepaperclipai/paperclip98k1 repos~3.1kAutomated safety check: PassMIT
Design Audit Against Rams' Principlesthedotmack/claude-mem97k—~4.6kAutomated safety check: PassApache-2.0
Figma Design to Codewarpdotdev/warp65k4 repos~2.9kAutomated safety check: PassAGPL-3.0
Design Consultationgarrytan/gstack136k—~15kAutomated safety check: NotesMIT

Similar skills

  • Design System

    affaan-m/ECC

    Generate a design system from an existing codebase or audit one for visual consistency: extract tokens (colors, typography, spacing, shadows) into design-tokens.json and CSS custom properties with…

    274k GitHub stars~698 tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed
  • Design Guide

    paperclipai/paperclip

    Paperclip UI design system guide for building consistent, reusable frontend components.

    98k GitHub starsUsed in 1 repo~3.1k tokens
    Frontend & DesignAuto-check passed
  • Audits a design against Dieter Rams' ten principles of good design, scores each with evidence, and hands off a make-plan prompt for a new, refined or redesigned outcome.

    97k GitHub stars~4.6k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Figma Design to Code

    warpdotdev/warp

    Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.

    65k GitHub starsUsed in 4 repos~2.9k tokens
    Frontend & DesignAuto-check passed
  • Design Consultation

    garrytan/gstack

    Learns about your product, studies the landscape and writes a DESIGN.md with a full design system covering type, color, layout, spacing and motion.

    136k GitHub stars~15k tokensUpdated yesterday
    Frontend & DesignAuto-check: notes
  • Product Design Workflow Bundle

    XiaomiMiMo/MiMo-Code

    Entry point to a bundle of product design workflows covering context, research, audits, ideation, URL or image to code, design QA and sharing a prototype.

    14k GitHub stars~721 tokensUpdated 4 days ago
    Frontend & DesignAuto-check passed

More from FerroxLabs/wayland

All 1,194 skills in this repo
  • Star Office Helper

    FerroxLabs/wayland

    Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.

    608 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes
  • Openclaw Setup

    FerroxLabs/wayland

    OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.

    608 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Tvcontrol Setup

    FerroxLabs/wayland

    Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.

    608 GitHub stars~5.7k tokensUpdated yesterday
    Auto-check passed
  • Ab Testing Specialist

    FerroxLabs/wayland

    End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.

    608 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • Academic Writer

    FerroxLabs/wayland

    Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…

    608 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed
  • Accessibility Auditor

    FerroxLabs/wayland

    Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…

    608 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Questions about Create Tabletop Rpg

What does Create Tabletop Rpg do?

End-to-end workflow for designing, playtesting, illustrating, laying out, and publishing a tabletop role-playing game. Create Tabletop Rpg is an agent skill from FerroxLabs/wayland. End-to-end workflow for designing, playtesting, illustrating, laying out, and publishing a tabletop role-playing game.

When should I use Create Tabletop Rpg?

Create Tabletop Rpg fits situations like: the user wants to create tabletop rpg; needs a structured multi-step process for this goal; the request is a single-step task; requires professional advice beyond educational guidance.

How do I install Create Tabletop Rpg in Claude Code?

Run `npx skills add FerroxLabs/wayland --skill create-tabletop-rpg -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/workflows/create-tabletop-rpg in FerroxLabs/wayland) into .claude/skills/create-tabletop-rpg in your project. Claude Code loads it when a task matches its description.

How do I install Create Tabletop Rpg in Codex?

Run `npx skills add FerroxLabs/wayland --skill create-tabletop-rpg -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/workflows/create-tabletop-rpg in FerroxLabs/wayland) into .agents/skills/create-tabletop-rpg in your project. Codex loads it when a task matches its description.

Can I use Create Tabletop Rpg in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill create-tabletop-rpg -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-tabletop-rpg, .gemini/skills/create-tabletop-rpg, .github/skills/create-tabletop-rpg and .opencode/skills/create-tabletop-rpg in your project.

What does Create Tabletop Rpg need to run?

SKILL.md names no scripts, command-line tools or credentials: Create Tabletop Rpg is instructions for the agent only.

Does Create Tabletop Rpg access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Create Tabletop Rpg safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Create Tabletop Rpg use?

Create Tabletop Rpg is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Create Tabletop Rpg use?

About 2.6k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Create Tabletop Rpg?

Skills that share tags, products or a category with Create Tabletop Rpg: Design System (affaan-m/ECC, 274k stars), Design Guide (paperclipai/paperclip, 98k stars), Design Audit Against Rams' Principles (thedotmack/claude-mem, 97k stars) and Figma Design to Code (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Tabletop Rpg?

FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.

Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.