agent-protocol
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only skill defines a transparent protocol for C-suite-style agents to coordinate, with no code execution, credentials, installation steps, or persistence.
This skill appears safe to install as an instruction-only coordination protocol. Before using it with real executive, financial, customer, or HR information, make sure you are comfortable with that context being reused across the simulated C-suite roles in the conversation.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If used with real company data, information provided to one role may be included in questions, responses, or synthesized outputs involving other roles.
The skill explicitly enables inter-agent communication. This is the core purpose of the skill and is paired with loop-prevention and isolation rules, but users should recognize that business context may be shared across role agents during use.
Any agent can query another using: ``` [INVOKE:role|question] ```
Use this only in contexts where sharing the relevant business information across the selected agent roles is acceptable, and continue to review final outputs for sensitive details.
A poorly framed prompt could influence several role responses at once, producing a broader but still bounded synthesis error.
The skill supports multi-role broadcasts, which can propagate one prompt across several role outputs. The artifacts also include containment controls such as independent responses, depth limits, conflict surfacing, and loop prevention, so this remains purpose-aligned.
CEO can broadcast to all roles simultaneously: ``` [BROADCAST:all|What's the impact if we miss the fundraise?] ```
Use specific, scoped prompts for broadcasts and rely on the skill’s conflict and assumption markers to review uncertain or conflicting outputs.