Name: board-meeting
Rating: 70.39999999999999 (1 reviews)
Author: alirezarezvani

board-meeting

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.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is board-meeting in alirezarezvani/claude-skills

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable protocol with clear sequencing and validation gates. The primary defect is broken progressive disclosure: every referenced bundle file is absent and core output formatting is deferred to an external skill.

Suggestions

Create the missing referenced files (templates/meeting-agenda.md, templates/meeting-minutes.md, references/meeting-facilitation.md) or remove the references from the body.

Inline the Board Meeting Output format and the canonical two-layer memory layout instead of deferring them to ../agent-protocol/SKILL.md, or confirm that skill is bundled alongside this one.

Consider moving the role→reasoning-technique mapping and the 14-role ordering into references/meeting-facilitation.md to tighten the overview.

Dimension	Reasoning	Score
Conciseness	Lean and operational — tables, checklists, and a contribution-format template with no padding about what a board meeting is — though the role-technique mapping line and 14-role ordering could be trimmed into a reference file.	4 / 5
Actionability	Provides a copy-paste contribution-format template, exact memory paths (~/.claude/decisions/raw/...), a topic→role activation table, and a concrete critic checklist — fully actionable guidance for an instruction-only skill.	5 / 5
Workflow Clarity	Six phases are clearly sequenced with an explicit founder-review validation gate (Phase 5), per-agent self-verification, a critic checkpoint, and a failure-mode table providing feedback loops for error recovery.	5 / 5
Progressive Disclosure	Section structure is well-organized and references are explicitly signaled, but all three referenced bundle files (templates/meeting-agenda.md, templates/meeting-minutes.md, references/meeting-facilitation.md) are missing, and the core output format is deferred to an external ../agent-protocol/SKILL.md, breaking navigation.	3 / 5
	Total	17 / 20 Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states capability and trigger conditions with concrete phrases. The main weakness is slight technicality in one trigger phrase and modest breadth in the "strategic question" tail.

Dimension	Reasoning	Score
Specificity	Names the domain and lists multiple concrete actions — "context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction" — giving comprehensive coverage of the 6-phase protocol.	5 / 5
Completeness	Explicitly answers both what ("Multi-agent board meeting protocol... Runs a structured 6-phase deliberation") and when ("Use when the user invokes /cs:boardroom, calls a board meeting, or wants... executive deliberation on a strategic question") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms like "calls a board meeting" and "/cs:boardroom" are present, but the phrasing "structured multi-perspective executive deliberation" leans technical rather than what a user would naturally say.	4 / 5
Distinctiveness Conflict Risk	The board-meeting/C-suite framing and /cs:boardroom command form a clear niche, but the "strategic question" tail is broad enough to risk minor overlap with general strategy/advisory skills.	4 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/board-meeting/SKILL.md
Commit: 19392f7

Reviewed: ~2 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.