google-slides-presentations

by hith3sh

Install this Skill

curl -fsSL -o google-slides-presentations.zip https://skill.seembox.com/api/v1/skills/google-slides-presentations/download && unzip google-slides-presentations.zip

Download google-slides-presentations.zip

SKILL.md About

---
name: google-slides-presentations
description: Work with presentations, slides, decks, and Google Slides content workflows — powered by ClawLink.
---

# Google Slides via ClawLink

Work with Google Slides from chat — inspect presentations, create or update slide content, and coordinate deck workflows.

Powered by [ClawLink](https://claw-link.dev), an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Google Slides API access yourself.

## Quick start

1. Install the verified ClawLink plugin: `openclaw plugins install clawhub:clawlink-plugin`
2. Start a fresh OpenClaw chat if the plugin was just installed and ClawLink tools are not visible yet
3. If ClawLink is not configured, call `clawlink_begin_pairing`
4. Tell the user to open the returned pairing URL, sign in to ClawLink if needed, and approve the device
5. After the user confirms approval, call `clawlink_get_pairing_status`
6. Tell the user to connect Google Slides at [claw-link.dev/dashboard?add=google-slides](https://claw-link.dev/dashboard?add=google-slides)
7. When the user confirms Google Slides is connected, call `clawlink_list_integrations` and then `clawlink_list_tools` with the `google-slides` integration slug

## Setup details

### Installing the plugin

If the ClawLink plugin is not installed yet, tell the user to run:

```
openclaw plugins install clawhub:clawlink-plugin
```

If the current chat started before the plugin was installed and ClawLink tools are still unavailable, tell the user to start a fresh chat so OpenClaw reloads the plugin tool catalog.

### Pairing ClawLink

If ClawLink reports that the plugin is not configured, the plugin has not been paired with the user's ClawLink account yet.

1. Call `clawlink_begin_pairing`.
2. Tell the user to open the returned pairing URL in their browser.
3. The user signs in to ClawLink if needed and approves the OpenClaw device.
4. After the user confirms approval, call `clawlink_get_pairing_status` to finish local setup.

The resulting device credential is stored locally in OpenClaw's plugin config and is only sent to `claw-link.dev`. The user should not paste raw credentials into chat.

### Connecting Google Slides

Tell the user to open https://claw-link.dev/dashboard?add=google-slides and connect Google Slides there. The page opens the add-connection panel filtered to Google Slides. ClawLink's hosted page runs the hosted OAuth flow — the user signs in with Google and approves the requested access. When they confirm it is done, call `clawlink_list_integrations` to verify, then call `clawlink_list_tools` with integration `google-slides`.

## Using Google Slides tools

ClawLink provides tools dynamically based on what the user has connected. You do not need to know tool names or schemas in advance.

### Discovery

1. Call `clawlink_list_integrations` to confirm Google Slides is connected.
2. Call `clawlink_list_tools` with integration `google-slides`.
3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.
4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `google-slides`.
5. If no Google Slides tools appear, direct the user to https://claw-link.dev/dashboard?add=google-slides.

### Execution

1. Call `clawlink_describe_tool` before using an unfamiliar tool, before any write, or when the request is ambiguous.
2. Use the returned schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups`.
3. Prefer read, list, search, and get operations before writes.
4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first, then confirm with the user.
5. Execute with `clawlink_call_tool`.
6. If it fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.

## What you can do

Typical Google Slides tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog):

- Inspect presentations and slide structure
- Create or update slide content after confirmation
- Help manage decks and presentation workflows
- Review current presentation state before write actions
- Preview changes when the tool supports dry-run behavior
- Use live discovery for the current Google Slides tool catalog

## Rules

- Always use ClawLink tools for Google Slides. Do not ask the user for separate Google credentials.
- Do not claim a capability is missing without checking the live ClawLink catalog in the current turn.
- Do not invent slash commands or ask the user to paste raw credentials.
- Ask for confirmation before destructive, external-facing, or bulk write actions.
- If Google Slides is not connected, direct the user to https://claw-link.dev/dashboard?add=google-slides.
- Never echo or repeat the user's ClawLink credential.

## Resources

- ClawLink: https://claw-link.dev
- ClawLink Docs: https://docs.claw-link.dev/openclaw
- ClawLink Verification: https://claw-link.dev/verify
- ClawLink Source: https://github.com/hith3sh/clawlink
- Google Slides API: https://developers.google.com/slides

_meta.json Metadata

{
  "ownerId": "kn713pxvayh8fjhb503zjb8yxh815j54",
  "publishedAt": 1778095356365,
  "slug": "google-slides-presentations",
  "version": "0.1.0"
}