[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75TGFG5QNYCZ09K0Y0F1NSC":3,"skill-same:01M75TGFG5QNYCZ09K0Y0F1NSC":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},"01M75TGFG5QNYCZ09K0Y0F1NSC","investigate",null,"Investigate an issue report, or analyze the constraints of a proposed change, with strict, evidence-driven diagnosis.","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\u002Fpackages\u002Feve-code\u002Fextension\u002Fskills\u002Finvestigate\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: investigate\ndescription: Investigate an issue report, or analyze the constraints of a proposed change, with strict, evidence-driven diagnosis.\n---\n\n# Investigate\n\nDetermine unambiguously what the report means from the system's perspective. Collect the available evidence for it, such as error output, logs, and failing inputs, and check what changed recently in the affected area. Then establish whether it is real with a precise reproduction. If not, pause and report that result.\n\nStart at the observed effect and identify the code paths directly responsible. Climb one layer at a time across call frames, processes, network hops, and persistence boundaries. Go only as wide and deep as the evidence requires.\n\nKeep an explicit hypothesis at every branch and try to disprove it. Prefer the simplest explanation that accounts for all observed evidence. Do not jump to solutions before diagnosis.\n\nBefore proposing a change, name the fundamental constraints, including the relevant data flows and the entry points that reach the affected code paths.\n\n## Standards\n\n- Resolve every cited call frame and reference.\n- Distinguish observations, inferences, and unknowns.\n- Map relevant dependencies and identify other reports or users affected by the same mechanism.\n- Question assumptions about timing, state, identity, retries, and execution boundaries.\n- Stop when required evidence is unavailable rather than filling gaps with guesses.\n\n## Questions for every hypothesis\n\n- How can this be disproved?\n- Is there a simpler or more likely explanation?\n- Which source references remain unresolved?\n- Do the surrounding code and runtime state support the conclusion?\n- Does this explain both why the behavior occurs and why it began now?\n\nReturn compact but complete evidence, the diagnosed mechanism, a decision tree when useful, and the smallest prognosis justified by the evidence.\n","# Investigate\n\nDetermine unambiguously what the report means from the system's perspective. Collect the available evidence for it, such as error output, logs, and failing inputs, and check what changed recently in the affected area. Then establish whether it is real with a precise reproduction. If not, pause and report that result.\n\nStart at the observed effect and identify the code paths directly responsible. Climb one layer at a time across call frames, processes, network hops, and persistence boundaries. Go only as wide and deep as the evidence requires.\n\nKeep an explicit hypothesis at every branch and try to disprove it. Prefer the simplest explanation that accounts for all observed evidence. Do not jump to solutions before diagnosis.\n\nBefore proposing a change, name the fundamental constraints, including the relevant data flows and the entry points that reach the affected code paths.\n\n## Standards\n\n- Resolve every cited call frame and reference.\n- Distinguish observations, inferences, and unknowns.\n- Map relevant dependencies and identify other reports or users affected by the same mechanism.\n- Question assumptions about timing, state, identity, retries, and execution boundaries.\n- Stop when required evidence is unavailable rather than filling gaps with guesses.\n\n## Questions for every hypothesis\n\n- How can this be disproved?\n- Is there a simpler or more likely explanation?\n- Which source references remain unresolved?\n- Do the surrounding code and runtime state support the conclusion?\n- Does this explain both why the behavior occurs and why it began now?\n\nReturn compact but complete evidence, the diagnosed mechanism, a decision tree when useful, and the smallest prognosis justified by the evidence.\n",{"name":5,"description":7},"main","a318dcf054343b7a9007dd4e4367ac19374a6809","packages\u002Feve-code\u002Fextension\u002Fskills\u002Finvestigate",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 investigate",{"tool":40,"command":41},"bunx","bunx skills add vercel\u002Feve --skill investigate",{"tool":43,"command":44},"pnpm","pnpm dlx skills add vercel\u002Feve --skill investigate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fpackages\u002Feve-code\u002Fextension\u002Fskills\u002Finvestigate\u002FSKILL.md",true,[],[49,57,63,70,77,84],{"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":56},"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",[],[],"2026-11-15 14:19:17",{"skillNo":58,"name":51,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":56},"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":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":56},"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":56},"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":56},"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":56},"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",[],[]]