CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

67

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/board-prep/SKILL.md

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

SKILL.md
Quality
Evals
Security

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 board-prep skill with a clear phased workflow, explicit validation/feedback loop, and strong concrete guidance (question banks, templates, checklists). The weakest dimension is conciseness, where motivational framing and a near-verbatim restatement of the description add tokens that don't earn their place.

Suggestions

Trim the 'The Reality of Board Meetings' section and the opening paragraph (which restates the description) to remove motivational framing Claude already infers.

Add one fully worked example (a completed pre-meeting email or a sample 5-part narrative) to lift actionability from strong to copy-paste ready.

Replace rhetorical prose ('They know when you're not being straight with them') with direct, imperative guidance to tighten token efficiency.

DimensionReasoningScore

Conciseness

Mostly efficient instructional prose with no padding about what board meetings are, matching anchor 3's 'mostly efficient but includes some unnecessary explanation'; sections like 'The Reality of Board Meetings' and the near-verbatim restatement of the description are motivational framing Claude could infer, and the rhetorical phrasing ('They know when you're not being straight with them') is more than minor, keeping it below 4.

3 / 5

Actionability

Provides highly specific, executable guidance for an instruction-only skill — an exact list of numbers to know cold, quoted adversarial questions by topic, a named 5-part narrative structure, a 5-sentence pre-meeting email template, and director archetypes with their concerns — matching anchor 4's 'mostly executable guidance... with minor gaps'; it stops short of 5 because no fully worked example (e.g., a complete narrative or finished email) is included.

4 / 5

Workflow Clarity

A clear 5-phase sequence (Numbers Cold through Director-by-Director) with explicit validation and a feedback loop (the mock meeting: 'note every question that made you pause... The questions that made you defensive = the questions you need to prepare for'), plus 48h/day-of/during/after checklists, matching anchor 5's 'clear sequence with explicit validation steps; feedback loops; checklists'; operations are non-destructive so the cap-3 rule does not apply.

5 / 5

Progressive Disclosure

A single self-contained file (no bundle files, no nested references) with clean section headers and content appropriately scoped inline for a prep skill; the rubric's simple-skill exception permits a 5 for a well-organized self-contained skill with no external references, matching anchor 5's 'clear overview... easy navigation'.

5 / 5

Total

17

/

20

Passed

Description

82%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, specific description that clearly answers both what and when with concrete trigger phrases and a well-defined adversarial-board niche. The main weakness is voice: it uses second-person ('Use when...', 'your head') instead of the third-person voice the rubric rewards, which caps the specificity score.

Suggestions

Rewrite the description in third person ('Prepares for board meetings... Use when the user is preparing for...') to avoid the voice penalty.

Add a couple more natural shorthand triggers ('board prep', 'pitch deck review') to push trigger-term coverage toward comprehensive.

Consider enumerating one or two more concrete actions (e.g., 'runs a mock board session', 'profiles each director') to broaden capability coverage.

DimensionReasoningScore

Specificity

Names the domain plus three concrete actions ('forces numbers-cold mastery, anticipates hard questions, builds a narrative that acknowledges weakness without losing the room'), matching anchor 4's 'several specific actions; minor gaps', but the rubric's voice penalty applies because the description uses second person ('Use when preparing...', 'must live in your head') rather than third person, reducing the score by 1.

3 / 5

Completeness

Explicitly answers both what ('Board meeting preparation... 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 example directly.

5 / 5

Trigger Term Quality

Good coverage of natural phrases a user would say ('board meeting', 'investor update', 'fundraising presentation', 'high-stakes adversarial review'), matching anchor 4's 'good keyword coverage; a few natural terms missing' — shorthand like 'board prep' or 'pitch deck' are absent, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

The adversarial framing ('for the adversarial scenario, not the friendly one') carves a clear niche distinct from general pitch or presentation skills, matching anchor 5's 'clear niche with distinct triggers; minimal conflict risk'; only minor conceptual overlap with generic fundraising-presentation skills.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/claude-skills
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.