research-crawl-email

Research Crawl Email

Argument: $ARGUMENTS (required, see Runtime Inputs)

If $ARGUMENTS is empty or missing required fields, STOP and report which fields are absent.

---

Preamble

Runtime Inputs

Parse from $ARGUMENTS:

--senders=[EMAIL1,EMAIL2,...]   [JSON-style array of exact RFC-5322 email addresses, non-empty; display names not supported. Singular invocation expressed as a single-element array.]
--raw-output-dir={PATH}          [absolute path to a directory where per-sender rendered markdown files will be written]

# Optional power params (omit when not needed):
--days={N}                       [positive integer time window in days; default 1]
--max-per-sender={N}             [per-sender message cap; default 10; truncates newest-first]

Validation rules (executed before §1.0):

• --senders and --raw-output-dir are mandatory. If either missing, STOP and report which is absent.
• --senders must parse as a JSON array of strings, non-empty. Reject otherwise (senders-malformed).
• Each entry in --senders must match RFC-5322 email shape (<local>@<host> with at least one . in host). First failing entry → STOP and report the offending value (senders-malformed).
• --raw-output-dir must be absolute. Reject relative paths (callers own path resolution).
• --days must parse as positive integer when supplied; default 1.
• --max-per-sender must parse as positive integer when supplied; default 10.

If any validation fails, STOP and report which field failed.

Global References

GMAIL_SEARCH_TOOL  = mcp__claude_ai_Gmail__search_threads
GMAIL_GET_THREAD   = mcp__claude_ai_Gmail__get_thread

The leaf composes these two MCP tools directly in the caller's context. Both require harness permission approval on first use per context, any caller may hit the prompt on its first invocation per session; surface which tool needs approval and re-invoke after the user grants it.

Caller Isolation

Pure primitive, no agent spawn, no pipeline agents, no telemetry. The skill runs the Gmail search + per-thread body fetch + render directly in the invoking context; the caller absorbs the Gmail thread context cost (full thread bodies land in the caller's window). Callers crawling many senders, or composing this leaf alongside other work, wrap the invocation in their own isolation: