Built for Multica — an open-source platform for running and managing coding agents with reusable skills.
A portable skill that teaches any local coding agent — Claude Code, Codex, Cursor,
and others — how to operate Multica
through the authenticated multica CLI: read and triage issues, reply to
comments safely, manage metadata, and handle mention/status side effects.
English | 简体中文
This repository does not grant Multica access by itself. Permissions come only from the user's local CLI login, selected profile, active workspace, and explicit approval for any commands the agent runs. The skill teaches how to drive Multica safely; it never bypasses workspace permissions or stores secrets.
- Checking CLI auth, profile, and workspace state (and how to log in)
- Reading issues, comments, metadata, labels, custom properties, subscribers, projects, agents, squads, runtimes, repos, skills, autopilots, and attachments
- Searching issues across titles, descriptions, and comment bodies
- Reading comment history cheaply — thread scans,
--compact, and resolved-thread folding - Writing safe issue comments with
--content-file, including the working-directory restriction on file arguments - Creating or updating issues and high-signal metadata
- Handling mention, status, assignment, rerun, and sub-issue side effects, and
suppressing unwanted agent runs with
--no-start - Inspecting run history and token usage; cancelling a run when asked
- Linking pull requests back to Multica issues
- Saying so plainly when the CLI cannot do something, instead of faking it
The skill lives at skills/multica-cli/. Pick the path for your tool.
/plugin marketplace add multica-ai/multica-cli
/plugin install multica-cli@multica-cli
install-skill-from-github.py --repo multica-ai/multica-cli --path skills/multica-cliRestart Codex after installing new skills.
Copy the skill into your personal Cursor skills directory:
mkdir -p ~/.cursor/skills/multica-cli
cp -R skills/multica-cli/* ~/.cursor/skills/multica-cli/Or drop the project rule .cursor/rules/multica-cli.mdc
into a project's .cursor/rules/ directory. See CURSOR.md for details.
Copy skills/multica-cli/SKILL.md into wherever
your tool loads skills or instructions from.
- The
multicaCLI is installed locally, at v0.4.26 or newer. Earlier versions lack commands the skill relies on (notably--no-start), and will reject them. Check withmultica version. - The user has run
multica login(ormultica setup) to authenticate. - The intended workspace/profile is selected, or passed explicitly with
--workspace-idand--profile.
Ask your agent to work with Multica once the skill is installed, for example:
Read MUL-123 with the multica CLI and draft a reply for me to review.
For write operations (comments, status changes, mentions, new issues), the agent should ask before making state changes unless you have already clearly authorized that exact action. See EXAMPLES.md for more.
This skill is only useful while it matches the CLI it describes, so the docs are
linted against a real multica binary:
scripts/lint-skill-commands.py # or --verbose to see every checkIt fails when a documented command or flag no longer exists, and when a CLI
command exists that SKILL.md never mentions. Deliberate omissions belong in
UNDOCUMENTED_OK in that script, with a reason. CI runs it on every push and
on a daily schedule, so drift surfaces as a failure rather than as a stale skill.