[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DYEE0NEA26E67WD84CK0AK":3,"skill-same:01M7DYEE0NEA26E67WD84CK0AK":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},"01M7DYEE0NEA26E67WD84CK0AK","hypothesis-validation",null,"Given a hypothesis, take the necessary investigation steps to validate, invalidate, or reach an inconclusive result for the hypothesis.","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\u002Feve-sre-agent-template\u002Fagent\u002Fskills\u002Fhypothesis-validation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: hypothesis-validation\ndescription: Given a hypothesis, take the necessary investigation steps to validate, invalidate, or reach an inconclusive result for the hypothesis.\n---\n\n# Hypothesis Validation\n\nInvestigate the related context for a given hypothesis holistically. Record evidence and conclude whether the hypothesis is validated, invalidated, or inconclusive.\n\n## Procedure\n\n### 1: Context hydration\n\nScan the conversation for:\n\n- alert or incident metadata\n- service names, environment names, region hints\n- timestamps or time ranges\n- symptoms (errors, latency, downtime)\n- links to external pieces of context\n\nThe goal here is getting a quick hydration of possibly relevant context for the hypothesis before doing a deeper dive.\n\n### 2: Dig deep\n\nAfter identifying possibly relevant context, dig deep into the most relevant pieces of context to gather enough evidence to validate, invalidate, or reach an inconclusive result for the hypothesis.\n\nRecord findings as you dig. Follow the Evidence rules in the agent instructions. Call `evidence_record`, `evidence_remove`, and `evidence_list` as those rules say.\n\n### 3: Draw conclusions\n\nAfter gathering enough evidence, draw a final conclusion about the hypothesis. The conclusion for the hypothesis should be \"validated\", \"invalidated\", or \"inconclusive\". Include a description that cites the most important pieces of evidence used to draw the conclusion.\n\n## Result\n\nA synthesized conclusion for the hypothesis.\n\n## Boundaries\n\n- Do not use this skill to run a full investigation. Use the deep investigation skill.\n","# Hypothesis Validation\n\nInvestigate the related context for a given hypothesis holistically. Record evidence and conclude whether the hypothesis is validated, invalidated, or inconclusive.\n\n## Procedure\n\n### 1: Context hydration\n\nScan the conversation for:\n\n- alert or incident metadata\n- service names, environment names, region hints\n- timestamps or time ranges\n- symptoms (errors, latency, downtime)\n- links to external pieces of context\n\nThe goal here is getting a quick hydration of possibly relevant context for the hypothesis before doing a deeper dive.\n\n### 2: Dig deep\n\nAfter identifying possibly relevant context, dig deep into the most relevant pieces of context to gather enough evidence to validate, invalidate, or reach an inconclusive result for the hypothesis.\n\nRecord findings as you dig. Follow the Evidence rules in the agent instructions. Call `evidence_record`, `evidence_remove`, and `evidence_list` as those rules say.\n\n### 3: Draw conclusions\n\nAfter gathering enough evidence, draw a final conclusion about the hypothesis. The conclusion for the hypothesis should be \"validated\", \"invalidated\", or \"inconclusive\". Include a description that cites the most important pieces of evidence used to draw the conclusion.\n\n## Result\n\nA synthesized conclusion for the hypothesis.\n\n## Boundaries\n\n- Do not use this skill to run a full investigation. Use the deep investigation skill.\n",{"name":5,"description":7},"main","2e99dc3564dd243224e74b970a3c990b625cc8c0","apps\u002Ftemplates\u002Feve-sre-agent-template\u002Fagent\u002Fskills\u002Fhypothesis-validation",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 hypothesis-validation",{"tool":40,"command":41},"bunx","bunx skills add vercel\u002Feve --skill hypothesis-validation",{"tool":43,"command":44},"pnpm","pnpm dlx skills add vercel\u002Feve --skill hypothesis-validation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Feve-sre-agent-template\u002Fagent\u002Fskills\u002Fhypothesis-validation\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",[],[]]