Skill Market

pptx author

Build PowerPoint decks headless with python-pptx. Pairs with excel-author for model-backed decks where every number traces to a workbook cell. Use for pitch decks, IC memos, earnings notes.

GitHub
githubcommunityaiai-agentai-agentsanthropicchatgptclaude
0.0
0 installs245.9K GitHub starsby NousResearch

Skill Introduction

Overview
Build PowerPoint decks headless with python-pptx. Pairs with excel-author for model-backed decks where every number traces to a workbook cell. Use for pitch decks, IC memos, earnings notes.

Core value

Turns reusable Debugging know-how into an installable skill, helping users complete github, community, ai, ai-agent work faster.

Target users

  • Developers, testers, and maintainers who handle Debugging tasks in Focus Code.
  • Teams that already trust workflows or content from NousResearch.
  • Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

  • Read the skill content first to confirm required inputs, expected outputs, and dependencies.
  • Try it on a small task before relying on it for critical work.
  • Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
  • For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

  • Tasks related to github, community, ai, ai-agent that need a reusable execution flow.
  • Converting a community repo, team convention, or personal workflow into day-to-day assistance.
  • Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

  • Results depend on the quality of the original skill content and may need human correction.
  • It does not replace code review, tests, security review, or professional judgment.
  • External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

  • Structured around Debugging, making it easier to discover and reuse than loose prompt snippets.
  • Marked as GitHub, which helps users judge trust and maintenance expectations.
  • Keeps the original source link available for repository, documentation, or discussion follow-up.
  • Tagged with github, community, ai, ai-agent, so it can be filtered by concrete task intent.

Install and use

Install
Copy Install Command
focus install pptx-author-8fbab5
View source

Detail Preview

SKILL.md

Primary filemarkdown7 KB

name: pptx-author description: Build PowerPoint decks headless with python-pptx. Pairs with excel-author for model-backed decks where every number traces to a workbook cell. Use for pitch decks, IC memos, earnings notes. version: 1.0.0 author: Anthropic (adapted by Nous Research) license: Apache-2.0 platforms: [linux, macos, windows] metadata: hermes: tags: [powerpoint, pptx, python-pptx, presentation, finance] related_skills: [excel-author, powerpoint]

pptx-author

Produce a .pptx file on disk using python-pptx. Use when you need to deliver a deck as a file artifact, not drive a live PowerPoint session.

Adapted from Anthropic's pptx-author and pitch-deck skills in anthropics/financial-services. The MCP / Office-JS branches of the originals are dropped — this assumes headless Python.

For the broader, already-shipped PowerPoint authoring skill (slides, speaker notes, embeds, media), see the built-in powerpoint skill. This skill is a lighter-weight pattern tuned for model-backed decks (pitch decks, IC memos, earnings notes) where every number must trace to a source workbook.

Output contract

  • Write to ./out/<name>.pptx. Create ./out/ if it does not exist.
  • Return the relative path in your final message.

Setup

pip install "python-pptx>=0.6"

Core conventions

One idea per slide

Title states the takeaway; body supports it. A slide titled "Q3 Revenue" is weak; "Revenue growth accelerated to 14% Y/Y in Q3" is strong.

Every number traces to the model

If a figure on a slide came from ./out/model.xlsx, footnote the sheet and cell.

Revenue: $1,250M  (Source: model.xlsx, Inputs!C3)

Never transcribe numbers from memory or from a summary — open the workbook, read the named range, and bind the deck value to it programmatically when you can.

Use the firm template when one is mounted

If ./templates/firm-template.pptx exists, load it so the deck inherits branded colors, fonts, and master layouts.

from pptx import Presentation
from pathlib import Path

template = Path("./templates/firm-template.pptx")
prs = Presentation(str(template)) if template.exists() else Presentation()

Charts: PNG-from-model beats native pptx charts

