# Send Clawback to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "clawback-sh", "name": "Clawback", "source": "tencent", "type": "skill", "category": "效率提升", "sourceUrl": "https://clawhub.ai/rotemtam/clawback-sh", "canonicalUrl": "https://clawhub.ai/rotemtam/clawback-sh", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/clawback-sh", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=clawback-sh", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "SKILL.md", "package-lock.json", "package.json" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "clawback-sh", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-29T10:21:36.021Z", "expiresAt": "2026-05-06T10:21:36.021Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=clawback-sh", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=clawback-sh", "contentDisposition": "attachment; filename=\"clawback-sh-0.2.0.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "clawback-sh" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/clawback-sh" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/clawback-sh", "downloadUrl": "https://openagent3.xyz/downloads/clawback-sh", "agentUrl": "https://openagent3.xyz/skills/clawback-sh/agent", "manifestUrl": "https://openagent3.xyz/skills/clawback-sh/agent.json", "briefUrl": "https://openagent3.xyz/skills/clawback-sh/agent.md" } } ``` ## Documentation ### clawback Use clawback for Gmail with policy enforcement. All operations go through a server-side proxy that enforces policies and logs an audit trail. Sends may require human approval. Prerequisites The clawback binary must be installed and on your PATH. If it's missing, releases are available at https://github.com/honeybadge-labs/clawback/releases. Setup (once) clawback auth login (device flow — opens browser) clawback auth status (verify connection) Common commands Gmail search: clawback gmail search 'newer_than:7d' --max 10 Gmail search (all pages): clawback gmail search 'from:boss@company.com' --all --json Gmail get message: clawback gmail get --json Gmail send (plain): clawback gmail send --to a@b.com --subject "Hi" --body "Hello" Gmail send (HTML): clawback gmail send --to a@b.com --subject "Hi" --body-html "

Hello

" Gmail send (reply): clawback gmail send --to a@b.com --subject "Re: Hi" --body "Reply" --reply-to-message-id --thread-id Thread list: clawback gmail thread list 'subject:meeting' --max 20 Thread get: clawback gmail thread get --json Thread modify labels: clawback gmail thread modify --add STARRED --remove UNREAD Labels list: clawback gmail labels list Labels create: clawback gmail labels create --name "Important/Clients" Labels modify message: clawback gmail labels modify --add STARRED --remove UNREAD Drafts list: clawback gmail drafts list --json Drafts create: clawback gmail drafts create --to a@b.com --subject "Draft" --body "WIP" Drafts send: clawback gmail drafts send (may require approval) Drafts delete: clawback gmail drafts delete History: clawback gmail history --since --max 50 Batch delete: clawback gmail batch delete Batch modify: clawback gmail batch modify --add INBOX --remove SPAM Settings filters list: clawback gmail settings filters list --json Settings send-as list: clawback gmail settings send-as list Settings vacation get: clawback gmail settings vacation get Settings forwarding list: clawback gmail settings forwarding list Settings delegates list: clawback gmail settings delegates list Approvals list: clawback approvals list --status pending --json Approvals get: clawback approvals get --json Policy list: clawback policy list --json Agent behavior Never expose approval IDs, exit codes, or CLI commands to the user. Those are internal plumbing. When composing email on the user's behalf, draft a natural subject and body — don't parrot their words verbatim. If they say "send a hello to Alex," write a friendly greeting, not --subject "hello" --body "hello". Confirm with the user before sending. Show them the draft (to, subject, body) and ask if it looks good. Handling approvals (exit code 8) When a send command exits with code 8, it means the email needs human approval before it goes out. Tell the user in plain language: "Sent! It needs approval in Clawback before it goes through — I'll keep an eye on it." Poll clawback approvals get --json in the background every ~30s. When resolved, proactively tell the user: "Approved and delivered" or "The approval was rejected/expired — the email was not sent." Never ask the user to run commands or check approval status themselves. Handling other errors Exit 4 (not authenticated): "You're not signed in — let me open the login flow." Then run clawback auth login. Exit 6 (blocked by policy): "Your org's policy doesn't allow this action." Explain what was blocked. Exit 3 (no results): Report naturally, e.g. "No emails matched that search." Exit 1 (unexpected error): Report the error and suggest retrying. Notes CB_SERVER defaults to https://clawback.sh; set it to use a different server. Prefer --json plus --no-input plus --fail-empty for reliable output parsing. --connection selects which Gmail connection to use; auto-detected if you have one connection. --all auto-paginates search results (gmail search and thread list). --select field1,field2 projects JSON output to specific fields. --results-only strips the envelope and returns just the data array. ## Trust - Source: tencent - Verification: Indexed source record - Publisher: rotemtam - Version: 0.2.0 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-04-29T10:21:36.021Z - Expires at: 2026-05-06T10:21:36.021Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/clawback-sh) - [Send to Agent page](https://openagent3.xyz/skills/clawback-sh/agent) - [JSON manifest](https://openagent3.xyz/skills/clawback-sh/agent.json) - [Markdown brief](https://openagent3.xyz/skills/clawback-sh/agent.md) - [Download page](https://openagent3.xyz/downloads/clawback-sh)