Google Slides from Markdown

# Google Slides from Markdown

Turn an approved presentation outline into a Google Slides deck through <integration-tag>composio:googleslides_tools</integration-tag>.

## Inputs

Collect the topic, audience, objective, approximate slide count, language, source material, and preferred theme. Separate source-backed facts from proposed narrative. Ask for missing information only when it changes the deck structure or factual accuracy.

## Plan before creating

1. Write the one-sentence audience outcome.
2. Build a slide sequence with one message per slide.
3. Keep titles short and use no more than five primary bullets on a normal content slide.
4. Put evidence, units, dates, and source links next to the claims they support.
5. Use a table only when rows and columns communicate the comparison more clearly than prose.
6. Show the complete outline and selected live theme to the user before the write Action.

## Markdown contract

Inspect the live Action schema before preparing the final input. Use `---` on its own line between slides. Use the live schema's supported title, bullet, table, quote, image, and two-column syntax. Images must be public URLs accepted by the Action; omit images whose provenance or accessibility is uncertain.

Do not invent a theme name. At the time this Skill was authored, the Action documented these themes: `default`, `corporate_blue`, `modern_dark`, `professional_gray`, `creative_purple`, `warm_orange`, `forest_green`, and `minimal_beige`. Re-check the live schema because that set can change.

## Creation

After approval:

1. Call the Action once with `title` and `markdown_text`.
2. Treat `successful: false` or a populated error field as failure.
3. Report the returned presentation ID, slide count, and execution message.
4. If the provider skipped an invalid image or altered content, disclose that change.

Do not claim that this creates a local PPTX file. The output is a Google Slides presentation and requires the user's Google Slides connection.

## Attribution

This native Loadout re-authoring preserves the source package's presentation-planning and visual-consistency ideas while replacing local Python, generated slide images, and PPTX composition with one live Google Slides Action. See [UPSTREAM.md](UPSTREAM.md) and [LICENSE.txt](LICENSE.txt).