When fidelity matters (the model's chart styling must match the deck exactly), render the chart to PNG from the source workbook and embed the image. Native pptx.chart charts are fragile and often don't match firm conventions.

from pptx.util import Inches
slide.shapes.add_picture("./out/charts/football_field.png",
                         Inches(1), Inches(2),
                         width=Inches(8))

No external sends

This skill writes a file. It never emails, uploads, or posts. Orchestration layers handle delivery.

Skeleton

from pptx import Presentation
from pptx.util import Inches, Pt
from pptx.dml.color import RGBColor
from pathlib import Path

template = Path("./templates/firm-template.pptx")
prs = Presentation(str(template)) if template.exists() else Presentation()

# Title slide
slide = prs.slides.add_slide(prs.slide_layouts[0])
slide.shapes.title.text = "Project Aurora — Strategic Alternatives"
slide.placeholders[1].text = "Preliminary Discussion Materials"

# Valuation summary slide (title-only layout)
slide = prs.slides.add_slide(prs.slide_layouts[5])
slide.shapes.title.text = "Valuation implies $38–$52 per share across methodologies"

# Add a table bound to model outputs
rows, cols = 5, 4
tbl_shape = slide.shapes.add_table(rows, cols,
                                   Inches(0.5), Inches(1.5),
                                   Inches(9), Inches(3))
tbl = tbl_shape.table
headers = ["Methodology", "Low ($)", "Mid ($)", "High ($)"]
for c, h in enumerate(headers):
    tbl.cell(0, c).text = h

# In a real deck, read these from the model workbook with openpyxl
data = [
    ("Trading comps",     "35", "41", "48"),
    ("Precedent M&A",     "39", "45", "52"),
    ("DCF (base)",        "36", "43", "51"),
    ("LBO (10% IRR)",     "33", "38", "44"),
]
for r, row in enumerate(data, start=1):
    for c, val in enumerate(row):
        tbl.cell(r, c).text = val

# Embed a chart rendered from the model
slide = prs.slides.add_slide(prs.slide_layouts[5])
slide.shapes.title.text = "Football field — current price $42"
slide.shapes.add_picture("./out/charts/football_field.png",
                         Inches(1), Inches(1.8), width=Inches(8))

Path("./out").mkdir(exist_ok=True)
prs.save("./out/pitch-aurora.pptx")

Binding deck numbers to the source workbook

Read named ranges or specific cells from your Excel model so deck numbers never drift.

from openpyxl import load_workbook

wb = load_workbook("./out/model.xlsx", data_only=True)
def nr(name):
    """Resolve a named range to its current computed value."""
    rng = wb.defined_names[name]
    sheet, coord = next(rng.destinations)
    return wb[sheet][coord].value

revenue_fy24 = nr("RevenueFY24")
implied_mid  = nr("ImpliedSharePriceBase")

Then build deck content using those values:

slide.shapes.title.text = f"Implied share price of ${implied_mid:.2f} (base case)"

Remember to recalculate the workbook before reading it — openpyxl only sees computed values if something has already calculated the sheet. Run the recalc helper in the excel-author skill first, or open/save through a real Excel session.

Slide-type checklist for pitch decks

A typical banking pitch deck follows this structure. Not prescriptive, but useful as a starting skeleton:

  1. Cover / title
  2. Disclaimer
  3. Table of contents
  4. Situation overview
  5. Company snapshot (the target)
  6. Market / sector context
  7. Valuation summary (football field) — the money slide
  8. Trading comps detail
  9. Precedent transactions detail
  10. DCF summary
  11. Illustrative LBO / sponsor case
  12. Process considerations
  13. Appendix

When NOT to use this skill

  • Users in a live PowerPoint session with an Office MCP available — drive their live doc instead.
  • Non-financial slideware (quarterly all-hands, marketing decks) — use the broader powerpoint skill.
  • Decks with heavy animation, transitions, or speaker notes — use the broader powerpoint skill.

Attribution

Conventions adapted from Anthropic's Claude for Financial Services plugin suite, Apache-2.0 licensed. Original: https://github.com/anthropics/financial-services/tree/main/plugins/agent-plugins/pitch-agent/skills/pptx-author

Reviews

Overall rating

0.0
0.0

0 comments

No reviews yet