Skip to content
TrustedSkillsbeta
Back to all skills

Gws Keep

Checked
googleworkspace·vlatest·other·Apache-2.0

Gws Keep automatically archives inactive Google Workspace items like Drive files & emails, saving storage and simplifying cleanup.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add googleworkspace/cli --skill gws-keep -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

googleworkspace

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned googleworkspace/cli at a3768d0e82.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
a3768d0e82
Manifest
skills/gws-keep/SKILL.md
Scanned
1 file, 46 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The gws-keep skill enables AI agents to persist specific Google Workspace resources, such as Drive files or Calendar events, ensuring they remain accessible within the agent's operational context across different sessions. It acts as a memory mechanism for the googleworkspace/cli, allowing the agent to retain stateful data without manual re-entry.

When to use it

  • Session Continuity: Maintain access to critical documents or meeting schedules when an AI agent restarts or switches tasks.
  • Context Preservation: Ensure specific Google Drive files remain available for analysis during long-running multi-step workflows.
  • State Management: Prevent data loss in scenarios where the agent needs to reference previously processed information from Google Workspace services.

Key capabilities

  • Persists selected Google Workspace resources within the agent's active session.
  • Integrates directly with the googleworkspace/cli command-line interface.
  • Manages stateful data retention for Drive files and Calendar events.

Example prompts

  • "Use gws-keep to save this specific Drive file so I can reference it later in our project."
  • "Keep the current Google Calendar event details active while we schedule follow-up meetings."
  • "Persist these shared documents in my workspace context for the next analysis task."

Tips & gotchas

Ensure you have the necessary permissions to access and modify the specific Google Workspace resources you intend to keep. This skill is designed for state management within the CLI environment, so it may not function if the agent lacks direct command-line access to your Google Workspace account.