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

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

77%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 body with strong workflow sequencing and validation. The main weakness is progressive disclosure: two of three listed reference files do not exist in the bundle, and the output format is inlined rather than referenced.

Suggestions

Create the missing templates/meeting-agenda.md and templates/meeting-minutes.md files (or remove those Reference entries) so every referenced path resolves.

Move the 'Board Meeting Output' format (currently pointing at ../agent-protocol/SKILL.md) and the inlined contribution format into a templates file referenced one level deep.

Tighten the Phase 2 reasoning-technique roster and the legacy-folder migration note, which assume context or restate history Claude can infer.

Dimension	Reasoning	Score
Conciseness	Mostly efficient tables and terse phase descriptions assume Claude's competence; a few sections (e.g. the reasoning-technique roster, contribution-format block) could be tightened, and the migration note is mild padding.	4 / 5
Actionability	Provides concrete, executable guidance — exact file paths, a copy-paste contribution format block, a founder-review prompt template, and a role-activation table — with minor gaps where steps rely on sibling SKILL.md definitions.	4 / 5
Workflow Clarity	A clearly sequenced 6-phase process with explicit validation checkpoints (Phase 5 full-stop founder review, Phase 6 Layer 1/2 logging) and a failure-mode quick reference with feedback loops for groupthink and contamination.	5 / 5
Progressive Disclosure	Some structure and one real reference (references/meeting-facilitation.md is referenced and exists), but the References section also lists templates/meeting-agenda.md and templates/meeting-minutes.md whose templates/ directory does not exist, and several bodies are inlined that could live in separate files.	3 / 5
	Total	16 / 20 Passed

Description

87%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 description that clearly states both capability and trigger conditions in third person, with concrete phase names and specific invocation guidance. Minor room for additional synonyms but overall highly actionable.

Dimension	Reasoning	Score
Specificity	Names the domain (multi-agent board meeting) and lists several concrete actions — 'context loading, independent C-suite contributions, critic analysis, synthesis, founder review, and decision extraction' — with minor gaps in coverage.	4 / 5
Completeness	Explicitly answers both what (the 6-phase deliberation protocol) and when ('Use when the user invokes /cs:boardroom, calls a board meeting, or wants structured multi-perspective executive deliberation') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('calls a board meeting', 'structured multi-perspective executive deliberation', '/cs:boardroom') with good coverage, though a few common synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	A clear niche (structured C-suite board protocol with isolation and two-layer memory) with distinct triggers (/cs:boardroom, board meeting) and minimal conflict risk against other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

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

Reviewed: ~1 hour 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.