ben-agent-email_skill

This skill manages ben-agent@zerofinance.ai email flows using Resend, enabling inbound parsing, session updates, and reliable outbound replies.
  • TypeScript

186

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill different-ai/agent-bank --skill ben-agent-email

  • SKILL.md2.3 KB

Overview

This skill provides a canonical Resend-backed inbox for ben-agent@zerofinance.ai and integrates with the existing AI email pipeline. It centralizes inbound and outbound email handling for 0 Finance operations, exposing CLI-first controls and programmatic hooks. The skill enforces secure webhook verification and a predictable session-driven message model.

How this skill works

Inbound mail for the zerofinance.ai domain is routed to Resend, which posts messages to POST /api/ai-email. The webhook is verified with RESEND_WEBHOOK_SECRET before the AI pipeline parses content, updates session state, and decides whether to respond, continue, or signal an error. Outbound mail is sent through Resend with the from address "Ben Agent ben-agent@zerofinance.ai" using the resend-provider implementation.

When to use it

  • Automate handling of operational emails sent to ben-agent@zerofinance.ai
  • Route inbound messages into an AI-managed session workflow for parsing and replies
  • Send confirmations, replies, or follow-ups from the canonical agent address
  • Integrate email events into CLI-first workflows for 0 Finance operations
  • Maintain a single source of truth for message history and attachments

Best practices

  • Store credentials in the collocated .opencode/skill/ben-agent-email/.env file and never hardcode keys
  • Ensure RESEND_WEBHOOK_SECRET is set and rotation procedures are in place to keep webhooks secure
  • Use the AI email session model to track state: complete, continue, or error
  • Prefer session-based operations (create/read/update) rather than ad-hoc state outside the pipeline
  • Validate incoming webhooks and stop processing if credentials are missing

Example use cases

  • Check ben-agent@zerofinance.ai for new invoices and generate a short summary for finance
  • Automatically reply to a customer confirming receipt of their request and next steps
  • Draft a follow-up asking for missing bank details when a payment request is incomplete
  • Persist attachments from inbound messages and surface them in the session history
  • Integrate inbound email events with CLI tools to trigger operational workflows

FAQ

RESEND_API_KEY, RESEND_WEBHOOK_SECRET, EMAIL_PROVIDER=resend, and AI_EMAIL_INBOUND_DOMAIN=zerofinance.ai must be set in .opencode/skill/ben-agent-email/.env.

What happens if credentials are missing?

The skill will prompt for the missing credentials and stop processing. Do not proceed or invent keys without explicit access.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational