agentsclimarketplace

Google cloud slides

Skill williamtsoi1/google-cloud-slides-skill/skills/google-cloud-slides

Create slide decks with the visual style of the Google Cloud 2025 presentation template. Use for: generating professional, branded presentations with specific Google Cloud layouts, colors, and typography.From its SKILL.md

Install
npx -y skills add williamtsoi1/google-cloud-slides-skill --skill google-cloud-slides

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

8.7 KB, as published. Nobody here has run it

Google Cloud Slides Skill

This skill provides instructions and assets for creating slide decks that match the visual style of the Google Cloud 2025 presentation template.

Core Visual Style

When creating slides using this skill, always adhere to the following brand guidelines:

  • Brand name: Google Cloud
  • Slide frame: Every slide — including the cover and thank-you slides — must use the fixed-size .slide container (1280×720, 16:9) from CSS_SNIPPETS.md. The fixed height (not min-height) plus overflow: hidden is what forces the aspect ratio; never let a slide size itself to its content, or slides with the large logo will render off-ratio in both HTML and PDF.
  • Footer: Every slide must include "Google Cloud" in the bottom-left corner and "Proprietary & Confidential [page#]" in the bottom-right corner.
  • Font: Use Google Sans (or a clean, rounded, modern sans-serif fallback like Product Sans).
  • Primary text color: Near-black (#202124).

Color Palette

RoleHex CodeUsage
Background (light)#FFFFFFDefault slide background
Background (dark)#202124Dark-mode slides
Text (light bg)#202124Body and headings
Text (dark bg)#FFFFFFBody and headings on dark backgrounds
Google Blue#3186FFAccent, section dividers, chart fills, highlighted text
Google Red#FC413DAccent, section dividers
Google Yellow/Gold#FEC700Accent, section dividers
Google Green#00AF57Accent, section dividers

Key Decorative Elements

  1. Rainbow divider bar: A thin horizontal line graduating Red → Yellow → Green → Blue. Used as a section separator, sometimes partial-width (left-aligned or right-aligned). Use the bundled asset at templates/GC_Progress_Bar_Gradient_RGB.jpg as an <img> element. Do NOT recreate this bar using CSS gradients.
  2. Google Cloud icon: The official Google Cloud icon (multicolour cloud logo). Use the bundled asset at templates/gradient_super_cloud_512_2x.png — always find the absolute path of the image and reference it this way. Place it prominently on the right side of cover and thank-you slides. Do NOT recreate this with CSS arcs.
  3. Colored section backgrounds: Full-bleed solid backgrounds in Google Green (#00AF57), Google Blue (#3186FF), or Google Red (#FC413D) for section dividers.

Slide Layouts

The template supports a variety of layouts. When generating content, select the appropriate layout type from the catalog below.

For detailed descriptions of all available layouts, see LAYOUTS.md.

Common Layouts

  • Cover / Title: Large bold headline left, date below, Google Cloud wordmark logo top-left, official Google Cloud icon (templates/gradient_super_cloud_512_2x.png) large on the right side (400×400 px, object-fit: contain). Do NOT use CSS arcs as a substitute. Wrap the slide in the standard fixed-size .slide frame (see CSS_SNIPPETS.md) and give the logo the .logo class — the slide's fixed height is what keeps it 16:9; without it the large logo makes the slide grow off-ratio.
  • Section divider: Rainbow bar top, large section number (zero-padded, e.g., "01") + title.
  • Title + body (1-col): Slide title top-left, body text below.
  • 2-column text: Slide title, two equal text columns.
  • Stat / Big number: Large bold stat (e.g., "40%") in Google Blue, label below, supporting text.
  • Bullets: Title + bullet list (6–8 items max, no punctuation).
  • Big statement: Full-slide large text, first phrase in Google Blue, rest in dark.

Typography Rules

  • Bullets: Keep them clear and punchy. Use single lines when possible. Maximum 6–8 items per slide. Do not use punctuation at the end of bullet points.
  • Images: Images should help "do the heavy lifting." Keep copy concise and aligned with the image.
  • Section numbers: Always use zero-padded 2-digit numbers (01, 02, 03, etc.).
  • Chart subtitles: Use UPPERCASE text in Google Blue.

Usage Instructions

  1. Understand the Content: Review the content to be presented and determine the best layout for each slide.
  2. Select Layouts: Refer to LAYOUTS.md to choose the appropriate layout structure.
  3. Apply Styling: Ensure all colors, fonts, and decorative elements match the guidelines above.
  4. Generate Slides: Use the slides tool in html mode to generate the presentation, applying the necessary CSS to match the Google Cloud style.

Example CSS Snippets

For reference on how to implement the visual style in HTML/CSS, see CSS_SNIPPETS.md.

Exporting to PDF (CLI environments)

On Manus, the platform converts the generated deck to Google Slides / PDF / PPTX for you. When this skill runs from a CLI agent (Claude Code, Antigravity CLI, Gemini CLI) there is no built-in export — you must produce the PDF yourself using the bundled converter.

  1. Author the deck as a single self-contained HTML file. Put every slide in its own .slide section within one .html file, and include the Print / PDF export CSS from CSS_SNIPPETS.md (the @page size, the .slide page-break rules, and print-color-adjust: exact). This is what makes each slide map to exactly one PDF page with brand backgrounds intact. Do not put margins, gaps, borders, or shadows on .slide — they add to the printed box and spill each slide onto a second page. Scope any on-screen layout under @media screen and zero it under @media print (see CSS_SNIPPETS.md).

  2. Use absolute paths for the brand assets (templates/gradient_super_cloud_512_2x.png, templates/GC_Progress_Bar_Gradient_RGB.jpg) so they load during printing, as noted in CSS_SNIPPETS.md.

  3. Run the converter from the skill directory:

    bash scripts/html_to_pdf.sh deck.html deck.pdf
    

    Resolve the script's absolute path from the skill location when invoking it. The script renders with system Chrome/Chromium (--headless --print-to-pdf) when available, and falls back to Playwright otherwise.

  4. If neither is installed, the script exits with a clear message. Install Google Chrome, or set up Playwright once:

    uv run --with playwright playwright install chromium
    
  5. Verify the page count matches the slide count. A doubled count means a screen-only margin/shadow is leaking into print — fix the @media print reset before shipping.

    # macOS
    mdls -name kMDItemNumberOfPages deck.pdf
    # Linux (poppler-utils)
    pdfinfo deck.pdf | grep Pages
    

Exporting to Google Slides (editable, via PPTX)

When the user wants a native, editable Google Slides deck (not a flat PDF), produce a PowerPoint (.pptx) with the bundled builder and let the user convert it in Drive. This path needs no authentication — the upload is a manual step.

  1. Author a deck spec as JSON. Describe each slide as an object keyed by type (cover, section, bullets, stat, statement, two-tone, quote, thank-you, …). The full schema and supported slide types are in GSLIDES_SPEC.md; a complete example is in scripts/examples/sample_deck.json. You only supply content — the builder enforces the footer on every slide, zero-padded section numbers, the palette, and embeds the brand assets.

  2. Build the .pptx with the bundled script (resolve its absolute path from the skill location):

    bash scripts/build_gslides.sh deck.json deck.pptx
    

    It runs the Python builder with uv (auto-installs python-pptx) or a system python3 that has python-pptx importable.

  3. Tell the user to convert it in Drive. Upload deck.pptx to Google Drive, then either: open it and choose File → Save as Google Slides, or turn on Drive Settings → "Convert uploads to Google Docs editor format" before uploading. Drive converts the .pptx into a native, editable Slides deck.

Font note (important): the .pptx is built in Roboto, not Google Sans. Google Sans is proprietary, is not in the Google Slides font library, and Slides ignores fonts embedded in a .pptx on import — so an editable Slides deck cannot render real Google Sans. Roboto is Google's own typeface and the closest freely-available relative. Everything else (exact hex colors, layout, the embedded cloud logo and rainbow bar, all text and shapes) stays brand-accurate and fully editable. Use the PDF path above when you need real Google Sans rendering.

Keep looking

Skills are one crate of 609,689. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.