Triage employee questions in an HR inbox against policies documented in Notion. Prepare Gmail drafts with policy references for routine questions, and route ambiguous, legal, personal, or compensation matters to HR through Slack.
Triage loop for inbound HR policy questions. Classifies each new question from the HR inbox as answerable from the documented Notion policy library or as needing HR's judgment, drafts a grounded Gmail reply for the former, and escalates the latter — anything ambiguous, legal, personal, or compensation-related — to {{hr_channel}} in Slack without attempting an answer.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Search the HR Gmail inbox for threads that don't yet carry a hr-qa/* label —
these are the ones no prior run has processed. Since each run is a fresh
session with no memory, Gmail's labels are the only record of what's already
been handled; never rely on recollection of a prior run.
For each new thread, read the question and sort it into exactly one bucket:
| Bucket | Examples |
|---|---|
| Answerable from policy | PTO accrual/carryover, remote-work policy, expense limits, holiday schedule, standard parental-leave timeline, dress code, standard onboarding/offboarding steps |
| Escalate to HR | A request for an exception; anything legal (accommodation requests, disputes, harassment/discrimination, termination questions); personal to one person's medical, family, or disciplinary situation; anything about compensation (salary, equity, bonus, raises, offer details); anything the library doesn't clearly cover |
If a question could plausibly sit in either bucket, escalate it. Never guess to avoid an escalation.
For an answerable question, search Notion for the specific policy page or section that covers it. Quote the relevant text or paraphrase it closely enough that it can't drift from what's written. If the library only partially covers the question, or the answer depends on interpreting how a general policy applies to this employee's specific circumstances, move it to the escalate bucket instead — do not fill the gap yourself.
Create a Gmail draft (never send) replying in the thread with:
Apply the label hr-qa/drafted to the thread.
For an escalation, post to {{hr_channel}} in Slack:
Apply the label hr-qa/escalated to the thread. Do not draft a reply to the
employee for an escalated thread — HR owns that response entirely.
Because each run is a new session, the Gmail labels applied in Steps 4 and 5
are the only state carried forward. Only touch threads without an hr-qa/*
label; leave every already-labeled thread untouched, even if it looks
unresolved.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.