agentleFS
Sign inStart free
RylaispiritRylaispirit/rylai-codex-hermes-skills/skills/rylai-ppt/SKILL.md

rylai-ppt

Skill56 starsChanged 3 months agoMITView on GitHub

Create editable PowerPoint decks from a local JSON specification using Rylai's visual system, python-pptx, deterministic slide types, and optional rendering.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 8 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the bundled Python workflow to create a clean, editable .pptx.

    line 18
  2. Distinctive:

    Read the user's source material and identify the audience, purpose, slide count, language, and required facts.

    line 31
  3. Very specific:

    Create a JSON deck specification by adapting examples/deck.json.

    line 32
  4. Distinctive:

    Keep one message per slide.

    line 33
  5. Distinctive:

    Check clipping, contrast, reading order, repeated wording, and slide count before delivery.

    line 52
  6. Very specific:

    Read references/deck-spec.md when field-level constraints are needed.

    line 66
  7. Distinctive:

    Use the theme fields in the JSON spec rather than editing renderer constants for each deck.

    line 70
  8. Distinctive:

    Use a restrained multi-color palette with one primary accent and one secondary accent.

    line 71
  9. Distinctive:

    Keep titles short, body copy specific, and metrics attributable to the user's material.

    line 72
  10. Very specific:

    Use only the supported local vector icons: circle, square, diamond, check, and arrow.

    line 73
  11. Distinctive:

    Do not add remote URLs as image sources.

    line 74
  12. Distinctive:

    Write generated decks to the user's requested workspace, not inside the installed skill.

    line 81

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Rylai PPT

Use the bundled Python workflow to create a clean, editable .pptx. The renderer is an original Rylai implementation built on python-pptx. It uses local PowerPoint elements and does not load HTML templates, remote images, or hosted assets.

Requirements

  • Python 3
  • python-pptx
  • Optional LibreOffice for rendering to PDF

Workflow

  1. Read the user's source material and identify the audience, purpose, slide count, language, and required facts.
  2. Create a JSON deck specification by adapting examples/deck.json.
  3. Keep one message per slide. Split dense content instead of shrinking text.
  4. Validate the specification:
python <skill-dir>/scripts/build_deck.py build <deck.json> <output.pptx>
  1. Build the presentation:
python <skill-dir>/scripts/build_deck.py inspect <output.pptx>
  1. Render the result when LibreOffice is available:
python <skill-dir>/scripts/build_deck.py render <output.pptx> <render-dir>
  1. Check clipping, contrast, reading order, repeated wording, and slide count before delivery.

Slide Types

  • cover: title, subtitle, eyebrow, footer
  • section: number, title, summary
  • bullets: title, kicker, and two to six structured items
  • metrics: title and two to four value cards
  • comparison: two labeled lists with two to five items each
  • timeline: two to five ordered steps
  • quote: quotation and attribution
  • closing: final title, subtitle, and contact line

Read references/deck-spec.md when field-level constraints are needed. Unknown slide fields fail validation so the deck stays portable and deterministic.

Design Rules

  • Use the theme fields in the JSON spec rather than editing renderer constants for each deck.
  • Use a restrained multi-color palette with one primary accent and one secondary accent.
  • Keep titles short, body copy specific, and metrics attributable to the user's material.
  • Use only the supported local vector icons: circle, square, diamond, check, and arrow.
  • Do not add remote URLs as image sources. This workflow intentionally has no image field.
  • Preserve user-provided brand wording. Do not invent customer names, testimonials, statistics, or claims.

Runtime Notes

  • Codex, Hermes, and Claude execute the same bundled Python scripts.
  • Resolve all bundled paths from this skill directory.
  • Write generated decks to the user's requested workspace, not inside the installed skill.
  • Report the final path and the number and types of slides created.

Authored by Rylai for Codex, Hermes, and Claude.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free