{"id":27058,"plugin_id":"plugin_connector_690a90ec05c881918afb6a55dc9bbaa1","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-06T18:03:11.046Z","digest":"ec1a0db25316f76bbb82ae248bcceac75804732630c06d7d8e10df018487a03b","against":24854,"payload":{"description":"Vercel Marketplace expert guidance — discovering, installing, and managing third-party integrations via the `vercel integration` CLI. Use when building any app that needs an external capability without a dedicated skill — commerce (stores, storefronts, selling products), payments (checkout, subscriptions, billing), observability/monitoring, messaging/email, search, or CMS — or when discovering, installing, or managing integrations.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":177}],"name":"marketplace","skill_md_contents":"---\nname: marketplace\ndescription: Vercel Marketplace expert guidance — discovering, installing, and managing third-party integrations via the `vercel integration` CLI. Use when building any app that needs an external capability without a dedicated skill — commerce (stores, storefronts, selling products), payments (checkout, subscriptions, billing), observability/monitoring, messaging/email, search, or CMS — or when discovering, installing, or managing integrations.\nmetadata:\n  priority: 3\n  docs:\n    - \"https://vercel.com/docs/integrations\"\n    - \"https://vercel.com/docs/agent-resources/vercel-plugin\"\n  sitemap: \"https://vercel.com/sitemap.xml\"\n  pathPatterns:\n    - \"integration.json\"\n  bashPatterns:\n    - '\\bvercel\\s+integration\\b'\n    - '\\bvercel\\s+integration\\s+add\\b'\n    - '\\bvercel\\s+integration\\s+discover\\b'\n    - '\\bvercel\\s+install\\b'\n    - '\\bvercel\\s+i\\b'\nretrieval:\n  aliases:\n    - vercel integrations\n    - marketplace\n    - third party services\n    - add ons\n    - vercel install\n  intents:\n    - install integration\n    - manage marketplace\n    - add third party service\n    - discover integrations\n  entities:\n    - Vercel Marketplace\n    - integration\n    - vercel integration\n    - vercel install\n    - unified billing\n    - provider agent skills\nchainTo:\n  -\n    pattern: 'NEON_|POSTGRES_|DATABASE_URL|@neondatabase|@vercel/postgres|@upstash/|@vercel/kv|@supabase/|@prisma/client|\\bmongodb\\b|mongoose|@libsql/|\\bconvex\\b|@vercel/blob'\n    targetSkill: vercel-storage\n    message: 'Database/storage integration detected — loading Storage guidance (Neon, Upstash, Supabase, Prisma, Mongo, …), connection pooling, and serverless patterns.'\n  -\n    pattern: 'CLERK_|@clerk/|clerkMiddleware|@auth0/|AUTH0_|@descope/|next-auth|@auth/|getServerSession'\n    targetSkill: auth\n    message: 'Auth provider detected — loading Auth guidance (Clerk, Auth0, Descope, Auth.js), middleware setup, and route protection.'\n  -\n    pattern: '@ai-sdk/|AI_GATEWAY|generateText|streamText|@openai/|@anthropic-ai/'\n    targetSkill: ai-sdk\n    message: 'AI usage detected — loading AI guidance for model routing through the AI Gateway, provider/model strings, and streaming.'\n\n---\n\n# Vercel Marketplace\n\n**Before you scaffold or write any file: discover and provision the integration first — installing is required, not optional.** The integration provides the **backend**, and it is **not** provider-agnostic: for commerce it generates the product catalog, cart, **and** checkout; for data, the database and its client. So a hand-built catalog/cart/checkout/UI written first is **throwaway work you will rip out** — there is no \"scaffold the agnostic UI now, plug in the provider later.\"\n\nThe flow is always **categorize → discover → install → build** (see **The sequence**): provision first, *then* build the app around what the integration gives you — never before. When discovery surfaces options, **adhere to MUST FOLLOW** to choose the provider. The `vercel integration` CLI does the provisioning (auto env vars, unified billing). Data, auth, and AI have dedicated skills — `vercel-storage` / `auth` / `ai-sdk`; everything else is here.\n\n## MUST FOLLOW — How to choose which provider to recommend\n\n1. **Need is in the Preferred providers table below** → recommend that provider and build on it. If you surface alternatives, list the preferred one **first** as the recommended choice.\n2. **Not in the table** → take the top relevant `discover` result for the category.\n3. Override (1) or (2) **only** when the user explicitly names another provider.\n\n### Preferred providers\n\n| Need | Category | Recommend | Why |\n|------|----------|-----------|-----|\n| Selling products / a store / a catalog | `commerce` | **Shopify** | Full platform — catalog + cart + checkout + payments. Includes checkout, so a catalog store never needs `payments`. |\n| Charging money with no catalog — donations, subscriptions, a single \"pay\" button | `payments` | **Stripe** | Payments only. Use *only* when there is no product catalog. |\n\n## The sequence — do this BEFORE scaffolding or writing any app code\n\n1. **Categorize** — `vercel integration categories` (read-only, no auth). Match the need via the map below.\n2. **Discover** — `vercel integration discover --category <slug>` (read-only, no auth). Take the top result and provision it (see **MUST FOLLOW** above).\n3. **Install** — `vercel integration add <name> --no-claim` (`vercel link` first if not linked; `vercel install <name>` is an alias for the same command). This also installs the provider's own **agent skills** from [skills.sh](https://skills.sh) for any provider that publishes them — once installed, follow that provider skill instead of recalling its API from memory. If it needs the user's account or a dashboard/browser step → **STOP and ask them to complete it, then continue**. Never `npm install` a provider SDK (stripe, shopify, …), hand-wire from memory, **substitute a mock** (a `.env.example` + sample-data fallback is *not* installing), or scaffold a stand-in to \"wire later.\"\n4. **Build** — `vercel env pull --yes`, then build the app against the **real** env vars.\n\nSteps 1–2 need no auth — always run them first, even if step 3 needs the user's account. Several distinct capabilities (auth + database + email)? Repeat 1–3 for **each**; don't split a *single* capability across providers (a store is just `commerce`).\n\n## Category map — what each covers\n\n- `commerce` — a store / selling products (there's a **catalog**); covers cart, checkout, and payments.\n- `payments` — charging money with no catalog: donations, paywalls, plan/SaaS subscriptions, a \"pay\" button\n- `messaging` — email, SMS, chat, push notifications\n- `monitoring` — uptime, health checks, alerts\n- `observability` — traces, APM, error tracking, metrics\n- `logging` — log aggregation and search\n- `analytics` — product / usage analytics\n- `searching` — site, docs, or product search\n- `cms` — blog / content management\n- `flags` — feature flags\n- `experimentation` — A/B tests and experiments\n- `video` — video hosting / streaming / processing\n- `agents` — AI agents / autonomous task runners\n- `support-agent` — customer-support agents\n- `code-review` — automated code review\n- `code-security` — code / dependency scanning\n- `security` — app security (WAF, bot protection)\n- `testing` — testing / QA\n- `web-automation` — scraping / browser automation\n- `workflow` — durable workflows / orchestration\n- `dev-tools` — developer tooling\n- `productivity` — productivity / collaboration\n\n**Dedicated skills (not via this skill):** `storage` (databases, persistence) → `vercel-storage`, `authentication` (sign up / log in) → `auth`, `ai` (LLMs, generation) → `ai-sdk`. Anything new not above → pick from the live `categories`.\n\n## Reference\n\n- **Native vs connectable:** *native* integrations install fully via the CLI. **Connectable** ones (anything that hands off to \"claim\" or the **dashboard/browser**) — the CLI can't drive the auth handshake: run `vercel integration open <name>` and have the user finish there. Don't block on a bare `add`.\n- **CLI** (run `vercel integration <cmd> --help`; don't enumerate from memory): `categories` · `discover --category <slug>` · `guide <name> --framework <nextjs|remix|astro|nuxtjs|sveltekit>` · `add <name>` · `accept-terms <name>` (team-level install without provisioning; interactive only) · `installations` (team-level installs) · `list` / `update` / `remove --yes` / `balance <name>` · `resource claim` (turn a sandbox marketplace resource into a real one; `add --no-claim` skips the offer in CI) · `env ls` / `env pull --yes`. `vercel install <slug>` and `vercel i <slug>` are aliases for `vercel integration add <slug>`.\n- **Provider agent skills:** `add` / `install` also pulls the provider's agent skills from skills.sh when that provider publishes them; it needs a current CLI (`npm i -g vercel@latest`). **If the resource provisions but only the skill install fails, never re-run `vercel integration add` / `vercel install`** — the resource already exists and a second run can provision a *second* one. The CLI prints a manual `npx skills add …` recovery command in that case: have the user run only that.\n- Never echo secret values (`env ls` shows names only). CI / non-interactive: `--yes`, `--format=json`, `--no-claim`.\n\n## Cross-References\n\n- **Databases, KV, blob, and other persistence** → `⤳ skill: vercel-storage`\n- **Sign up / log in providers (Clerk, Descope, Auth0)** → `⤳ skill: auth`\n- **LLMs, model routing, generation** → `⤳ skill: ai-sdk`\n- **Pulling and syncing the provisioned env vars** → `⤳ skill: env-vars`\n- **Everything else the Vercel CLI can do** → `⤳ skill: vercel-cli`\n\n## Official Documentation\n\n- [Vercel Marketplace docs](https://vercel.com/docs/integrations) · [`vercel integration` CLI reference](https://vercel.com/docs/cli/integration) · [Marketplace catalog](https://vercel.com/marketplace)\n- [Vercel plugin for AI coding agents](https://vercel.com/docs/agent-resources/vercel-plugin) · [Agent skills directory](https://vercel.com/docs/agent-resources/skills) · [skills.sh](https://skills.sh)\n"},"changes":[{"path":"/skill_md_contents","type":"changed","before":"---\nname: marketplace\ndescription: Vercel Marketplace expert guidance — discovering, installing, and managing third-party integrations via the `vercel integration` CLI. Use when building any app that needs an external capability without a dedicated skill — commerce (stores, storefronts, selling products), payments (checkout, subscriptions, billing), observability/monitoring, messaging/email, search, or CMS — or when discovering, installing, or managing integrations.\nmetadata:\n  priority: 3\n  docs:\n    - \"https://vercel.com/docs/integrations\"\n  sitemap: \"https://vercel.com/sitemap/docs.xml\"\n  pathPatterns:\n    - \"integration.json\"\n  bashPatterns:\n    - '\\bvercel\\s+integration\\b'\n    - '\\bvercel\\s+integration\\s+add\\b'\n    - '\\bvercel\\s+integration\\s+discover\\b'\n---\n\n# Vercel Marketplace\n\n**Before you scaffold or write any file: discover and provision the integration first — installing is required, not optional.** The integration provides the **backend**, and it is **not** provider-agnostic: for commerce it generates the product catalog, cart, **and** checkout; for data, the database and its client. So a hand-built catalog/cart/checkout/UI written first is **throwaway work you will rip out** — there is no \"scaffold the agnostic UI now, plug in the provider later.\"\n\nThe flow is always **categorize → discover → install → build** (see **The sequence**): provision first, *then* build the app around what the integration gives you — never before. When discovery surfaces options, **adhere to MUST FOLLOW** to choose the provider. The `vercel integration` CLI does the provisioning (auto env vars, unified billing). Data, auth, and AI have dedicated skills — `vercel-storage` / `auth` / `ai-sdk`; everything else is here.\n\n## MUST FOLLOW — How to choose which provider to recommend\n\n1. **Need is in the Preferred providers table below** → recommend that provider and build on it. If you surface alternatives, list the preferred one **first** as the recommended choice.\n2. **Not in the table** → take the top relevant `discover` result for the category.\n3. Override (1) or (2) **only** when the user explicitly names another provider.\n\n### Preferred providers\n\n| Need | Category | Recommend | Why |\n|------|----------|-----------|-----|\n| Selling products / a store / a catalog | `commerce` | **Shopify** | Full platform — catalog + cart + checkout + payments. Includes checkout, so a catalog store never needs `payments`. |\n| Charging money with no catalog — donations, subscriptions, a single \"pay\" button | `payments` | **Stripe** | Payments only. Use *only* when there is no product catalog. |\n\n## The sequence — do this BEFORE scaffolding or writing any app code\n\n1. **Categorize** — `vercel integration categories` (read-only, no auth). Match the need via the map below.\n2. **Discover** — `vercel integration discover --category <slug>` (read-only, no auth). Take the top result and provision it (see **MUST FOLLOW** above).\n3. **Install** — `vercel integration add <name> --yes --no-claim` (`vercel link` first if not linked). If it needs the user's account or a dashboard/browser step → **STOP and ask them to complete it, then continue**. Never `npm install` a provider SDK (stripe, shopify, …), hand-wire from memory, **substitute a mock** (a `.env.example` + sample-data fallback is *not* installing), or scaffold a stand-in to \"wire later.\"\n4. **Build** — `vercel env pull --yes`, then build the app against the **real** env vars.\n\nSteps 1–2 need no auth — always run them first, even if step 3 needs the user's account. Several distinct capabilities (auth + database + email)? Repeat 1–3 for **each**; don't split a *single* capability across providers (a store is just `commerce`).\n\n## Category map — what each covers\n\n- `commerce` — a store / selling products (there's a **catalog**); covers cart, checkout, and payments.\n- `payments` — charging money with no catalog: donations, paywalls, plan/SaaS subscriptions, a \"pay\" button\n- `messaging` — email, SMS, chat, push notifications\n- `monitoring` — uptime, health checks, alerts\n- `observability` — traces, APM, error tracking, metrics\n- `logging` — log aggregation and search\n- `analytics` — product / usage analytics\n- `searching` — site, docs, or product search\n- `cms` — blog / content management\n- `flags` — feature flags\n- `experimentation` — A/B tests and experiments\n- `video` — video hosting / streaming / processing\n- `agents` — AI agents / autonomous task runners\n- `support-agent` — customer-support agents\n- `code-review` — automated code review\n- `code-security` — code / dependency scanning\n- `security` — app security (WAF, bot protection)\n- `testing` — testing / QA\n- `web-automation` — scraping / browser automation\n- `workflow` — durable workflows / orchestration\n- `dev-tools` — developer tooling\n- `productivity` — productivity / collaboration\n\n**Dedicated skills (not via this skill):** `storage` (databases, persistence) → `vercel-storage`, `authentication` (sign up / log in) → `auth`, `ai` (LLMs, generation) → `ai-sdk`. Anything new not above → pick from the live `categories`.\n\n## Reference\n\n- **Native vs connectable:** *native* integrations install fully via the CLI. **Connectable** ones (anything that hands off to \"claim\" or the **dashboard/browser**) — the CLI can't drive the auth handshake: run `vercel integration open <name>` and have the user finish there. Don't block on a bare `add`.\n- **CLI** (run `vercel integration <cmd> --help`; don't enumerate from memory): `categories` · `discover --category <slug>` · `guide <name> --framework <nextjs|remix|astro|nuxtjs|sveltekit>` · `add <name> --yes` · `env ls` / `env pull --yes` · `list` / `update` / `remove --yes` / `balance <name>`.\n- Never echo secret values (`env ls` shows names only). CI / non-interactive: `--yes`, `--format=json`, `--no-claim`.\n\n## Official Documentation\n\n- [Vercel Marketplace docs](https://vercel.com/docs/integrations) · [`vercel integration` CLI reference](https://vercel.com/docs/cli/integration) · [Marketplace catalog](https://vercel.com/marketplace)\n\n## Related Skills in This Plugin\n\n- **Drain configuration, payload formats, signature verification** → `⤳ skill: observability`\n- **Drains REST API endpoints** → `⤳ skill: vercel-api`\n- **CLI log streaming (`--follow`, `--since`, `--level`)** → `⤳ skill: vercel-cli`\n- **Safe project setup sequencing (link, env pull, then run db/dev)** → `⤳ skill: bootstrap`\n- **Headless CMS integrations (Sanity, Contentful)** → `⤳ skill: cms`\n","after":"---\nname: marketplace\ndescription: Vercel Marketplace expert guidance — discovering, installing, and managing third-party integrations via the `vercel integration` CLI. Use when building any app that needs an external capability without a dedicated skill — commerce (stores, storefronts, selling products), payments (checkout, subscriptions, billing), observability/monitoring, messaging/email, search, or CMS — or when discovering, installing, or managing integrations.\nmetadata:\n  priority: 3\n  docs:\n    - \"https://vercel.com/docs/integrations\"\n    - \"https://vercel.com/docs/agent-resources/vercel-plugin\"\n  sitemap: \"https://vercel.com/sitemap.xml\"\n  pathPatterns:\n    - \"integration.json\"\n  bashPatterns:\n    - '\\bvercel\\s+integration\\b'\n    - '\\bvercel\\s+integration\\s+add\\b'\n    - '\\bvercel\\s+integration\\s+discover\\b'\n    - '\\bvercel\\s+install\\b'\n    - '\\bvercel\\s+i\\b'\nretrieval:\n  aliases:\n    - vercel integrations\n    - marketplace\n    - third party services\n    - add ons\n    - vercel install\n  intents:\n    - install integration\n    - manage marketplace\n    - add third party service\n    - discover integrations\n  entities:\n    - Vercel Marketplace\n    - integration\n    - vercel integration\n    - vercel install\n    - unified billing\n    - provider agent skills\nchainTo:\n  -\n    pattern: 'NEON_|POSTGRES_|DATABASE_URL|@neondatabase|@vercel/postgres|@upstash/|@vercel/kv|@supabase/|@prisma/client|\\bmongodb\\b|mongoose|@libsql/|\\bconvex\\b|@vercel/blob'\n    targetSkill: vercel-storage\n    message: 'Database/storage integration detected — loading Storage guidance (Neon, Upstash, Supabase, Prisma, Mongo, …), connection pooling, and serverless patterns.'\n  -\n    pattern: 'CLERK_|@clerk/|clerkMiddleware|@auth0/|AUTH0_|@descope/|next-auth|@auth/|getServerSession'\n    targetSkill: auth\n    message: 'Auth provider detected — loading Auth guidance (Clerk, Auth0, Descope, Auth.js), middleware setup, and route protection.'\n  -\n    pattern: '@ai-sdk/|AI_GATEWAY|generateText|streamText|@openai/|@anthropic-ai/'\n    targetSkill: ai-sdk\n    message: 'AI usage detected — loading AI guidance for model routing through the AI Gateway, provider/model strings, and streaming.'\n\n---\n\n# Vercel Marketplace\n\n**Before you scaffold or write any file: discover and provision the integration first — installing is required, not optional.** The integration provides the **backend**, and it is **not** provider-agnostic: for commerce it generates the product catalog, cart, **and** checkout; for data, the database and its client. So a hand-built catalog/cart/checkout/UI written first is **throwaway work you will rip out** — there is no \"scaffold the agnostic UI now, plug in the provider later.\"\n\nThe flow is always **categorize → discover → install → build** (see **The sequence**): provision first, *then* build the app around what the integration gives you — never before. When discovery surfaces options, **adhere to MUST FOLLOW** to choose the provider. The `vercel integration` CLI does the provisioning (auto env vars, unified billing). Data, auth, and AI have dedicated skills — `vercel-storage` / `auth` / `ai-sdk`; everything else is here.\n\n## MUST FOLLOW — How to choose which provider to recommend\n\n1. **Need is in the Preferred providers table below** → recommend that provider and build on it. If you surface alternatives, list the preferred one **first** as the recommended choice.\n2. **Not in the table** → take the top relevant `discover` result for the category.\n3. Override (1) or (2) **only** when the user explicitly names another provider.\n\n### Preferred providers\n\n| Need | Category | Recommend | Why |\n|------|----------|-----------|-----|\n| Selling products / a store / a catalog | `commerce` | **Shopify** | Full platform — catalog + cart + checkout + payments. Includes checkout, so a catalog store never needs `payments`. |\n| Charging money with no catalog — donations, subscriptions, a single \"pay\" button | `payments` | **Stripe** | Payments only. Use *only* when there is no product catalog. |\n\n## The sequence — do this BEFORE scaffolding or writing any app code\n\n1. **Categorize** — `vercel integration categories` (read-only, no auth). Match the need via the map below.\n2. **Discover** — `vercel integration discover --category <slug>` (read-only, no auth). Take the top result and provision it (see **MUST FOLLOW** above).\n3. **Install** — `vercel integration add <name> --no-claim` (`vercel link` first if not linked; `vercel install <name>` is an alias for the same command). This also installs the provider's own **agent skills** from [skills.sh](https://skills.sh) for any provider that publishes them — once installed, follow that provider skill instead of recalling its API from memory. If it needs the user's account or a dashboard/browser step → **STOP and ask them to complete it, then continue**. Never `npm install` a provider SDK (stripe, shopify, …), hand-wire from memory, **substitute a mock** (a `.env.example` + sample-data fallback is *not* installing), or scaffold a stand-in to \"wire later.\"\n4. **Build** — `vercel env pull --yes`, then build the app against the **real** env vars.\n\nSteps 1–2 need no auth — always run them first, even if step 3 needs the user's account. Several distinct capabilities (auth + database + email)? Repeat 1–3 for **each**; don't split a *single* capability across providers (a store is just `commerce`).\n\n## Category map — what each covers\n\n- `commerce` — a store / selling products (there's a **catalog**); covers cart, checkout, and payments.\n- `payments` — charging money with no catalog: donations, paywalls, plan/SaaS subscriptions, a \"pay\" button\n- `messaging` — email, SMS, chat, push notifications\n- `monitoring` — uptime, health checks, alerts\n- `observability` — traces, APM, error tracking, metrics\n- `logging` — log aggregation and search\n- `analytics` — product / usage analytics\n- `searching` — site, docs, or product search\n- `cms` — blog / content management\n- `flags` — feature flags\n- `experimentation` — A/B tests and experiments\n- `video` — video hosting / streaming / processing\n- `agents` — AI agents / autonomous task runners\n- `support-agent` — customer-support agents\n- `code-review` — automated code review\n- `code-security` — code / dependency scanning\n- `security` — app security (WAF, bot protection)\n- `testing` — testing / QA\n- `web-automation` — scraping / browser automation\n- `workflow` — durable workflows / orchestration\n- `dev-tools` — developer tooling\n- `productivity` — productivity / collaboration\n\n**Dedicated skills (not via this skill):** `storage` (databases, persistence) → `vercel-storage`, `authentication` (sign up / log in) → `auth`, `ai` (LLMs, generation) → `ai-sdk`. Anything new not above → pick from the live `categories`.\n\n## Reference\n\n- **Native vs connectable:** *native* integrations install fully via the CLI. **Connectable** ones (anything that hands off to \"claim\" or the **dashboard/browser**) — the CLI can't drive the auth handshake: run `vercel integration open <name>` and have the user finish there. Don't block on a bare `add`.\n- **CLI** (run `vercel integration <cmd> --help`; don't enumerate from memory): `categories` · `discover --category <slug>` · `guide <name> --framework <nextjs|remix|astro|nuxtjs|sveltekit>` · `add <name>` · `accept-terms <name>` (team-level install without provisioning; interactive only) · `installations` (team-level installs) · `list` / `update` / `remove --yes` / `balance <name>` · `resource claim` (turn a sandbox marketplace resource into a real one; `add --no-claim` skips the offer in CI) · `env ls` / `env pull --yes`. `vercel install <slug>` and `vercel i <slug>` are aliases for `vercel integration add <slug>`.\n- **Provider agent skills:** `add` / `install` also pulls the provider's agent skills from skills.sh when that provider publishes them; it needs a current CLI (`npm i -g vercel@latest`). **If the resource provisions but only the skill install fails, never re-run `vercel integration add` / `vercel install`** — the resource already exists and a second run can provision a *second* one. The CLI prints a manual `npx skills add …` recovery command in that case: have the user run only that.\n- Never echo secret values (`env ls` shows names only). CI / non-interactive: `--yes`, `--format=json`, `--no-claim`.\n\n## Cross-References\n\n- **Databases, KV, blob, and other persistence** → `⤳ skill: vercel-storage`\n- **Sign up / log in providers (Clerk, Descope, Auth0)** → `⤳ skill: auth`\n- **LLMs, model routing, generation** → `⤳ skill: ai-sdk`\n- **Pulling and syncing the provisioned env vars** → `⤳ skill: env-vars`\n- **Everything else the Vercel CLI can do** → `⤳ skill: vercel-cli`\n\n## Official Documentation\n\n- [Vercel Marketplace docs](https://vercel.com/docs/integrations) · [`vercel integration` CLI reference](https://vercel.com/docs/cli/integration) · [Marketplace catalog](https://vercel.com/marketplace)\n- [Vercel plugin for AI coding agents](https://vercel.com/docs/agent-resources/vercel-plugin) · [Agent skills directory](https://vercel.com/docs/agent-resources/skills) · [skills.sh](https://skills.sh)\n"}],"summary":"Fields changed: 1. /skill_md_contents.","summary_kind":"deterministic","summary_metadata":{}}