agentleFS
aadi-labsaadi-labs/agentmailer-plugins/agentmailer-manage-inboxes/SKILL.md

agentmailer-manage-inboxes

Skill1 starsChanged 3 months agoMITView on GitHub

Compatibility alias for managing human-approved AgentMailer identities, inboxes, and unique @agentmailer.ai addresses.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 2 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill when a user wants to create an agent identity or manage the inbox and unique handle@agentmailer.ai address attached to an …

    line 8
  2. Very specific:

    Call auth_me. Inbox creation requires a trusted, human-approved identity with inboxes:create.

    line 12
  3. Very specific:

    Call list_inboxes before creating a new inbox when an existing identity might satisfy the request.

    line 13
  4. Very specific:

    Use a stable, task-specific idempotencyKey for create_inbox so a retry cannot create a duplicate.

    line 15
  5. Very specific:

    Verify that the returned address uses @agentmailer.ai, then return the identity's unique handle, inbox ID, address, display name, and …

    line 16
  6. Very specific:

    Use update_inbox for display name, metadata, or client correlation changes.

    line 17
  7. Very specific:

    If auth_me reports an unverified identity or creation returns human_approval_required, stop and follow the signup sequence at …

    line 19
  8. Distinctive:

    Read references/inbox-tools.md when choosing tool inputs or handling permissions.

    line 23
  9. Distinctive:

    Start with the AgentMailer quickstart for inbox discovery and the [human-approved signup

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

AgentMailer Inbox

Use this skill when a user wants to create an agent identity or manage the inbox and unique handle@agentmailer.ai address attached to an existing identity.

Workflow

  1. Call auth_me. Inbox creation requires a trusted, human-approved identity with inboxes:create.
  2. Call list_inboxes before creating a new inbox when an existing identity might satisfy the request.
  3. For creation, clarify the intended display name and requested address only when they materially affect the result. Omitting the username lets AgentMailer generate a deterministic address.
  4. Use a stable, task-specific idempotencyKey for create_inbox so a retry cannot create a duplicate.
  5. Verify that the returned address uses @agentmailer.ai, then return the identity's unique handle, inbox ID, address, display name, and relevant metadata.
  6. Use update_inbox for display name, metadata, or client correlation changes.

If auth_me reports an unverified identity or creation returns human_approval_required, stop and follow the signup sequence at https://api.agentmailer.ai/llms.txt. Do not substitute another domain or bypass human approval.

delete_inbox deactivates the mailbox and reserves its handle. Before calling it, identify the exact inbox, explain that effect, and obtain explicit confirmation in the current conversation.

Read references/inbox-tools.md when choosing tool inputs or handling permissions.

Examples

Start with the AgentMailer quickstart for inbox discovery and the human-approved signup example for the first-time identity ceremony. Browse the complete examples catalog for inbox-backed application workflows.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.