Kiro CLI - Check Docs

Check supports Kiro CLI through installable skills plus an example custom agent. Skills are invoked on demand — there are no background hooks, matching how Check integrates with Droid and Copilot CLI.

Setup

Kiro is auto-detected. If ~/.kiro exists (or kiro-cli is on your PATH) when you run the installer, the Kiro skills install automatically — the same convention used for Codex and Gemini. No extra flags or steps. Auto-detection works on every platform; use the installer for your OS:

macOS / Linux / WSL:

curl -fsSL https://check.pleaseai.dev/install.sh | bash

Windows PowerShell:

irm https://check.pleaseai.dev/install.ps1 | iex

Windows CMD:

curl -fsSL https://check.pleaseai.dev/install.cmd -o install.cmd && install.cmd && del install.cmd

This installs the Kiro skills to ~/.kiro/skills and the Check agent to ~/.kiro/agents/check.json. If you install Kiro after Check, just re-run the installer. See Use the Check agent below.

Installed Kiro skills

Kiro-specific skills (run with CHECK_ORIGIN=kiro-cli):

check-review
check-annotate

Shared extra skills (installed from Check’s canonical integrations/skills/extra/ set, not duplicated):

check-setup-goal
check-visual-explainer

The shared skills show the default agent badge rather than “Kiro CLI” — origin is cosmetic for Kiro and has no functional effect.

Use the Check agent

The installer writes the agent to ~/.kiro/agents/check.json. It wires every Check skill through the resources field (skill:// URIs), grants the shell tool scoped to check commands, and its prompt spells out which skill to use for which task:

Skill	Use it to
`check-review`	Review the current code changes or a pull request
`check-annotate`	Annotate a markdown/HTML file, folder, or URL
`check-setup-goal`	Turn an idea into a structured goal package
`check-visual-explainer`	Generate a polished visual HTML explainer

Launch it:

kiro-cli chat --agent check

Prefer your own agent? Add the same skill://~/.kiro/skills/check-*/SKILL.md resources to any custom agent’s resources list.

Assumptions

The custom-agent JSON is intentionally conservative because Kiro’s schema can evolve. If your Kiro version expects different field names for resources or tool permissions, edit ~/.kiro/agents/check.json for your runtime.