multica-working-on-issues skill

by multica-ai·multica-ai/multica·56k stars

Superseded by the multica-platform skill — load that instead. This file only records where the Multica issue contracts moved to.

A100/100content scan

Is the multica-working-on-issues skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-10-25.

No findings.

Install the multica-working-on-issues skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.

git clone --depth 1 https://github.com/multica-ai/multica.git /tmp/multica
mkdir -p ~/.claude/skills
cp -r /tmp/multica/server/internal/service/builtin_skills_legacy/multica-working-on-issues ~/.claude/skills/multica-working-on-issues

available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Moved into multica-platform

Multica's platform contracts are now one skill. Everything this skill used to carry — PR linking vs close intent, reading a linked PR's real state, custom properties, status side effects, sub-issues and stages, and finding who else is running — lives in:

multica-platform  →  references/issues.md

Load the multica-platform skill and open that file. Its routing table also names the reference for every other platform domain: mentions, agents, squads, autopilots, projects, runtimes, and skill import.

The contracts were reorganized, not shortened — with one exception. The issue metadata guidance was retired (MUL-6966), so a brief that sends you here for it points at something that is no longer there. What replaces it: durable state a person should see and filter by goes on a custom property, the stage the issue is at goes in its status, and everything else — what you did this run, what you found — goes in the result comment.

You are seeing this redirect because the Multica app on this machine is older than the server it is talking to, so its task brief still refers to the previous skill name. Updating the app removes this extra hop.

More skills from multica-ai/multica

Aincident-responseHow this team handles a production incident issue — what to establish before proposing a fix, and what an agent may and may not do on its own.
Amultica-iconsUse when a Multica web/desktop UI change needs an icon that `@multica/ui/icons` does not export yet, or when redrawing or reviewing a Multica glyph. Covers the grid, corner and stroke construction, the body/detail markers, and the generate-and-preview loop. Never reach for an icon library, inline SVG, or emoji instead.
Amultica-onboardingUse when a product-authored kickoff starts or resumes Mika's interactive onboarding for a Multica workspace. The opening greeting has already been sent; carry the member from their first message to one real, confirmed, issue-based execution and a clear handoff.
Amultica-platformUse for Multica platform actions the runtime brief does not fully cover: issue and PR contracts, sub-issues, saved views, charts and files in comments, mentions, agents, squads, autopilots, projects, runtimes, local environments, skill import, themes. Not for the product code you are working on.
Aweb-design-guidelinesReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

All agent skills → · MCP servers