fsi-fa-ppt-template-creator
Skill16 starsChanged 9 months agoApache-2.0View on GitHub
Creates self-contained PPT template SKILLS (not presentations) from user-provided PowerPoint templates. Use ONLY when a user wants to create a reusable skill from their template. For creating actual presentations, use the pptx skill instead.
In this repository99 other files it gives its agents.
- fsi-comps-analysisSkill
- fsi-er-catalyst-calendarSkill
- fsi-er-cmd-catalystsSkill
- fsi-er-cmd-earnings-previewSkill
- fsi-er-cmd-earningsSkill
- fsi-er-cmd-initiateSkill
- fsi-er-cmd-model-updateSkill
- fsi-er-cmd-morning-noteSkill
- fsi-er-cmd-screenSkill
- fsi-er-cmd-sectorSkill
- fsi-er-cmd-thesisSkill
- fsi-er-earnings-analysisSkill
- fsi-er-earnings-previewSkill
- fsi-er-idea-generationSkill
- fsi-er-initiating-coverageSkill
- fsi-er-model-updateSkill
- fsi-er-morning-noteSkill
- fsi-er-sector-overviewSkill
- fsi-er-thesis-trackerSkill
- fsi-fa-3-statementsSkill
- fsi-fa-check-deckSkill
- fsi-fa-check-modelSkill
- fsi-fa-cmd-3-statementsSkill
- fsi-fa-cmd-check-deckSkill
- fsi-fa-cmd-competitive-analysisSkill
- fsi-fa-cmd-compsSkill
- fsi-fa-cmd-dcfSkill
- fsi-fa-cmd-debug-modelSkill
- fsi-fa-cmd-lboSkill
- fsi-fa-cmd-ppt-templateSkill
- fsi-fa-competitive-analysisSkill
- fsi-fa-dcf-modelSkill
- fsi-fa-lbo-modelSkill
- fsi-fa-skill-creatorSkill
- fsi-ib-buyer-listSkill
- fsi-ib-cim-builderSkill
- fsi-ib-cmd-buyer-listSkill
- fsi-ib-cmd-cimSkill
- fsi-ib-cmd-deal-trackerSkill
- fsi-ib-cmd-merger-modelSkill
- fsi-ib-cmd-one-pagerSkill
- fsi-ib-cmd-process-letterSkill
- fsi-ib-cmd-teaserSkill
- fsi-ib-datapack-builderSkill
- fsi-ib-deal-trackerSkill
- fsi-ib-merger-modelSkill
- fsi-ib-pitch-deckSkill
- fsi-ib-process-letterSkill
- fsi-ib-teaserSkill
- fsi-lseg-bond-futures-basisSkill
- fsi-lseg-bond-relative-valueSkill
- fsi-lseg-cmd-analyze-bond-basisSkill
- fsi-lseg-cmd-analyze-bond-rvSkill
- fsi-lseg-cmd-analyze-fx-carrySkill
- fsi-lseg-cmd-analyze-option-volSkill
- fsi-lseg-cmd-analyze-swap-curveSkill
- fsi-lseg-cmd-macro-ratesSkill
- fsi-lseg-cmd-research-equitySkill
- fsi-lseg-cmd-review-fi-portfolioSkill
- fsi-lseg-equity-researchSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 2 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
This skill creates SKILLS, not presentations: Use this when a user wants to turn their PowerPoint template into a reusable skill that can …
- Very specific: line 22
Initialize skill: - use the skill-creator skill to set up the skill structure
- Very specific: line 24
Write SKILL.md: - follow template below with PPT-specific details
- Very specific: line 26
Package: - use the skill-creator skill to package into a .skill file
- Very specific: line 66
Best approach: Look at Layout 2 or similar "content" layouts that have an OBJECT placeholder - this placeholder's y position indicates …
- Very specific: line 86
Use the OBJECT placeholder's y position as your content start, not the subtitle's end position.
- Distinctive: line 252
Template in assets/: - always bundle the .pptx file
- Very specific: line 253
Self-contained SKILL.md: - all instructions embedded, no external references
- Very specific: line 254
No manual bullets: - use paragraph.level for hierarchy
- Distinctive: line 255
Delete slides first: - always clear existing slides before adding new ones
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PPT Template Creator
This skill creates SKILLS, not presentations. Use this when a user wants to turn their PowerPoint template into a reusable skill that can generate presentations later. If the user just wants to create a presentation, use the pptx skill instead.
The generated skill includes:
assets/template.pptx- the template fileSKILL.md- complete instructions (no reference to this meta skill needed)
For general skill-building best practices, refer to the skill-creator skill. This skill focuses on PPT-specific patterns.
Workflow
- User provides template (.pptx or .potx)
- Analyze template - extract layouts, placeholders, dimensions
- Initialize skill - use the
skill-creatorskill to set up the skill structure - Add template - copy .pptx to
assets/template.pptx - Write SKILL.md - follow template below with PPT-specific details
- Create example - generate sample presentation to validate
- Package - use the
skill-creatorskill to package into a .skill file
Step 2: Analyze Template
CRITICAL: Extract precise placeholder positions - this determines content area boundaries.
from pptx import Presentation
prs = Presentation(template_path)
print(f"Dimensions: {prs.slide_width/914400:.2f}\" x {prs.slide_height/914400:.2f}\"")
print(f"Layouts: {len(prs.slide_layouts)}")
for idx, layout in enumerate(prs.slide_layouts):
print(f"\n[{idx}] {layout.name}:")
for ph in layout.placeholders:
try:
ph_idx = ph.placeholder_format.idx
ph_type = ph.placeholder_format.type
# IMPORTANT: Extract exact positions in inches
left = ph.left / 914400
top = ph.top / 914400
width = ph.width / 914400
height = ph.height / 914400
print(f" idx={ph_idx}, type={ph_type}")
print(f" x={left:.2f}\", y={top:.2f}\", w={width:.2f}\", h={height:.2f}\"")
except:
passKey measurements to document:
- Title position: Where does the title placeholder sit?
- Subtitle/description: Where is the subtitle line?
- Footer placeholders: Where do footers/sources appear?
- Content area: The space BETWEEN subtitle and footer is your content area
Finding the True Content Start Position
CRITICAL: The content area does NOT always start immediately after the subtitle placeholder. Many templates have a visual border, line, or reserved space between the subtitle and content area.
Best approach: Look at Layout 2 or similar "content" layouts that have an OBJECT placeholder - this placeholder's y position indicates where content should actually start.
# Find the OBJECT placeholder to determine true content start
for idx, layout in enumerate(prs.slide_layouts):
for ph in layout.placeholders:
try:
if ph.placeholder_format.type == 7: # OBJECT type
top = ph.top / 914400
print(f"Layout [{idx}] {layout.name}: OBJECT starts at y={top:.2f}\"")
# This y value is where your content should start!
except:
passExample: A template might have:
- Subtitle ending at y=1.38"
- But OBJECT placeholder starting at y=1.90"
- The gap (0.52") is reserved for a border/line - do not place content there
Use the OBJECT placeholder's y position as your content start, not the subtitle's end position.
Step 5: Write SKILL.md
The generated skill should have this structure:
[company]-ppt-template/
├── SKILL.md
└── assets/
└── template.pptxGenerated SKILL.md Template
The generated SKILL.md must be self-contained with all instructions embedded. Use this template, filling in the bracketed values from your analysis:
---
name: [company]-ppt-template
description: [Company] PowerPoint template for creating presentations. Use when creating [Company]-branded pitch decks, board materials, or client presentations.
---
# [Company] PPT Template
Template: `assets/template.pptx` ([WIDTH]" x [HEIGHT]", [N] layouts)
## Creating Presentations
```python
from pptx import Presentation
prs = Presentation("path/to/skill/assets/template.pptx")
# DELETE all existing slides first
while len(prs.slides) > 0:
rId = prs.slides._sldIdLst[0].rId
prs.part.drop_rel(rId)
del prs.slides._sldIdLst[0]
# Add slides from layouts
slide = prs.slides.add_slide(prs.slide_layouts[LAYOUT_IDX])
```
## Key Layouts
| Index | Name | Use For |
|-------|------|---------|
| [0] | [Layout Name] | [Cover/title slide] |
| [N] | [Layout Name] | [Content with bullets] |
| [N] | [Layout Name] | [Two-column layout] |
## Placeholder Mapping
**CRITICAL: Include exact positions (x, y coordinates) for each placeholder.**
### Layout [N]: [Name]
| idx | Type | Position | Use |
|-----|------|----------|-----|
| [idx] | TITLE (1) | y=[Y]" | Slide title |
| [idx] | BODY (2) | y=[Y]" | Subtitle/description |
| [idx] | BODY (2) | y=[Y]" | Footer |
| [idx] | BODY (2) | y=[Y]" | Source/notes |
### Content Area Boundaries
**Document the safe content area for custom shapes/tables/charts:**
```
Content Area (for Layout [N]):
- Left margin: [X]" (content starts here)
- Top: [Y]" (below subtitle placeholder)
- Width: [W]"
- Height: [H]" (ends before footer)
For 4-quadrant layouts:
- Left column: x=[X]", width=[W]"
- Right column: x=[X]", width=[W]"
- Top row: y=[Y]", height=[H]"
- Bottom row: y=[Y]", height=[H]"
```
**Why this matters:** Custom content (textboxes, tables, charts) must stay within these boundaries to avoid overlapping with template placeholders like titles, footers, and source lines.
## Filling Content
**Do NOT add manual bullet characters** - slide master handles formatting.
```python
# Fill title
for shape in slide.shapes:
if hasattr(shape, 'placeholder_format'):
if shape.placeholder_format.type == 1: # TITLE
shape.text = "Slide Title"
# Fill content with hierarchy (level 0 = header, level 1 = bullet)
for shape in slide.shapes:
if hasattr(shape, 'placeholder_format'):
idx = shape.placeholder_format.idx
if idx == [CONTENT_IDX]:
tf = shape.text_frame
for para in tf.paragraphs:
para.clear()
content = [
("Section Header", 0),
("First bullet point", 1),
("Second bullet point", 1),
]
tf.paragraphs[0].text = content[0][0]
tf.paragraphs[0].level = content[0][1]
for text, level in content[1:]:
p = tf.add_paragraph()
p.text = text
p.level = level
```
## Example: Cover Slide
```python
slide = prs.slides.add_slide(prs.slide_layouts[[COVER_IDX]])
for shape in slide.shapes:
if hasattr(shape, 'placeholder_format'):
idx = shape.placeholder_format.idx
if idx == [TITLE_IDX]:
shape.text = "Company Name"
elif idx == [SUBTITLE_IDX]:
shape.text = "Presentation Title | Date"
```
## Example: Content Slide
```python
slide = prs.slides.add_slide(prs.slide_layouts[[CONTENT_IDX]])
for shape in slide.shapes:
if hasattr(shape, 'placeholder_format'):
ph_type = shape.placeholder_format.type
idx = shape.placeholder_format.idx
if ph_type == 1:
shape.text = "Executive Summary"
elif idx == [BODY_IDX]:
tf = shape.text_frame
for para in tf.paragraphs:
para.clear()
content = [
("Key Findings", 0),
("Revenue grew 40% YoY to $50M", 1),
("Expanded to 3 new markets", 1),
("Recommendation", 0),
("Proceed with strategic initiative", 1),
]
tf.paragraphs[0].text = content[0][0]
tf.paragraphs[0].level = content[0][1]
for text, level in content[1:]:
p = tf.add_paragraph()
p.text = text
p.level = level
```Step 6: Create Example Output
Generate a sample presentation to validate the skill works. Save it alongside the skill for reference.
PPT-Specific Rules for Generated Skills
- Template in assets/ - always bundle the .pptx file
- Self-contained SKILL.md - all instructions embedded, no external references
- No manual bullets - use
paragraph.levelfor hierarchy - Delete slides first - always clear existing slides before adding new ones
- Document placeholders by idx - placeholder idx values are template-specific
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

