More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    office-3-apps — brand templates for PowerPoint and Word

    1

    Writes the OOXML directly to build .potx and .dotx in your own brand — themes, masters, table styles, embedded fonts — then assembles the documents from them.

    Free

    Security scanned
    office-3-apps — brand templates for PowerPoint and Word

    office-3-apps — brand templates for PowerPoint and Word

    Example session with this skill installed

    We have no PowerPoint template. Every deck in the company looks different and people
    rebuild the title slide from scratch every time.

    Our brand: deep navy #12263A, a warm orange accent #E2773A, Inter for headings. Logo is
    in assets/logo.svg.

    Make us a template, and show me what a real deck out of it looks like.

    • Read your context and instructions
    • Compiled the office-3-apps
    • Generated the document

    Summary

    Built a .potx with 7 layouts and a .dotx to match, both carrying your palette and
    typeface, then assembled a 15-slide sample deck out of the template so you can see it
    behaving. Three things need your decision before this is final — listed at the end.

    What went into the theme

    SlotValueWhere it shows up
    Dark 1#12263ASection dividers, title slide, table headers
    Accent 1#E2773AOne highlighted element per slide — never two
    Accent 2–6derived rampChart series, in this order
    Heading fontInterEmbedded, so it survives being emailed

    The palette is set in the theme, not painted onto shapes. When someone opens the
    colour picker in PowerPoint, they see your colours, not Office defaults. That is the
    difference between a template and a styled file.

    The 7 layouts

    Title / Section / Agenda / Statement / Body / Body with figure / Closing.

    Seven, not twenty. Every layout you add is one more thing nobody picks correctly, and
    one more thing to maintain when the brand moves. If a slide does not fit these, that is
    usually a sign the slide is doing two jobs.

    Charts

    .venv/bin/python scripts/build_charts.py

    Produces report_charts.xlsx, and the same chart embedded in both PPTX and DOCX as a
    native chart. Your reader clicks a bar and sees the number. Change the figure in the
    workbook and re-run; the deck and the report both follow.

    Files

    build/your_brand.potx            template, 6.6MB with fonts embedded
build/your_brand.dotx            Word, same palette and type scale
build/your_brand_sample.pptx     15 slides, built from the template
build/your_brand_sample.docx     the same content as a report
build/charts/report_charts.xlsx  native chart source

    Open them before we go further

    I exported to PDF and checked the layout, but how this looks when you open it in
    PowerPoint is something only you can see     — your font environment, your view mode, any
    dialog that appears. Please open build/ and tell me what you find.

    Three decisions I left to you

    1. Section dividers are dark navy, full bleed. Light dividers are also defensible —
      it changes the rhythm of the deck. Your call.
    2. I used your orange only once per slide. This is a rule I would keep, but it is
      yours to drop.
    3. The sample content is invented. Replace it with a real deck you have already
      given, and we will see where the layouts actually strain.

    report_charts.xlsx

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    Every deck in your company looks slightly different. Not because anyone is careless — because there is nothing for them to start from. So each person opens the last file they made, deletes the content, and the template drifts one more step.

    The usual fix is to make a real template. Then you find out that the Python libraries cannot reach the parts that matter. python-pptx cannot set the theme palette, the slide master guides, the table styles or embedded fonts. You get a file that looks right until someone opens the colour picker and finds the default Office palette staring back.

    What this does

    An Office file is a ZIP with XML inside. So this writes the XML.

    Theme palette, slide master and layouts, guides, table styles, Word's full style tree, embedded fonts — all of it set directly, because all of it is just XML in a known place. Then the same agent assembles the actual deck or report from that template, so what ships is consistent by construction rather than by review.

    Charts are native and editable, not images. The person receiving your deck can click a bar and see the number. The same chart definition produces the Excel workbook, the PowerPoint chart and the Word chart, so the three never disagree.

    What is in here

    • PLAYBOOK.md — the whole process, written to be read by an agent. It opens with a section addressed to the agent, including which rules may not be changed and which decisions must be put back to you before work starts.
    • Working scripts — build_potx_figma.py, build_dotx.py, build_charts.py and the supporting tools for fonts, logos and text fitting.
    • notes/ — the traps, already hit and written down. OOXML basics, text layout, table styles, font embedding. Reading these first saves hours.
    • A design system as data — tokens.json holds the colours and type sizes. Replace that one file and every output changes.

    The part that is unusual

    PLAYBOOK marks every instruction with how much it binds you:

    MarkMeaning
    Do not changeChanging it breaks something or kills the effect
    Ask firstThe agent must ask you before proceeding
    Starting pointUsable, but meant to be replaced
    (unmarked)Default. The agent proceeds and tells you afterwards

    This exists because a handbook without reasons produces agents that follow it blindly into the wrong result. Anything written down here has to say why, or it is not a rule — it is just a default.

    Do not copy the sample design

    The included bigtree/ brand is there to show the mechanism working end to end. It is not a look to imitate. The skill is instructed to propose rebuilding it in your brand instead. The value here is being able to decide your own look, not inheriting this one.

    What you need

    Python 3.9+, plus fonttools and pillow. Static Noto Sans JP if you want fonts embedded (variable fonts cannot be embedded) — or pass --no-embed and skip it.

    Honest limits

    • Verified on macOS. The files open correctly in PowerPoint and Word there. Windows and Google Slides are untested.
    • The documentation is in Japanese. PLAYBOOK.md and the design notes. An agent reads them without any trouble — that is who they were written for — but a human skimming them will want a translator.
    • Embedding fonts makes each file about 6.6MB. That is the cost of the receiver seeing what you saw.
    • This does not design for you. It makes your design reproducible.

    MIT licensed. Source: https://github.com/bigtree1984/office_3_apps_with_claude

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 11 days ago

    • Free to download with an account

    Requires

    Python

    Listed11 days ago

    What's inside

    Frequently Asked Questions