AI Agent Use Cases

Added today

44All 189

Prompt to Prepare a Shopping Cart from a Recipe Photo

The author reports that Grok Bot receives a recipe photo, organizes the ingredients and quantities, and creates a shopping list by excluding ingredients already available at home.

Grok Bot
Life & Hobbies

1–20 of 189

Work & ResearchWalkthrough

Agent for Finding Conversations and Attachments Matching Criteria in Email

The author reports that Claude's local email example uses a search tool to find candidate emails, then reads the selected email body again to answer questions.

How it works

  1. The author connects a test IMAP account and API key to run the local email app. For Gmail, the instructions specify using an app password instead of a regular password.
  2. The agent calls search_inbox using criteria such as sender, subject, or date. Based on the returned email IDs and log file paths, the agent can read the necessary email bodies.
  3. read_emails returns the body of the selected email and indicates whether there are attachments. The response includes the email ID to allow linking to the specific message.

Results

The author reports confirming in the public code that the process of re-reading email search results and linking them to answers works.

Notes

Credentials are stored in an environment file, and this is a local demo without separate authentication features. The creator prohibits operational deployment. The author did not run it with personal email.

Source

GitHub Original post ↗

Example prompt · Claude

Goal: Find conversations and attachment details in email that match specified criteria.

Input & Environment: [Test email account], [Search criteria], [Question to check], [Local Bun or Node.js environment].

Reference original: https://github.com/anthropics/claude-agent-sdk-demos/tree/main/email-agent

Please prepare the email-agent example only in a local test environment. Do not leave secrets in chats or repositories; instruct the user where to put them in an environment file. After finding emails by sender and date, read the body of the relevant ID and write an evidence-based answer. Sending, deleting, or changing email categories is outside the scope for this implementation; focus on the reading flow first.

Do not speculate about account connection methods or results not in the original; first, provide the necessary setup and execution order. Start from a working copy to preserve existing materials, and indicate if any items are inaccessible and need checking.

Verification: Check cases with emails from different senders with the same subject, emails without attachments, and when there are no search results. Make sure the linked email ID and actual body match in the answer, and do not hide search failures as 'no result.'

Summarize the used inputs, execution logs, and confirmed results along with the output. Clearly distinguish between completed tasks and those that failed or have not yet been executed.