CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

board-deck-builder

Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives. Covers structure, narrative framework, bad news delivery, and common mistakes.

68

Quality

85%

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-deck-builder in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

Highly actionable, well-organized content with concrete examples and per-section rules that cover the common deck types. Its main weakness is the bundle structure: both referenced files are missing from the bundle, and the detailed section spec is inlined where the template file was meant to live.

Suggestions

Add the referenced files to the bundle (references/deck-frameworks.md and templates/board-deck-template.md) or remove the citations — both paths are currently broken, so a reader following 'See references/deck-frameworks.md for Sequoia format' finds nothing.

Move the detailed 11-section specification into templates/board-deck-template.md and keep SKILL.md as a lean overview (section order, narrative framework, bad-news delivery, cadence notes), which would also improve token efficiency.

Remove the '## Keywords' section: it duplicates trigger terms already carried by the frontmatter description and consumes tokens without instructing the model on how to execute the skill.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive throughout (section rules, tables, good/bad examples) and never explains concepts Claude already knows, but the "## Keywords" section lists 12 trigger phrases that duplicate the frontmatter description's job and add no executable guidance. That is minor trimmable padding, placing it between the 3 and 5 anchors, closer to lean-and-efficient.

4 / 5

Actionability

For an instruction-only skill the guidance is fully executable: "3 sentences. No more.", "6-8 metrics max. Use a table." with a filled example table, a good/bad executive-summary pair, a 5-step bad-news script with example phrasings, and "High confidence $2.6M, upside to $2.9M..." forecast formatting. Specific examples cover the common cases (quarterly, monthly early-stage, fundraising) via the Cadence Notes.

5 / 5

Workflow Clarity

A clear sequence exists (Quick Start invocation → 11 sections in standard order → 4-act narrative → cadence variant), and per-section constraints ("The forecast must have a confidence level", "One sentence on each variance") plus the mistakes table act as implicit checkpoints. It falls short of 5 because there is no explicit final validation/review step; deck building is not a destructive or batch operation, so the cap of 3 does not apply.

4 / 5

Progressive Disclosure

The body is well-organized with clear section headers and a clearly signaled References section, but it cites "references/deck-frameworks.md" and "templates/board-deck-template.md", neither of which exists in the bundle (no references/ or templates/ directories are present). Additionally, the full 11-section deck specification is inlined in SKILL.md even though the (missing) template file is described as the fill-in home for that detail — matching the 3 anchor's "references present but content that should be separate is inline".

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: explicit what-and-when structure, natural trigger phrases, and a distinct niche. The only gaps are action-level specificity (coverage is partly topic enumeration) and a few missing synonyms that would push trigger coverage to comprehensive.

DimensionReasoningScore

Specificity

"Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles" names concrete actions, and "Covers structure, narrative framework, bad news delivery, and common mistakes" enumerates scope, but the coverage is topic-level rather than action-level (no mention of metrics dashboards or cadence variants). This sits between the 3 anchor (1-2 concrete actions, not comprehensive) and the 5 anchor (multiple specific actions, comprehensive), noticeably above the midpoint.

4 / 5

Completeness

It clearly answers "what" ("Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles") and explicitly answers "when" with concrete trigger scenarios ("Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives"). This matches the 5 anchor's pattern of explicit what-and-when with concrete trigger phrases.

5 / 5

Trigger Term Quality

"Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives" includes natural phrases a user would say. Common synonyms like "board deck", "board pack", "QBR", and "investor pitch" are missing from the description itself (they appear only in the body's Keywords section), so it falls just short of the 5 anchor's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Board and investor update decks tied to C-suite roles is a clear niche with distinct triggers ("board meetings", "quarterly business reviews", "fundraising narratives"), matching the 5 anchor: minimal conflict risk with other skills. It is written in third person ("Assembles"), so no voice penalty applies.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/board-deck-builder/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.