| name | oysterun-mail |
| description | Use for Oysterun Mail commands through the P86 CLI, including send, unread-count, list, get, read/unread, archive/unarchive, update, and confirm/dry-run protected delete. |
| metadata | {"short-description":"Manage Oysterun Mail"} |
Oysterun Mail
Canonical product skill source lives at skills/oysterun-mail/. The repo-local Codex mirror at .codex/skills/Oysterun/modules/oysterun-mail/ and Host packaged assets at host-service/assets/product-skills/oysterun-mail/ and host-service/assets/product-skills/Oysterun/modules/oysterun-mail/ are generated mirrors. Run node tool_scripts/sync_product_skills_to_codex.mjs after changing this skill and node tool_scripts/check_product_skill_mirrors.mjs before review.
Use this module skill for normal product Mail operations. It wraps the P86 product CLI contract:
oysterun mail <action> [options]
The helper delegates to the same CLI surface:
$OYSTERUN_CLI_BIN mail send \
--title "Digest ready" \
--html-file data/latest_report.html \
--source-ref route-owned-mail
When Host injects this skill into a live session, the helper path is:
node .claude/skills/Oysterun/modules/oysterun-mail/scripts/oysterun_mail.mjs list
Commands
sendunread-countlistgetreadunreadarchiveunarchiveupdatedelete --confirm or delete --dry-run
P183/P307 Runtime Authority
P183/P307 runtime authority alignment means every command in this skill is
callable from a live Host session through Host-injected product runtime
environment:
OYSTERUN_HOST_ORIGIN, OYSTERUN_CAPABILITY_TOKEN, OYSTERUN_SESSION_ID,
OYSTERUN_AGENT_ID, and OYSTERUN_CLI_BIN. Inside a live Host session,
helper scripts and direct command examples must execute the injected CLI from
OYSTERUN_CLI_BIN; do not call bare oysterun, because it may resolve to a
globally installed package with older command behavior. That authority is
Host-wide for installed Oysterun product skills. Do not ask an in-session agent
to run dashboard login for these commands. Explicit --token is the operator
override; external operator shells may still use dashboard CLI auth.
Guardrails
- Do not call
/mail/send or /mail/items/* directly from this skill.
mail send defaults to the Host owner recipient. Dashboard auth claims stay actor/audit identity only.mail send is HTML-only. Generate a durable .html deliverable first and pass it with --html-file <path>.html; markdown, auto, stdin, and plain text bodies are not supported.- Explicit recipient overrides must fail closed when the Host app user is unavailable.
- Do not print tokens, cookies, passwords, auth headers, raw profile files, or raw Mail capability tokens.
- Use
--dry-run before deleting Mail unless the route explicitly authorizes mutation.
Scheduler/Agent Runtime Compatibility
Scheduler jobs and injected Host runtime environments should use the product
CLI Mail command. Prefer the injected CLI path when it is available:
$OYSTERUN_CLI_BIN mail send \
--title "Digest ready" \
--text "Daily tracker finished" \
--source-ref route-owned-mail
When a scheduler run receives OYSTERUN_HOST_ORIGIN,
OYSTERUN_CAPABILITY_TOKEN or OYSTERUN_MAIL_WRITE_TOKEN,
OYSTERUN_SCHEDULE_ID, OYSTERUN_SCHEDULE_RUN_ID, and OYSTERUN_AGENT_ID,
mail send uses the scheduler-run mail:create capability and preserves the
schedule/run/agent attribution. Do not branch between two Mail stacks, do not
call /mail/* Host endpoints directly, and do not inspect or print raw
capability tokens.
The legacy send_mail.mjs helper remains available only for old generated
scripts that already call it:
node .claude/skills/Oysterun/modules/oysterun-mail/scripts/send_mail.mjs --title "Digest ready" --html-file data/latest_report.html
External operator shells should prefer oysterun_mail.mjs with dashboard CLI
auth; live Host sessions must rely on Host-injected product runtime env instead
of dashboard tokens.
Scheduler and report-producing agents must not pass HTML through
OYSTERUN_CLI_TEXT, --text, --body, markdown fields, or direct Host
/mail/* requests. The .html file extension is the Mail deliverable contract.
