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 alirezarezvani/claude-skills.
Install Board Meeting
$ npx skills add alirezarezvani/claude-skills --skill board-meeting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alirezarezvani/claude-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/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/c-level-advisor/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/alirezarezvani/claude-skills/tree/main/c-level-advisor/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/alirezarezvani/claude-skills/tree/main/c-level-advisor/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 alirezarezvani/claude-skills --skill board-meeting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alirezarezvani/claude-skills board-meeting --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/c-level-advisor/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/alirezarezvani/claude-skills/tree/main/c-level-advisor/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 alirezarezvani/claude-skills --skill board-meeting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alirezarezvani/claude-skills board-meeting --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/c-level-advisor/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/alirezarezvani/claude-skills/tree/main/c-level-advisor/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/alirezarezvani/claude-skills.git --path c-level-advisor/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 alirezarezvani/claude-skills --skill board-meeting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alirezarezvani/claude-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/alirezarezvani/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/c-level-advisor/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/alirezarezvani/claude-skills/tree/main/c-level-advisor/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 alirezarezvani/claude-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 alirezarezvani/claude-skills --skill board-meeting -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/c-level-advisor/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/alirezarezvani/claude-skills/tree/main/c-level-advisor/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 alirezarezvani/claude-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 alirezarezvani/claude-skills board-meeting --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/c-level-advisor/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/alirezarezvani/claude-skills/tree/main/c-level-advisor/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
- 28k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 609 words
- Files
- 4 (incl. references)
- Skills in repo
- 342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Multi-agent board meeting protocol for strategic decisions. An agent skill from alirezarezvani/claude-skills.
- Works in 6 steps: Context Gathering → Independent Contributions (ISOLATED) → Critic Analysis → …
- The user invokes /cs:boardroom
- 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 alirezarezvani/claude-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:boardroom, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/meeting-facilitation.md`, `templates/meeting-agenda.md` and `templates/meeting-minutes.md`).
It sits in Agent Workflows, covering Context engineering. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.
When your agent uses it
- The user invokes /cs:boardroom
- 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 19392f7. 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.6k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 104 tokens; SKILL.md has 609 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 alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 609 words, ~1,616 tokens.
Download SKILL.mdSave it as
.claude/skills/board-meeting/SKILL.md (or your agent's skills folder). This skill also uses 3 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:boardroom, 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:boardroom, founder review, decision extraction, independent perspectives
Invoke
/cs:boardroom [topic] — e.g. /cs:boardroom Should we expand to Spain in Q3?
The 6-Phase Protocol
PHASE 1: Context Gathering
- Load
~/.claude/company-context.md - Load Layer 2 approved decisions from
~/.claude/decisions/approved/(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 14 every time):
| Topic | Activate |
|---|---|
| Market expansion | CEO, CMO, CFO, CRO, COO |
| Product direction | CEO, CPO, CTO, CMO |
| Hiring/org | CEO, CHRO, CFO, COO (+ VPE for eng hiring) |
| Pricing | CMO, CFO, CRO, CPO |
| Technology | CTO, CPO, CFO, CISO |
| Contracts / term sheets / legal exposure | GC, CEO, CFO |
| Data strategy / training-data rights | CDO, CAIO, GC, CISO |
| AI strategy / model selection / AI risk | CAIO, CTO, CDO, CFO |
| Retention / churn / customer success | CCO, CRO, CPO |
| Eng delivery / DORA / team structure | VPE, CTO, CHRO, CFO |
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 → GC → CDO → CAIO → CCO → VPE (activated roles only)
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 | GC: Risk-Based (clause exposure) | CDO: Decision-Driven (what decision does this data drive) | CAIO: Eval-Demanding (no eval, no ship) | CCO: Retention-Obsessed (GRR over NRR) | VPE: Throughput-First (cycle-time math)
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 (250 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:boardroom resume
PHASE 6: Decision Extraction
After founder approval:
- Layer 1: Write full transcript →
~/.claude/decisions/raw/YYYY-MM-DD-<slug>.md - Layer 2: Write approved decision record →
~/.claude/decisions/approved/YYYY-MM-DD-<slug>.mdand append to the index~/.claude/decisions/approved/decisions.md - Mark rejected proposals
[DO_NOT_RESURFACE] - Confirm to founder with count of decisions logged, actions tracked, flags added
Memory Structure
Uses the canonical two-layer decision memory (see ../agent-protocol/SKILL.md → "Decision Memory (Canonical Layout)"):
~/.claude/decisions/
├── raw/YYYY-MM-DD-<slug>.md # Layer 1 — full transcripts (never auto-loaded)
├── raw/archive/YYYY/ # Raw transcripts after 90 days
├── approved/YYYY-MM-DD-<slug>.md # Layer 2 — founder-approved records (Phase 1 loads these)
└── approved/decisions.md # Layer 2 index — append-onlyFuture meetings load Layer 2 only. Never Layer 1. This prevents hallucinated consensus.
Migration: a legacy memory/board-meetings/ folder may exist from earlier versions; read it for history but write new transcripts and decisions to ~/.claude/decisions/.
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 ~/.claude/decisions/approved/ only — hard rule |
References
templates/meeting-agenda.md— agenda formattemplates/meeting-minutes.md— final output formatreferences/meeting-facilitation.md— conflict handling, timing, failure modes
© alirezarezvani, 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 3 other files (references) in c-level-advisor/skills/board-meeting of alirezarezvani/claude-skills.
- SKILL.md
- references/meeting-facilitation.md
- templates/meeting-agenda.md
- templates/meeting-minutes.md
Open the folder on GitHubat commit 19392f7
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 skillalirezarezvani/claude-skills | 28k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Context Optimizationguanyang/open-agent-hub | 977 | 2 repos | ~4k | Automated safety check: Pass | MIT | |
| Board MeetingLeoYeAI/openclaw-master-skills | 2.2k | — | ~1.3k | 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
LeoYeAI/openclaw-master-skills
Multi-agent board meeting protocol for strategic decisions. An agent skill from LeoYeAI/openclaw-master-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 alirezarezvani/claude-skills
All 342 skills in this repoAgile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Product Strategist
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
App Store Optimization
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.
AWS Solution Architect
alirezarezvani/claude-skills
Design AWS architectures for startups using serverless patterns and IaC templates.
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
Code to PRD
alirezarezvani/claude-skills
Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.
Related
Categories
Questions about Board Meeting
What does Board Meeting do?
Multi-agent board meeting protocol for strategic decisions. An agent skill from alirezarezvani/claude-skills. Board Meeting is an agent skill from alirezarezvani/claude-skills. Multi-agent board meeting protocol for strategic decisions.
When should I use Board Meeting?
Board Meeting fits situations like: the user invokes /cs:boardroom; 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 alirezarezvani/claude-skills --skill board-meeting -a claude-code`. Or copy the skill folder (c-level-advisor/skills/board-meeting in alirezarezvani/claude-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 alirezarezvani/claude-skills --skill board-meeting -a codex`. Or copy the skill folder (c-level-advisor/skills/board-meeting in alirezarezvani/claude-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 alirezarezvani/claude-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.6k tokens (SKILL.md is roughly 6.5k 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 (LeoYeAI/openclaw-master-skills, 2.2k 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?
alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,938 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.
Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.