Imported from callstackincubator/cali (
skills/cali/SKILL.md). Install upstream withnpx skills add callstackincubator/cali --skill cali. Copyright stays with the author.
Cali
Use this skill as a router with mandatory defaults. Read this file first. For normal Cali tasks, always load references/running-cali.md before acting. If the task changes Cali itself, also load references/extending-cali.md.
Default operating rules
- Start with the shipped command surface and docs. Do not invent new Cali commands, envs, or config shapes.
- Treat
qaas the stable command. Treatreview,perf-review, anddevas experimental unless the task explicitly expands them. - Prefer the shared
cali-context.jsoncontract over workflow-specific runtime scraping. - Keep setup and CI instructions copy-pasteable when editing docs.
- If the task is about running Cali, verify the required local CLIs and model credentials before assuming the environment is ready.
- Required role skills are Cali-managed; local CLIs are not.
- If the task is about changing Cali, prefer small explicit runtime contracts over broad abstraction.
Default flow
- Load references/running-cali.md.
- If the task changes implementation or runtime behavior, then load references/extending-cali.md.
- Confirm which command is actually in scope before changing code or docs.
- Keep the task aligned to the current runtime model: command + local/CI mode + shared context + tool packs + publishers.
Command surface
cali qa- ship-ready mobile QA with
agent-device
- ship-ready mobile QA with
cali review- experimental findings-first repository review
cali perf-review- experimental runtime performance review with
agent-deviceandagent-react-devtools
- experimental runtime performance review with
cali dev- experimental repository-backed implementation flow
Runtime modes
- local mobile:
--local android|ios - CI: implicit provider detection in GitHub Actions and EAS, with optional
--ci github-actions|easoverride
Required references
- For every normal Cali task, after reading this file, load references/running-cali.md first.
- If the task changes code, runtime behavior, or extension points, also load references/extending-cali.md.
- Load additional repo files only after you identify the owning command, role, or runtime module.
Additional references
- Public CLI, provider setup, required CLIs, and copy-pasteable CI examples:
packages/cali/README.md - Repo implementation guidance and validation expectations:
AGENTS.md