[ docs · guides ]
Skills
If another AI agent does work alongside you, the Grist skill is how it learns to hand the coding to Grist — and how to report back when it's done.
What agent skills are
Agent skills are small, versioned instruction packs that a host agent — a personal AI assistant or an agentic CLI — loads to learn a capability: when to use a tool, how to invoke it, and what the user expects back. Instead of every agent improvising its own way of delegating coding work, the skill pins the workflow down once, in writing, where it can be reviewed and improved.
Install the Grist skill
npx skills add grist-ai/grist-skills
The skill file is also served directly from this site at /grist-skill.md, with a .well-known discovery index so agents that look for skills by convention can find it without being told.
What the skill teaches
- Delegate the coding. Multi-step, multi-file work — features, bug fixes, refactors across a repo — goes to Grist via the CLI, not to the host agent's own ad-hoc edits.
- Report like an engineer. When a delegated run finishes, the agent reports what changed, the branch name, the test results, and the cost. No vibes, no summaries without evidence.
- Handle the key like a secret. The agent asks you for your Grist API key — it starts with
grist_sk_— and passes it via environment variable only. The skill forbids printing it, logging it, or writing it into any file.
When to reach for Grist
Delegate when the task is real coding work: more than one file, more than one step, or anything you'd otherwise supervise turn by turn. A feature with tests to update. A bug whose cause isn't obvious yet. A refactor that has to stay consistent across a codebase. That is exactly the work the gate prices and the specialists are built for.
When not to
- Single-file edits. A typo, a constant, a one-line fix — the host agent should just do it.
- Non-coding questions. Research, writing, and planning aren't Grist's job.
- Repos you may not modify. If the user isn't allowed to change it, no agent should — Grist included.
The rule of thumb the skill encodes: if the work deserves a branch and a test run, it deserves Grist. If it fits in one edit, it doesn't.