c-suite-agent-protocolInter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-sui...
Install via ClawdBot CLI:
clawdbot install alirezarezvani/c-suite-agent-protocolGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Mar 21, 2026
The CEO needs to assess the financial impact of expanding the engineering team. They invoke the CFO for burn rate analysis and the CTO for capacity planning. The CFO provides runway projections while the CTO evaluates technical capacity, with both responses aggregated for a comprehensive recommendation.
During Phase 2 isolation, each C-suite agent independently analyzes quarterly performance without invoking others. The CFO examines financials, CRO reviews pipeline, and CTO assesses product milestones. All assumptions are explicitly documented before Phase 3 critique where the Executive Mentor references these outputs without new invocations.
The CEO broadcasts a critical question about missing fundraising targets to all roles simultaneously. Each agent independently assesses impact on their domain—CFO on cash flow, CRO on revenue projections, CHRO on hiring plans—with responses aggregated to form a unified crisis response strategy.
The CMO invokes the CTO for technical feasibility and the CPO for user experience insights when planning a major feature launch. The chain follows depth-2 rules (CMO→CTO→CPO) with no circular calls, ensuring coordinated go-to-market planning without loops.
When CFO and CRO provide conflicting runway projections, the protocol requires explicit conflict flagging. The CEO receives both responses with confidence scores, then applies probabilistic weighting or escalates for human decision, ensuring transparent resolution rather than silent data selection.
This protocol enables C-suite agents to coordinate cross-functional analysis for enterprise clients. The CFO analyzes subscription economics, CRO manages enterprise sales pipelines, and CTO oversees platform scalability—all communicating through structured invocations during quarterly business reviews.
Startups use this protocol for investor reporting and board meetings. Agents coordinate burn rate analysis (CFO), fundraising timelines (CRO), and product roadmap alignment (CTO) while maintaining isolation during critical decision phases to prevent groupthink in high-stakes environments.
Large corporations deploy C-suite agent teams to analyze new venture opportunities. The protocol ensures proper chain tracking and loop prevention as agents assess financial viability (CFO), market fit (CMO), and technical feasibility (CTO) for innovation portfolio management.
💬 Integration Tip
Implement chain tracking at the orchestration layer to enforce loop prevention rules, and use metadata tagging to identify board meeting phases for isolation rule enforcement.
Scored Apr 19, 2026
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.
A unified OpenClaw skill that merges self-improvement and proactivity: learn from corrections, maintain active state, recover context fast, and keep work mov...
Meta-skill for AI agent self-improvement. Analyzes runtime logs to detect error patterns, regressions, and inefficiencies, then generates structured improvem...
Automatically assess task complexity and adjust reasoning level. Triggers on every user message to evaluate whether extended thinking (reasoning mode) would improve response quality. Use this as a pre-processing step before answering complex questions.
Associative memory with spreading activation for persistent, intelligent recall. Use PROACTIVELY when: (1) You need to remember facts, decisions, errors, or...