Gws Slides

What Is This?

Overview

Gws Slides is a command-line interface skill that enables developers and technical users to interact with Google Slides presentations directly from the terminal. Built on top of the gws CLI tool, this skill provides programmatic access to the Google Slides API, allowing users to read presentation data, write content, and perform batch updates without opening a browser or the Google Slides web application.

The skill is part of the broader Google Workspace CLI ecosystem, which means it shares authentication, global flags, and security conventions with other gws skills. Once authenticated, users can automate repetitive presentation tasks, integrate slide management into development pipelines, and build scripts that generate or modify presentations based on dynamic data sources.

For teams that produce regular reports, documentation, or client-facing materials, Gws Slides removes the manual overhead of updating presentations by hand. Instead of clicking through menus and editing slides one at a time, developers can write scripts that apply changes programmatically, making the process faster, more consistent, and easier to audit.

Who Should Use This

• Backend developers who need to generate presentation reports from application data or database outputs as part of automated workflows.
• DevOps engineers who want to include slide generation or updates as steps in CI/CD pipelines alongside deployment summaries or status reports.
• Data analysts who regularly produce slide decks from structured data and want to automate the formatting and population of content.

Why Use It?

Problems It Solves

• Manual presentation updates consume significant time when content changes frequently. Gws Slides allows scripts to apply updates automatically, reducing repetitive editing work.
• Inconsistent formatting across presentations created by different team members can be standardized by using shared scripts that apply the same structure and style programmatically.
• Lack of version control integration for presentations is addressed by enabling slide content to be generated from code, making changes trackable through standard source control tools.

Core Highlights

• Command-line access to the Google Slides API without requiring a browser session
• Support for batchUpdate operations to apply multiple changes in a single API call
• Consistent authentication and flag conventions shared across the gws CLI ecosystem
• Scriptable interface suitable for integration into shell scripts, Makefiles, and CI pipelines
• Lightweight interaction model using resource and method arguments
• Compatible with other gws skills for cross-product Google Workspace automation
• Accessible via a single binary dependency on the gws tool

How to Use It?

Basic Usage

The general command structure for Gws Slides follows the pattern below.

gws slides <resource> <method> [flags]

To view available options and flags for the slides skill, run the built-in help command.

gws slides --help

To perform a batch update on a presentation, use the presentations batchUpdate method with the required presentation ID and a request body.

gws slides presentations batchUpdate --presentation-id YOUR_PRESENTATION_ID --request body.json

Specific Scenarios

Scenario 1: Automated report generation. A developer writes a shell script that queries a database, formats the results into a JSON request body, and calls gws slides presentations batchUpdate to populate a slide template with the latest figures. This script runs nightly via a cron job.

Scenario 2: CI pipeline slide updates. After a deployment completes, a pipeline step calls gws slides presentations batchUpdate to update a status slide deck with the current build version, deployment time, and environment details.

Real-World Examples

A data team uses Gws Slides to refresh weekly metrics presentations by passing structured JSON payloads to the batchUpdate endpoint, replacing placeholder text with live figures pulled from their analytics platform.

An engineering team maintains a release notes presentation that is updated automatically on each merge to the main branch, using a script that reads the changelog and formats it into slide content.

When to Use It?

Use Cases

• Generating weekly or monthly status presentations from live data sources
• Applying bulk text replacements across large presentation files
• Updating slide decks as part of a post-deployment pipeline step
• Creating presentation templates programmatically from a base structure
• Synchronizing content between a data source and an existing slide deck
• Building internal tools that produce client-facing presentations on demand
• Automating the creation of onboarding or training materials from structured content

Important Notes

Requirements

• The gws binary must be installed and available in the system PATH before using this skill.
• Authentication must be configured according to the gws-shared prerequisites, which cover OAuth credentials and token management.
• A valid Google account with access to the target presentations is required for all read and write operations.
• The gws-shared skill documentation should be reviewed before use to understand global flags and security rules.