E

Easy Gws Executor

Production-ready command that handles manage, google, groups, settings. Includes structured workflows, validation checks, and reusable patterns for google workspace.

CommandClipticsgoogle workspacev1.0.0MIT
0 views0 copies

Easy GWS Executor

Simplified Google Workspace command executor for common daily tasks with preset configurations.

When to Use This Command

Run this command when you need to:

  • Execute frequent Google Workspace tasks using shorthand presets instead of full configurations
  • Run common workflows like checking email, reviewing calendar, or searching Drive quickly
  • Perform daily administrative checks across multiple Workspace services in one command

Consider alternatives when:

  • You need full control over every parameter and the dedicated service commands offer more options
  • You are performing one-time complex operations that require custom API parameter tuning

Quick Start

Configuration

name: easy-gws-executor type: command category: google-workspace

Example Invocation

claude command:run easy-gws-executor --preset daily-summary

Example Output

Running daily summary preset...

Gmail:
  Unread: 14 messages
  Flagged: 3 messages requiring attention
  Top sender: [email protected] (6 messages)

Calendar:
  Today's events: 4
    9:00 AM  Team Standup (30 min)
   11:00 AM  Design Review (60 min)
    2:00 PM  Sprint Planning (90 min)
    4:30 PM  1:1 with Manager (30 min)
  Free time: 3.5 hours

Drive:
  Recent updates: 7 files modified in last 24h
  Shared with you: 2 new files
  Storage: 12.4 GB / 30 GB used (41%)

All services healthy. Have a productive day!

Core Concepts

Preset System Overview

AspectDetails
PresetsPre-configured command bundles for common daily tasks and workflows
ShortcutsSingle-word commands that expand to multi-service operations
CustomizationUser-defined presets stored in local configuration for personal workflows
SchedulingPresets can be scheduled to run at specific times via cron integration
OutputUnified formatted output combining results from multiple service calls

Executor Workflow

Select Preset
      |
      v
Expand to Service Calls
  |      |      |
  v      v      v
Gmail  Calendar Drive
  |      |      |
  v      v      v
Execute in Parallel
      |
      v
Merge Results
      |
      v
Format Summary

Configuration

ParameterTypeDefaultDescription
presetstring(required)Preset name: daily-summary, inbox-zero, weekly-report, cleanup
servicesstring[]allLimit execution to specific services within the preset
formatstringsummaryOutput format: summary, detailed, json
savestring(none)Save output to file for record keeping
customstring(none)Path to custom preset definition file

Best Practices

  1. Create personal presets - Define custom presets for your specific daily workflow. A developer might combine PR notifications, deployment calendar, and shared drive updates into one command.

  2. Run daily-summary first thing - Start each workday with the daily summary preset to get a quick overview of emails, meetings, and file updates without opening multiple browser tabs.

  3. Use the save parameter for records - When running weekly reports, save the output to a dated file for historical comparison and trend tracking over time.

  4. Combine with scheduling - Set up a cron job to run your daily summary preset every morning and pipe the output to Slack or email for zero-effort daily briefings.

Common Issues

  1. Preset execution slow with all services - If you only care about Gmail and Calendar, use the services parameter to skip Drive and other services for faster execution.

  2. Custom preset file not found - Custom preset definitions must be valid JSON or YAML files. Check the file path and validate the syntax with a linter before referencing it.

  3. Partial results when a service fails - If one service in the preset fails (e.g., Drive API timeout), the executor still returns results from other services with a warning about the failure. Review the warning output to determine whether the failed service needs manual attention.

  4. Preset output format inconsistent - Different services return data in different shapes, and the summary format normalizes them. If you need raw data for scripting, use --format json for consistent machine-parseable output across all service results.

  5. Daily summary takes too long - Large mailboxes and drive accounts can slow down the summary generation. Create a focused preset that only queries the most recent day of data and limits results to the top items rather than fetching comprehensive lists.

Community

Reviews

Write a review

No reviews yet. Be the first to review this template!

Similar Templates