菜单
Build a dossier on a task issue — gather context from Gmail, Drive, and the wiki, and post it as one sourced comment. Use when asked to "collect for
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Google Calendar via `hq cal` — agenda, free slots, time checks, and session proposals. Use for meetings, appointments, availability, scheduling. Trigger on "calendar", "meeting", "free", "schedule".
Google Drive search via `hq drive` (read-only). Use to find work documents, spreadsheets, or slides and pull short excerpts. Trigger on "drive", "document", "doc", "spreadsheet".
Gmail via `hq mail` — search, read, label, and draft (never send). Use for anything involving email. Trigger on "email", "inbox", "reply", "message from".
Interactive setup wizard for `config/hq.yaml`. Use when the user says "setup", "configure", "set up env", or when `config/hq.yaml` is missing.
GTD tasks on the Forgejo repo via `hq task`. Use for adding, listing, and updating tasks (defer/complete are `hq task update` status changes), and for task context/dossiers. Trigger on "task", "todo", "inbox", "what's on my plate".
Email triage — turn unread mail into Inbox task cards and draft replies. Use when asked to "triage", "process email/inbox", or during a triage job.
| name | collect |
| description | Build a dossier on a task issue — gather context from Gmail, Drive, and the wiki, and post it as one sourced comment. Use when asked to "collect for |
Goal: give the user everything they need to act on a task, as clickable sources with short excerpts. You collect and summarize; you never decide, promote, close, book, or send.
Follow these steps exactly, one command each:
Context. hq task context <issue> — read the title, body, fields, last dossier, and user_comments_since. Treat the user's comments as directives (what to look for, what to skip).
last_dossier is under 3 days old AND user_comments_since is empty, stop: reply that the dossier is current. Post nothing.Search mail. Up to 2 precise queries: hq mail find --text "<key terms>" --newer-than 6m --max 5 (or --from when a person is named). Pick the relevant hits.
Search drive. Up to 2 queries: hq drive find --text "<key terms>" --max 5. For the single most relevant Google Doc, optionally hq drive show <id> --query "<term>".
Search wiki. Up to 2 queries: hq wiki find "<key terms>" --max 5.
Write entries.json — only sources that genuinely help this task (fewer, better entries beat padding; 0–12 entries):
{
"summary": "2-3 sentences: what you found and what it means for this task.",
"decision_needed": "Only if the user must choose something — state the question. Otherwise omit.",
"entries": [
{"source": "gmail", "url": "<url from hq mail output>", "title": "Subject or doc name", "excerpt": "2-3 sentences of what this source says."}
]
}
source is one of gmail|drive|wiki|calendar. Always copy url from CLI output — never construct URLs yourself.decision_needed when the sources reveal a fork only the user can resolve (e.g. two conflicting deadlines, an unanswered question from a collaborator).hq task dossier <issue> entries.json. The run is NOT done until this command has printed "posted": true. Printing the JSON without posting is a failed run. Post at most one dossier per run.Never: change task status or fields, send/label email, book calendar, edit wiki files during a collect run.