shared

Document cross-skill protocol references for distributed mode in the AgentOps ecosystem.

418|40|Updated Nov 5, 2025
One-click install
npx skills add https://github.com/boshu2/agentops --skill shared-boshu2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shared
Source: https://github.com/boshu2/agentops/tree/main/skills/shared
Command: npx skills add https://github.com/boshu2/agentops --skill shared-boshu2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill centralizes and documents cross-skill references used by distributed mode within the AgentOps ecosystem.

Core Features & Use Cases

  • Provides shared reference documents for multiple skills (crank, swarm, inbox, implement)
  • Exposes protocol references like agent-mail-protocol.md and validation-contract.md to ensure consistency
  • Acts as a non-invocable knowledge base loaded by other skills at runtime to guide coordination

Quick Start

Ask: "Show me the agent-mail-protocol and validation-contract references used by distributed mode."

Frequently Asked Questions about shared

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

FAQPage Schema
What shared protocols are required for distributed mode coordination in agentops?

Distributed mode in agentops requires shared protocols like agent-mail-protocol.md and validation-contract.md to coordinate crank, swarm, implement, and inbox skills at runtime.

How do I centralize cross-skill references for multiple distributed agents?

You centralize cross-skill references by loading a shared knowledge base that exposes protocol files and validation guidance, ensuring consistency across distributed mode skills during runtime coordination.

Can I use the crank and swarm skills without shared validation contracts?

Using crank and swarm without shared validation contracts risks breaking coordination. The shared references provide necessary protocol documentation to ensure these distributed mode skills interact consistently.

When do I need to load shared reference documents for distributed mode?

You need to load shared reference documents when distributed mode skills require coordination guidance. The shared skill acts as a non-invocable knowledge base loaded at runtime to provide protocol and validation consistency.

What is the best way to ensure protocol consistency across distributed agent skills?

The best way to ensure protocol consistency is referencing centralized documents like agent-mail-protocol.md and validation-contract.md, which standardize interactions between distributed mode components such as crank, swarm, implement, and inbox.