agentleFS
aadi-labsaadi-labs/agentmailer-plugins/agentmailer-cli/SKILL.md

agentmailer-cli

Skill1 starsChanged 3 months agoMITView on GitHub

Operate AgentMailer from a shell with the generated CLI for inboxes, messages, threads, drafts, attachments, domains, webhooks, policy, events, billing, and A2A resources.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Use the agentmailer command for shell automation, inspection, and reproducible operational checks.

    line 8
  2. Distinctive:

    Read references/commands.md for global controls and operational patterns.

    line 32
  3. Distinctive:

    Use the CLI example directory for inbox listing, monitoring, identity discovery, and sending.

    line 36

≈ “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 CLI

Use the agentmailer command for shell automation, inspection, and reproducible operational checks. The CLI is generated from the same reviewed OpenAPI contract as the SDKs.

Start safely

Set AGENTMAILER_API_KEY in the process environment or a local secret manager. Do not pass credentials as command arguments or commit .env files.

Begin with a read-only check:

agentmailer inboxes list --limit 10 --format table

Discover the exact current surface instead of guessing flags:

agentmailer --help
agentmailer inboxes --help
agentmailer --help --format json

For a mutating command, use --dry-run when available, inspect the exact target and payload, and keep a stable idempotency key for retryable creates or sends. Scripted output defaults to structured data when piped; set --format json when the consumer requires a fixed contract.

The checked-in CLI is currently the source-of-truth client until a release asset is independently verified. Build it from cli/ with the Rust toolchain rather than assuming an installer exists.

Read references/commands.md for global controls and operational patterns.

Examples

Use the CLI example directory for inbox listing, monitoring, identity discovery, and sending. The complete examples catalog provides equivalent TypeScript and Python 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.