mercury-shared
Mercury Shared Rules
The mercury CLI handles authentication on its own. If MERCURY_API_KEY is set in the environment, the CLI uses it as a bearer token; otherwise it falls back to the OAuth token saved by mercury login. Either way, skills never construct auth headers or pass --api-key themselves — just invoke mercury <command> and the CLI picks the right credential. To check current auth state, run mercury status. If a call fails with 401/403, tell the user to either export MERCURY_API_KEY or run mercury login; do not retry.
These rules cover the few things that aren't obvious from mercury --help.
Use --format jsonl for reads
jsonl collapses the response onto a single line with no indentation whitespace — the cheapest format to load into context. Use it for every read this skill performs:
mercury accounts list --max-items -1 --format jsonl
mercury transactions list --start 2026-04-01 --end 2026-04-29 --status sent --max-items -1 --format jsonl
Pair it with --transform (GJSON syntax — see https://github.com/tidwall/gjson/blob/master/SYNTAX.md) when you only need a few fields: