Multica Working On Issues logo

Multica Working On Issues

OrganizationPopular
multica-ai
multica-working-on-issues

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

Overview

Publishermultica-ai
Repositorymultica
Skill namemultica-working-on-issues
Stars
50.4K
Forks
6.5K
Bundled files
Instructions only
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by multica-ai on GitHub. Read the source before you install it.

Installation

Install the Multica Working On Issues AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
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
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Multica Working On Issues in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Multica Working On Issues on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Multica Working On Issues is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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:

text
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.

Frequently asked questions

What does the Multica Working On Issues AI skill do?

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

Why use Multica Working On Issues on TypingMind?

Because you install it once and use it with any model. Multica Working On Issues is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Multica Working On Issues in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/multica-ai/multica/tree/main/server/internal/service/builtin_skills_legacy/multica-working-on-issues. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Multica Working On Issues?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Multica Working On Issues?

As many as you like. As long as a model supports skills, you can use Multica Working On Issues with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Multica Working On Issues AI skill free?

It is published on GitHub by multica-ai. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
ruvnet logo

Cost Health

ruvnet
CommunityPopular

Composite CI gate — runs cost-budget-check + cost-burn + cost-anomaly + cost-projection in parallel and surfaces a single combined health status with max exit code. The operationally-useful entry…

8.6K
72.7K
Instructions
View
ruvnet logo

Cost Projection

ruvnet
CommunityPopular

Forward-looking spend extrapolation. Computes a USD-per-day rate from the recent measurement window, projects to 7d/30d/90d/365d horizons, and surfaces "days until budget exhausted" when a budget is…

8.6K
72.7K
Instructions
View
ruvnet logo

Cost Report

ruvnet
CommunityPopular

Generate a cost report showing token usage and USD costs by agent and model

8.6K
72.7K
Instructions
View
ruvnet logo

Cost Summary

ruvnet
CommunityPopular

Single-shot programmatic dump of all cost data — total spend, per-tier, top session, budget status, federation aggregate. JSON or markdown.

8.6K
72.7K
Instructions
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