[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DYFPGK36Q0S7R8YXS2ZMGE":3,"skill-same:01M7DYFPGK36Q0S7R8YXS2ZMGE":54},{"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},"01M7DYFPGK36Q0S7R8YXS2ZMGE","content-planning",null,"Use when deciding what content to write: matching topics to buyer stages, choosing between searchable and shareable pieces, and grouping topics into pillars and clusters.","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\u002Fcontent-marketer\u002Fskills\u002Fcontent-planning\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Use when deciding what content to write: matching topics to buyer stages, choosing between searchable and shareable pieces, and grouping topics into pillars and clusters.\"\n---\n\n# Content planning\n\nWhen deciding what to write, before writing it:\n\n- Start from why someone buys, not from a keyword list. A topic earns a place if it either answers a question a buyer actually has or shows the product doing the thing they're stuck on. Volume without either is traffic that never converts.\n- Know which kind of piece you're writing. **Searchable** content answers a query someone typed and lives or dies on being findable: it needs the question in the title, a direct answer near the top, and durable structure. **Shareable** content earns attention on its own: an opinion, original data, a story with a specific outcome. Optimizing one as though it were the other produces a piece that does neither.\n- Match the piece to where the reader is:\n  - **Unaware of the problem**: symptoms, not solutions. Name the thing they're experiencing.\n  - **Comparing approaches**: how the options actually differ, including where yours is the wrong choice.\n  - **Comparing products**: specifics. Pricing, migration, limits, what breaks.\n  - **Already sold**: implementation, onboarding, getting to value.\n- Group topics rather than listing them. Pick a few pillars the team wants to be known for, then write clusters of related pieces under each that link to one another. Ten pieces on three pillars beats thirty scattered ones, because the cluster compounds and the scatter doesn't.\n- Check a topic isn't already covered before adding it. Two pieces answering the same question split the traffic and neither wins; strengthening the existing piece usually beats writing a second.\n- Prioritize honestly. The best next piece is the one with real demand, a clear tie to the product, and evidence you can actually get. When you're missing the evidence, either go find it or pick a different topic.\n\nRead `references\u002Fbuyer-stage-topics.md` for questions to mine at each stage and where to find them.\n","# Content planning\n\nWhen deciding what to write, before writing it:\n\n- Start from why someone buys, not from a keyword list. A topic earns a place if it either answers a question a buyer actually has or shows the product doing the thing they're stuck on. Volume without either is traffic that never converts.\n- Know which kind of piece you're writing. **Searchable** content answers a query someone typed and lives or dies on being findable: it needs the question in the title, a direct answer near the top, and durable structure. **Shareable** content earns attention on its own: an opinion, original data, a story with a specific outcome. Optimizing one as though it were the other produces a piece that does neither.\n- Match the piece to where the reader is:\n  - **Unaware of the problem**: symptoms, not solutions. Name the thing they're experiencing.\n  - **Comparing approaches**: how the options actually differ, including where yours is the wrong choice.\n  - **Comparing products**: specifics. Pricing, migration, limits, what breaks.\n  - **Already sold**: implementation, onboarding, getting to value.\n- Group topics rather than listing them. Pick a few pillars the team wants to be known for, then write clusters of related pieces under each that link to one another. Ten pieces on three pillars beats thirty scattered ones, because the cluster compounds and the scatter doesn't.\n- Check a topic isn't already covered before adding it. Two pieces answering the same question split the traffic and neither wins; strengthening the existing piece usually beats writing a second.\n- Prioritize honestly. The best next piece is the one with real demand, a clear tie to the product, and evidence you can actually get. When you're missing the evidence, either go find it or pick a different topic.\n\nRead `references\u002Fbuyer-stage-topics.md` for questions to mine at each stage and where to find them.\n",{"description":7},"main","2e99dc3564dd243224e74b970a3c990b625cc8c0","apps\u002Ftemplates\u002Fmarketing-team-eve-template\u002Fagent\u002Fsubagents\u002Fcontent-marketer\u002Fskills\u002Fcontent-planning",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 content-planning",{"tool":40,"command":41},"bunx","bunx skills add vercel\u002Feve --skill content-planning",{"tool":43,"command":44},"pnpm","pnpm dlx skills add vercel\u002Feve --skill content-planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fmarketing-team-eve-template\u002Fagent\u002Fsubagents\u002Fcontent-marketer\u002Fskills\u002Fcontent-planning\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fbuyer-stage-topics.md","REFERENCE","参考文档",2240,"https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fmarketing-team-eve-template\u002Fagent\u002Fsubagents\u002Fcontent-marketer\u002Fskills\u002Fcontent-planning\u002Freferences\u002Fbuyer-stage-topics.md",[55,62,68,75,82,89],{"skillNo":56,"name":57,"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},"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":63,"name":57,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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",[],[]]