Pitch Deck
AnthropicOfficialPublished by Anthropic
- Skill
- Content generator
- Documents and content
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill assists in populating investment banking PowerPoint templates with data extracted from external sources like Excel, CSV, or reports. It follows a structured workflow to map data to template sections, apply formatting standards, and ensure consistency across slides. The process includes a validation loop to check for structural accuracy, table implementation, and formatting compliance, while providing guidance on handling common pitfalls like placeholder boxes and text-based tables.
What it does
- Extracts and validates data from source files like Excel or CSV.
- Maps extracted data to specific sections of a provided PowerPoint template.
- Replaces placeholder instruction boxes with properly formatted content.
- Creates actual PowerPoint table objects instead of text-based separators.
- Applies consistent formatting, font sizes, and alignment across slides.
- Performs visual validation checks to ensure content readability and structure.
When to use it
- When you have a PowerPoint template that needs to be filled with specific data.
- When you have source data in Excel or CSV files ready for presentation.
- When you need to ensure consistent formatting and alignment across a pitch deck.
- When you need to verify calculations and data accuracy within a slide deck.
Advantages
- Ensures data consistency across multiple slides.
- Automates the mapping of raw data into structured slide layouts.
- Enforces professional formatting standards for tables and bullet points.
- Provides a systematic validation loop to catch structural errors.
Usage examples
- “Populate the attached pitch deck template using the data in the provided quarterly_results.xlsx file.”
- The agent will extract the data, map it to the template sections, apply the required formatting, and provide a populated PowerPoint file.
- “I have a market sizing slide in my deck that needs to be updated with the figures from this CSV report.”
- The agent will identify the relevant slide, update the figures, ensure the table is correctly formatted, and verify the data against the source.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/anthropics/pitch-deck/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip pitch-deck.zip -d .agents/skills
Documentation by Anthropic
Populating Investment Banking Pitch Deck Templates
Reference Files
Read all reference files at task start before beginning any work. These contain critical patterns and anti-patterns that will affect your approach. Do not wait until you encounter issues.
| File | Purpose |
|---|---|
formatting-standards.md | Text, bullets, tables, charts, alignment |
slide-templates.md | Content mapping guidance for common slide types |
xml-reference.md | PowerPoint XML patterns for tables, shapes, arrows |
calculation-standards.md | Financial formulas for verification (CAGR, consensus) |
Workflow Decision Tree
What type of task is this?
┌─ Populating empty template with source data?
│ └─→ Follow "Template Population Workflow" below
│
├─ Editing existing populated slides?
│ └─→ Extract current content, modify, revalidate
│
└─ Fixing formatting issues on existing slides?
└─→ See "Common Failures" table, apply targeted fixes⚠️ Critical Rendering Limitation
LibreOffice is used for validation but DOES NOT render PowerPoint files accurately. It will mangle fonts, gradients, shape positions, text wrapping, and some table formatting.
What this means: A slide that passes visual validation in LibreOffice may still have issues in Microsoft PowerPoint. The validation loop catches structural issues (missing content, broken tables, placeholder formatting retained) but cannot catch font substitution, subtle alignment shifts, or gradient problems.
Required action: Always include this statement when delivering output:
"This file was validated using LibreOffice. Please review in Microsoft PowerPoint before distribution, as rendering differences may exist."
Template Population Workflow
Copy and track progress:
Pitch Deck Progress:
- [ ] Phase 1: Extract and validate source data
- [ ] Phase 2: Map content to template sections
- [ ] Phase 3: Populate slides with proper formatting
- [ ] Phase 4: Validate → Fix → Repeat until clean
- [ ] Phase 5: Final verificationPhase 1: Data Extraction
Create backup of original template before any modifications — copy to
[filename]_backup.pptx. Direct XML editing or unexpected errors can corrupt files.Identify all source materials (Excel, CSV, PDF reports, Word documents, databases, web sources)
Extract relevant data points from each source
Validate all numbers against original sources
Standardize units and currency (convert all figures to the primary unit/currency used in the template)
Note any calculations that need verification → see
calculation-standards.mdfor formulas
Phase 2: Content Mapping
Open and visually review the template — understand its structure, style, and existing content before modifying
Analyze template structure — identify all placeholder areas and content boxes
Map source data to corresponding template sections → see
slide-templates.mdfor mapping guidanceIdentify placeholder guidance boxes (colored instruction boxes from task creator)
Note any data gaps or mismatches → see
slide-templates.mdfor resolution
Phase 3: Template Population
Remove or reformat placeholder boxes — colored instruction boxes show WHAT to create, not HOW to format. Delete them and create properly formatted content in their place. See Critical Anti-Patterns.
Populate each section with mapped content (focus on content first)
Then apply formatting to match template style → see
formatting-standards.mdCreate tables as actual table objects (NEVER use pipe/tab-separated text) → see
xml-reference.mdCreate arrows/shapes as PowerPoint objects → see
xml-reference.mdInsert company logo if provided in task files; if not available, flag to user: "[LOGO NOT PROVIDED - please supply company logo]"
Phase 4: Validate → Fix → Repeat
This is a feedback loop. Repeat until all checks pass OR escalation is triggered.
# Convert to images for visual validation
soffice --headless --convert-to pdf presentation.pptx
pdftoppm -jpeg -r 150 presentation.pdf slideValidation checklist (check each slide image):
[ ] Text readable against background?
[ ] Tables are actual objects (columns aligned, NOT pipe/tab-separated text)?
[ ] Charts/tables fill designated areas?
[ ] Bullet formatting consistent within sections?
[ ] Font sizes match across same-level boxes?
[ ] No content beyond slide boundaries?
[ ] No placeholder formatting retained (no large colored boxes with data dumped in)?
[ ] No text-based "tables" (no
|or tab separators creating fake columns)?[ ] Cross-slide consistency: Same metrics/figures identical across all slides where they appear?
Fix cycle protocol:
| Cycle | Action |
|---|---|
| 1 | Fix all identified issues, re-validate |
| 2 | Fix remaining issues, re-validate |
| 3 | If issues persist, document remaining problems and escalate to user |
After 3 cycles, if issues remain:
List each unresolved issue with slide number and description
Explain what was attempted
Deliver the file with explicit disclaimer: "The following issues could not be resolved automatically: [list]. Manual review required."
Do not continue cycling indefinitely. Some issues (font rendering, complex shape alignment) may require manual intervention in PowerPoint.
Phase 5: Final Verification
Run through the Final Quality Checklist before delivering.
Quick Reference Tables
Bullet Symbols
| Context | Symbol | Usage |
|---|---|---|
| Included/Positive | ✓ | Items within scope, features present |
| Excluded/Negative | × | Items outside scope, features absent |
| Neutral list | • | General enumeration, commentary |
| Numbered sequence | 1. 2. 3. | Process steps, rankings |
| Sub-bullets | – | Secondary points under main bullets |
Slide Hierarchy Levels (Typical)
These are typical ranges—adjust based on template specifications:
| Level | Examples | Typical Size | Style |
|---|---|---|---|
| Title | Slide title | 40-48pt | Bold |
| Subtitle | Market definition, slide descriptor | 18-22pt | Bold |
| Section Header | "Key Projections", "Commentary" | 14-16pt | Regular |
| Block Label | "Segments Included", "Definition" sidebar | 12-14pt | Regular |
| Block Content | Bullet points, body text | 11-14pt | Regular |
| Table Header | Column headers | 10-12pt | Bold |
| Table Body | Cell content | 9-11pt | Regular |
| Footnotes | Sources, notes | 8-9pt | Italic |
Font Consistency Matching
Boxes at the same hierarchy level MUST use identical font sizes:
| Same Level | Must Match With |
|---|---|
| "Segments Included" | "Segments Excluded" |
| "Definition" | "Scope Rationale" |
| Left column bullets | Right column bullets |
| All block labels | Each other |
| All section headers | Each other |
Rounding for Presentation
These are typical conventions — adjust based on the magnitude of values and template style:
| Value Type | Typical Rounding | Example |
|---|---|---|
| Large market sizes ($10bn+) | Nearest $1bn | 18.5 → $19bn |
| Smaller market sizes (<$10bn) | Nearest $0.5bn or $0.1bn | 2.3 → $2.5bn |
| Size ranges | Match precision of sources | 14.9-22.1 → $15-22bn |
| CAGR | Whole % or 0.5% | 16.4% → 16% or 16.5% |
| Market share | Nearest 5% or match source | 21.4% → 20% |
| Multiples | 1 decimal | 9.69 → 9.7x |
Principle: Rounding should not materially change the figure. For smaller values, use finer precision.
Text Density Rules
Max 6-7 bullets per content box
Max 2 lines per bullet point
Parenthetical examples: same line or indented below
No orphan words (single word on new line)
Alignment Principles
Vertically stacked boxes must have identical:
Left margin position, bullet indentation, text start position, box width
Horizontally adjacent boxes must have identical:
Top position, height (where possible), internal padding
Multi-Slide Consistency
When the same data appears on multiple slides:
Use identical figures, formatting, and terminology
If a metric is updated on one slide, update all occurrences
Cross-reference during validation to catch mismatches
MUST Requirements
These requirements are non-negotiable regardless of template:
| Requirement | Details |
|---|---|
| Text Readability | All text MUST have sufficient contrast with background. Examples: white/light text on dark blue, dark green, black backgrounds; black/dark text on white, light gray, light yellow backgrounds. |
| Actual Table Objects | Tabular data MUST be table objects, not tab-separated text. See xml-reference.md. |
| Proper Chart/Table Sizing | Pasted visuals MUST fill designated area. See formatting-standards.md. |
| Consistent Formatting | Bullets within section MUST match (symbol, size, indent). Same-level boxes MUST use same font size. |
| Content Boundaries | All content MUST stay within slide edges. Footnote box width: ~32.5cm for 16:9, ~24cm for 4:3. |
| No Placeholder Formatting | Remove colored instruction boxes. Main body: dark text on light background per template. |
Critical Anti-Patterns: NEVER DO THESE
These failures occur when placeholder formatting is mistaken for output formatting. Recognizing these patterns is essential.
Anti-Pattern 1: Populating Data INTO Placeholder Boxes
What happens: Template has colored instruction boxes (yellow, orange, etc.) with guidance text. Model replaces the guidance text with actual data BUT KEEPS THE COLORED BOX.
Why it's wrong: The colored box IS the placeholder. It tells you what content goes there. The output should have different formatting — typically dark text on white/light background, or properly styled shapes.
Recognition test: If your populated slide has large colored rectangles filled with data text, you have copied the placeholder format instead of replacing it.
Critical distinction — two types of "placeholders":
| Type | How to identify | What to do |
|---|---|---|
| Instruction boxes | Bright colors (yellow, orange), contains guidance text like "Insert X here", white/light text on colored background | DELETE the entire shape, then create new content with production formatting |
| Layout placeholders | Part of slide master/layout, neutral colors matching template theme, "Click to add text" | KEEP the shape, REPLACE the text content only |
If uncertain: check if the shape exists on an empty slide from the same template. Layout placeholders persist; instruction boxes are regular shapes.
Anti-Pattern 2: Text-Based "Tables"
What happens: Model creates table-like content using separator characters (|, tabs, spaces) instead of actual table objects.
Why it's wrong: This is NOT a table. Columns will never align properly, it cannot be formatted consistently, and it looks unprofessional.
Recognition test: If you're typing | characters or relying on spaces/tabs to create columns, you're creating text, not a table.
MUST verify: After creating any table, verify it is an actual table object. See xml-reference.md for verification methods.
Anti-Pattern 3: Inheriting Placeholder Contrast
What happens: Placeholder uses light text on colored background (e.g., white on yellow). Model populates data but keeps this color scheme, resulting in hard-to-read output.
Why it's wrong: Placeholder colors are deliberately distinct to signal "replace me." Production slides typically use dark text on light backgrounds for body content.
Recognition test: If your populated content has light/white text on bright colored backgrounds in body areas (not headers), you've inherited placeholder formatting.
Correct approach: Apply production formatting — typically dark text (#000000 or #333333) on white or light backgrounds for body content. Headers and accent areas may use brand colors.
Summary: Placeholder vs. Production
| Element | Placeholder (Input) | Production (Output) |
|---|---|---|
| Instruction boxes | Colored background, guidance text | Removed or reformatted |
| Data areas | "[Insert data here]" text | Actual data with clean formatting |
| Tables | Description of what table should contain | Actual table object with rows/columns |
| Body text | Light text on colored background | Dark text on light background |
The placeholder tells you WHAT to create, not HOW to format it.
Common Failures
For detailed explanations of the most critical failures, see Critical Anti-Patterns above.
| Failure | Solution | Reference |
|---|---|---|
| Unstructured text dumps | Break into bullets (✓, ×, •) | formatting-standards.md |
| Pipe/tab-separated "tables" | Create actual table objects — text with separators is NOT a table | xml-reference.md |
| Poor text/background contrast | Audit every text element | — |
| Tiny pasted charts | Resize to fill area, paste chart only | formatting-standards.md |
| Source data pasted with charts | Select only chart object before copy | — |
| Data dumped into placeholder boxes | Delete colored instruction boxes, create new properly formatted content | Anti-Patterns |
| Inconsistent bullets | Define style once, apply to all | formatting-standards.md |
| Inconsistent fonts across boxes | Standardize same-level boxes | formatting-standards.md |
| Content overflow | Set explicit box widths (footnotes: 32.5cm for 16:9, 24cm for 4:3) | — |
| Missing logo | Use logo from task files; if not provided, flag to user | — |
Remaining [brackets] | Search and replace all placeholders | — |
| Text arrows (→, ⟹) | Use PowerPoint shape objects | xml-reference.md |
Error Handling
If PDF/image conversion fails:
Check LibreOffice is installed:
which sofficeTry alternative:
libreoffice --headless --convert-to pdf presentation.pptxIf still failing, open in PowerPoint/LibreOffice manually and export
If source data has inconsistencies or conflicts:
Priority order: Use data explicitly provided in the task files first
If using data from other sources (web search, external documents), flag this to the user
Document any discrepancies explicitly
Add footnote explaining data source choice
If calculations don't match source projections:
Show your calculation methodology
Note the discrepancy and possible causes (different base year, methodology)
Present both values if material difference
Flag to user for resolution
Table Structure Guidelines
When creating tables (MUST be actual table objects):
Column Alignment:
Text columns: Left-aligned (header and content)
Numeric columns: Right-aligned or center-aligned (header matches content)
Header Row:
Bold text
Shaded background (template's brand color)
White or contrasting text
Consensus/Total Row:
Bold text
Separator line above
Distinct background shading
Width: Fill designated section width completely.
For XML implementation, see xml-reference.md.
Footnote Format
Format:
Sources: [Source 1] (Year), [Source 2] (Year).
Notes: (1) [First note]; (2) [Second note].Example:
Sources: Grand View Research (2024), Mordor Intelligence (2024), Markets and Markets (2023).
Notes: (1) Excludes hardware revenue; (2) Includes both B2B and B2C segments.All superscript numbers (¹, ², ³) in slide body MUST have corresponding Notes entries.
Logo Placement
Use logo file provided in task materials
If no logo provided, flag to user: "[LOGO NOT PROVIDED - please supply company logo]"
Position: typically top-right, consistent size across slides, must not overlap content
Data Requirements by Slide Type
For detailed data requirements, formatting principles, and example column headers for each slide type, see slide-templates.md.
Common slide types covered: Market Definition, Market Sizing/TAM, Competitive Landscape, Financial Summary, Transaction Comparables.
Final Quality Checklist
Before delivering the populated template, verify:
Data Accuracy
[ ] All figures match original source documents
[ ] Calculated values verified against formulas (see
calculation-standards.md)[ ] Years and time periods are correct
[ ] Company/competitor names spelled correctly
[ ] Same figures are identical across all slides where they appear
Content Mapping
[ ] Every template section populated with appropriate data
[ ] No
[bracket]placeholder text remaining[ ] All source citations included in footnotes
[ ] Footnote numbers (¹²³) have corresponding Notes entries
Formatting
[ ] Text readable against all backgrounds (sufficient contrast)
[ ] Tables are actual table objects (NOT pipe/tab-separated text)
[ ] Charts/tables fill designated areas (no thumbnails)
[ ] Bullet formatting consistent within each section
[ ] Font sizes match across same-level boxes
[ ] No content extends beyond slide boundaries
[ ] No placeholder boxes retained with data dumped inside
[ ] No colored instruction boxes in final output
Template Compliance
[ ] Placeholder instruction boxes reformatted or removed
[ ] Formatting matches template style (colors, fonts)
[ ] Logo present and correctly positioned
[ ] Production formatting applied (dark text on light background for main content)
Final Step
[ ] Recommend user validate in Microsoft PowerPoint before distribution (LibreOffice may render differently)
Files
- ATTRIBUTION.mdAdded by AutoGineer912 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md19.1 KiB
- reference/calculation-standards.md5.3 KiB
- reference/formatting-standards.md8.4 KiB
- reference/slide-templates.md11.0 KiB
- reference/xml-reference.md10.8 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Written for: Claude Code, Claude apps
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Anthropic
- Publisher
- Anthropic (Official)
- Source
- anthropics/financial-services · plugins/agent-plugins/pitch-agent/skills/pitch-deck · commit 6056506
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Also distributed in
- anthropics/financial-services
AutoGineer is not affiliated with or endorsed by Anthropic or Anthropic.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download pitch-deck.zip