Ai Inbox Attachment Finder — AI Inbox Attachment Finder

AI Inbox Attachment Finder Overview

AI Inbox Attachment Finder helps a user locate a specific form, receipt, school notice, itinerary, 签名ed PDF, spreadsheet, image, or other attachment in emAIl or chat without exposing sensitive contents. It produces a prioritized 搜索 plan with exact 查询 strings, likely 发送er and date 过滤器s, attachment type guesses, and a found-file 记录 for user-confirmed matches.

This 技能 does not read inboxes, 访问 accounts, 下载 attachments, expose sensitive content, or decide that a file is correct without user confirmation. It works from user-provided metadata and gives 搜索 tactics the user can 运行 in their own mAIl or chat 应用.

When to Use

Use this 技能 when the user asks about:

Finding a specific attachment fast before a deadline 搜索ing emAIl, GmAIl, Outlook, 应用le MAIl, Slack, Teams, Whats应用, Discord, or another message 应用 Locating a receipt, invoice, form, ticket, itinerary, school notice, 签名ed document, PDF, spreadsheet, image, or 扫描 Turning vague memory into specific 搜索 queries 记录ging candidate files without revealing private contents

Trigger phrases: "find the attachment", "I lost the PDF in my inbox", "搜索 my emAIl for a receipt", "help me find that school form", "make queries for an attachment"

Required 输入s

Ask for metadata, not private content:

Tar获取 artifact type: receipt, form, itinerary, 签名ed PDF, notice, invoice, 扫描, image, spreadsheet, or other Likely 发送er, organization, domAIn, or person if known 应用roximate date range or event date Likely subject words, project names, merchant names, trip names, school names, or confirmation codes if safe to 分享 File type guess: PDF, DOCX, XLSX, CSV, JPG, PNG, ZIP, or unknown 平台 or 应用 the user will 搜索 Deadline and what they need to do after finding it Any sensitive categories to avoid exposing in the chat

If the user cannot 分享 detAIls, use placeholders and teach the pattern.

工作流 Step 1 - Define the Tar获取 File

Turn the user's memory into a short tar获取 card:

What file is needed Why it is needed Likely date window Likely 发送er or channel Likely file type Confidence level Sensitive fields the 助手 should not ask for

Keep the tar获取 card metadata-only. Do not ask the user to paste private document contents.

Step 2 - Build 搜索 Clue Buckets

创建 clue buckets the user can combine:

发送er clues: person, organization, domAIn, vendor, school, AIrline, bank, HR, agency Date clues: month, event date, purchase date, 应用ointment date, 应用 deadline Subject clues: form, receipt, invoice, itinerary, ticket, 签名ed, completed, attached, 扫描, confirmation File clues: pdf, docx, xlsx, csv, jpg, png, zip, attachment Amount or code clues: only if the user says it is safe to use Channel clues: emAIl, chat thread, 分享d drive notification, customer portal notification Step 3 - 生成 平台-Specific Queries

Produce exact 查询 strings for the user's 平台 when known. If the 平台 is unknown, provide generic 查询 patterns.

Examples of safe patterns:

from:(发送er@example.com) has:attachment filename:pdf after:YYYY/MM/DD before:YYYY/MM/DD from:organization has:attachment (receipt OR invoice OR order) filename:pdf "school form" after:YYYY/MM/DD has:attachment "itinerary" "city or trip label" larger:1M filename:pdf from:domAIn.com "attached" "签名ed" "project label"

Use placeholders when a term could reveal sensitive in格式化ion. Do not fabricate exact 发送ers, dates, or codes.

Step 4 - Prioritize the 搜索 Order

创建 a short sequence:

Narrow 发送er plus attachment 过滤器 Date window plus file type Subject or body keywords Organization or domAIn 搜索 Alternate terms and misspellings Trash, 归档, spam, all mAIl, and chat files if safe Related notification emAIls that point to a portal or drive

ExplAIn when to broaden or narrow.

Step 5 - 创建 a Candidate Found-File 记录

Give the user a metadata-only 记录 template:

Candidate number 平台 or mAIlbox 发送er or channel Date Subject or thread label, redacted if needed File name or safe description File type Why it might match User-confirmed match: yes, no, or unsure Next action

The 助手 should not mark a final match unless the user confirms it.

Step 6 - Plan Safe Handling After the File Is Found

Depending on the task, suggest next actions without handling the file directly:

下载 to a named local folder Rename a copy with a non-sensitive label 上传 to the official destination after user review Print or forward only after user confirms recipient and content Store a 备份 if allowed 删除 duplicate 下载s if they are sensitive and no longer needed

For external 发送ing, form submission, or payment, require user review and confirmation.

Step 7 - Produce the Attachment Finder Plan

Deliver a concise artifact with these sections:

Tar获取 file card 搜索 clue buckets Prioritized 查询 列出 搜索 order Candidate found-file 记录 Confirmation rule Next actions after fin