multica-mentioning

Name: multica-mentioning
Availability: InStock
Author: waltcow

Enforce mention link contracts for agent, squad, member, issue, and all in issue comments.

1|Updated May 24, 2026

Search Tags:#backend #delegation #agent #triggers #comment #mention #squad

Ready to run

npx skills add https://github.com/waltcow/multica --skill multica-mentioning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: multica-mentioning
Source: https://github.com/waltcow/multica/tree/main/server/internal/service/builtin_skills/multica-mentioning
Command: npx skills add https://github.com/waltcow/multica --skill multica-mentioning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This contract standardizes how mention links in issue comments map to real entities (agent, squad, member, issue, and all) and how they enqueue actions or render safe references, reducing ambiguity and misrouted work.

Core Features & Use Cases

Defines the four mention types and exactly what each enqueues: agent → a run for that agent, squad → a run for the squad leader, member and issue → a rendered link with no run.
Documents the @all broadcast behavior and how it suppresses the assignee's automatic trigger.
Explains runtime guardrails for archived or private agents/squads and for pending tasks.

Quick Start

Create a real mention link to trigger an agent.

Frequently Asked Questions about multica-mentioning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do mention links in issue comments trigger agent runs or delegate tasks?▼

Mention links in issue comments trigger specific actions based on type: agent mentions enqueue a run for that agent, squad mentions enqueue a run for the squad leader, while member and issue mentions render safe links without enqueuing any runs.

What happens when I use @all in a comment and does it suppress automatic triggers?▼

Using @all in a comment initiates a broadcast behavior that explicitly suppresses the assignee's automatic trigger, ensuring that the broadcast mention does not cause duplicate or unintended agent runs for the assigned entity.

How do I create a mention link that successfully triggers a backend agent delegation?▼

To trigger an agent delegation, create a real mention link to an agent within an issue comment. The parsing logic identifies this agent mention and enqueues a run specifically for that agent to execute the delegated task.

What are the guardrails for mentioning archived, private, or pending entities in comments?▼

Runtime guardrails prevent triggers for archived or private agents and squads, blocking unintended runs. The system also includes edge-case guards for pending tasks to ensure mentions do not enqueue actions on inactive or restricted entities.

Why does mentioning a squad member or an issue not trigger a backend agent run?▼

Mentioning a squad member or an issue renders a safe reference link without enqueuing a run because these mention types are designed for visibility and context rather than task delegation or triggering agent execution.

Does this mention rule contract work without external dependencies?▼

Yes, the mention rule contract operates with no external dependencies, relying solely on internal parsing patterns and enqueuing logic to map comment mentions to agent, squad, member, issue, and broadcast actions.