CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pitch-deck

Populates investment banking pitch deck templates with data from source files. Use when: user provides a PowerPoint template to fill in, user has source data (Excel/CSV) to populate into slides, user mentions populating or filling a pitch deck template, or user needs to transfer data into existing slide layouts. Not for creating presentations from scratch.

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 ./plugins/vertical-plugins/investment-banking/skills/pitch-deck/SKILL.md

The canonical home for this skill is pitch-deck in anthropics/financial-services

SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is a well-engineered operational playbook: an explicit phased workflow with validation feedback loops, concrete commands, and exact formatting specs. Its main weaknesses are notable repetition of the placeholder anti-patterns across multiple sections and a broken reference layer — the body heavily relies on four reference files that are absent from the evaluated bundle.

Suggestions

Consolidate the placeholder/anti-pattern guidance, which currently appears in four or more places (Critical Anti-Patterns, Placeholder vs. Production table, MUST Requirements, Common Failures, Final Quality Checklist), into one authoritative section with brief pointers to it.

Ship the four reference files (formatting-standards.md, slide-templates.md, xml-reference.md, calculation-standards.md) with the skill, or inline the critical content — as evaluated, every 'see reference/...' link is a dead path and the instructed 'read all reference files at task start' cannot be performed.

Move the detailed quick-reference tables (bullet symbols, hierarchy levels, rounding) into the referenced formatting/calculation files once they exist, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is dense and domain-specific with no padding about concepts Claude already knows, but the placeholder/anti-pattern rules are repeated across at least four sections (Critical Anti-Patterns, the Placeholder vs. Production summary table, MUST Requirements, Common Failures, and the Final Quality Checklist), and cross-slide consistency is stated three times. This is more than the 'minor instances' of anchor 4 — the document could be meaningfully tightened by consolidating — but it is not 'severely verbose' padding, so it sits at anchor 3.

3 / 5

Actionability

The body provides copy-paste-ready commands ('soffice --headless --convert-to pdf presentation.pptx', 'pdftoppm -jpeg -r 150 presentation.pdf slide'), exact numeric specs (footnote widths of 32.5cm/24cm, font-size ranges, rounding examples like '18.5 → $19bn'), and exact escalation strings ('[LOGO NOT PROVIDED - please supply company logo]'). However, the core population mechanics (how to actually edit the pptx) are delegated to xml-reference.md, leaving a minor gap in executable guidance within the body itself, which keeps it below anchor 5.

4 / 5

Workflow Clarity

A decision tree routes task types, a 5-phase workflow is explicitly sequenced with a copyable progress checklist, Phase 4 is a validate → fix → repeat feedback loop with a capped 3-cycle escalation protocol, and error-handling sections cover conversion failures, data conflicts, and calculation mismatches, plus a final quality checklist. This matches the anchor-5 example of explicit validation steps, feedback loops, and checklists for a complex process.

5 / 5

Progressive Disclosure

The structure is well designed: a reference-file table with per-file purposes, clearly signaled one-level-deep links with section anchors, and appropriate inline quick-reference content. However, the four referenced files (reference/formatting-standards.md, slide-templates.md, xml-reference.md, calculation-standards.md) do not exist in the evaluated bundle (no reference/ or references/ directory is present), so 'Read all reference files at task start' points at unresolvable paths. Against the actual bundle structure this is a real navigation failure, not the 'minor organization gaps' of anchor 4, placing it at anchor 3 — though the in-document organization itself is good.

3 / 5

Total

15

/

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 description that clearly states what the skill does and gives explicit, natural 'Use when' triggers plus a negative boundary that reduces conflict risk. Its only weakness is thin capability coverage — a single populate action rather than several distinct ones — and a few missing trigger synonyms like '.pptx'.

Suggestions

List 2-3 more concrete capabilities alongside 'populates' (e.g., 'maps source data to slide sections, applies template formatting, validates rendered output') to raise specificity.

Add natural trigger variations such as '.pptx files', 'deck', and 'slide layouts' to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain ('investment banking pitch deck templates') and one concrete action ('Populates ... with data from source files'), which matches the anchor for 1-2 concrete actions but not comprehensive coverage. It does not list several distinct actions (e.g., validate, format, convert), so it is below anchor 4, while the single action is specific rather than generic, keeping it above anchor 2.

3 / 5

Completeness

It explicitly answers both what ('Populates investment banking pitch deck templates with data from source files') and when (a 'Use when:' clause with four concrete trigger scenarios), plus an explicit negative boundary ('Not for creating presentations from scratch'). This mirrors the anchor-5 example structure of clear what AND when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases users would say are well covered: 'user provides a PowerPoint template to fill in', 'source data (Excel/CSV) to populate into slides', 'populating or filling a pitch deck template', 'transfer data into existing slide layouts'. A few natural variations are missing (e.g., '.pptx' file extension, 'deck' alone, 'slides'), so it falls just short of the comprehensive-synonym anchor 5 but is clearly above anchor 3's 'missing common variations'.

4 / 5

Distinctiveness Conflict Risk

A clear niche (populating investment banking pitch deck templates) with distinct triggers, and the explicit exclusion 'Not for creating presentations from scratch' fences off the closest competing presentation-creation skill. Overlap risk with generic PowerPoint editing skills is minimal, matching the clear-niche anchor 5.

5 / 5

Total

17

/

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

relative_links

Relative link issues: 22 missing

Warning

Total

15

/

16

Passed

Repository

anthropics/financial-services

Path

plugins/vertical-plugins/investment-banking/skills/pitch-deck/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.