CtrlK
BlogDocsLog inGet started
Tessl Logo

officecli-pitch-deck

Use this skill when the user is building a fundraising / investor pitch deck — seed, Series A / B / C, convertible note, SAFE round, strategic raise. Trigger on: 'pitch deck', 'investor deck', 'Series A deck', 'Series B deck', 'Series C deck', 'fundraising deck', 'seed pitch', 'VC deck', 'raising capital', 'term sheet presentation'. Output is a single .pptx. This skill is a scene layer on top of officecli-pptx — inherits every pptx v2 rule (visual floor, grid, palettes, connector canon, Delivery Gate). DO NOT invoke for a generic board review, sales deck, all-hands, or product launch — route those to officecli-pptx base.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

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.

Highly actionable and well-sequenced content with strong validation loops, but it is a monolithic ~800-line file with duplicated sections (Gate 5b checklist, assumptions paragraph, repeated hockey-stick warnings) that inflates token cost. Splitting reference material into bundle files and de-duplicating would lift both weak dimensions.

Suggestions

De-duplicate: keep one Gate 5b checklist (the (a)–(f) per-slide list) and drop the earlier bullet duplication; merge the two 'assumptions panel is load-bearing' paragraphs in recipe 9 into one.

Consolidate the hockey-stick warning into its recipe 7 home plus one Gate reference — it is currently repeated in §identity, the stage table, ship-check row 3, Gate 5b, Gate 6.6, and Known Issues.

Split the slide-pattern tables, the 10+2 slide recipes, and the numbers-convention table into references/ files (e.g. patterns.md, recipes.md, numbers.md) so SKILL.md stays a navigable overview with one-level-deep pointers.

DimensionReasoningScore

Conciseness

Mostly efficient — it delegates inherited rules via '→ see pptx v2 §X' instead of re-teaching them — but contains avoidable repetition: the Gate 5b visual checklist appears twice (bullet list plus the (a)–(f) list), the 'assumptions panel is load-bearing' paragraph is duplicated in recipe 9, and the hockey-stick warning recurs ~7 times across sections. Not 4 because the duplication is noticeable rather than minor; not 2 because the bulk is dense, non-generic pitch/CLI content Claude does not already know.

3 / 5

Actionability

Fully executable copy-paste bash with exact geometry ('usable = 33.87 − 3 − 2·0.76 = 29.35, col_width = 29.35 / 3 = 9.78cm'), per-recipe QA one-liners, and a complete runnable Gate 6 script. Deferrals like 'Full batch block → see pptx v2 §(e)' are explicitly justified scene-layer inheritance, not pseudocode gaps.

5 / 5

Workflow Clarity

Clear sequenced workflow (Setup → stage diagnosis flagged 'Read this before writing a single command' → arc template → patterns → recipes → numbers convention → ship-check → Gates 1–6) with explicit validation checkpoints, REJECT/exit-1 feedback loops, and fix instructions for each gate, matching the top anchor.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent); the skill is a single ~800-line SKILL.md. The '→ see pptx v2 §X' pointers are one level deep and clearly signaled, but slide patterns, per-slide recipes, the numbers convention, and gate scripts are inline content that would fit better in dedicated reference files. Anchor 3 (some structure, content that should be separate is inline); not 4 because there is no actual file split at all.

3 / 5

Total

16

/

20

Passed

Description

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

An exemplary description: concrete what/when, a rich set of natural trigger terms, and explicit boundary routing against the parent pptx skill. The only soft spot is that capability enumeration leans on inheritance from officecli-pptx rather than listing the deck-building operations themselves.

DimensionReasoningScore

Specificity

Names concrete scope and output ('building a fundraising / investor pitch deck — seed, Series A / B / C, convertible note, SAFE round', 'Output is a single .pptx', 'inherits every pptx v2 rule (visual floor, grid, palettes, connector canon, Delivery Gate)'), matching the anchor that lists several specific actions with minor gaps. Not 5 because it enumerates deck types and inherited rule areas more than a comprehensive list of concrete operations.

4 / 5

Completeness

Explicitly answers both 'what' (build a fundraising pitch deck, output a single .pptx, scene layer over officecli-pptx) and 'when' ('Use this skill when the user is building…' plus a concrete trigger-on list and DO-NOT-invoke exclusions), matching the top anchor with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases — 'pitch deck', 'investor deck', 'Series A deck', 'fundraising deck', 'seed pitch', 'VC deck', 'raising capital', 'term sheet presentation' — covering synonyms, round-stage variants, and file-format context, matching the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

Clear fundraising niche with distinct round-stage triggers, and explicit negative routing ('DO NOT invoke for a generic board review, sales deck, all-hands, or product launch — route those to officecli-pptx base') minimizes overlap with the parent skill, matching the minimal-conflict anchor.

5 / 5

Total

19

/

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

skill_md_line_count

SKILL.md is long (811 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
iOfficeAI/OfficeCLI
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.