quests

Create and validate structured quest definitions for the Voyage narrative engine.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Quest designers often struggle to create consistent, valid quest definitions that the engine can execute. This skill provides a clear schema and rules to standardize the data model for quests.

Core Features & Use Cases

  • Enforces required fields such as name, questSource, questStatement, mainObjective, completionCondition, and detailType to ensure consistent quest definitions.
  • Supports both basic quests (AI-generated locations) and detailed quests (predefined locations) with conditional fields like spatialRelationship or questLocation.
  • Provides references to runtime schemas and design guidance to speed up quest creation and validation for Voyage engine content.

Quick Start

Create a new quest entry in tabs/quests.json that adheres to the defined schema and validate against the reference.

Frequently Asked Questions about quests

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

FAQPage Schema
How do I validate quest definitions for a narrative engine?

Quest definitions require specific fields depending on the detailType. Basic quests use AI-generated locations with a spatialRelationship, while detailed quests require a predefined questLocation to specify exact placement.

What's the best way to structure game-design quests across NPCs and items?

Quest creation requires a detailType declaration to determine the location format. Basic quests rely on AI-generated locations with a spatialRelationship, whereas detailed quests need a predefined questLocation.

Does quest validation work with both procedural and hand-crafted narratives?

Required fields for a valid quest definition include name, questSource, questStatement, mainObjective, completionCondition, and detailType. Depending on the detailType, you must also provide either a spatialRelationship or a questLocation.

Can I use AI-generated locations for quest definitions without predefined coordinates?

For basic quest definitions, the schema requires a spatialRelationship field to define AI-generated locations. For detailed quests, you must supply a predefined questLocation instead.

Why does my quest definition fail schema validation?

Validation also fails if the conditional location field is mismatched with the detailType. Basic quests must include a spatialRelationship, while detailed quests must define a questLocation.