xy-toolchain
XY Toolchain
Authority. This skill is maintained only in ariestools/ariestools-skills. Copies under XYOracleNetwork/xyo-skills are redirect stubs — edit here, never there. If the repository also has xylabs-* skills, .claude/rules/xylabs-*.md, or .claude/commands/xy-*.md and xylabs-*.md, they are retired output of the removed xy claude command; this skill supersedes them. Since 10.1.2, xy skills lint reports them and --fix removes most of them (legacy agent files).
Toolchain versions. This skill is verified against @ariestools/toolchain 10.2.0; anything not marked "(since X)" exists from 9.0.0. Find the installed version with pnpm list @ariestools/toolchain --depth 0 (pnpm xy --version is reliable only from 10.0.6). A top-level command the installed version lacks prints Command not found. From 10.1.2 that exits 1; through 10.1.1, where newer commands are the ones missing, it exits 0, even under --strict. A missing subcommand may be silently ignored (for example, xy node <typo> prints only its banner and exits 0) or read as a package target, so check the output and the Version notes, not only the exit code. Version notes collects the gates.
Skill identity. When you present a plan, an acknowledgement, or a completion summary, state which skills informed it as xy-toolchain v<version>, and list each other active skill from this pack the same way. Read the version from this file's metadata.version, never from an example or from verified-toolchain.
Use the active @ariestools/toolchain packages. Do not install the retired @xylabs/* compatibility names in new work.
Channels. xy is semver-stable. xyex (since 9.2.0) is an experimental superset whose commands, flags, and config may change on a minor release. Prefer xy; run the commands that pnpm xy --stability marks experimental, such as work, dead, and plan, as pnpm xyex <cmd> (before 9.2.0, see channels).
Inspect the repository's package.json, lockfile, xy.config.ts, ESLint config, TypeScript configs, and test config before choosing commands. Prefer existing repository scripts; use the xy CLI directly when the repository exposes no narrower wrapper.
This skill builds on xy-development, which covers language and workflow principles. Load only the reference needed for the task: