mcpbeat

Cali

callstackincubator/cali

Use when working in the Cali repository or when you need to run, extend, or debug the Cali CLI for mobile React Native and Expo workflows. Covers Cali commands (`qa`, `review`, `perf-review`, `dev`), the shared `cali-context.json` contract, local mode selection, required local CLIs, provider setup, and CI integration patterns.

2k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
0
copies elsewhere
how many repositories repackaged it
988
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/callstackincubator/cali --skill cali

What comes with it

5 318 bytes besides the instruction
agents/openai.yaml
references/extending-cali.md
references/running-cali.md

The instruction itself

7 sections, as written by 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 qa as the stable command. Treat review, perf-review, and dev as experimental unless the task explicitly expands them.
  • Prefer the shared cali-context.json contract 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
  • cali review
  • experimental findings-first repository review
  • cali perf-review
  • experimental runtime performance review with agent-device and agent-react-devtools
  • 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|eas override

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

How to use it

Copy the folder

Take callstackincubator/cali from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.