菜单
Reads emails from Gmail account. Use when the user asks to "look at emails", "check emails from [sender]", "read recent emails", or "/read-email". Fetches emails with full body content for analysis.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | read-email |
| description | Reads emails from Gmail account. Use when the user asks to "look at emails", "check emails from [sender]", "read recent emails", or "/read-email". Fetches emails with full body content for analysis. |
| allowed-tools | Bash,Read |
Fetches and displays emails from Gmail using OAuth credentials.
GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET environment variables must be set~/.claude/gmail_token.yaml (or custom path via GMAIL_TOKEN_PATH)When the user requests to read emails, extract:
support@example.com)Extract the sender email address or search query from the user's request:
--from support@example.com--from notifications@acme.com --limit 5--query "subject:invoice"source ~/.rvm/scripts/rvm && rvm use ruby-3.4.2 && ruby ~/.claude/skills/read-email/bin/gmail-reader.rb --from <sender> --limit <n>
Options:
-f, --from SENDER - Filter by sender email address-q, --query QUERY - Gmail search query (overrides --from)-l, --limit N - Maximum emails to return (default: 10)Parse the JSON output and present emails in a readable format:
## Email from [sender]
**Subject**: [subject]
**Date**: [date]
[body content]
---
For each email:
After presenting emails, suggest relevant actions:
User: "look at recent emails from support@example.com"
source ~/.rvm/scripts/rvm && rvm use ruby-3.4.2 && ruby ~/.claude/skills/read-email/bin/gmail-reader.rb --from support@example.com --limit 10
User: "check my last 3 emails from Acme Corp"
source ~/.rvm/scripts/rvm && rvm use ruby-3.4.2 && ruby ~/.claude/skills/read-email/bin/gmail-reader.rb --from notifications@acme.com --limit 3
User: "find emails about the project proposal"
source ~/.rvm/scripts/rvm && rvm use ruby-3.4.2 && ruby ~/.claude/skills/read-email/bin/gmail-reader.rb --query "subject:project proposal" --limit 10
GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET are set~/.claude/gmail_token.yamlThe script returns JSON:
[
{
"id": "message-id",
"from": "sender@example.com",
"to": "recipient@example.com",
"subject": "Email subject",
"date": "Fri, 10 Jan 2025 10:30:00 +0000",
"body": "Full plain-text email body..."
}
]
~/.claude/gmail_token.yaml, override with GMAIL_TOKEN_PATH env varCheck Copilot Review Comments. Fetches, adversarially verifies, and resolves Copilot code-review comments on the current PR, then drives an automated re-review loop (re-request → watch → verify → fix → converge). Use when the user asks to "check copilot comments", "what did copilot say", "copilot review", or "/copilot-check".
Execute a GitHub HLR (High-Level Requirement) issue end to end — first-cut breakdown, specialist co-production and synthesis, /plan:tasks → sub-issues, parallel build, QA verification, security gate, and PR. Use when the user runs `/do-hlr <issue#>` or asks to implement/execute an HLR. Runs the full pipeline for substantial HLRs and a lean path for small ones.
Interact with Zendesk API - read tickets, test connection, export data
Checks documentation consistency across the repository. Use when user asks to "check consistency", "are the documents consistent", "is everything aligned", "verify documentation", or "/repo-consistency".
Rewrites git history to permanently remove sensitive data. DESTRUCTIVE OPERATION - rewrites commit history. Use when user asks to "purge secrets from history", "remove sensitive data from git history", "clean git history", or "/repo-security-purge". Requires explicit confirmation.
Scans a repository for sensitive information and security vulnerabilities. Use when the user asks to "scan for security issues", "check for sensitive data", "repo security scan", "make sure this repo has no sensitive information", "security audit", "scan history for secrets", or "/repo-security-scan".