메뉴
Use when the user wants to clean up, organize, or triage their Gmail inbox interactively
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when constructing or interpreting the approval handoff envelope between subagent and orchestrator -- sealed_payload schema, approval_id format, APPROVAL_REQUEST contract shape, and reading a granted approval from the DB
Use when producing any agent response
Use when classifying any operation before executing it, or deciding whether user approval is required
Use when a mutative command was blocked by the hook and you need to request user approval, or when presenting a plan for a T3 operation before executing it
Use when the user wants to build, design, or extend a diagram — an architecture overview, a timeline, a planner board, a flow diagram, a presentation, a comparison, or a mind-map — as a portable, data-driven deck rendered from plain YAML. Triggers — "build a diagram", "architecture diagram", "diagram deck", "timeline", "flow diagram", "planner board", "add a page/section/component to the diagram".
Use when the user wants something to run routinely / on a schedule rather than once now -- "tarea programada", "rutinariamente", "cada mañana", "cada N horas", "todas las noches", "schedule", "cron". Covers mounting, structuring, and running an unattended headless task that reports back, plus consuming its reports. NOT for a live in-session agentic loop (that is agentic-loop).
| name | gmail-triage |
| description | Use when the user wants to clean up, organize, or triage their Gmail inbox interactively |
| metadata | {"user-invocable":false,"type":"technique"} |
Interactive GTD-inspired state machine for Gmail. Gaia analyzes threads, proposes transitions. User decides. Gaia executes. The gmail-policy skill governs allowed operations and label definitions.
Four active states (defined in gmail-policy):
_gaia/action — user must act_gaia/waiting — user acted, awaiting reply_gaia/someday — interesting, no urgency_gaia/pending — staging (triage backlog)_gaia/trash — soft delete; never truly deletedNo _gaia/* label = processed/done.
Before presenting ANY labeled email, check the thread: message count, who sent last, when. This determines framing:
action thread → move to waitingwaiting thread → move to actiontrash or somedaysomeday → actionModes 1–5 open with a state summary before their specific work:
"Antes de empezar: N en action, N en waiting, N en someday." Flag action items stale >3 days.
_gaia/action — present each item with thread framing. Did user already reply? Auto-propose → waiting._gaia/waiting — did the other party respond? Auto-propose → action. Stale >1 week → flag._gaia/someday — count only: "tienes 5 en someday." Detail only if asked.action. Interesting, no urgency → propose someday.Scan inbox, group by sender/category, report counts. Present top groups. User decides per group → trash/action/someday/content-label. Report progress: "Procesamos 500 de 2000. ¿Seguimos?"
Pick easiest batch (highest volume, most repetitive). "340 promos de retail. ¿Las mando a trash?" One confirmation = hundreds processed. Target: under 2 minutes.
Move unprocessed to _gaia/pending. Report: "847 correos: 600 promos, 120 banco, 80 LinkedIn, 47 otros." Work categories in follow-up modes.
Dedicated state review — all three active labels:
_gaia/action — stale >3 days? move to waiting/someday/done?_gaia/waiting — any responses arrived? stale >1 week?_gaia/someday — weekly review: promote to action? trash any?Group by sender, identify patterns. Flag genuinely interesting vs noise. Recommend bulk trash for repetitive senders.
Group by sender/topic. Show count + sample subject. Flag unusual items ("movimiento de $50K en Bci"). Propose action per group. Max 5-7 groups per interaction.
removeLabelIds changes visibility with no undo._gaia/trash — it is the user's safety net, not Gaia's to manage.gmail-policy — security rules, label definitions, operation tiersgws-setup — CLI installation and authentication