pato

name	pato
description	Use the pato CLI to inspect, lint, format, parse, and explain gram files. Use when pato is already installed and on PATH, or when updating this local pato skill with `pato skill`.

pato

Use this skill when working with gram files through the pato CLI.

Prerequisites

• pato must already be installed and available on PATH
• If pato is missing, install it first:
  • cargo install relateby-pato
  • or download the pato GitHub Release asset from https://github.com/relateby/pattern-rs/releases/latest and put the binary on PATH

When to use

• You need to inspect, lint, format, parse, or explain gram files
• You need to install or update the local pato skill for a project or user
• You need the command output to stay machine-friendly and parseable

Core workflow

1. Prefer pato lint for validation and pato fmt for canonical formatting.
2. Use pato check when you want linting plus schema discovery in one pass.
3. Use pato rule <code> when you need an explanation for a P-code.
4. Re-run the same command after edits to confirm the result is stable.

Install or update the skill

1. Run pato skill.
2. Use --scope user for a user-level install.
3. Use --target cursor only for user-scope client-native installs.
4. After upgrading the pato binary, re-run pato skill --force to re-sync the installed skill tree with the embedded content.

Notes

• Project installs must stay discoverable by Vercel-compatible skills tooling.
• The canonical repository source for this skill is .agents/skills/pato/.
• Keep stdout for data and stderr for status or errors.

References

• See workflows for common pato usage patterns.
• See output-contracts for stream conventions.