CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

board-prep

Board meeting preparation for the adversarial scenario, not the friendly one. Forces numbers-cold mastery, anticipates hard questions, builds a narrative that acknowledges weakness without losing the room. Use when preparing for a board meeting, an investor update, fundraising presentation, or any high-stakes adversarial review where every number must live in your head not just on a slide.

66

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 highly actionable, well-sequenced advisory skill: concrete question banks, a clear five-phase workflow with validation checkpoints and feedback loops, and timed checklists. Its weaknesses are motivational padding in the framing sections and a monolithic single-file layout where the question bank could be externalized.

Suggestions

Cut or compress "The Reality of Board Meetings" and closing flourishes ("The next board prep starts now") to pure instructional content.

Move the standard adversarial question bank by topic into a references/ file (e.g. questions.md), keeping SKILL.md as the workflow overview with a clearly signaled pointer.

DimensionReasoningScore

Conciseness

The bulk is lean checklists and question banks, but "The Reality of Board Meetings" ("Your board members have seen 50+ companies... They know when you're not being straight with them") is motivational framing Claude doesn't need, and flourishes like "The next board prep starts now" add tokens without adding instruction. Mostly efficient with some unnecessary explanation that could be tightened — anchor 3 rather than anchor 4's minor instances.

3 / 5

Actionability

Fully actionable guidance for an instruction-only skill: exact adversarial questions per topic ("At current burn you have N months. What's your plan if the next round takes 9 months?"), a five-part narrative structure, timed checklists ("48 hours before", "Within 24 hours"), and a copy-adaptable email template ("Revenue came in at $X vs $Y target. Here's what happened...").

5 / 5

Workflow Clarity

Clear chronological sequence (Phases 1–5, pre-meeting, during, after) with explicit validation checkpoints ("Stress test yourself... If you pause, you don't know it") and a genuine feedback loop in the mock meeting ("note every question that made you pause or feel defensive" → "the questions you need to prepare for"), plus checklists. No destructive or batch operations, so no cap applies.

5 / 5

Progressive Disclosure

Well-organized single file with clear section headers, working checklists, and no buried or nested references. At ~150 lines with no bundle files, the topic-by-topic adversarial question bank is content that could be split into a reference file — good structure with minor organization gaps (anchor 4) rather than anchor 5's appropriately split layout.

4 / 5

Total

17

/

20

Passed

Description

78%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 with an explicit "Use when..." clause covering concrete triggers and a clear niche. Its main weakness is specificity: the stated actions are conceptual ("forces numbers-cold mastery") rather than concrete operations, and it carries rhetorical padding.

Suggestions

Replace conceptual verbs with concrete operations, e.g. "Drills core metrics (burn, runway, churn, NRR) until recall is automatic, generates the adversarial question bank for each agenda item, and structures the pre-read narrative and follow-up plan."

Trim rhetorical flourishes ("not the friendly one", "without losing the room") to free tokens for one or two more operational specifics.

Add common trigger synonyms such as "board deck" or "board slides" to widen natural-matching coverage.

DimensionReasoningScore

Specificity

The description names the domain and three actions ("Forces numbers-cold mastery, anticipates hard questions, builds a narrative that acknowledges weakness"), but the verbs are conceptual rather than operational and phrases like "without losing the room" are rhetorical padding. It exceeds anchor 2 (actions are more than minimal) but is not noticeably above the midpoint toward anchor 4's several concrete operations.

3 / 5

Completeness

Explicitly answers both what ("Forces numbers-cold mastery, anticipates hard questions, builds a narrative") and when ("Use when preparing for a board meeting, an investor update, fundraising presentation, or any high-stakes adversarial review") with concrete trigger phrases, matching the anchor 5 pattern.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("board meeting", "investor update", "fundraising presentation", "high-stakes adversarial review") that a user would plausibly say, but common variations like "board deck", "board slides", or "pitch" are missing — above anchor 3, short of anchor 5's comprehensive synonyms.

4 / 5

Distinctiveness Conflict Risk

Clear niche (adversarial board prep) with distinct triggers, but "fundraising presentation" and "investor update" create minor overlap risk with pitch-deck and investor-communication skills — anchor 4's minor overlap with closely related skills.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

.gemini/skills/board-prep/SKILL.md

Reviewed

Table of Contents

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.