菜单
Send a threaded Gmail reply from the worker. Use when a quest requires replying to a Gmail message and the reply must thread correctly (In-Reply-To / References headers). The gws CLI's messages.send does not set threading headers natively — this script handles that.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/circlefin/sidequestor --skill yaas-gmail-reply命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Quality rules for composing replies in Slack threads, channels, and partner-facing quest conversations — research the asker/channel/partnership context first, consider multiple hypotheses for debugging questions, search prior Slack threads before answering tooling questions, follow up on answered threads within 48 hours, hedge confidence appropriately, and handle vague questions by clarifying or scoping the interpretation. Load whenever the worker is about to compose a Slack answer or partner-facing quest reply; the quest still owns its specific tone and objective.
Add a new watch type to the yaas triage loop by pairing an executable checkers/<type>.py with checkers/<type>.watch.json, then covering its behavior and affected docs. Load when asked to watch a source triage cannot watch yet (a new API, a queue, a feed), or when reviewing a checker someone else added.
Operating and extending the yaas triage system — adding new channel types, understanding the checker plugin architecture, state file layout, setup, and migration runbook. Load when asked to add a new watcher, debug triage, or understand how the system is wired.
正在显示 SKILL.md
| name | yaas-gmail-reply |
| description | Send a threaded Gmail reply from the worker. Use when a quest requires replying to a Gmail message and the reply must thread correctly (In-Reply-To / References headers). The gws CLI's messages.send does not set threading headers natively — this script handles that. |
| type | worker-tool |
Sends a Gmail reply with correct RFC 2822 threading headers so it appears as a reply in the recipient's thread, not a new message.
Any time a quest instructs you to reply to a Gmail message. The gws gmail users messages send command alone does not set In-Reply-To or References
headers, so replies show up as new conversations. This script fetches the
original message metadata, builds the headers, and sends via gws.
GWS_BIN=$(command -v gws || echo /opt/homebrew/bin/gws) \
python3 "$SIDEQUESTOR_RUNTIME_ROOT/yaas-triage/skills/yaas-gmail-reply/gmail-reply.py" <gmail_message_id> --body "<reply text>"
<gmail_message_id> — the Gmail message ID to reply to (from messages.list or timeline)--body "<text>" — reply body; alternatively pipe via stdinPrints the sent Gmail message ID on success. Exits 1 on failure.
GWS_BIN — path to gws CLI (defaults to gws on PATH)SIDEQUESTOR_FROM_EMAIL — sender display name + address, e.g. Jane Smith <jane@example.com>
Set in .env and sourced by the orchestrator.GWS_BIN=$(command -v gws || echo /opt/homebrew/bin/gws) \
python3 "$SIDEQUESTOR_RUNTIME_ROOT/yaas-triage/skills/yaas-gmail-reply/gmail-reply.py" 19e12bf3e4bb4694 \
--body "Why did the webhook retry queue go to therapy? It kept showing up uninvited."