shared-resend-portfolio skillA
shared-resend-portfolio is agent-read markdown (skill) from j-star-films-studios/vibecode-protocol-suite: Reuse one Resend account and one verified sender domain across multiple branded products, especially for solo developers and free-tier portfolios. Use when adding transactional email to another app without creating a separate Resend account or verified domain, while preserving per-product identity, recipients, Reply-To routing, templates, security boundaries, delivery reliability, and awareness of a shared sending quota..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Shared Resend Portfolio
Implement email for multiple products through one Resend account and verified domain. Optimize for a solo developer or small portfolio using the free tier without making every app look like the same product.
## Core model
Share infrastructure, not product identity:
```text
One Resend account
└── Existing verified sender domain
├── Product A sender identity
├── Product B sender identity
└── Product C sender identity
```
Each app keeps its own:
- sender display name
- destination inbox
- Reply-To routing
- subject conventions
- branded HTML and plain-text templates
- deployment environment variables
- delivery logs and failure behavior
All apps share the account-level free-tier quota and verified-domain reputation.
## Portfolio discovery
Before implementation:
1. Inspect the target app and any sibling app with a working Resend setup.
2. Identify the canonical Resend account and already verified domain.
3. Confirm the product display name, shared sender mailbox, internal recipient, support Reply-To inbox, and expected email types.
4. Confirm whether the target deployment already has a Resend API key.
…Read the whole file at its exact version.
How to install
mdr add j-star-films-studios/vibecode-protocol-suite/shared-resend-portfolio@git:20260820.4dbe9e4mdr add j-star-films-studios/vibecode-protocol-suite/shared-resend-portfolio@sha256:9658b5a6de65f03cPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_yut42f5atdmzup4w)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6183 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
j-star-films-studios/vibecode-protocol-suite · 24 stars · license ISC · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yut42f5atdmzup4w GET https://markdownregistry.com/api/v1/resolve?ref=j-star-films-studios/vibecode-protocol-suite/shared-resend-portfolio GET https://markdownregistry.com/api/v1/blob/9658b5a6de65f03c0585e111225ee39e02e2cbd1920ac2544ebb6713364e20c1
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.