Email Priority

AI Agent Instructions

Use this Classifier via the SuperClassify API from server code, not browser playground automation.

Connect an authorized inbox and evaluate each message/thread against the owner's fixed priorities, responsibilities and current time. Rank assessable scores within existing unread/deadline rules; keep missing-context items visible. Re-evaluate meaningful thread updates, not every inbox render, and never delete or mark mail read solely from a low score.

Class: superclassify/email-priority@1.0.0
Fetch setup as text: https://superclassify.com/skills/superclassify/SKILL.md
Contract (JSON): https://superclassify.com/v1/resolve?ref=superclassify%2Femail-priority%401.0.0

First-time API access

When the user asks to run or integrate this Class, explain its workflow and that live Jev runs use SuperClassify service credits. Public card descriptions can be read without an account. Reuse an existing account, credit balance and API key when available. Otherwise, guide the user through the official setup links below. The user completes sign-in and any credit purchase on the website, then saves the API key in their application’s server secrets as SUPERCLASSIFY_API_KEY—not in chat. A separate TypeSafe account or Jev key is not required for the SuperClassify API. Reading a link does not authorize a purchase or paid run.

1. Create an account or sign in
2. Add credits if needed
3. Create an API key

Immediate work blocker

Owner policy: prioritize issues blocking the scheduled deployment. Current time: 14:00; deployment 14:30. Email from deployment lead: the release cannot proceed until you approve the already-reviewed change.

Author expectation: {"priority":[3,4],"assessable":true}

Routine newsletter

Owner policy: current client delivery before optional reading. Message: weekly product newsletter, no action requested or deadline.

Author expectation: {"priority":[0,1],"assessable":true}

Missing timing

Message: URGENT, reply before the deadline. No actual deadline, request, owner responsibility or thread context supplied.

Author expectation: {"assessable":false}