Process email requests with AI
Check the original thread and permitted recipient before turning a message into work. Keep an intake record and distinguish an accepted send from verified delivery.
Process email requests with AI when several people share an inbox and a forwarded instruction may already have been carried out. The email-request-intake skill works from an approved intake route and the project’s written authority. It checks the whole thread, attachments and available records before treating a message as a new task.
Imagine a colleague forwards a request for the latest event programme. The quoted message names an old distributor, and another editor may already have delivered the file. A useful intake record identifies the real request, the permitted destination, any previous completion and what evidence is still missing.
What it does
- Check that an inbound route is on the approved list.
- Separate fresh requests from quoted or forwarded content.
- Look for earlier completion in the thread, task tracker and send log.
- Record the intended recipient, delivery limit and authority for any action.
- Verify the received copy or destination record before closing the request.
Install and use
- Install the skill in a compatible agent with authorised access to the inbox, tracker and send records. Outbound action needs a configured sender and a written policy identifying permitted recipients and actions.
- Ask, “Check this request against the thread and prior delivery. Prepare the reply only if the file has not already been supplied.”
- Review unresolved identity, destination or receipt details. Inspect an uncertain send before trying again.
FAQ
Source
Made by Joe Amditis. Original skill: email-request-intake, published on GitHub under the MIT licence.
View on GitHub