mcpbeat Sign in

Cali Agent Skill

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

Other skills for the same job

different authors, same section of the catalogue
MCP Builder
by anthropics
vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

30k tokens scripts
Changelog Generator
by frostant
×9

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens
Finishing A Development Branch
by ZhanlinCui
×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

1k tokens
MCP Builder
by JayZeeDesign
×7

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

37k tokens scripts
Vercel React Native Skills
by vercel-labs
vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens
Vercel React Best Practices
by ratacat
×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

34k tokens
Next Best Practices
by vercel-labs
vendor ×4

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

20k tokens
Using Git Worktrees
by ZhanlinCui
×4

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

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.