Sort new messages in a shared Gmail inbox, consult help documentation, and prepare reply drafts or Linear tickets. Leave unsupported questions for human review, with category labels applied consistently and no customer emails sent automatically.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
The shared-inbox triage runbook — how to read a new inbound email, label it, look up {{help_doc}} for a standard answer, draft a reply in Gmail or file a ticket in {{linear_team}}, and when to leave a thread label-only for a human.
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Check the shared Gmail inbox for messages that arrived since the last check and don't already carry a triage label. Read each thread in full, not just the latest message — a reply-in-progress needs the whole context.
Classify every thread into exactly one category:
| Category | Signal | Label |
|---|---|---|
| Support question | Asking how something works, a how-to, an account question with a known answer | triage/support |
| Bug report | Something broken, an error, unexpected behavior | triage/bug |
| Sales lead | Pricing, demo, or new-customer interest | triage/sales |
| Billing / invoice | Payment, invoice, or subscription question | triage/billing |
| Other / spam | Not a real request, or nothing the team needs to act on | triage/other |
Apply the label in Gmail regardless of what happens next — every message that's triaged gets exactly one category label.
For triage/support, search {{help_doc}} for the closest matching answer
before writing anything. Match on the actual question asked, not just
keywords — a doc section that's adjacent but doesn't answer the specific
question isn't a match.
| Match quality | Action |
|---|---|
| Doc directly answers the question | Draft a reply (Step 4) |
| Doc partially answers it, or the question combines two topics | Draft a reply covering what the doc supports; note in the draft what's uncertain |
| No relevant section in the doc | Label only — leave it for a human, don't guess |
Write the reply in the sender's language and tone: direct, helpful, answer first. Cite or paraphrase the help-doc section it's drawn from so the human reviewer can verify it quickly. Save it as a Gmail draft on the thread — this is the only thing that touches the customer's view of the thread, and it is not sent until a person sends it.
For triage/bug and any triage/support thread that needs engineering
follow-up rather than a reply, create a ticket in the {{linear_team}}
team:
Sales leads (triage/sales) and billing questions (triage/billing) get
labelled and, if the help doc covers the billing question, drafted per Step
3 — they don't automatically get a Linear ticket unless they also describe a
bug.
triage/other aloneLabel and move on. No draft, no ticket, no further action.
One pass over the new mail is one run. There's no ledger to update — the next scheduled check re-reads whatever the inbox looks like then.
</workflow> <guardrails> - **Draft only, never send.** Every reply is a Gmail draft on the thread. The agent never sends a customer-facing email itself, no matter how confident the match to {{help_doc}} is. - **No memory between runs.** Each check is a fresh session; the current inbox and label state is the only source of truth, not what a prior run concluded. - **Don't guess past the doc.** If {{help_doc}} doesn't clearly answer a support question, label it and stop — a wrong drafted answer waiting for rubber-stamp approval is worse than no draft. - **Scoped secrets.** Gmail, Linear, and help-doc access are brokered through connectors; no raw token is ever shown to the model or written to logs. - **People decide, not the agent.** The agent labels, drafts, and files — whether a draft sends or a ticket's priority changes is a human call. </guardrails> </skill>아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Review Slack access requests against Okta role and team information, then prepare narrowly scoped GitHub or AWS IAM permissions. Apply changes only after an eligible person's approval and record the grant, reasoning, approver, and timestamp.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Research companies and people before outreach or meetings. Combines business profiles, recent news, hiring signals, and key contacts into a sourced brief with talking points and suggested questions, adding relationship history when CRM data is connected.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review daily Google Ads and Meta Ads results for budget pacing, declining performance, and unusual activity. Get prioritized findings with supporting numbers and concrete recommendations for a marketing team to assess and carry out.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Automate website tasks such as navigating pages, filling forms, clicking buttons, taking screenshots, and extracting data. The skill also supports web app testing, with specialized guides for Electron desktop apps, Slack, and cloud browsers.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Process emailed vendor invoices by extracting details, comparing them with purchase orders and invoice history, and recording duplicates, overcharges, or missing orders. Summarize results in Slack for human review; payment approval and execution remain with people.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide changes to Kortix billing code, admin controls, and pricing screens. Explain how plans, trials, enterprise contracts, and access exceptions should work, where pricing is defined, and which audited routes must handle account changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.