القائمة
Gmail: Send, read, and manage email.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use ctx to search local coding-agent history before acting. Use when prior agent sessions may contain relevant insights, decisions, attempts, or transcript context.
Designs and executes QA test cases. Use for "テストして", "QA観点で確認", "動作確認して", "検証して", "QAして", "test this", "QA check", "merge前に確認", or after feature implementation / dependency updates. Also use in plan mode when designing QA or verification plans to apply risk-based prioritization and systematic test design techniques.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", "ブラウザで確認", "Chromeで開いて", "スクリーンショット", verifying UI, or any task requiring programmatic web interaction. Also use in plan mode when planning browser-based verification to apply correct data extraction strategies and avoid common anti-patterns.
Opt-in project-aware deterministic verification gate. Detects the project type (Nix flake, Deno, Node, Python) and runs build / typecheck / lint / test / security scan / diff-review. Outputs a READY / NOT READY verdict. Not invoked by the default /impl final gate (that default is /completion-audit → /subagent-review). Invoke explicitly when deterministic re-execution is genuinely required. Triggers include /verification-loop / /verify / verification gate / pre-PR check / 検証ループ.
Mandatory completion audit gate. Run this skill ONCE as the final gate task before declaring all work complete. Audits whether implementation and verification evidence are sufficient for the plan's stated purpose. Default mode is a self-audit table by the main session; a fresh completion-auditor subagent is dispatched only when escalation conditions fire. Do NOT run per-task — run only at the final gate. Skipping the completion audit is the #1 cause of false completion claims.
Execute the plan generated by /plan, one task at a time. Per-task — implement, verify acceptance criteria, optionally run simplify-review on large diffs, and mark complete. The final gate is /completion-audit → /subagent-review.
| name | gws-gmail |
| version | 1.0.0 |
| description | Gmail: Send, read, and manage email. |
| metadata | {"openclaw":{"category":"productivity","requires":{"bins":["gws"]},"cliHelp":"gws gmail --help"}} |
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
gws gmail <resource> <method> [flags]
| Command | Description |
|---|---|
+send | Send an email |
+triage | Show unread inbox summary (sender, subject, date) |
+watch | Watch for new emails and stream them as NDJSON |
getProfile — Gets the current user's Gmail profile.stop — Stop receiving push notifications for the given user mailbox.watch — Set up or update a push notification watch on the given user mailbox.drafts — Operations on the 'drafts' resourcehistory — Operations on the 'history' resourcelabels — Operations on the 'labels' resourcemessages — Operations on the 'messages' resourcesettings — Operations on the 'settings' resourcethreads — Operations on the 'threads' resourceBefore calling any API method, inspect it:
# Browse resources and methods
gws gmail --help
# Inspect a method's required params, types, and defaults
gws schema gmail.<resource>.<method>
Use gws schema output to build your --params and --json flags.