Each autark user has their own AgentMail inbox (e.g. kushal@kushalsm.com, laksh@kushalsm.com) provisioned at onboarding. Use the inbox tied to this user's autark login for all outreach and signups.
Auth — read the token from ~/.autark/credentials.json
The autark installer drops a per-inbox API key into ~/.autark/credentials.json (agentmail_token field). The same file holds the inbox email under agentmail_email. Every send goes through this token; it's scoped to one inbox so it can't read other users' mail.
Standard prelude for any shell call:
AGENTMAIL_API_KEY="${AGENTMAIL_API_KEY:-$(jq -r .agentmail_token ~/.autark/credentials.json 2>/dev/null)}"
AGENTMAIL_EMAIL="${AGENTMAIL_EMAIL:-$(jq -r .agentmail_email ~/.autark/credentials.json 2>/dev/null)}"
[ -z "$AGENTMAIL_API_KEY" ] && { echo "no agentmail token — run: autark onboard agentmail"; exit 1; }
[ -z "$AGENTMAIL_EMAIL" ] && { echo "no agentmail email — credentials missing agentmail_email"; exit 1; }
AGENTMAIL_API_KEY and AGENTMAIL_EMAIL are also honored from the environment (useful for one-off debugging) — credentials.json is just the default.
More from kiluazen/skills
outreach
How to write cold messages, posts, and replies. Voice, tone, and style rules for all outbound communication — email, Reddit, HN, Twitter, LinkedIn.
8plumcake
Flag a systemic blocker to the human running you — a missing credential, a dead browser session, an API gate you can't get past. Things you can't fix from inside the sandbox. Not for asking permission or chatting; only for "hey, this is broken at the system level, I need you to fix it so I (and your other agents) stop hitting it.
8autark
Autark — running a market-discovery loop for a product, posting outreach, and recording it. Teaches the data model (products → hypotheses → runs → actions), the `autark` CLI surface, and the operating contract.
7email-finder
Find a real person's work email from minimal input (name, name+company, GitHub handle, LinkedIn URL, Twitter handle). Use before sending outbound — never guess-and-send. Covers the free path (GitHub commits, Google dorking, Gmail-compose profile-pic trick, permutator+verifier) and the paid path (Apollo, Hunter, Crustdata) with when to use each.
7chrome-relay
Use when an agent needs to operate the user's real Chrome session — listing tabs, reading interactive elements, clicking, filling, typing into rich editors, pressing keys, evaluating JS, and capturing screenshots. All actions go through CDP and run on backgrounded tabs without stealing focus.
7