Automated summary
Provides a complete dialogue and quest system for games, supporting branching conversations, quest stages, objectives, and rewards.
Strengths
- Structured data management using ScriptableObjects
- Supports branching dialogues with multiple choices
- Includes quest states and objective types (Kill, Collect, Interact, etc.)
- Event-driven progression for responsive gameplay
Limitations
- Tied to Unity engine and ScriptableObject pattern
- Requires additional integration for save/load
- May be overkill for simple narrative systems
Use when building a quest-driven RPG or narrative game that needs complex NPC interactions and branching quests.
For linear stories, non-game applications, or when a simpler dialogue tree would suffice.
Security analysis
CautionThe skill declares run_command, a powerful tool, but only uses it for legitimate development tasks (building, running scripts) within the context of implementing a quest system. No destructive or exfiltrating instructions are present.
No concerns found
How this analysis is madeExamples
Quest to kill 10 wolves.NPC offers two quest paths.name: dialogue-quest-system description: "Complete dialogue and quest system with branching conversations, quest stages, and event triggers." version: 1.0.0 tags: ["gameplay", "dialogue", "quests", "NPCs", "narrative"] argument-hint: "action='create_quest' name='Kill10Rats' stages='Accept,InProgress,Complete'" disable-model-invocation: false user-invocable: true allowed-tools:
- run_command
- list_dir
- write_to_file
Dialogue Quest System
Overview
Complete dialogue and quest system with branching conversations, multiple quest stages, objectives, rewards, and event-driven progression.
When to Use
- Use when implementing NPC conversations
- Use when creating branching dialogue
- Use when tracking quest progress
- Use when implementing objectives (kill X, collect Y)
- Use when rewarding quest completion
Architecture
┌─────────────────────────────────────────────────────────────┐
│ DialogueSO │
├─────────────────────────────────────────────────────────────┤
│ DialogueNode[] (Speaker, Text, Choices) │
│ Conditions (RequiredQuest, MinLevel) │
└─────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────┐
│ QuestSO │
├─────────────────────────────────────────────────────────────┤
│ Stages: NotStarted → InProgress → Completed │
│ Objectives: [{Type, Target, Count}] │
│ Rewards: [Item, XP, Gold] │
└─────────────────────────────────────────────────────────────┘
Quest States
- NotStarted: Quest available but not accepted
- InProgress: Quest active, tracking objectives
- Completed: All objectives done, rewards pending
- TurnedIn: Rewards collected, quest finished
- Failed: Quest failed (optional)
Objective Types
- Kill: Kill X enemies of type Y
- Collect: Obtain X items
- Interact: Talk to NPC, use object
- Reach: Arrive at location
- Escort: Keep NPC alive to destination
Best Practices
- ✅ Use ScriptableObjects for dialogue/quest data
- ✅ Implement ISaveable for quest progress
- ✅ Use events for objective updates
- ✅ Support quest prerequisites
- ❌ NEVER hardcode dialogue text
- ❌ NEVER forget to save quest state
Few-Shot Examples
Example 1: Kill Quest
User: "Quest to kill 10 wolves."
Agent:
// QuestSO asset with objective:
// Type: Kill, TargetId: "wolf", RequiredCount: 10
// Reward: 100 gold, 50 XP
Example 2: Dialogue Choice
User: "NPC offers two quest paths."
Agent:
DialogueNode choice = new()
{
Speaker = "Elder",
Text = "Which path will you take?",
Choices = new[]
{
{ Text = "The Mountains", NextNode = mountainQuestNode },
{ Text = "The Forest", NextNode = forestQuestNode }
}
};
Related Skills
@save-load-serialization- Persist quest progress@inventory-crafting-logic- Quest rewards@scriptableobject-architecture- Data patterns
Template Files
Available in templates/ folder.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/dialogue-and-quest-system-mm8o51ro/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/dialogue-and-quest-system-mm8o51ro' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/dialogue-and-quest-system-mm8o51ro/download' --output '.skill-downloads/dialogue-and-quest-system-mm8o51ro/SKILL.md.part' && mv '.skill-downloads/dialogue-and-quest-system-mm8o51ro/SKILL.md.part' '.skill-downloads/dialogue-and-quest-system-mm8o51ro/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/dialogue-and-quest-system-mm8o51ro/SKILL.md' && test -s '.skill-downloads/dialogue-and-quest-system-mm8o51ro/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/dialogue-quest-system' && cp -R '.skill-downloads/dialogue-and-quest-system-mm8o51ro' '.claude/skills/dialogue-quest-system'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/dialogue-and-quest-system-mm8o51ro'openskills read 'dialogue-and-quest-system-mm8o51ro'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/dialogue-and-quest-system-mm8o51ro/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.