メニュー
Google Workspace CLI authentication and environment setup. Handles gws and gws-auth installation, OAuth login, and token injection. This skill is a shared dependency for gws-sheets, gws-gmail, and other gws-based skills.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | gws-auth |
| description | Google Workspace CLI authentication and environment setup. Handles gws and gws-auth installation, OAuth login, and token injection. This skill is a shared dependency for gws-sheets, gws-gmail, and other gws-based skills. |
| license | Apache-2.0 |
| metadata | {"author":"swen","version":"0.1"} |
| compatibility | Requires gws (@googleworkspace/cli) ≥0.22.3 and gws-auth (github:planetarium/gws-auth) ≥0.4.0 |
npm install -g @googleworkspace/cli https://github.com/planetarium/gws-auth/releases/download/v0.4.0/planetarium-gws-auth-0.4.0.tgz
Verify: gws --version && gws-auth --help
gws-auth is a dedicated OAuth CLI with embedded Client ID/Secret — no manual GCP credentials setup required.
gws-auth v0.4.0+ uses the authorization code flow (localhost redirect) which supports all Google Workspace scopes. Older versions (≤0.3.0) used the device code flow, which Google restricts to only 7 scopes (openid, email, profile, drive.appdata, drive.file, youtube, youtube.readonly). Gmail and Calendar scopes require v0.4.0+.
gws-auth status 2>/dev/null && echo "AUTH OK"
If not logged in, ask the user to run the login command (requires one-time Google OAuth consent in a browser — the agent cannot run this directly):
gws-auth login
Default scopes are spreadsheets and drive.file. To request additional scopes:
gws-auth login --scope gmail.modify --scope spreadsheets --scope drive.file
When re-logging in, include all desired scopes (existing scopes are not automatically retained).
export GOOGLE_WORKSPACE_CLI_TOKEN="$(gws-auth token)"
| Alias | Description |
|---|---|
spreadsheets | Google Sheets read/write (default) |
drive.file | Drive files created by the app (default) |
drive | Full Drive access |
drive.readonly | Drive read-only |
gmail.modify | Gmail read + write + label management |
gmail.readonly | Gmail read-only |
gmail.send | Gmail send-only |
calendar | Google Calendar read/write |
calendar.readonly | Google Calendar read-only |
docs | Google Docs read/write |
docs.readonly | Google Docs read-only |
Full list: gws-auth scopes
Combine independent gws calls into a single Bash call with ;. Export the token once at the top:
export GOOGLE_WORKSPACE_CLI_TOKEN="$(gws-auth token)"
echo "=== Step 1 ===" ; gws <service> <command1> 2>&1
echo "=== Step 2 ===" ; gws <service> <command2> 2>&1
# List all services
gws --help
# Inspect method signature
gws schema <service.resource.method>
# Dry-run (preview request without executing)
gws <service> <command> --dry-run
V8 platform admin API operations via GraphQL. Use when asked to manage users, grant or query credits, manage verses, game payments, coupons, analytics, or comments. Triggers on requests like "give credits to user", "search user", "set verse featured", "generate coupons", "find spam comments".
Triage Sentry issues and run Seer root-cause analysis using sentry-cli and the official Sentry MCP server (stdio transport, auth-token based — no OAuth). Covers token-auth MCP setup, issue/event querying, Seer autofix via a direct-API workaround, and manual event ingest with send-event. Use when asked to look at a Sentry issue, find what errors are firing, get a root-cause analysis / Seer analysis, send a test event to Sentry, or wire Sentry up for an agent.
Google Sheets operations via gws (Google Workspace CLI). Use when asked to read, write, append, or manage spreadsheets in Google Drive. Triggers on requests like "read the spreadsheet", "append rows to sheet", "create a new spreadsheet", "list Drive files", "share sheet with team".
flex API를 크롤링하여 로컬 데이터를 최신 상태로 갱신한다. Triggers: "데이터 최신화", "크롤링", "DB 갱신", "데이터 새로 가져와"
flex-ax CLI를 통해 SQL 쿼리를 실행하여 결재/근태/사용자 데이터를 조회한다. Triggers: "결재 현황", "휴가 조회", "사용자 검색", "데이터 조회"
Interact with A2A (Agent2Agent) protocol agents via the a2x CLI. Handles installation, agent card inspection, OAuth2 device-flow and SIWE bearer authentication, and blocking / streaming message exchange. Use when asked to talk to an A2A agent, send a message to an A2A endpoint, authenticate with an A2A service, or inspect an A2A agent card.