القائمة
Organize emails with labels and folders: attach labels, detach wrong ones, and move misfiled emails.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use the Spark MCP extension to access and act on the user's Spark email data - list emails, search by topic, read threads, check calendar events, find availability, look up contacts, view team info, draft messages (from scratch or saved templates), send drafts, share drafts with teammates, post team comments, triage threads, create/update/delete calendar events and manage attendees, and manage contacts. Use when the user asks about their emails, calendar, contacts, meetings, scheduling, or wants to send, reply, archive, snooze, assign, comment, categorize, or schedule.
Executive assistant persona for Spark. Morning briefings, draft replies, schedule management, and contact lookup.
Founder / CEO persona for Spark. High-volume triage, aggressive delegation, cross-team oversight, and selective engagement.
Freelancer / solo operator persona for Spark. Multi-client management, invoice follow-ups, availability, and quick responses.
Meeting manager persona for Spark. Meeting preparation, transcript review, follow-up drafts, and scheduling.
Project manager persona for Spark. Project thread tracking, stakeholder updates, action item extraction, and cross-team coordination.
| name | spark-recipe-label-organize |
| description | Organize emails with labels and folders: attach labels, detach wrong ones, and move misfiled emails. |
| metadata | {"version":"1.0.0","requires":{"skills":["spark"],"accessLevel":"triage"}} |
Organize emails using labels and folders. Attach project labels, detach incorrect ones, and move misfiled emails to the right location.
Prerequisite: Read the spark base skill for tool reference and filter syntax.
Access level required: triage.
folders {}
For a specific account:
folders { "account": "user@example.com" }
Note the existing labels and their message counts. Identify labels that are empty or no longer relevant.
Search for project-related or topic-related emails that should be labeled:
search { "query": "project name" }
emails { "filter": "from:client@company.com newer_than:30d" }
Add a label to an email without removing it from its current location:
action { "action_name": "attachLabel", "message_ids": ["<id>"], "folder": "user@example.com:ProjectAlpha" }
Label multiple emails in a batch:
action { "action_name": "attachLabel", "message_ids": ["<id1>"], "folder": "user@example.com:ProjectAlpha" }
action { "action_name": "attachLabel", "message_ids": ["<id2>"], "folder": "user@example.com:ProjectAlpha" }
Remove a label that was applied incorrectly:
action { "action_name": "detachLabel", "message_ids": ["<id>"], "folder": "user@example.com:WrongLabel" }
Move emails to the correct folder:
action { "action_name": "moveToFolder", "message_ids": ["<id>"], "folder": "user@example.com:Projects" }
Browse the organized label to confirm the right emails are there:
emails { "folder": "user@example.com:ProjectAlpha" }
folders to discover the exact qualified names for labels (e.g., user@gmail.com:MyLabel).attachLabel adds a label without moving the email - the email stays in its current folder too. This is how Gmail labels work.detachLabel removes a label without moving the email elsewhere.moveToFolder physically moves the email to a different folder - use this for IMAP-style organization.attachLabel/detachLabel over moveToFolder since Gmail uses labels rather than folders.shared@company.com:LabelName or "Team Name:LabelName".recipe-meeting-prep or project tracking workflows to label threads as part of a larger process.