gog-wrapper-server

name	gog-wrapper-server
description	Use the gws-safe wrapper as an API client for running gog subcommands with a bearer token. Focus only on forming safe /api calls, choosing correct subcommands, and interpreting plain-text gog output.

Gog Wrapper Client

Use POST /api to execute gog subcommands through the wrapper.

Scope

• This skill is user-facing and intentionally excludes admin operations.
• Assume the caller already has a valid bearer token.
• Use this skill to:
  • Build valid /api requests.
  • Pick the correct gog subcommand syntax (after root gog).
  • Validate whether output indicates success, auth issues, or scope denial.

Request Pattern

Single command:

curl -sS -X POST http://localhost:3000/api \
  -H "Authorization: Bearer <access-token>" \
  -H "Content-Type: application/json" \
  --data '{"subcommand":"<gog args after root>"}'

Multiple commands in parallel (max 10):

curl -sS -X POST http://localhost:3000/api \
  -H "Authorization: Bearer <access-token>" \
  -H "Content-Type: application/json" \
  --data '{"subcommands":["<command1>","<command2>"]}'

Examples

Read Gmail:

curl -sS -X POST http://localhost:3000/api \
  -H "Authorization: Bearer <access-token>" \
  -H "Content-Type: application/json" \
  --data '{"subcommand":"gmail messages search \"in:inbox\" -a [e-mail] --plain"}'

Create a Gmail draft:

curl -sS -X POST http://localhost:3000/api \
  -H "Authorization: Bearer <access-token>" \
  -H "Content-Type: application/json" \
  --data '{"subcommand":"gmail drafts create -a [e-mail] --to [e-mail] --subject \"Draft from wrapper\" --body \"Hello\" --plain"}'

Batch multiple commands:

curl -sS -X POST http://localhost:3000/api \
  -H "Authorization: Bearer <access-token>" \
  -H "Content-Type: application/json" \
  --data '{"subcommands":["gmail messages search \"in:inbox\" -a [e-mail] --plain","gmail drafts list -a [e-mail] --plain"]}'

Response Interpretation

Single command (subcommand):

• 200 text/plain with rows/text: command executed (even if gog reports an API error in text).
• 401 {"error":"unauthorized"}: missing/invalid bearer token.
• 403 {"error":"forbidden_by_scope_policy",...}: token scope does not allow that command.
• 400 {"error":"subcommand contains disallowed metacharacters"}: blocked injection pattern.

Batch (subcommands):

• 200 application/json with an array of per-command results. Each entry is either { "output": "...", "exitCode": 0 } on success or { "error": "...", "reason": "..." } on failure. Valid commands execute even if others fail (partial success).
• 400 {"error":"batch size exceeds maximum of 10"}: too many commands in one request.

Guardrails

• Always send only the portion after gog in subcommand.
• Do not include shell metacharacters: ;, |, &, backticks, $(.
• Prefer --plain for stable text output.