Context Optimization
guanyang/open-agent-hub
This skill should be used for improving context efficiency: context budgeting, observation masking, prefix or KV-cache strategy, partitioning, token-cost reduction, retrieval scoping, and extending…
Multi-agent board meeting protocol for strategic decisions. An agent skill from LeoYeAI/openclaw-master-skills.
Install Board Meeting
$ npx skills add LeoYeAI/openclaw-master-skills --skill board-meeting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills board-meeting --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/board-meeting .claude/skills/board-meeting && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "board-meeting" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/board-meeting into .claude/skills/board-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "board-meeting", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/board-meetingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LeoYeAI/openclaw-master-skills --skill board-meeting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills board-meeting --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/board-meeting .agents/skills/board-meeting && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "board-meeting" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/board-meeting into .agents/skills/board-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "board-meeting", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill board-meeting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills board-meeting --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/board-meeting .cursor/skills/board-meeting && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "board-meeting" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/board-meeting into .cursor/skills/board-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "board-meeting", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LeoYeAI/openclaw-master-skills.git --path skills/board-meeting--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LeoYeAI/openclaw-master-skills --skill board-meeting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills board-meeting --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/board-meeting .gemini/skills/board-meeting && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "board-meeting" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/board-meeting into .gemini/skills/board-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "board-meeting", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LeoYeAI/openclaw-master-skills board-meetingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LeoYeAI/openclaw-master-skills --skill board-meeting -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/board-meeting .github/skills/board-meeting && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "board-meeting" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/board-meeting into .github/skills/board-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "board-meeting", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill board-meeting -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills board-meeting --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/board-meeting .opencode/skills/board-meeting && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "board-meeting" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/board-meeting into .opencode/skills/board-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "board-meeting", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
board-meeting- GitHub stars
- 2.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 482 words
- Files
- 5 (incl. references)
- Skills in repo
- 1,235
- Repo updated
- First seen
- Licence
- MIT
At a glance
Multi-agent board meeting protocol for strategic decisions. An agent skill from LeoYeAI/openclaw-master-skills.
- Works in 6 steps: Context Gathering → Independent Contributions (ISOLATED) → Critic Analysis → …
- The user invokes /cs:board
- SKILL.md covers Keywords, Invoke, The 6-Phase Protocol and Memory Structure, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Board Meeting is an agent skill from LeoYeAI/openclaw-master-skills. Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes /cs:board, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `_meta.json`, `references/meeting-facilitation.md` and `templates/meeting-agenda.md`).
It sits in Agent Workflows, covering Context engineering. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
When your agent uses it
- The user invokes /cs:board
- Calls a board meeting
- Wants structured multi-perspective executive deliberation on a strategic question
Example prompts
- “/board-meeting”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Board Meeting loads about 1.3k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 103 tokens; SKILL.md has 482 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 482 words, ~1,325 tokens.
Download SKILL.mdSave it as
.claude/skills/board-meeting/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- board-meeting
- description
- Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes /cs:board, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.
- license
- MIT
- metadata.version
- 1.0.0
- metadata.author
- Alireza Rezvani
- metadata.category
- c-level
- metadata.domain
- board-protocol
- metadata.updated
- 2026-03-05
- metadata.frameworks
- 6-phase-board, two-layer-memory, independent-contributions
Board Meeting Protocol
Structured multi-agent deliberation that prevents groupthink, captures minority views, and produces clean, actionable decisions.
Keywords
board meeting, executive deliberation, strategic decision, C-suite, multi-agent, /cs:board, founder review, decision extraction, independent perspectives
Invoke
/cs:board [topic] — e.g. /cs:board Should we expand to Spain in Q3?
The 6-Phase Protocol
PHASE 1: Context Gathering
- Load
memory/company-context.md - Load
memory/board-meetings/decisions.md(Layer 2 ONLY — never raw transcripts) - Reset session state — no bleed from previous conversations
- Present agenda + activated roles → wait for founder confirmation
Chief of Staff selects relevant roles based on topic (not all 9 every time):
| Topic | Activate |
|---|---|
| Market expansion | CEO, CMO, CFO, CRO, COO |
| Product direction | CEO, CPO, CTO, CMO |
| Hiring/org | CEO, CHRO, CFO, COO |
| Pricing | CMO, CFO, CRO, CPO |
| Technology | CTO, CPO, CFO, CISO |
PHASE 2: Independent Contributions (ISOLATED)
No cross-pollination. Each agent runs before seeing others' outputs.
Order: Research (if needed) → CMO → CFO → CEO → CTO → COO → CHRO → CRO → CISO → CPO
Reasoning techniques: CEO: Tree of Thought (3 futures) | CFO: Chain of Thought (show the math) | CMO: Recursion of Thought (draft→critique→refine) | CPO: First Principles | CRO: Chain of Thought (pipeline math) | COO: Step by Step (process map) | CTO: ReAct (research→analyze→act) | CISO: Risk-Based (P×I) | CHRO: Empathy + Data
Contribution format (max 5 key points, self-verified):
## [ROLE] — [DATE]
Key points (max 5):
• [Finding] — [VERIFIED/ASSUMED] — 🟢/🟡/🔴
• [Finding] — [VERIFIED/ASSUMED] — 🟢/🟡/🔴
Recommendation: [clear position]
Confidence: High / Medium / Low
Source: [where the data came from]
What would change my mind: [specific condition]Each agent self-verifies before contributing: source attribution, assumption audit, confidence scoring. No untagged claims.
PHASE 3: Critic Analysis
Executive Mentor receives ALL Phase 2 outputs simultaneously. Role: adversarial reviewer, not synthesizer.
Checklist:
- Where did agents agree too easily? (suspicious consensus = red flag)
- What assumptions are shared but unvalidated?
- Who is missing from the room? (customer voice? front-line ops?)
- What risk has nobody mentioned?
- Which agent operated outside their domain?
Show full SKILL.md (209 more words)Show less
PHASE 4: Synthesis
Chief of Staff delivers using the Board Meeting Output format (defined in agent-protocol/SKILL.md):
- Decision Required (one sentence)
- Perspectives (one line per contributing role)
- Where They Agree / Where They Disagree
- Critic's View (the uncomfortable truth)
- Recommended Decision + Action Items (owners, deadlines)
- Your Call (options if founder disagrees)
PHASE 5: Human in the Loop ⏸️
Full stop. Wait for the founder.
⏸️ FOUNDER REVIEW — [Paste synthesis]
Options: ✅ Approve | ✏️ Modify | ❌ Reject | ❓ Ask follow-upRules:
- User corrections OVERRIDE agent proposals. No pushback. No "but the CFO said..."
- 30-min inactivity → auto-close as "pending review"
- Reopen any time with
/cs:board resume
PHASE 6: Decision Extraction
After founder approval:
- Layer 1: Write full transcript →
memory/board-meetings/YYYY-MM-DD-raw.md - Layer 2: Append approved decisions →
memory/board-meetings/decisions.md - Mark rejected proposals
[DO_NOT_RESURFACE] - Confirm to founder with count of decisions logged, actions tracked, flags added
Memory Structure
memory/board-meetings/
├── decisions.md # Layer 2 — founder-approved only (Phase 1 loads this)
├── YYYY-MM-DD-raw.md # Layer 1 — full transcripts (never auto-loaded)
└── archive/YYYY/ # Raw transcripts after 90 daysFuture meetings load Layer 2 only. Never Layer 1. This prevents hallucinated consensus.
Failure Mode Quick Reference
| Failure | Fix |
|---|---|
| Groupthink (all agree) | Re-run Phase 2 isolated; force "strongest argument against" |
| Analysis paralysis | Cap at 5 points; force recommendation even with Low confidence |
| Bikeshedding | Log as async action item; return to main agenda |
| Role bleed (CFO making product calls) | Critic flags; exclude from synthesis |
| Layer contamination | Phase 1 loads decisions.md only — hard rule |
References
templates/meeting-agenda.md— agenda formattemplates/meeting-minutes.md— final output formatreferences/meeting-facilitation.md— conflict handling, timing, failure modes
© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in skills/board-meeting of LeoYeAI/openclaw-master-skills.
- SKILL.md
- _meta.json
- references/meeting-facilitation.md
- templates/meeting-agenda.md
- templates/meeting-minutes.md
Open the folder on GitHubat commit e5199b5
Compare with similar skills
Board Meeting next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Board Meeting this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Context Optimizationguanyang/open-agent-hub | 977 | 2 repos | ~4k | Automated safety check: Pass | MIT | |
| Board Meetingalirezarezvani/claude-skills | 28k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Context Mode Output Sandboxmksglu/context-mode | 26k | — | ~4.1k | Automated safety check: Pass | Custom licence | |
| Memori Long-Term MemoryMemoriLabs/Memori | 17k | — | ~2k | Automated safety check: Notes | Custom licence | |
| Picoclaw Skill Creatorsipeed/picoclaw | 30k | — | ~4.4k | Automated safety check: Pass | MIT |
Similar skills
Board Meeting
alirezarezvani/claude-skills
Multi-agent board meeting protocol for strategic decisions. An agent skill from alirezarezvani/claude-skills.
Context Mode Output Sandbox
mksglu/context-mode
Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.
Memori Long-Term Memory
MemoriLabs/Memori
Connects Claude Code to Memori Cloud for long-term memory, recalling stored context before substantive replies and saving new context afterward.
Picoclaw Skill Creator
sipeed/picoclaw
Guidance for creating, updating and reviewing Picoclaw skills, from the SKILL.md structure to organizing bundled scripts, references and assets.
Context Mode for Antigravity CLI
mksglu/context-mode
Routing rules for using context-mode MCP tools in Antigravity CLI: sandboxed code runs, file analysis, indexed search and web fetches that keep large output out of the conversation.
More from LeoYeAI/openclaw-master-skills
All 1,200 skills in this repoDevOps Pipeline Management
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
Feishu Document Collaboration
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
Files Memory System
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
GEO-Claw AI Visibility Agent
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
Google Workspace CLI
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
HealthFit Health Advisors
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Related
Categories
Questions about Board Meeting
What does Board Meeting do?
Multi-agent board meeting protocol for strategic decisions. An agent skill from LeoYeAI/openclaw-master-skills. Board Meeting is an agent skill from LeoYeAI/openclaw-master-skills. Multi-agent board meeting protocol for strategic decisions.
When should I use Board Meeting?
Board Meeting fits situations like: the user invokes /cs:board; calls a board meeting; wants structured multi-perspective executive deliberation on a strategic question.
How do I install Board Meeting in Claude Code?
Run `npx skills add LeoYeAI/openclaw-master-skills --skill board-meeting -a claude-code`. Or copy the skill folder (skills/board-meeting in LeoYeAI/openclaw-master-skills) into .claude/skills/board-meeting in your project. Claude Code loads it when a task matches its description.
How do I install Board Meeting in Codex?
Run `npx skills add LeoYeAI/openclaw-master-skills --skill board-meeting -a codex`. Or copy the skill folder (skills/board-meeting in LeoYeAI/openclaw-master-skills) into .agents/skills/board-meeting in your project. Codex loads it when a task matches its description.
Can I use Board Meeting in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill board-meeting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/board-meeting, .gemini/skills/board-meeting, .github/skills/board-meeting and .opencode/skills/board-meeting in your project.
What does Board Meeting need to run?
SKILL.md names no scripts, command-line tools or credentials: Board Meeting is instructions for the agent only.
Does Board Meeting access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Board Meeting safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Board Meeting use?
Board Meeting is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Board Meeting use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.1k tokens, read only when the agent opens those files.
What are the alternatives to Board Meeting?
Skills that share tags, products or a category with Board Meeting: Context Optimization (guanyang/open-agent-hub, 977 stars), Board Meeting (alirezarezvani/claude-skills, 28k stars), Context Mode Output Sandbox (mksglu/context-mode, 26k stars) and Memori Long-Term Memory (MemoriLabs/Memori, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Board Meeting?
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.