Menu
How to handle inbound emails — decide whether to reply, compose the response, and send it back via the comms agent.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
How to orchestrate work across large documents and multi-agent delegations without burning token budgets. Reconnaissance-first, search-then-read, parallel-after-reconnaissance.
Decision criteria for delegating to the writer agent vs synthesising directly in your own response.
When and how to use the document library
How the Coder agent drives an OpenCode session via dispatch_coder — the engineering loop, when to dispatch, and how to verify the result is real (vs. claimed).
Maintain a personal index of interesting things, open questions, and follow-ups across sessions
When and how to render a promoted export to PDF via the export_pdf tool. Reads the writer's draft → export → PDF lifecycle and the operator-facing failure modes when the host is missing pandoc or tectonic.
| name | email-response |
| description | How to handle inbound emails — decide whether to reply, compose the response, and send it back via the comms agent. |
| agents | cognitive |
When an inbound email arrives, you receive it as a scheduler-triggered cycle
with <scheduler_context> containing tags email, inbound. The email body
includes Subject:, From:, and the message text.
This is someone writing to you. They expect a reply.
Reply to all inbound emails unless:
When in doubt, reply. Silence is worse than a brief acknowledgement.
Read the email carefully. Understand what is being asked or said.
Do any work needed first. If the email asks you to research something, schedule something, or check something — do that before composing your reply. Use your tools. Don't reply with "I'll look into it" when you can look into it right now and reply with the answer.
Compose your reply. Write as yourself — clear, direct, helpful. Match
the tone and formality of the sender. Keep it concise. Sign off naturally
with your own name (the agent_name in your persona — your "first name"),
not the framework name "Springdrift" (that's your "surname"). If you do
not know your name, check the persona before sending.
Send via agent_comms. Delegate to the comms agent:
agent_comms: Send a reply to <sender_email>.
Subject: Re: <original_subject>
Body: <your composed reply>
If you cannot reply (sender not on allowlist, comms disabled), note this in your response to the cognitive loop so the operator sees it in the chat UI.
If the email is a reply in an existing thread (subject starts with "Re:"),
check your comms history for context. Use check_inbox or read_message
via the comms agent if you need to see the full thread before replying.
Inbound:
Subject: Re: Weekly research update
From: seamus@corvideon.ie
Can you add inflation data to next week's report?
Your response:
agent_comms: Reply to seamus@corvideon.ie
Subject: Re: Weekly research update
Body: Done — I've added inflation data (CSO CPI + Eurostat HICP) to
the research template for next week's report. It'll appear in the
macro indicators section.