Project inbox

What this skill teaches

Workflow

1. 1

   List authorized Prism Email addresses and orient to the relevant inbox view.

2. 2

   List bounded message metadata, then open only the selected received message.

3. 3

   Use labels, read state, starring, archive, trash, restore, or sender status for reversible organization.

4. 4

   Create or update a sender rule only when the user wants repeatable label, archive, or Project auto-save behavior.

5. 5

   Save a selected message and requested attachments into an authorized Project with a useful edited title, cleaned body, and tags.

Tool routing

Safety boundaries

---
name: prism-project-inbox
description: "Use when an AI client needs to read authorized Prism Email, organize messages, manage sender rules, or save selected messages and attachments into a Project."
---

# Project inbox

Organize selected research email into traceable Project sources while preserving the received original.

## Before you start

Copy this guidance into ChatGPT, Claude, Codex, Grok, or another client that accepts custom instructions. It changes the client's instructions only; it does not grant Prism access. Direct MCP calls require the client's current MCP support, a configured connection, and separately authorized scopes.

Scopes this workflow may need:

- `email:read`
- `email:manage`
- `library:write`

The installed skill does not grant these permissions. Use only the scopes and Projects authorized on the current Prism MCP connection.

## Workflow

1. List authorized Prism Email addresses and orient to the relevant inbox view.
2. List bounded message metadata, then open only the selected received message.
3. Use labels, read state, starring, archive, trash, restore, or sender status for reversible organization.
4. Create or update a sender rule only when the user wants repeatable label, archive, or Project auto-save behavior.
5. Save a selected message and requested attachments into an authorized Project with a useful edited title, cleaned body, and tags.

## Tool routing

- `list_email_addresses`, `list_email_messages`, `get_email_message`: Read the smallest authorized inbox surface needed for the task.
- `update_email_messages`, `create_email_label`: Apply reversible inbox organization.
- `list_email_sender_rules`, `upsert_email_sender_rule`: Inspect existing automation before creating or changing a sender rule.
- `save_email_message_to_library`: Save an edited Project copy with selected attachments and provenance.

## Expected result

- Only explicitly authorized addresses and selected messages are opened.
- Inbox organization remains reversible, and sender automation is visible in a named rule.
- Saved Project copies can use an edited title and cleaned body while retaining message provenance.

## Boundaries

- A skill does not grant Prism access. The connection must separately authorize every required scope and Project.
- Call only tools verified callable by the current AI host. Use discover_prism_actions for granular actions. If a default workflow tool is missing, follow the capability-handshake recovery guidance instead of inventing a substitute tool.
- Read before writing. Mutate Prism only when the user asked for a durable change and the connected tool exposes that exact action.
- Keep retrieved evidence separate from analysis. Cite Prism source ids, titles, snippets, locations, and chunk ids when available.
- Email access is privacy-sensitive and never granted automatically with future read scopes.
- Prism MCP cannot send email, submit signup forms, click confirmation links, revoke addresses, or permanently delete received messages.
- Saving to a Project creates a separate editable copy. It does not mutate the received original.