Tutorials / Advanced

Build a PATH project with an AI agent

Available now

Install PATH Project Builder in a coding-agent project and generate a Player JSON from your own public Mux IDs.

On this page

Install the complete skill

Download PATH Project Builder (ZIP) and extract its entire path-project-builder/ folder, including references/path-format.md. To inspect it first, read SKILL.md. The single Markdown file is not a complete installation.

  • In a repository using Codex, place the folder at .agents/skills/path-project-builder/, then start your coding agent/CLI in that repository and invoke $path-project-builder.
  • In a Claude Code project, place it at .claude/skills/path-project-builder/, then invoke /path-project-builder.

This skill runs through your coding agent/CLI, not inside the PATH website. It interviews you and writes a path-story Player .json in your workspace. Supply your own public Mux playback IDs and confirmed source timings; never supply Mux API secrets or ask PATH to upload footage. An optional editable .pathproj requires the separately configured local PATH Studio MCP; an MCP .pathproj alone is not a Player manifest.

Give the agent a concrete request

$path-project-builder — Create route.path.json for a short branching project titled “Two routes.” My opening footage has the public Mux playback ID [my real public playback ID] and is confirmed to last at least 8 seconds. Use seconds 0–8 for the opening, then ask “Which route?” with “High” and “Ordinary” choices. Start score at 0; High adds 2. Reconnect both choices to an automatic Router: score at least 2 goes to the High ending, otherwise take the Ordinary ending as fallback. Enable Paths with adjacent reveal. Validate the manifest and tell me what I must check in the Player. Do not invent footage or ask for credentials.

Here is the intended Player manifest JSON shape, with a syntactically valid placeholder playback ID. Replace REPLACE_WITH_YOUR_PUBLIC_MUX_PLAYBACK_ID with your own actual public Mux playback ID, and confirm that your clip is at least 8 seconds long before loading it. This example is not playable as supplied and does not imply any example footage exists:

{
  "format": "path-story",
  "version": "1.2.0",
  "id": "twoRoutes",
  "title": "Two routes",
  "entry": "start",
  "navigation": { "map": "enabled", "reveal": "adjacent" },
  "media": { "clip": { "playbackId": "REPLACE_WITH_YOUR_PUBLIC_MUX_PLAYBACK_ID" } },
  "variables": { "score": { "type": "number", "initial": 0 } },
  "nodes": {
    "start": { "type": "start", "to": "opening" },
    "opening": { "type": "video", "title": "Opening", "media": "clip", "in": 0, "out": 8, "next": "choice" },
    "choice": { "type": "decision", "prompt": "Which route?", "options": [
      { "id": "high", "label": "High", "to": "gate", "effects": [{ "add": { "variable": "score", "value": 2 } }] },
      { "id": "ordinary", "label": "Ordinary", "to": "gate" }
    ] },
    "gate": { "type": "router", "rules": [
      { "id": "atLeastTwo", "when": { "compare": { "variable": "score", "op": "gte", "value": 2 } }, "to": "highEnd" }
    ], "fallback": "ordinaryEnd" },
    "highEnd": { "type": "ending", "title": "High" },
    "ordinaryEnd": { "type": "ending", "title": "Ordinary" }
  }
}

The shape follows the v1.2 schema: declared numeric variable, add on a choice, compare on an ordered rule, required fallback, one Start, terminating paths and no graph cycle. The agent should validate against the installed PATH validator when available; a text example alone does not establish media availability, measured duration, licensing or browser playback. If validation is unavailable, treat the output as unverified.

Play the output

Open PATH Player and choose Open Player manifest (.json) for the agent’s completed file. Correct any validation errors and test each route with your own public footage. Keep a separate .pathproj backup only if you made one with Studio or Studio MCP; renaming .json to .pathproj does not convert formats. Learn about local MCP file exchange · Format reference.

Back to all tutorials