Skip to content
TrustedSkillsbeta
Back to all skills

Gws Workflow Standup Report

Checked
googleworkspace·vlatest·productivity·Apache-2.0

Automatically generates concise daily stand-up reports summarizing Google Workspace activity and team progress.

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-workflow-standup-report -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-workflow-standup-report/SKILL.md
Scanned
1 file, 44 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-workflow-standup-report skill automates daily standup reporting within Google Workspace environments. It extracts relevant status updates, blockers, and progress metrics from connected workflows to generate concise team summaries. This capability streamlines morning meetings by reducing manual data gathering and ensuring consistent reporting formats across the organization.

When to use it

  • Automate daily syncs for distributed engineering teams using Jira or similar tools integrated with Google Workspace.
  • Generate pre-meeting digests that highlight critical blockers before a standup begins.
  • Standardize status reporting across multiple projects without requiring manual entry from team members.
  • Archive historical standup data directly into Google Docs or Sheets for trend analysis.

Key capabilities

  • Connects to existing workflow tools (e.g., Jira, Asana) via Google Workspace integrations.
  • Aggregates task status, completion percentages, and assignee information automatically.
  • Formats output into readable summaries suitable for chat channels or email distribution.
  • Supports scheduled execution to trigger reports at specific times daily.

Example prompts

  • "Generate today's standup report for the frontend team using data from our Jira board."
  • "Create a summary of all open blockers across active projects and send it to the channel."
  • "Pull progress updates for sprint 42 tasks and format them as a bulleted list in Google Docs."

Tips & gotchas

Ensure your workflow tools are properly authenticated with Google Workspace permissions before scheduling automated reports. Limit report frequency to once per day to avoid overwhelming team channels with redundant data.