[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DYG279WMZDA8R7P1KYRRBA":3,"skill-same:01M7DYG279WMZDA8R7P1KYRRBA":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7DYG279WMZDA8R7P1KYRRBA","resend-build",null,"Use when building, editing, or sending anything in Resend, including broadcasts, templates, segments, and contacts, or when checking what a past send did.","vercel\u002Feve","vercel","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F14985020?v=4","01M75TEEHHNJR9E6CG84ENB3MS","Vercel","01M75TEEJ5BJVTCPRH9YAWSMW4",5902,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fmarketing-team-eve-template\u002Fagent\u002Fsubagents\u002Femail\u002Fskills\u002Fresend-build\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: Use when building, editing, or sending anything in Resend, including broadcasts, templates, segments, and contacts, or when checking what a past send did.\n---\n\n# Building in Resend\n\nThe tools are discoverable but the order matters, and several of them fail in ways that are quiet rather than loud. Read this before the first call, not after a call goes wrong.\n\nResend's tools are not preloaded. Find them with `eve__search` (the query `resend__` lists only Resend's), then call one with `eve__tool` by its qualified name (`resend__\u003Ctool>`). Don't guess at a tool name or its arguments.\n\n## The build order\n\nFor a broadcast, which is one email to a segment:\n\n1. `list-domains` and pick a verified one for the from address.\n2. `list-segments` and pick the target. A broadcast requires a segment: there is no send-to-everyone option. If nothing covers the intended audience, say so and agree a segment with the user before creating one.\n3. `create-broadcast` with the name, segment, subject, and the plain text version. This does not send.\n4. `get-tiptap-json-content` with `include_schema: true`, then `compose-broadcast` to set the body.\n5. Show the user what you built: subject, preview text, from, segment and its size, and the send time.\n6. `send-broadcast`, which pauses for approval.\n\nFor a template, which is a reusable email with variables:\n\n1. `create-template`. It is created as a draft.\n2. `get-tiptap-json-content` with `include_schema: true`, then `compose-template`.\n3. `publish-template`. A template cannot be used for sending until it is published, and re-publishing is how an edit goes live.\n\n## The traps\n\n**Always read before you compose.** Call `get-tiptap-json-content` before `compose-broadcast` or `compose-template`, even when you are certain the body is empty. Someone may have edited it in the dashboard, and composing without reading overwrites their work.\n\n**Two content modes, and switching loses work.** Content set with `compose-*` is editable in the Resend visual editor; content set with `update-broadcast`'s `html` and `text` fields is not. Moving between the two modes is lossy. Prefer `compose-*` so the user can refine it themselves, and if raw HTML is genuinely wanted, ask before switching an existing body over.\n\n**`update-broadcast` needs fields you have to fetch.** The API requires `from` and `segmentId` to be set, and a broadcast created in the dashboard may have neither. Call `get-broadcast` first and include them in the update if they are missing, or the call fails on something unrelated to what you were changing.\n\n**Personalization needs fallbacks.** Placeholders use triple braces: `{{{FIRST_NAME}}}`, `{{{LAST_NAME}}}`, `{{{EMAIL}}}`, and `{{{RESEND_UNSUBSCRIBE_URL}}}`. `FIRST_NAME` and `LAST_NAME` take a fallback with a pipe, as in `{{{FIRST_NAME|there}}}`. Use it every time. Without one, contacts with no first name get \"Hi ,\".\n\n**Include the unsubscribe URL.** `{{{RESEND_UNSUBSCRIBE_URL}}}` is how a visible unsubscribe link gets into the body, and marketing mail needs one. See the `deliverability` skill for why this is a hard requirement rather than a courtesy.\n\n**Ids come in several forms.** Most tools accept a UUID, and many also accept a template alias or a Resend dashboard URL. Pass whatever the user gave you rather than trying to convert it.\n\n## Sending and the approval gate\n\nSending a broadcast, an email, or a batch pauses for the user's approval, and so do deletes and changes to a contact's topic subscriptions. This is deliberate. Do not try to route around a gate by using a different tool to achieve the same effect.\n\n- Say what the approval covers before you ask: the segment, the number of contacts, and the timing. That sentence is what the user is agreeing to.\n- Never test by sending to a real segment. Send a one-off with `send-email` to an address the user names, or have them preview it in the dashboard.\n- `send-broadcast` takes an optional `scheduledAt`. A scheduled send can be cancelled and an immediate one cannot, so when the user is hesitating, schedule it and tell them when the decision closes.\n- `cancel-email` cancels a scheduled one-off. There is a window, not an unlimited one.\n- If approval is denied, stop. Ask what to change rather than reissuing the call.\n\n## Reading what happened\n\n`get-email` and `list-emails` carry delivery outcomes for one-off sends, `get-broadcast` carries a broadcast's state, and `list-logs` and `get-log` carry the API request and response when something failed at the call level rather than at the delivery level.\n\nReport the numbers you read, over the volume you read them across. Do not convert a delivery count into a claim about inbox placement: `deliverability` covers what those numbers do and do not prove.\n","# Building in Resend\n\nThe tools are discoverable but the order matters, and several of them fail in ways that are quiet rather than loud. Read this before the first call, not after a call goes wrong.\n\nResend's tools are not preloaded. Find them with `eve__search` (the query `resend__` lists only Resend's), then call one with `eve__tool` by its qualified name (`resend__\u003Ctool>`). Don't guess at a tool name or its arguments.\n\n## The build order\n\nFor a broadcast, which is one email to a segment:\n\n1. `list-domains` and pick a verified one for the from address.\n2. `list-segments` and pick the target. A broadcast requires a segment: there is no send-to-everyone option. If nothing covers the intended audience, say so and agree a segment with the user before creating one.\n3. `create-broadcast` with the name, segment, subject, and the plain text version. This does not send.\n4. `get-tiptap-json-content` with `include_schema: true`, then `compose-broadcast` to set the body.\n5. Show the user what you built: subject, preview text, from, segment and its size, and the send time.\n6. `send-broadcast`, which pauses for approval.\n\nFor a template, which is a reusable email with variables:\n\n1. `create-template`. It is created as a draft.\n2. `get-tiptap-json-content` with `include_schema: true`, then `compose-template`.\n3. `publish-template`. A template cannot be used for sending until it is published, and re-publishing is how an edit goes live.\n\n## The traps\n\n**Always read before you compose.** Call `get-tiptap-json-content` before `compose-broadcast` or `compose-template`, even when you are certain the body is empty. Someone may have edited it in the dashboard, and composing without reading overwrites their work.\n\n**Two content modes, and switching loses work.** Content set with `compose-*` is editable in the Resend visual editor; content set with `update-broadcast`'s `html` and `text` fields is not. Moving between the two modes is lossy. Prefer `compose-*` so the user can refine it themselves, and if raw HTML is genuinely wanted, ask before switching an existing body over.\n\n**`update-broadcast` needs fields you have to fetch.** The API requires `from` and `segmentId` to be set, and a broadcast created in the dashboard may have neither. Call `get-broadcast` first and include them in the update if they are missing, or the call fails on something unrelated to what you were changing.\n\n**Personalization needs fallbacks.** Placeholders use triple braces: `{{{FIRST_NAME}}}`, `{{{LAST_NAME}}}`, `{{{EMAIL}}}`, and `{{{RESEND_UNSUBSCRIBE_URL}}}`. `FIRST_NAME` and `LAST_NAME` take a fallback with a pipe, as in `{{{FIRST_NAME|there}}}`. Use it every time. Without one, contacts with no first name get \"Hi ,\".\n\n**Include the unsubscribe URL.** `{{{RESEND_UNSUBSCRIBE_URL}}}` is how a visible unsubscribe link gets into the body, and marketing mail needs one. See the `deliverability` skill for why this is a hard requirement rather than a courtesy.\n\n**Ids come in several forms.** Most tools accept a UUID, and many also accept a template alias or a Resend dashboard URL. Pass whatever the user gave you rather than trying to convert it.\n\n## Sending and the approval gate\n\nSending a broadcast, an email, or a batch pauses for the user's approval, and so do deletes and changes to a contact's topic subscriptions. This is deliberate. Do not try to route around a gate by using a different tool to achieve the same effect.\n\n- Say what the approval covers before you ask: the segment, the number of contacts, and the timing. That sentence is what the user is agreeing to.\n- Never test by sending to a real segment. Send a one-off with `send-email` to an address the user names, or have them preview it in the dashboard.\n- `send-broadcast` takes an optional `scheduledAt`. A scheduled send can be cancelled and an immediate one cannot, so when the user is hesitating, schedule it and tell them when the decision closes.\n- `cancel-email` cancels a scheduled one-off. There is a window, not an unlimited one.\n- If approval is denied, stop. Ask what to change rather than reissuing the call.\n\n## Reading what happened\n\n`get-email` and `list-emails` carry delivery outcomes for one-off sends, `get-broadcast` carries a broadcast's state, and `list-logs` and `get-log` carry the API request and response when something failed at the call level rather than at the delivery level.\n\nReport the numbers you read, over the volume you read them across. Do not convert a delivery count into a claim about inbox placement: `deliverability` covers what those numbers do and do not prove.\n",{"description":7},"main","2e99dc3564dd243224e74b970a3c990b625cc8c0","apps\u002Ftemplates\u002Fmarketing-team-eve-template\u002Fagent\u002Fsubagents\u002Femail\u002Fskills\u002Fresend-build",656,"https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve","https:\u002F\u002Feve.dev","https:\u002F\u002Fgithub.com\u002Fvercel","https:\u002F\u002Fvercel.com","Agentic infrastructure for every app and agent.","2026-11-15 05:08:34",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add vercel\u002Feve --skill resend-build",{"tool":40,"command":41},"bunx","bunx skills add vercel\u002Feve --skill resend-build",{"tool":43,"command":44},"pnpm","pnpm dlx skills add vercel\u002Feve --skill resend-build","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fmarketing-team-eve-template\u002Fagent\u002Fsubagents\u002Femail\u002Fskills\u002Fresend-build\u002FSKILL.md",true,[],[49,56,62,69,76,83],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7DYJETPKENT6T9THCB7WKFD","writing-quality","The review rubric: writing-quality rules and reference lists for judging a content draft, covering AI-sounding phrasing, bloated wording, structure, and web-content specs. Load at the start of every review.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fsubagents\u002Freviewer\u002Fskills\u002Fwriting-quality\u002FSKILL.md",[],[],{"skillNo":57,"name":51,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7DYJAZM6Y5VNF2PCM01N145","Writing-quality guardrails for any prose the agent drafts or edits: blog posts, page copy, Notion drafts, release notes, marketing text. Use this skill whenever writing or revising content meant for humans to read, to keep the prose natural, plain, and free of AI-sounding phrasing. Not needed for code, queries, or structural CMS work.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fwriting-quality\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7DYJ40G4YADA5P8YAEQ7W7F","seo-aeo-best-practices","SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces. Use this skill when implementing page SEO, technical SEO, schema markup, international SEO, AI-overview readiness, or improving content for Google, ChatGPT, Perplexity, and similar assistants.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fseo-aeo-best-practices\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7DYHX5JXJFHF2DZV64VFC13","sanity-best-practices","Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this skill whenever working with Sanity schemas, defineType or defineField, GROQ or defineQuery, content modeling, Presentation or preview setups, Sanity-powered frontend integrations, Sanity Functions, documentEventHandler, defineDocumentFunction, defineMediaLibraryAssetFunction, @sanity\u002Ffunctions, @sanity\u002Fblueprints, sanity.blueprint.ts, event-driven content automation, or when reviewing and fixing a Sanity codebase.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fsanity-best-practices\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7DYHQG96APC7EV3FANC90WX","portable-text-serialization","Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fportable-text-serialization\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7DYHJJ89WGRXXVWJAQNQW9M","portable-text-conversion","Convert HTML and Markdown content into Portable Text blocks for Sanity. Use when migrating content from legacy CMSs, importing HTML or Markdown into Sanity, building content pipelines that ingest external content, converting rich text between formats, or programmatically creating Portable Text documents. Covers @portabletext\u002Fmarkdown (markdownToPortableText), @portabletext\u002Fblock-tools (htmlToBlocks), custom deserializers, and the Portable Text specification for manual block construction.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fportable-text-conversion\u002FSKILL.md",[],[]]