endueendue

Presentation (PPTX)

endue default skill for PowerPoint output: how to plan, structure and write a clear slide deck with save_presentation.

v1.0.0

What this skill does

The full instructions your agent follows. Nothing here is hidden behind sign-in.

Presentation (PPTX)

How to build a slide deck with save_presentation. Write every slide in the user's language.

Before you write

  • Work out the audience, the goal of the deck and the one thing they should remember. If the request leaves these open, infer them from the conversation instead of asking.
  • Length: follow the user. With no length given, aim for 8-12 slides; a quick update can be 3-5.
  • Use only facts from the conversation, tool results and files you read. Never invent numbers, names or quotes. If a figure is missing, mark it "TBD" or leave it out.

Structure

  1. Title slide: every deck opens with one. title + subtitle only (date, team or a one-line summary); no bullets, table or chart on it.
  2. Summary: the conclusion and the 3 points that support it, before any detail.
  3. Body: one slide per point, in the order the story needs. When the deck has several parts, open each part with a slide that has only title + subtitle.
  4. Close: the decision, recommendation or next steps, with owners and dates when known.
  5. Sources: a last slide listing where the data came from, if you used any.

Each slide

  • One message per slide, and the title is that message: a full sentence with the key number when there is one.
    • Bad: "Monthly revenue", "Customer metrics", "Q4 plan".
    • Good: "Revenue grew every month, reaching 150M in September", "Churn fell from 4.2% to 3.1%", "We will raise online ad spend by 20% in Q4".
    • Before saving, check every content slide's title against this rule.
  • 3-5 bullets, each one line (about 60 characters or less). Write phrases, not paragraphs. Indent a sub point with two leading spaces only when it belongs under the point above; never go deeper than one level.
  • Put what the presenter would say in notes, not on the slide.
  • Numbers go in a chart or a table, not in a long bullet:
    • comparing items: chart.type "bar"
    • change over time: "line"
    • share of a whole with 5 slices or fewer: "pie" with exactly one series
    • several items by several attributes: table (up to 20 rows by 8 columns; split a longer table across slides)
  • categories and every series' values have the same length. Put units in the slide title or the series name ("Revenue (USD M)").
  • One body per slide, two at most: bullets with a chart, or bullets with a table. They are placed side by side.
  • Never show the same numbers twice on a slide. Pick the chart for trends and comparisons, the table for exact values.
  • One chart shows one unit. Don't put counts and percentages in the same chart; use two slides or put one of them in bullets.
  • Leave out fields you don't use instead of sending empty strings or empty arrays.

Saving

  • Call save_presentation once with the whole deck: a path under /decks/ ending in .pptx, a deck title and a one-line description.
  • theme: "light" unless the user asks for dark.
  • To revise, call save_presentation again with the same path and the complete updated slides.

Your reply

Two or three lines: how many slides and what the deck covers. Don't paste the slide text into the chat.

Start for free

After signing up, add Presentation (PPTX) to your agent in one click.

More skills