[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79XH436RGQRMTM14TEP8VRB":3,"skill-same:01M79XH436RGQRMTM14TEP8VRB":89},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M79XH436RGQRMTM14TEP8VRB","vercel-docs",null,"Look up authoritative, up-to-date Vercel documentation covering deployments, builds, Functions, Fluid Compute, CDN\u002Fcaching, environment variables, domains, the Vercel CLI, REST API, Security\u002FFirewall, Observability, Storage, AI SDK\u002FGateway, and the kb troubleshooting guides. Use when the user asks how a Vercel feature works, what a vercel.json field does, how to configure deploys\u002Ffunctions\u002Fcaching\u002Fenv vars, when troubleshooting a Vercel build or runtime error, or when you need to cite current official docs rather than rely on training-cutoff knowledge.","MacHu-GWU\u002Fshsk_vercel-project","MacHu-GWU","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6800411?v=4","01M79BMG0V767YAMAMTG1ZQ7FY","Sanhe Hu","01M79XGJ8JEW3S85HM32XX4VM7",0,"MIT","https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fshsk_vercel-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvercel\u002Fskills\u002Fvercel-docs\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vercel-docs\ndescription: Look up authoritative, up-to-date Vercel documentation covering deployments, builds, Functions, Fluid Compute, CDN\u002Fcaching, environment variables, domains, the Vercel CLI, REST API, Security\u002FFirewall, Observability, Storage, AI SDK\u002FGateway, and the kb troubleshooting guides. Use when the user asks how a Vercel feature works, what a vercel.json field does, how to configure deploys\u002Ffunctions\u002Fcaching\u002Fenv vars, when troubleshooting a Vercel build or runtime error, or when you need to cite current official docs rather than rely on training-cutoff knowledge.\nargument-hint: '[topic or doc title]'\nallowed-tools: Bash(python3 *)\n---\n\n# Vercel Docs\n\nAnswers Vercel questions from the official docs on demand: searches a cached copy of the\n202 KB `llms.txt` index (only matching lines ever reach context), then fetches matching\npages as raw markdown. Always prefer this skill over recalling Vercel docs from memory —\nVercel ships changes weekly and model knowledge about it goes stale fast (Edge Functions,\nVercel Postgres\u002FKV, and default runtimes have all changed).\n\nIf the user passed an argument (`$ARGUMENTS`), treat it as the topic. Otherwise infer it\nfrom the conversation.\n\n## When to use this skill\n\n- Deployments, builds, Functions, Fluid Compute, Cron Jobs, Middleware\n- CDN\u002Fcaching, ISR, Image Optimization, domains, `vercel.json` configuration\n- CLI commands, REST API, Security\u002FFirewall, Observability, Storage\n- AI SDK\u002FGateway\u002FMCP, and `kb` troubleshooting guides for build\u002Fruntime errors\n\nOut of scope: Next.js framework APIs proper (routing, data fetching, etc.) — prefer\nnextjs.org for those; this index covers Next.js only as it runs *on* Vercel.\n\n## How this site works\n\nMeasured 2026-07-31; full fact sheet in [references\u002Fmechanism.md](references\u002Fmechanism.md).\n\n- **Index**: `https:\u002F\u002Fvercel.com\u002Fllms.txt` — 202,696 B, 1406 entries, 20 sections, 13%\n  with prose descriptions (1% terse, 86% bare title-only).\n- **Coverage**: the index is the site's own page list (leaf-level), not a curated hub —\n  no second hop needed to find an area.\n- **Content**: every `\u002Fdocs\u002F*` and `\u002Fkb\u002F*` page has a `.md` twin — 4,991 B vs 916,350 B of\n  HTML on a sampled page (99% cheaper). Never `curl` the HTML page directly.\n- **Gotchas**: `https:\u002F\u002Fvercel.com\u002Fdocs\u002Fllms.txt` 308-redirects to the URL above (the\n  script follows redirects transparently, no special handling needed). Never fetch\n  `https:\u002F\u002Fvercel.com\u002Fdocs\u002Fllms-full.txt` — 7.66 MB, a full-text dump, not an index.\n  **Guides** (531 entries, 62 KB) has **zero** prose descriptions — grep it, never read it\n  whole.\n\n## Procedure\n\n### 1. Find candidate pages\n\n```bash\npython3 ${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fdocs_query.py search '\u003Cterm>|\u003Csynonym>|\u003Cthe word the docs would use>'\n```\n\nThe index is fetched once and cached for 24 h, so repeat queries cost no requests. Only\nmatching lines enter context — never load the whole index.\n\nRouting commands, cheapest first:\n\n| Command | Cost | Use when |\n| :--- | :--- | :--- |\n| `search '\u003Cregex>'` | ~200 tok | always start here |\n| `sections` | ~250 tok | search missed and you need the map |\n| `section '\u003Cname>'` | 200–15,600 tok | full recall inside one area (skip for **Guides**) |\n\n### 2. If the search comes back empty\n\nDo **not** conclude the topic is undocumented. Escalate:\n\n1. Widen with synonyms — the docs' word is often not the user's. A page about function\n   request timeouts is titled **\"Duration\"**, under Compute.\n2. If the query was not in English, retry with English terms. This index is English-only\n   and a non-English query scores zero matches for reasons that have nothing to do with\n   coverage.\n3. `sections`, then `section '\u003Cmost plausible>'` for full recall inside it — except\n   **Guides**, which is too large and undescribed to read whole; keep narrowing the\n   `search` pattern instead (Guides titles read like questions — search the noun, e.g.\n   `rate limit`, not the phrasing).\n4. Only then say it is not in the docs, and state what you searched.\n\nUse the section routing table below to translate a topic (including a Chinese one) into a\nsection name.\n\n### 3. Read the pages\n\n```bash\npython3 ${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fdocs_query.py get \u003Curl-from-search>\n```\n\nReturns raw markdown (~3–13 KB\u002Fpage, measured). Always pass the full URL from a `search`\nor `section` hit — Vercel renames slugs, so a remembered or guessed URL is not reliable.\n\nFetch **1–3 pages per batch**, then judge whether that answers the question. Loop if not,\nto a cap of **9 pages**. At 9 and still short, stop and tell the user what you read and\nwhat is missing — do not silently continue or fill the gap with guesses.\n\n## Section routing table\n\n20 sections. Sizes are entry counts as of the last measurement.\n\n| Section (entries) | What it covers \u002F 中文触发词 |\n| :--- | :--- |\n| **Compute** (77) | Fluid Compute, Functions, runtimes, streaming, WebSockets, Routing Middleware, Cron Jobs, OG image generation, Sandbox, Queues, Workflows, Container Registry — 函数, 定时任务, 冷启动, 中间件, 队列 |\n| **Build & Deploy** (68) | Builds, Deployments, Environment Variables, Git integrations, Deploy Hooks, Deployment Checks, Instant Rollback, Rolling Releases, Monorepos, Microfrontends, Skew Protection, Webhooks, Vercel Drop — 部署, 构建, 环境变量, 回滚, 单体仓库 |\n| **CDN** (40) | Caching, ISR, Partial Prerendering, Image Optimization, routing, system headers, Global Network & regions, custom error pages — 缓存, 图片优化, 边缘网络, 区域 |\n| **CLI** (70) | Every `vercel \u003Ccommand>` (deploy, env, dev, link, pull, logs, promote, rollback, crons, blob, sandbox, …), global options, release notes. **100% prose descriptions — `search` alone works very well here** — 命令行 |\n| **Platform** (49) | `vercel.json` Project Configuration, Projects, Domains, Limits, Glossary, Notifications, Build Output API, Checks — 项目配置, 域名, 限额 |\n| **Security** (56) | Firewall\u002FWAF, Bot Management, BotID, OIDC, RBAC, Audit Logs, networking, 2FA enforcement — 防火墙, 限流, 权限, 安全 |\n| **Observability** (52) | Logs, Tracing, Alerts, Query, Notebooks, Speed Insights, Web Analytics, Drains — 日志, 监控, 链路追踪, 性能 |\n| **AI** (168) | Vercel Agent, AI SDK, AI Gateway, MCP, Agent Resources, eve |\n| **Storage** (26) | Blob, Marketplace storage (Postgres\u002FRedis\u002Fetc.), Global Config — 存储, 数据库, 对象存储 |\n| **Access** (34) | Account management, Sign in with Vercel, SAML SSO, Directory Sync, Organizations, Deployment Protection, 2FA, Activity Log — 账号, 登录, 单点登录, 部署保护 |\n| **Integrations** (34) | Marketplace, installing\u002Fcreating integrations, CMS, commerce & payments — 集成 |\n| **Flags** (27) | Vercel Flags, Flags Explorer, Flags SDK — 功能开关, 特性标记, A\u002FB |\n| **Pricing** (35) | Plans, pricing, spend management — 价格, 计费, 用量 |\n| **Vercel for Platforms** (28) | Multi-tenant and multi-project platforms, custom domains per tenant — 多租户 |\n| **Collaboration** (16) | Comments, Draft Mode, Edit Mode, Toolbar — 协作, 评论 |\n| **Connect** (11) | Secure Compute \u002F private network connectivity — 私有网络 |\n| **Topics** (38) | Assorted cross-cutting topic pages |\n| **SDK Examples** (10) | Vercel SDK code snippets |\n| **(root)** (36) | Top-level\u002Fgetting-started pages: Getting Started, Fundamentals, Frameworks, Production Checklist, Incremental Migration |\n| **Guides** (531) | `vercel.com\u002Fkb\u002Fguide\u002F*` how-tos and troubleshooting. **Zero prose descriptions — grep only, never `section` this whole** |\n\n**Guides** is also the right place to look for error-message troubleshooting, which the\nmain `\u002Fdocs` sections often don't cover. Search it on the noun rather than the phrasing.\n\n## Context budget\n\n| Step | Cost | Notes |\n| :--- | :--- | :--- |\n| `search` | ~200 tok | only matched lines |\n| `section` | 200–15,600 tok | one area, full recall (skip for Guides) |\n| page | ~750–3,250 tok each | 1–3 per batch |\n\nTypical question: `search` + 1–2 pages ≈ under 5k tokens total. Loading the index whole\nwould be ~50,700 tokens, which is why nothing here does that. Read **one** section at a\ntime; if you cannot tell which section to read, that is a signal to search again with\nbetter terms, not to load several.\n\n## Rules\n\n- **Never invent a doc URL.** Not in the index → say so. Slugs get renamed.\n- **Never load the whole index**, and never touch `llms-full.txt` (7.66 MB).\n- **Cite the URL that served the content.**\n- **A 404 on a page URL means the index is stale** — re-run `\u002Fdocs-skill-builder check\n  .claude\u002Fskills\u002Fvercel\u002Fskills\u002Fvercel-docs`.\n- **Pass through what the docs say.** Don't blend with prior knowledge — several\n  widely-held beliefs about Vercel are now wrong (Edge Functions are de-emphasized in\n  favor of Fluid Compute, streaming\u002FSSE work on the Node.js runtime, Vercel Postgres and\n  Vercel KV are retired in favor of Marketplace integrations). Report current docs, not\n  recollection.\n","# Vercel Docs\n\nAnswers Vercel questions from the official docs on demand: searches a cached copy of the\n202 KB `llms.txt` index (only matching lines ever reach context), then fetches matching\npages as raw markdown. Always prefer this skill over recalling Vercel docs from memory —\nVercel ships changes weekly and model knowledge about it goes stale fast (Edge Functions,\nVercel Postgres\u002FKV, and default runtimes have all changed).\n\nIf the user passed an argument (`$ARGUMENTS`), treat it as the topic. Otherwise infer it\nfrom the conversation.\n\n## When to use this skill\n\n- Deployments, builds, Functions, Fluid Compute, Cron Jobs, Middleware\n- CDN\u002Fcaching, ISR, Image Optimization, domains, `vercel.json` configuration\n- CLI commands, REST API, Security\u002FFirewall, Observability, Storage\n- AI SDK\u002FGateway\u002FMCP, and `kb` troubleshooting guides for build\u002Fruntime errors\n\nOut of scope: Next.js framework APIs proper (routing, data fetching, etc.) — prefer\nnextjs.org for those; this index covers Next.js only as it runs *on* Vercel.\n\n## How this site works\n\nMeasured 2026-07-31; full fact sheet in [references\u002Fmechanism.md](references\u002Fmechanism.md).\n\n- **Index**: `https:\u002F\u002Fvercel.com\u002Fllms.txt` — 202,696 B, 1406 entries, 20 sections, 13%\n  with prose descriptions (1% terse, 86% bare title-only).\n- **Coverage**: the index is the site's own page list (leaf-level), not a curated hub —\n  no second hop needed to find an area.\n- **Content**: every `\u002Fdocs\u002F*` and `\u002Fkb\u002F*` page has a `.md` twin — 4,991 B vs 916,350 B of\n  HTML on a sampled page (99% cheaper). Never `curl` the HTML page directly.\n- **Gotchas**: `https:\u002F\u002Fvercel.com\u002Fdocs\u002Fllms.txt` 308-redirects to the URL above (the\n  script follows redirects transparently, no special handling needed). Never fetch\n  `https:\u002F\u002Fvercel.com\u002Fdocs\u002Fllms-full.txt` — 7.66 MB, a full-text dump, not an index.\n  **Guides** (531 entries, 62 KB) has **zero** prose descriptions — grep it, never read it\n  whole.\n\n## Procedure\n\n### 1. Find candidate pages\n\n```bash\npython3 ${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fdocs_query.py search '\u003Cterm>|\u003Csynonym>|\u003Cthe word the docs would use>'\n```\n\nThe index is fetched once and cached for 24 h, so repeat queries cost no requests. Only\nmatching lines enter context — never load the whole index.\n\nRouting commands, cheapest first:\n\n| Command | Cost | Use when |\n| :--- | :--- | :--- |\n| `search '\u003Cregex>'` | ~200 tok | always start here |\n| `sections` | ~250 tok | search missed and you need the map |\n| `section '\u003Cname>'` | 200–15,600 tok | full recall inside one area (skip for **Guides**) |\n\n### 2. If the search comes back empty\n\nDo **not** conclude the topic is undocumented. Escalate:\n\n1. Widen with synonyms — the docs' word is often not the user's. A page about function\n   request timeouts is titled **\"Duration\"**, under Compute.\n2. If the query was not in English, retry with English terms. This index is English-only\n   and a non-English query scores zero matches for reasons that have nothing to do with\n   coverage.\n3. `sections`, then `section '\u003Cmost plausible>'` for full recall inside it — except\n   **Guides**, which is too large and undescribed to read whole; keep narrowing the\n   `search` pattern instead (Guides titles read like questions — search the noun, e.g.\n   `rate limit`, not the phrasing).\n4. Only then say it is not in the docs, and state what you searched.\n\nUse the section routing table below to translate a topic (including a Chinese one) into a\nsection name.\n\n### 3. Read the pages\n\n```bash\npython3 ${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fdocs_query.py get \u003Curl-from-search>\n```\n\nReturns raw markdown (~3–13 KB\u002Fpage, measured). Always pass the full URL from a `search`\nor `section` hit — Vercel renames slugs, so a remembered or guessed URL is not reliable.\n\nFetch **1–3 pages per batch**, then judge whether that answers the question. Loop if not,\nto a cap of **9 pages**. At 9 and still short, stop and tell the user what you read and\nwhat is missing — do not silently continue or fill the gap with guesses.\n\n## Section routing table\n\n20 sections. Sizes are entry counts as of the last measurement.\n\n| Section (entries) | What it covers \u002F 中文触发词 |\n| :--- | :--- |\n| **Compute** (77) | Fluid Compute, Functions, runtimes, streaming, WebSockets, Routing Middleware, Cron Jobs, OG image generation, Sandbox, Queues, Workflows, Container Registry — 函数, 定时任务, 冷启动, 中间件, 队列 |\n| **Build & Deploy** (68) | Builds, Deployments, Environment Variables, Git integrations, Deploy Hooks, Deployment Checks, Instant Rollback, Rolling Releases, Monorepos, Microfrontends, Skew Protection, Webhooks, Vercel Drop — 部署, 构建, 环境变量, 回滚, 单体仓库 |\n| **CDN** (40) | Caching, ISR, Partial Prerendering, Image Optimization, routing, system headers, Global Network & regions, custom error pages — 缓存, 图片优化, 边缘网络, 区域 |\n| **CLI** (70) | Every `vercel \u003Ccommand>` (deploy, env, dev, link, pull, logs, promote, rollback, crons, blob, sandbox, …), global options, release notes. **100% prose descriptions — `search` alone works very well here** — 命令行 |\n| **Platform** (49) | `vercel.json` Project Configuration, Projects, Domains, Limits, Glossary, Notifications, Build Output API, Checks — 项目配置, 域名, 限额 |\n| **Security** (56) | Firewall\u002FWAF, Bot Management, BotID, OIDC, RBAC, Audit Logs, networking, 2FA enforcement — 防火墙, 限流, 权限, 安全 |\n| **Observability** (52) | Logs, Tracing, Alerts, Query, Notebooks, Speed Insights, Web Analytics, Drains — 日志, 监控, 链路追踪, 性能 |\n| **AI** (168) | Vercel Agent, AI SDK, AI Gateway, MCP, Agent Resources, eve |\n| **Storage** (26) | Blob, Marketplace storage (Postgres\u002FRedis\u002Fetc.), Global Config — 存储, 数据库, 对象存储 |\n| **Access** (34) | Account management, Sign in with Vercel, SAML SSO, Directory Sync, Organizations, Deployment Protection, 2FA, Activity Log — 账号, 登录, 单点登录, 部署保护 |\n| **Integrations** (34) | Marketplace, installing\u002Fcreating integrations, CMS, commerce & payments — 集成 |\n| **Flags** (27) | Vercel Flags, Flags Explorer, Flags SDK — 功能开关, 特性标记, A\u002FB |\n| **Pricing** (35) | Plans, pricing, spend management — 价格, 计费, 用量 |\n| **Vercel for Platforms** (28) | Multi-tenant and multi-project platforms, custom domains per tenant — 多租户 |\n| **Collaboration** (16) | Comments, Draft Mode, Edit Mode, Toolbar — 协作, 评论 |\n| **Connect** (11) | Secure Compute \u002F private network connectivity — 私有网络 |\n| **Topics** (38) | Assorted cross-cutting topic pages |\n| **SDK Examples** (10) | Vercel SDK code snippets |\n| **(root)** (36) | Top-level\u002Fgetting-started pages: Getting Started, Fundamentals, Frameworks, Production Checklist, Incremental Migration |\n| **Guides** (531) | `vercel.com\u002Fkb\u002Fguide\u002F*` how-tos and troubleshooting. **Zero prose descriptions — grep only, never `section` this whole** |\n\n**Guides** is also the right place to look for error-message troubleshooting, which the\nmain `\u002Fdocs` sections often don't cover. Search it on the noun rather than the phrasing.\n\n## Context budget\n\n| Step | Cost | Notes |\n| :--- | :--- | :--- |\n| `search` | ~200 tok | only matched lines |\n| `section` | 200–15,600 tok | one area, full recall (skip for Guides) |\n| page | ~750–3,250 tok each | 1–3 per batch |\n\nTypical question: `search` + 1–2 pages ≈ under 5k tokens total. Loading the index whole\nwould be ~50,700 tokens, which is why nothing here does that. Read **one** section at a\ntime; if you cannot tell which section to read, that is a signal to search again with\nbetter terms, not to load several.\n\n## Rules\n\n- **Never invent a doc URL.** Not in the index → say so. Slugs get renamed.\n- **Never load the whole index**, and never touch `llms-full.txt` (7.66 MB).\n- **Cite the URL that served the content.**\n- **A 404 on a page URL means the index is stale** — re-run `\u002Fdocs-skill-builder check\n  .claude\u002Fskills\u002Fvercel\u002Fskills\u002Fvercel-docs`.\n- **Pass through what the docs say.** Don't blend with prior knowledge — several\n  widely-held beliefs about Vercel are now wrong (Edge Functions are de-emphasized in\n  favor of Fluid Compute, streaming\u002FSSE work on the Node.js runtime, Vercel Postgres and\n  Vercel KV are retired in favor of Marketplace integrations). Report current docs, not\n  recollection.\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25},"Bash(python3 *)","[topic or doc title]","main","8062e0b06c2ef4ed173bb01086533ac237846295",".claude\u002Fskills\u002Fvercel\u002Fskills\u002Fvercel-docs","https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fshsk_vercel-project","https:\u002F\u002Fgithub.com\u002FMacHu-GWU","Founder mindset, engineer’s hands. Customers first, product second. Forward-deployed AI architect · ex-AWS · 200+ OSS libs · 4K+ commits\u002Fyr","2026-07-31 13:05:58",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add MacHu-GWU\u002Fshsk_vercel-project --skill vercel-docs",{"tool":39,"command":40},"bunx","bunx skills add MacHu-GWU\u002Fshsk_vercel-project --skill vercel-docs",{"tool":42,"command":43},"pnpm","pnpm dlx skills add MacHu-GWU\u002Fshsk_vercel-project --skill vercel-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fshsk_vercel-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvercel\u002Fskills\u002Fvercel-docs\u002FSKILL.md",true,[47,53,57,61,65,69,75,79,83],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"CHANGELOG.md","REFERENCE","参考文档",1737,"https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fshsk_vercel-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvercel\u002Fskills\u002Fvercel-docs\u002FCHANGELOG.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"README-cn.md",2521,"https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fshsk_vercel-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvercel\u002Fskills\u002Fvercel-docs\u002FREADME-cn.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"README.md",2438,"https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fshsk_vercel-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvercel\u002Fskills\u002Fvercel-docs\u002FREADME.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fmechanism-cn.md",4193,"https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fshsk_vercel-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvercel\u002Fskills\u002Fvercel-docs\u002Freferences\u002Fmechanism-cn.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fmechanism.md",4045,"https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fshsk_vercel-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvercel\u002Fskills\u002Fvercel-docs\u002Freferences\u002Fmechanism.md",{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Fdocs_query.py","SCRIPT","脚本",11423,"https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fshsk_vercel-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvercel\u002Fskills\u002Fvercel-docs\u002Fscripts\u002Fdocs_query.py",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Fdocs-source.json",231,"https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fshsk_vercel-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvercel\u002Fskills\u002Fvercel-docs\u002Fscripts\u002Fdocs-source.json",{"path":80,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":81,"sourceHtmlUrl":82},"SKILL-cn.md",11809,"https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fshsk_vercel-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvercel\u002Fskills\u002Fvercel-docs\u002FSKILL-cn.md",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"VERSION","OTHER","其他",6,"https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fshsk_vercel-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvercel\u002Fskills\u002Fvercel-docs\u002FVERSION",[90,97,104,111,118],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M79XHA2JXC2JQKW3AWS4RYV2","write-agent-skill","Claude Code Agent Skill Author Guide","https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fshsk_vercel-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwrite-agent-skill\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M79XGZX5SEDW79P8HZV30EY5","skill-subagent-design","How Agent Skills and Subagents differ and how to combine them — the skill-as-caller \u002F subagent-as-doer best practice. Use when deciding whether a task should be a skill or a subagent, or when authoring a skill and subagent that work together (e.g. a \u002Fname skill that delegates to an isolated subagent).","https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fshsk_vercel-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fskill-subagent-design\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M79XGT8J3PCE4F32CXRDT5A8","py-changelog","Maintain the release-history.rst changelog for a Python project before publishing a new version. Use when the user wants to prepare release notes, update changelog, or is about to publish\u002Ftag a new version.","https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fshsk_vercel-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpy-changelog\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M79XGMYH5GDASV3WGA2AGJWJ","maintain-claude-plugins","My personal, authoritative spec for building, developing, versioning, releasing, and wiring dependencies for my own Claude Code plugins through a split-repo plus central-marketplace setup. Use when creating a new plugin repo, laying out a plugin's .claude\u002Fskills\u002F\u003Cname>\u002F folder, writing plugin.json or marketplace.json, tagging a plugin release, wiring plugin-to-plugin dependencies, authenticating private repos, or when I ask how to structure, release, or publish my Claude Code plugin.","https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fshsk_vercel-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmaintain-claude-plugins\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M79XGKN1R2SH0WEPH6043GHN","create-sub-agent","Claude Code Sub Agent Author Guide","https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fshsk_vercel-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreate-sub-agent\u002FSKILL.md",[],[]]