contribution-protocol

Coordinate multi-agent contributions with JSON decision objects and conflict metadata.

160|20|Updated Dec 6, 2025
One-click install
npx skills add https://github.com/kryptobaseddev/cleo --skill contribution-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contribution-protocol
Source: https://github.com/kryptobaseddev/cleo/tree/main/skills/contribution-protocol
Command: npx skills add https://github.com/kryptobaseddev/cleo --skill contribution-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Contribution Protocol Skill provides a structured, machine-parseable workflow to coordinate multi-agent contributions, detect conflicts, and compute consensus using JSON-first formats.

Core Features & Use Cases

  • Structured decisions: JSON-formatted decision objects with evidence and rationale for auditability.
  • Conflict detection & resolution: Tools to identify, classify, and propose resolutions for divergent agent inputs.
  • Epics and contributions management: End-to-end tracking of epic tasks, contributions, and statuses.
  • Use Case: For a research team coordinating parallel experiments, the protocol ensures every decision is codified and traceable.

Quick Start

Initialize a contribution for epic T2204, then add a focus task and begin recording decisions.

Frequently Asked Questions about contribution-protocol

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

FAQPage Schema
How do I coordinate multi-agent contributions with structured JSON decisions?

Multi-agent contribution coordination uses JSON-formatted decision objects with evidence and rationale to ensure auditability. The protocol tracks epic tasks, manages statuses, and computes consensus for parallel agent inputs.

What is the best way to detect and resolve conflicts in parallel agent inputs?

Conflict detection for parallel agent inputs identifies, classifies, and proposes resolutions for divergent contributions. The protocol captures conflict metadata within JSON artifacts to maintain traceable consensus.

How does consensus building work for multi-agent epic-level coordination?

Consensus building for multi-agent coordination codifies every decision into machine-parseable JSON artifacts. It links evidence and rationale to epic tasks, ensuring all agent contributions are traceable and auditable.

Can I use JSON-based decision objects to manage epic task lifecycles?

JSON-based decision objects manage epic task lifecycles by tracking contributions and statuses end-to-end. The protocol initializes contributions for specific epics and records focus tasks with traceable evidence.

Does multi-agent contribution protocol require external dependencies for evidence linking?

Multi-agent contribution protocol requires no external dependencies for evidence linking. It operates standalone using JSON-first formats to structure decisions, classify conflicts, and compute consensus.

When should I avoid using structured protocols for multi-agent contribution tracking?

Avoid structured multi-agent contribution protocols for simple, single-agent workflows lacking parallel inputs. The protocol suits complex scenarios requiring conflict detection, consensus computation, and auditable evidence artifacts.