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.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

73%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 dense, highly actionable scene-layer skill with an excellent validation-gated workflow and strong progressive-disclosure discipline toward its parent pptx skill. Its main weaknesses are length/repetition across sections and a few recipe blocks that defer or leave card-repetition as exercises.

Suggestions

Consolidate the repeated hockey-stick y-axis and 4-bucket Use-of-Funds explanations into a single canonical statement and cross-reference it, to trim roughly 806 lines of redundancy.

For recipes that currently say 'Repeat the 4-block pattern at x=...' (e.g. Problem, Why-Now, Team), provide the full multi-card batch JSON inline so each recipe is copy-paste complete.

Move the per-recipe bash blocks or the 12-recipe catalog into a references/ file (e.g. RECIPES.md) so SKILL.md stays a navigable overview, improving progressive disclosure for this >50-line skill.

Dimension	Reasoning	Score
Conciseness	Largely lean and additive (it deliberately inherits rather than re-teaches pptx rules, and uses tables/code blocks that earn their tokens), but at 806 lines it repeats several motifs — the hockey-stick y-axis, the 4-bucket Use-of-Funds, 'VCs read it in <2 seconds' narration — across multiple sections, which could be tightened.	3 / 5
Actionability	Most recipes (Cover, Problem, Market, Traction, Team, Financials, Ask, Pipeline, Competitive) ship copy-paste-ready officecli bash blocks with real props and grid math, but a few use 'Repeat for cards 2 and 3' placeholders or defer full batch blocks to '→ see pptx v2 §X', leaving minor gaps.	4 / 5
Workflow Clarity	The build flow is explicitly sequenced (pick stage → pick 赛道 template → recipes → Delivery Gate) and the Gate system provides explicit validation checkpoints with REJECT/exit-1 feedback loops and 'fix and re-validate' retry guidance for this batch/destructive file-generation operation.	5 / 5
Progressive Disclosure	Well-organized into clearly signaled sections and it pushes inherited material one level deep via '→ see pptx v2 §X' cross-references to the parent skill, but no bundle files exist in references/scripts/assets and the 12 recipes + large tables all live inline in a single 806-line file, a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

90%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, third-person description with comprehensive trigger terms, explicit when/what guidance, and clear routing boundaries against the sibling pptx skill. Its only gap is listing concrete build actions rather than routing/identity language, which keeps specificity at the midpoint.

Dimension	Reasoning	Score
Specificity	Names the domain richly ('fundraising / investor pitch deck — seed, Series A / B / C, convertible note, SAFE round') and one concrete output ('Output is a single .pptx'), but does not enumerate several specific build actions, so it sits at 'domain + 1-2 concrete actions' rather than a comprehensive action list.	3 / 5
Completeness	Explicitly answers both what ('Output is a single .pptx', 'scene layer on top of officecli-pptx — inherits every pptx v2 rule') and when ('Use this skill when the user is building a fundraising / investor pitch deck', 'Trigger on: ...', plus a DO-NOT routing clause) with concrete trigger phrases.	5 / 5
Trigger Term Quality	Lists comprehensive natural trigger phrases users would actually say ('pitch deck', 'investor deck', 'Series A/B/C deck', 'fundraising deck', 'seed pitch', 'VC deck', 'raising capital', 'term sheet presentation') plus explicit negative triggers, covering synonyms and round variants.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (fundraising pitch decks) with distinct round-specific triggers and an explicit boundary clause routing board reviews / sales decks / all-hands / product launches to the officecli-pptx base, minimizing conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (811 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: iOfficeAI/OfficeCLI
Path: skills/officecli-pitch-deck/SKILL.md
Commit: 459b1a4

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