Skip to main content
Knowledge and Skills are two complementary systems that give the agent context during test runs. They serve different purposes and are not interchangeable.

Knowledge

Long-form game context that tells the agent what the game is.
  • Scope: Project-wide — applies across all scenarios in a project
  • Format: Single markdown document (one per project)
  • Versioned: Each knowledge item has numbered versions, so you can track how game documentation evolves over time
  • Tied to builds: Knowledge versions can be linked to specific builds. When you select a build for a run, the matching knowledge version is auto-selected
  • Always on: Knowledge is always given to the agent — no per-run opt-in needed
  • Examples: Game mechanics guide, UI layout descriptions, expected behaviors, in-game economy rules, explanation about different quests/features

Skills

Short behavioral instructions that tell the agent how to act.
  • Scope: Scenario-specific or project-wide defaults
  • Format: Short text blocks (a name + description + body for each)
  • Not versioned: Edited in place
  • Mix and match: Pick which skills to include each run
  • Origin: A collection of the “instructions” field from several checkpoints, written together for better readability and reusability across scenarios
  • Selection: Can be set as project defaults or selected ad-hoc per scenario
  • Examples: “How to use the Cheat Menu”, “Video Ad Handling”, “Bridge building instructions”, “Item building on the Island Screen instructions”

How They Work Together

At run time, both are injected into the agent’s system prompt:
  1. Knowledge appears first — provides the world context (“here’s how this game works”)
  2. Skills appear after — provide behavioral rules (“here’s how you should play”)
Think of it like onboarding a new QA tester: you first hand them the game design doc (knowledge), then give them testing instructions (skills).

Quick Comparison

KnowledgeSkills
Answers”What is this game?""How should I behave?”
PurposeDescribe the game world — mechanics, UI, expected behaviors, loreInstruct agent behavior — tap patterns, navigation strategies, error handling
ScopeProject-scoped (applies to all scenarios)Scenario-scoped or project-default
FormatLong-form markdown (can be multi-page)Short text block (name + description + body)
VersioningExplicit version numbers, coupled to buildsNo versioning (edit in place)
Prompt locationSystem prompt, before skills (# Game Knowledge section)System prompt, # Game Skills section
AnalogyGame design documentQA playbook rules