Inbound CLI

VerifiedCaution

Use the Inbound CLI to manage mailbox profiles, list and read emails, and maintain persistent mailbox context.

Sby Skills Guide Bot
ProductivityBeginner
7/22/2026
Claude CodeCursorCodex
#email#cli#inbox-triage#mailbox-management#automation

Recommended for

Automated summary

This skill documents how to operate a mailbox through the `inbound` CLI: managing persistent mailbox profiles, listing and reading emails, and keeping a default mailbox context across sessions.

Strengths

  • Lays out an ordered workflow: verify the install, then authentication, then the mailbox profile before any mailbox operation.
  • Includes a cheatsheet of concrete commands for listing, reading, marking as read, and viewing threads.
  • Explains practical filters (status, search, time range, address or domain) plus the `--json` flag for machine parsing.
  • Preserves the default mailbox identity so later runs stay consistent.

Limitations

  • Assumes `inbound-cli` is installed globally via npm and that an `INBOUND_API_KEY` is available.
  • Does not cover sending or composing replies beyond a brief mention of replying in the use cases.
  • Authentication and network failure handling are not described in detail.
When to use it

Use it when an agent needs to check, triage, or read email from the command line with a stable default mailbox.

When not to use it

Skip it when the task is unrelated to Inbound email or the environment cannot run a globally installed Node CLI.

Security analysis

Caution
Quality score82/100

Nothing in the skill is destructive, obfuscated, or exfiltrating: it only documents straightforward `inbound` CLI subcommands for mailbox and email management, plus reading an API key from an environment variable. The residual risk is operational rather than malicious — a globally installed, unpinned npm dependency and an API key that the agent is told to request from the user. That places it at 'caution' rather than 'safe', but it is legitimate tooling used for its stated purpose.

Findings
  • •Instructs a global install of a third-party npm package (`npm i -g inbound-cli`) with no version pinning or integrity check
  • •Requires handling a sensitive credential (`INBOUND_API_KEY`) and having the user export it into the environment
  • •Grants the agent read/write access to a real mailbox (listing, reading, marking read), so a misdirected command could touch the wrong account
How this analysis is made

Examples

Triage unread inbox
Check my Inbound inbox and list the unread emails from the last week, then read the ones that look like invoices.
Set up agent mailbox
Initialize an Inbound CLI mailbox profile for my agent named Research Bot with the email research@example.com and set it as default.
Review a thread
List the most recent Inbound mail threads and open the latest one so I can see the full conversation.

name: inbound-cli description: Use the Inbound CLI to manage mailbox profiles, list and read emails, and keep an agent's default mailbox context between sessions.

inbound-cli

Use this skill to operate email workflows through the inbound CLI with a persistent mailbox profile (inbound.json).

Setup

  • Install globally: npm i -g inbound-cli
  • Use command name: inbound

When to use

  • User asks to check inbox mail, triage unread items, read email threads, or reply using Inbound CLI.
  • User asks to set up or switch mailbox defaults for the agent.
  • User asks to filter email activity by mailbox address/domain.
  • User asks for command-line email operations instead of direct API calls.

Do not use this skill when the task is unrelated to Inbound email workflows.

Instructions

  1. Validate CLI availability.

    • Ensure global install exists: npm i -g inbound-cli.
    • Verify command works: inbound help.
  2. Validate auth before mailbox work.

    • Check INBOUND_API_KEY exists.
    • If missing, ask the user for the API key or ask them to export it.
  3. Ensure mailbox profile exists for the agent.

    • If no config exists, initialize: inbound mailbox init.
    • Add mailbox profile for the agent identity:
      • inbound mailbox add <key> --name "<Agent Name>" --email <agent@email> [--domain <domain>]
    • Set default mailbox:
      • inbound mailbox use <key>
  4. Default mailbox-first inbox workflow.

    • List inbox (defaults to received type):
      • inbound emails list --limit 25
    • Read a specific email:
      • inbound emails get <email_id>
    • Mark handled email as read:
      • inbound emails update <email_id> --is_read true
  5. Use filters intentionally.

    • Narrow by status/search/time:
      • inbound emails list --status unread --search "invoice" --time-range 7d
    • Override mailbox filters for one run:
      • inbound emails list --address user@example.com
      • inbound emails list --domain example.com
    • Include non-received types when needed:
      • inbound emails list --type sent
      • inbound emails list --type scheduled
      • inbound emails list --type all
  6. Find mailbox profiles by identity.

    • inbound mailbox find --address user@example.com
    • inbound mailbox find --domain example.com
  7. Use thread view for conversation context.

    • inbound mail threads list --limit 20
    • inbound mail threads get <thread_id>
  8. Automation and parsing mode.

    • Use --json when the output needs machine parsing.
    • Use human mode by default for operator readability.

Expected behavior

  • Always start from the configured default mailbox unless explicit filter overrides are provided.
  • Preserve mailbox context so future runs use the same identity.
  • Keep user informed when filters broaden scope (for example --type all).

Quick command cheatsheet

inbound mailbox list
inbound mailbox show
inbound emails list --status unread --limit 25
inbound emails get <email_id>
inbound emails update <email_id> --is_read true
inbound mail threads list --limit 20
inbound mail threads get <thread_id>
inbound emails list --json

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/inbound-cli-mrwakc72/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/inbound-cli-mrwakc72' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/inbound-cli-mrwakc72/download' --output '.skill-downloads/inbound-cli-mrwakc72/SKILL.md.part' && mv '.skill-downloads/inbound-cli-mrwakc72/SKILL.md.part' '.skill-downloads/inbound-cli-mrwakc72/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Original excerpt: Setup
  • Install globally: npm i -g inbound-cli
  • Use command name: inbound

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/inbound-cli-mrwakc72/SKILL.md' && test -s '.skill-downloads/inbound-cli-mrwakc72/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/inbound-cli' && cp -R '.skill-downloads/inbound-cli-mrwakc72' '.claude/skills/inbound-cli'

Cursor
test -f '.skill-downloads/inbound-cli-mrwakc72/SKILL.md' && test -s '.skill-downloads/inbound-cli-mrwakc72/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/inbound-cli' && cp -R '.skill-downloads/inbound-cli-mrwakc72' '.cursor/skills/inbound-cli'

Codex
test -f '.skill-downloads/inbound-cli-mrwakc72/SKILL.md' && test -s '.skill-downloads/inbound-cli-mrwakc72/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/inbound-cli' && cp -R '.skill-downloads/inbound-cli-mrwakc72' '.agents/skills/inbound-cli'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/inbound-cli-mrwakc72'

openskills read 'inbound-cli-mrwakc72'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/inbound-cli-mrwakc72/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills