kleene-analyze

Analyze Kleene scenarios for structure, paths, and grid coverage.

Updated Jan 11, 2026
One-click install
npx skills add https://github.com/kleene-games/kleene --skill kleene-analyze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kleene-analyze
Source: https://github.com/kleene-games/kleene/tree/main/skills/kleene-analyze
Command: npx skills add https://github.com/kleene-games/kleene --skill kleene-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps analyze Kleene scenarios to validate narrative structure, identify missing paths, ensure grid coverage, and detect potential dead ends and railroads.

Core Features & Use Cases

  • Graph & grid analysis: Evaluates scenario graphs, 3x3 grid coverage, and path diversity to ensure robust storytelling.
  • Endings & reachability: Enumerates endings and checks their reachability from the start.
  • Deep structural checks: Performs precondition, item/trait/flag dependencies, and relationship network validation using yq-enabled queries.
  • Use Case: You want to confirm that a scenario provides multiple endings and no dead ends before sharing it with players.

Quick Start

Start by running the analyze command on a loaded scenario to generate a full structural report.

Frequently Asked Questions about kleene-analyze

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

FAQPage Schema
How do I check my scenario graph for dead ends and missing paths?

Scenario graph analysis validates narrative structure by evaluating path diversity to detect railroads and dead ends. It enumerates paths and verifies reachability from the start node to ensure robust storytelling before sharing.

What is grid coverage analysis and when do I need it for scenario validation?

Grid coverage analysis evaluates a 3x3 grid to ensure path diversity across narrative branches. You need it during scenario validation to confirm structural completeness and identify missing paths before deployment.

How do I enumerate endings and verify their reachability in a YAML scenario?

To enumerate endings and verify reachability in a YAML scenario, run the analyze command to generate a structural report. This applies yq-enabled queries to extract graph data and validate paths from start to finish.

Does yq work for precondition validation and dependency tracking in scenarios?

Yes, yq works for precondition validation by enabling deep structural checks across items, traits, flags, and relationships. It extracts dependency networks and validates YAML-based graph structures.

What's the best way to validate item, trait, and flag dependencies in a narrative graph?

The best way to validate item, trait, and flag dependencies is performing deep structural checks using yq-enabled queries. This extracts relationship networks and validates preconditions to detect potential dead ends.