Generates valid XAIOP v0.6.0 cursor-construction wire streams that materialize JSON deterministically.
npx skills add https://github.com/AboutUip/XAIOP --skill xaiop-aboutuip
Please help me install this Agent Skill. Skill: xaiop Source: https://github.com/AboutUip/XAIOP/tree/main/skills/xaiop Command: npx skills add https://github.com/AboutUip/XAIOP --skill xaiop-aboutuip
= locate lines, and indentation habits from JSON or YAML all produce syntax errors or wrong trees. This Skill teaches the sealed XAIOP v0.6.0 wire grammar so an AI emits only valid, parseable cursor-construction streams. ## Core Features & Use Cases - Complete line grammar reference: Covers every Structure and Content line form (>, >name, >name-, -, <, <name, ., =, @, !, ?, &, #) with hard rules and forbidden forms. - Ambiguity and blacklist tables: Maps common wrong instincts (JSON braces, key=value, dotted paths, indent-as-structure) to the correct XAIOP equivalent. - Copy-ready playbooks: Provides patterns for multi-section objects, arrays of objects, deep chains, locate-and-append, deletes, and annotation lines. - Use Case: Ask the AI to convert a JSON configuration or a structured script breakdown into XAIOP, and it emits a pure wire stream starting with > that a conforming parser materializes into identical JSON. ## Quick Start Convert this JSON object into a valid XAIOP stream using the xaiop skill.High-intent search queries and answers about installing and using this skill.
Open with `>` for an object root or `-` for an array root, then emit one Label or Content line per node: `>name` enters objects, `>name-` opens arrays, `key:value` writes fields, and `<` or `.` leaves sections. The stream materializes into the equivalent JSON tree.
XAIOP is a streaming, line-oriented cursor-construction wire format where programs materialize JSON deterministically. A Cursor walks a tree as you emit enter, leave, locate, reset, and delete instructions, making it suitable for incremental structured output generation.
Open the array with `>name-` on one line, then for each object element emit `>`, the field lines, and `<`. After the final element, emit `.` before starting any new named section, since one `<` only returns to array level.
Common causes are bare labels without `>`, blank lines, indentation used as structure, `key=value` instead of `key:value`, or opening a new named section while still inside an array. Fields always use a colon, and `=` is locate-only, never assignment.
`=path` performs a fuzzy locate to the first matching existing node and never creates anything, while `@path` follows an exact path from Root and creates missing object segments. Both take segments joined by `>`, and neither assigns field values.
The Skill itself is deprecated as an official product and retained source-only; the documentation recommends preferring programmatic Generators such as the official SDK encode functions or skeleton WebSocket generators over Skill-driven emit for production use.
mymx2Diagnose Kotlin and Jackson JSON serialization issues in Spring applications.
kreuzberg-devMaps document consumers to the correct Xberg CLI format and content-format flags.
apakouAnalyze code changes for accessibility, data protection, and security violations.
speakeasy-apiBootstrap an SDK project from an OpenAPI specification with a workflow file.