npcs

Enforce a YAML-backed schema for NPC names, locations, attributes, and dialogue anchors.

14|7|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/nikolaj-lat/World-Puppeteer --skill npcs-nikolaj-lat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: npcs
Source: https://github.com/nikolaj-lat/World-Puppeteer/tree/main/.claude/skills/npcs
Command: npx skills add https://github.com/nikolaj-lat/World-Puppeteer --skill npcs-nikolaj-lat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a rigid, reusable framework for creating non-player characters by enforcing a complete, YAML-backed schema that ensures consistency across names, locations, attributes, and dialogue anchors.

Core Features & Use Cases

  • Standardized NPC definition: every NPC must declare required fields like name, location, gender, abilities, and lore-ready information.
  • Inheritance & extensibility: NPCs can inherit core traits from species templates and add unique abilities and backstory.
  • Validation-ready data: tight field rules simplify tooling, validation, and integration with game engines.

Quick Start

Create an NPC by editing tabs/npcs.json to add a new entry that conforms to the schema, ensuring all required fields are present.

Frequently Asked Questions about npcs

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

FAQPage Schema
How do I create consistent NPCs with a structured schema for RPG game design?

To create consistent NPCs for RPG game design, use a strict YAML-backed schema that enforces required fields like name, location, gender, abilities, and dialogue anchors. This structured data approach ensures NPCs have repeatable traits and clear integration with game worlds.

How does NPC trait inheritance work when defining species templates for worldbuilding?

NPC trait inheritance works by allowing characters to derive core attributes from predefined species templates. Creators can then extend these inherited traits by adding unique abilities and specific backstory lore to individual NPCs.

How do I validate required NPC fields to ensure balanced abilities and locations?

Validating required NPC fields involves enforcing tight schema rules for names, locations, and attributes. This validation-ready data simplifies tooling checks and ensures balanced abilities and proper faction integration before game engine export.

What's the best way to structure NPC dialogue anchors and lore for game engines?

The best way to structure NPC dialogue anchors and lore is through a rigid, YAML-backed schema. By declaring complete fields for lore-ready information and dialogue, you ensure validation-ready data that simplifies integration with game engines.

Can I use this NPC schema framework without predefined species traits?

You can use this NPC schema framework without predefined species traits, but you must manually declare all required fields. Inheriting from species templates is an extensible feature that simplifies generation, yet complete core data remains strictly enforced.