Verified:GitHub

inter-agent-communication

Route asynchronous messages between Toti and Mercury through GitLab Issues.

Updated Jul 7, 2026

Search Tags:#handoff #issues #asynchronous #gitlab #reviews #inter-agent

One-click install

npx skills add https://github.com/TitoPrausee/nexus-toti --skill inter-agent-communication-titoprausee

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: inter-agent-communication
Source: https://github.com/TitoPrausee/nexus-toti/tree/main/data/skills/autonomous-ai-agents/inter-agent-communication
Command: npx skills add https://github.com/TitoPrausee/nexus-toti --skill inter-agent-communication-titoprausee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of coordinating work between two AI agents without relying on fragile chat history, by using GitLab Issues as a persistent, asynchronous message queue.

Core Features & Use Cases

Agent-to-Agent Messaging: Send structured updates from Toti to Mercury and receive replies back through labeled GitLab issues.
Review and Handoff Workflow: Use it for skill reviews, feature-branch reviews, task handoffs, and status coordination when work spans sessions.
Operational Conventions: It defines issue labels, branch strategy, reply behavior, and closing rules so communication stays organized and traceable.
Use Case: If a task is unfinished at the end of a session, create a handoff issue so the other agent can pick it up, continue the work, and close the loop.

Quick Start

Use this skill to create a GitLab issue for the other agent with the correct direction label and a clear handoff message.

Frequently Asked Questions about inter-agent-communication

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

FAQPage Schema

How do I coordinate handoffs between AI agents without losing context?▼

You can coordinate agent handoffs by routing asynchronous messages through GitLab Issues, which acts as a persistent message queue. This approach maintains context without relying on fragile chat history across sessions.

How do I use GitLab issues for asynchronous communication between agents?▼

To use GitLab issues for asynchronous agent communication, create an issue with the correct direction label and a handoff message. The receiving agent then reads the issue, continues the work, and closes the loop.

What is the best way to handle task handoffs when work spans multiple sessions?▼

The best way to handle task handoffs across sessions is creating a GitLab handoff issue. This allows the next agent to pick up the unfinished task, continue the work, and close the issue for traceable collaboration.

Do I need GitLab API access to enable inter-agent communication?▼

Yes, you need GitLab API access to enable inter-agent communication. The skill requires API access for creating, reading, replying to, and closing issues to route asynchronous messages between agents.

What conventions are required for issue-based agent collaboration?▼

Issue-based agent collaboration requires defined conventions including issue labels, branch naming strategies, reply behavior, and closing rules. These operational standards ensure communication stays organized and traceable.