Kapso
Leeroo-AI/kapso
Optimize code using KAPSO (Knowledge-Grounded Optimization).
Multi-agent board meeting protocol running a structured 6-phase deliberation with isolated C-suite contributions to prevent groupthink.
$ npx skills add borghei/Claude-Skills --skill board-meeting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/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/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/c-level-advisor/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/borghei/Claude-Skills/tree/main/c-level-advisor/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/borghei/Claude-Skills/tree/main/c-level-advisor/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 borghei/Claude-Skills --skill board-meeting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/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/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/c-level-advisor/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/borghei/Claude-Skills/tree/main/c-level-advisor/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 borghei/Claude-Skills --skill board-meeting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/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/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/c-level-advisor/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/borghei/Claude-Skills/tree/main/c-level-advisor/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/borghei/Claude-Skills.git --path c-level-advisor/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 borghei/Claude-Skills --skill board-meeting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/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/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/c-level-advisor/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/borghei/Claude-Skills/tree/main/c-level-advisor/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 borghei/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 borghei/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/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/c-level-advisor/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/borghei/Claude-Skills/tree/main/c-level-advisor/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 borghei/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 borghei/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/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/c-level-advisor/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/borghei/Claude-Skills/tree/main/c-level-advisor/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.
board-meetingMulti-agent board meeting protocol running a structured 6-phase deliberation with isolated C-suite contributions to prevent groupthink.
Board Meeting is an agent skill from borghei/Claude-Skills. Multi-agent board meeting protocol running a structured 6-phase deliberation with isolated C-suite contributions to prevent groupthink. Use when making major strategic decisions or resolving cross-functional disagreements.
Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/complexity_scorer.py`, `scripts/decision_tracker.py` and `scripts/meeting_simulator.py`).
It sits in Agent Workflows. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
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.
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Board Meeting loads about 4.1k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 1,308 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.
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); the scripts in this folder are not scanned.
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 1,308 words, ~4,056 tokens.
.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.Structured multi-agent deliberation that prevents groupthink, captures minority views, and produces clean, actionable decisions. Every phase has a purpose, a format, and rules that cannot be skipped.
board meeting, executive deliberation, strategic decision, C-suite, multi-agent, founder review, decision extraction, independent perspectives, groupthink prevention, synthesis, critic analysis, structured deliberation
Before generating, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
PHASE 1: Context Gathering
|
PHASE 2: Independent Contributions (ISOLATED)
|
PHASE 3: Critic Analysis (Executive Mentor)
|
PHASE 4: Synthesis (Chief of Staff)
|
PHASE 5: Founder Review (FULL STOP -- human decides)
|
PHASE 6: Decision Extraction and LoggingPurpose: Load all relevant context before anyone contributes.
Step 1: Load company context (if exists)
Step 2: Load decision history (Layer 2 ONLY -- NEVER raw transcripts)
Step 3: Reset session state -- no bleed from previous conversations
Step 4: Present agenda and activated roles
Step 5: Wait for founder confirmation before proceedingNot all roles attend every meeting. Select based on topic:
| Topic Domain | Activate | Exclude |
|---|---|---|
| Market expansion | CEO, CMO, CFO, CRO, COO | CTO (unless tech expansion) |
| Product direction | CEO, CPO, CTO, CMO | CFO (unless budget question) |
| Hiring / org | CEO, CHRO, CFO, COO | CMO, CTO (unless their teams) |
| Pricing | CMO, CFO, CRO, CPO | CTO, CHRO |
| Technology | CTO, CPO, CFO, CISO | CMO, CRO |
| Fundraising | CEO, CFO, CRO | CISO, CHRO |
| Security incident | CEO, CTO, CISO, COO | CMO, CRO |
| M&A | CEO, CFO, CTO, CHRO, COO | -- (all relevant) |
Maximum attendees: 6 roles per meeting. More than 6 creates noise, not insight.
Critical Rule: No cross-pollination. Each advisor contributes without seeing others' outputs. This is the primary groupthink prevention mechanism.
1. Research/data gathering (if needed)
2. CMO -- market perspective
3. CFO -- financial perspective
4. CEO -- strategic perspective
5. CTO -- technical perspective
6. COO -- operational perspective
7. CHRO -- people perspective
8. CRO -- revenue perspective
9. CISO -- security/risk perspective
10. CPO -- product perspectiveEach advisor's contribution must follow this exact format:
## [ROLE] -- [DATE]
Key Points (maximum 5):
1. [Finding] -- Confidence: [High/Medium/Low] -- Source: [data source]
2. [Finding] -- Confidence: [High/Medium/Low] -- Source: [data source]
3. [Finding] -- Confidence: [High/Medium/Low] -- Source: [data source]
Recommendation: [Clear position statement]
Confidence: [High / Medium / Low]
Key Assumption: [The one assumption this recommendation depends on]
What Would Change My Mind: [Specific condition or data point]| Role | Technique | How It Works |
|---|---|---|
| CEO | Tree of Thought | Explore 3 possible futures, evaluate each |
| CFO | Chain of Thought | Show the math, step by step |
| CMO | Recursion of Thought | Draft -> self-critique -> refine |
| CPO | First Principles | Decompose to fundamental user needs |
| CRO | Chain of Thought | Pipeline math must be explicit |
| COO | Step by Step | Map the operational process |
| CTO | Analyze then Act | Research -> analyze -> recommend |
| CISO | Risk-Based | Probability x Impact for every option |
| CHRO | Empathy + Data | Human impact first, then validate with metrics |
Purpose: The Executive Mentor receives ALL Phase 2 outputs simultaneously and performs adversarial review.
| Check | Question |
|---|---|
| Suspicious consensus | Where did agents agree too easily? |
| Shared assumptions | What assumptions are shared but unvalidated? |
| Missing voice | Who is not in the room? (customer voice? front-line ops?) |
| Unmentioned risk | What risk has nobody mentioned? |
| Domain bleed | Did any agent operate outside their domain? |
| Data quality | Which claims are backed by data vs. assumption? |
| Reversibility | Has anyone assessed if this decision can be undone? |
## CRITIC ANALYSIS
Consensus Assessment:
[Genuine agreement / Suspicious alignment / Split decision]
Unvalidated Assumptions:
1. [Assumption shared by multiple advisors but not verified]
2. [Assumption]
Missing Perspectives:
- [Voice or data point not represented]
Unmentioned Risks:
- [Risk nobody raised]
Domain Violations:
- [If any agent operated outside their domain]
The Uncomfortable Truth:
[The one thing nobody wants to say but needs to be said]Purpose: Chief of Staff combines all inputs into a decision-ready format.
## BOARD MEETING SYNTHESIS
Topic: [topic]
Date: [date]
Attendees: [roles]
### Decision Required
[One sentence: what must be decided]
### Perspectives Summary
| Role | Position | Confidence | Key Concern |
|------|----------|-----------|-------------|
| [Role] | [1-line summary] | [H/M/L] | [Top concern] |
| [Role] | [1-line summary] | [H/M/L] | [Top concern] |
### Where They Agree
[2-3 consensus points]
### Where They Disagree
[Named conflicts with each side's reasoning]
[What the disagreement is really about]
### Critic's View
[The uncomfortable truth from Phase 3]
### Recommended Decision
[Clear recommendation with rationale]
### Action Items (if approved)
1. [Action] -- Owner: [role] -- Deadline: [date]
2. [Action] -- Owner: [role] -- Deadline: [date]
3. [Action] -- Owner: [role] -- Deadline: [date]
### Your Call
[If you disagree with the recommendation, here are alternatives:]
Option A: [description] -- Trade-off: [what you gain/lose]
Option B: [description] -- Trade-off: [what you gain/lose]FULL STOP. Wait for the founder. No agent acts beyond this point.
FOUNDER REVIEW
[Paste synthesis above]
Options:
[A] Approve as recommended
[M] Modify (specify changes)
[R] Reject (specify reason)
[Q] Ask follow-up question to specific role
[D] Defer decision (specify timeline)| Rule | Rationale |
|---|---|
| Founder corrections override all agent proposals | Human judgment is final |
| No pushback on founder decisions | Agents advise, founder decides |
| 30-minute inactivity auto-closes as "pending review" | Prevents zombie meetings |
| Founder can reopen any time | Decisions are not time-locked |
| Follow-up questions go to specific role | Keeps discussion focused |
Purpose: After founder approval, extract and log all decisions.
Step 1: Write full transcript to Layer 1
--> memory/board-meetings/YYYY-MM-DD-raw.md
Step 2: Run conflict detection against existing decisions
--> Check for DO_NOT_RESURFACE violations
--> Check for topic contradictions
--> Check for owner conflicts
Step 3: Surface any conflicts to founder for resolution
Step 4: Append approved decisions to Layer 2
--> memory/board-meetings/decisions.md
Step 5: Mark rejected proposals with DO_NOT_RESURFACE
Step 6: Confirm to founder:
"Meeting concluded. Logged: [N] decisions, [M] action items,
[K] DO_NOT_RESURFACE flags."| Failure | Detection | Fix |
|---|---|---|
| Groupthink | All advisors agree without tension | Re-run Phase 2 isolated; force "strongest argument against" |
| Analysis paralysis | Discussion exceeds 5 points per advisor | Cap at 5; force recommendation even with Low confidence |
| Bikeshedding | Discussion on minor points, major decisions deferred | Log as async action; return to main agenda |
| Role bleed | CFO making product calls, CTO pricing | Critic flags in Phase 3; exclude from synthesis |
| Layer contamination | Raw transcripts loaded in Phase 1 | Hard rule: decisions.md only. Never raw. |
| Founder absence | Phase 5 timeout | Auto-close as pending. No decisions without founder. |
| Stale context | Company context not loaded | Phase 1 mandatory context check |
| Missing role | Key perspective not activated | Chief of Staff reviews topic against routing matrix |
| Trigger | Meeting Type | Typical Duration |
|---|---|---|
| Scheduled quarterly | Full strategic review | 2-3 hours |
| Complexity score >= 8 | On-demand strategic | 1-2 hours |
| Cross-functional conflict | Resolution meeting | 1 hour |
| Crisis or urgent decision | Emergency session | 30-60 minutes |
| Founder request | Any topic | Varies |
| Request | Deliverable |
|---|---|
| "Convene the board on [topic]" | Full 6-phase protocol execution |
| "Quick advisory meeting" | Abbreviated: Phase 1-2-4-5 (skip critic) |
| "Review a past meeting" | Load Layer 1 raw transcript (explicit request only) |
| "What did we decide about [topic]?" | Search Layer 2 decision history |
| "Resume a pending meeting" | Reload Phase 5 with pending synthesis |
Validates role activation, contribution completeness, and phase sequencing.
# Simulate with defaults
python scripts/meeting_simulator.py
# Specify topic and complexity
python scripts/meeting_simulator.py --topic "Series B timing" --type fundraising --complexity 9
# Specify activated roles
python scripts/meeting_simulator.py --type m_and_a --roles CEO CFO CTO CHRO
# List all topic types and required roles
python scripts/meeting_simulator.py --list-topics
# JSON output
python scripts/meeting_simulator.py --type strategy --jsonTracks board decisions, detects conflicts, flags overdue reviews and actions.
# Track demo decisions
python scripts/decision_tracker.py
# From decision log file
python scripts/decision_tracker.py --input decisions.json
# JSON output
python scripts/decision_tracker.py --jsonScores decision complexity to determine single/dual/multi-advisor or board routing.
# Score with CLI flags
python scripts/complexity_scorer.py --topic "Market expansion" --domains 2 --reversibility 2 --financial 1 --team 2 --urgency 0
# Add modifiers
python scripts/complexity_scorer.py --topic "Acquisition" --domains 2 --reversibility 2 --financial 2 --team 2 --urgency 1 --modifiers cross_functional external_stakeholders sets_precedent
# JSON output
python scripts/complexity_scorer.py --topic "Pricing change" --json| Problem | Likely Cause | Fix |
|---|---|---|
| All advisors agree without any tension in Phase 2 | Groupthink or trivial topic; isolation may have been breached | Re-run Phase 2 with forced "strongest argument against" from each role |
| Discussion exceeds 5 points per advisor | Analysis paralysis; no cap enforced | Hard cap at 5 key points; force a recommendation even with Low confidence |
| Phase 5 times out with no founder response | Founder absence or decision avoidance | Auto-close as "pending review" at 30 min; no decisions without founder |
| Same topic discussed in 3+ meetings | Decision avoidance or new data not surfaced | Escalate: force decision or formally defer with stated timeline |
| Decisions logged but never reviewed | Decision logger not integrated into meeting cadence | Add "previous decisions review" to Phase 1 context loading |
| Roles operating outside their domain | No critic analysis conducted or critic missed it | Enforce Phase 3 critic checklist; flag domain violations explicitly |
In Scope: Multi-agent deliberation protocol, role activation matrix, contribution formats, critic analysis, synthesis, decision extraction, decision conflict detection, meeting simulation.
Out of Scope: Actual AI agent orchestration (this is a protocol specification, not runtime code), real-time meeting facilitation, video/audio recording, external board member management.
Limitations: The protocol assumes all advisor contributions are available in text format. Complexity scoring provides routing guidance but cannot account for political dynamics. Decision conflict detection works on exact topic matching -- semantic conflicts across different topics require human judgment.
| Skill | Integration |
|---|---|
chief-of-staff | Routes questions that score 9-10 complexity into the board meeting protocol |
decision-logger | Phase 6 feeds decisions directly into the two-layer decision memory |
board-deck-builder | Board deck sections provide pre-read context for Phase 1 |
executive-mentor | Phase 3 critic analysis can be performed by the Executive Mentor skill |
ceo-advisor through ciso-advisor | All C-suite advisors contribute independently in Phase 2 |
strategic-alignment | Validates that meeting decisions align with strategic goals |
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (scripts) in c-level-advisor/board-meeting of borghei/Claude-Skills.
Open the folder on GitHubat commit 4a698e8
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 skillborghei/Claude-Skills | 891 | — | ~4.1k | Automated safety check: Pass | MIT | |
| KapsoLeeroo-AI/kapso | 121 | — | ~642 | Automated safety check: Pass | MIT | |
| Edt MCP Tool DescriptionsDitriXNew/EDT-MCP | 296 | — | ~3k | Automated safety check: Pass | AGPL-3.0 | |
| Co MarketingNexus-JPF/note-companion | 870 | 3 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Ads Quickzubair-trabzada/ai-ads-claude | 268 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Book Ideationrobertguss/claude-code-toolkit | 124 | — | ~2k | Automated safety check: Pass | Proprietary |
Leeroo-AI/kapso
Optimize code using KAPSO (Knowledge-Grounded Optimization).
DitriXNew/EDT-MCP
How to size, write and A/B-test the text of a tool — its description and its inputSchema parameter prose — so that cutting it does not cost call quality, and so that a tool that IS getting called…
Nexus-JPF/note-companion
When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities.
zubair-trabzada/ai-ads-claude
60-Second Ad Readiness Snapshot — quick assessment without subagents
robertguss/claude-code-toolkit
Develop raw book ideas into structured nonfiction book concepts.
rampstackco/claude-skills
Generate, evaluate, and narrow brand concepts during early ideation including positioning territories, naming candidates, mood directions, and narrative angles.
borghei/Claude-Skills
Test and evaluation harness for AI agents — scenario suites, deterministic replay, regression diffing, cost and latency budgets.
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Categories
Multi-agent board meeting protocol running a structured 6-phase deliberation with isolated C-suite contributions to prevent groupthink. Board Meeting is an agent skill from borghei/Claude-Skills. Multi-agent board meeting protocol running a structured 6-phase deliberation with isolated C-suite contributions to prevent groupthink.
Board Meeting fits situations like: making major strategic decisions; resolving cross-functional disagreements.
Run `npx skills add borghei/Claude-Skills --skill board-meeting -a claude-code`. Or copy the skill folder (c-level-advisor/board-meeting in borghei/Claude-Skills) into .claude/skills/board-meeting in your project. Claude Code loads it when a task matches its description.
Run `npx skills add borghei/Claude-Skills --skill board-meeting -a codex`. Or copy the skill folder (c-level-advisor/board-meeting in borghei/Claude-Skills) into .agents/skills/board-meeting in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/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.
Going by SKILL.md and its folder, Board Meeting needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
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.
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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
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.
About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Board Meeting: Kapso (Leeroo-AI/kapso, 121 stars), Edt MCP Tool Descriptions (DitriXNew/EDT-MCP, 296 stars), Co Marketing (Nexus-JPF/note-companion, 870 stars) and Ads Quick (zubair-trabzada/ai-ads-claude, 268 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 891 GitHub stars. The repository holds 354 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/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.