{"id":"9db6556e-e5b2-4be5-8714-04ea3b8a0a3e","entityType":"agent","slug":"clawhub-hith3sh-vercel-deployments","name":"Vercel","canonicalUrl":"https://www.xpersona.co/agent/clawhub-hith3sh-vercel-deployments","canonicalPath":"/agent/clawhub-hith3sh-vercel-deployments","generatedAt":"2026-10-09T20:20:46.921Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-09T12:26:32.624Z","emptyReason":null},"description":"Manage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API. Use this skill when users want to inspect de... Skill: Vercel Owner: hith3sh Summary: Manage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API. Use this skill when users want to inspect de... Tags: latest:1.0.6 Version history: v1.0.6 | 2026-06-09T07:20:43.913Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 2.7K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:vercel-deployments","sourceUrl":"https://clawhub.ai/hith3sh/vercel-deployments","homepage":"https://clawhub.ai/hith3sh/skills/vercel-deployments","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/hith3sh/vercel-deployments","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/hith3sh/skills/vercel-deployments","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":68,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Manage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API. Use this skill when users want to inspect de..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T12:26:32.624Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T12:26:32.624Z","emptyReason":null},"stars":null,"forks":null,"downloads":2654,"packageName":null,"latestVersion":"1.0.6","tractionLabel":"2.7K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T12:26:32.624Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T12:26:32.624Z","lastCrawledAt":"2026-10-09T12:26:32.624Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T12:26:32.624Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.6","createdAt":"2026-06-09T07:20:43.913Z","changelog":"Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.","fileCount":3,"zipByteSize":5628},{"version":"1.0.5","createdAt":"2026-06-09T05:37:48.552Z","changelog":"- Removed the file: skill-card.md - No other user-facing changes were made.","fileCount":3,"zipByteSize":5571},{"version":"1.0.4","createdAt":"2026-06-09T04:49:37.953Z","changelog":"- Removed the file skill-card.md for this version. - No other changes to functionality or documentation. - The skill continues to provide all original Vercel management features via ClawLink integration.","fileCount":3,"zipByteSize":5619},{"version":"1.0.1","createdAt":"2026-06-08T16:43:21.372Z","changelog":"- Added Vercel logo to the top of the documentation for improved branding. - Minor documentation cleanup and formatting updates. - Removed the file skill-card.md.","fileCount":3,"zipByteSize":5497},{"version":"0.2.1","createdAt":"2026-06-07T13:52:28.353Z","changelog":"Fix display name: show app name only (was including tool list).","fileCount":3,"zipByteSize":5442},{"version":"0.2.0","createdAt":"2026-06-07T13:41:15.023Z","changelog":"Full rewrite to new standard","fileCount":3,"zipByteSize":5602},{"version":"0.1.0","createdAt":"2026-05-24T14:31:18.213Z","changelog":"Initial release of Vercel Deployments skill. - Manage Vercel projects, deployments, domains, and environment variables through ClawLink integration. - Guides users through plugin installation, ClawLink account pairing, and Vercel connection. - Provides safe procedures for tool discovery, execution, and confirmation for sensitive actions. - Enforces security and best practices: never asks for raw credentials, always checks ClawLink live catalog. - Typical tasks include inspecting and managing teams, projects, deployments, domains, and environment variables.","fileCount":3,"zipByteSize":3349}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:vercel-deployments","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-vercel-deployments/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-vercel-deployments/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-vercel-deployments/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-vercel-deployments/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-vercel-deployments/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-vercel-deployments/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-09T20:20:46.919Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-vercel-deployments/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-vercel-deployments/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-vercel-deployments/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-vercel-deployments/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-09T12:26:32.624Z","emptyReason":null},"readme":"Skill: Vercel\n\nOwner: hith3sh\n\nSummary: Manage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API. Use this skill when users want to inspect de...\n\nTags: latest:1.0.6\n\nVersion history:\n\nv1.0.6 | 2026-06-09T07:20:43.913Z | user\n\nAdd UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.\n\nv1.0.5 | 2026-06-09T05:37:48.552Z | auto\n\n- Removed the file: skill-card.md\n- No other user-facing changes were made.\n\nv1.0.4 | 2026-06-09T04:49:37.953Z | auto\n\n- Removed the file skill-card.md for this version.\n- No other changes to functionality or documentation.\n- The skill continues to provide all original Vercel management features via ClawLink integration.\n\nv1.0.1 | 2026-06-08T16:43:21.372Z | auto\n\n- Added Vercel logo to the top of the documentation for improved branding.\n- Minor documentation cleanup and formatting updates.\n- Removed the file skill-card.md.\n\nv0.2.1 | 2026-06-07T13:52:28.353Z | user\n\nFix display name: show app name only (was including tool list).\n\nv0.2.0 | 2026-06-07T13:41:15.023Z | user\n\nFull rewrite to new standard\n\nv0.1.0 | 2026-05-24T14:31:18.213Z | auto\n\nInitial release of Vercel Deployments skill.\n\n- Manage Vercel projects, deployments, domains, and environment variables through ClawLink integration.\n- Guides users through plugin installation, ClawLink account pairing, and Vercel connection.\n- Provides safe procedures for tool discovery, execution, and confirmation for sensitive actions.\n- Enforces security and best practices: never asks for raw credentials, always checks ClawLink live catalog.\n- Typical tasks include inspecting and managing teams, projects, deployments, domains, and environment variables.\n\nArchive index:\n\nArchive v1.0.6: 3 files, 5628 bytes\n\nFiles: skill-card.md (2475b), SKILL.md (13743b), _meta.json (137b)\n\nFile v1.0.6:SKILL.md\n\n---\nname: vercel-deployments\ndescription: Manage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API. Use this skill when users want to inspect deployments, manage projects, configure domains, or automate Vercel DevOps workflows.\n---\n\n# Vercel\n\n\n\nManage Vercel projects, deployments, domains, environment variables, and team resources from chat via the Vercel REST API.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=vercel-deployments) for hosted connection flows and credentials so you do not need to configure Vercel API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Vercel |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Vercel |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Vercel REST │\n│ (User Chat) │ │ (OAuth) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Vercel │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Vercel │\n │ File │ │ Auth │ │ Account │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Vercel again.\"\n\n## Quick Start\n\n```bash\n# List projects\nclawlink_call_tool --tool \"vercel_list_projects\" --params '{}'\n\n# Get deployment details\nclawlink_call_tool --tool \"vercel_get_deployment\" --params '{\"deployment_id\": \"DEPLOYMENT_ID\"}'\n\n# List deployments\nclawlink_call_tool --tool \"vercel_list_deployments\" --params '{\"project_name\": \"my-project\"}'\n```\n\n## Authentication\n\nAll Vercel tool calls are authenticated automatically by ClawLink using the user's connected Vercel account token.\n\n**No API token is required in chat.** ClawLink stores the token securely and injects it into every Vercel API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=vercel and connect Vercel.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `vercel` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration vercel\n```\n\n**Response:** Returns the live tool catalog for Vercel.\n\n### Reconnect\n\nIf Vercel tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=vercel\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration vercel`\n\n## Security & Permissions\n\n- Access is scoped to the Vercel account connected during OAuth setup and the scopes granted.\n- **All write operations (deploy, create project, update settings, add domains) require explicit user confirmation.**\n- Destructive operations (delete deployment, remove domain) are high-impact and must be confirmed.\n- Environment variable changes can affect running deployments — confirm before modifying.\n\n## Tool Reference\n\n### Projects\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_projects` | List all projects in the account/team | Read |\n| `vercel_get_project` | Get project configuration and settings | Read |\n| `vercel_create_project` | Create a new project | Write |\n| `vercel_update_project` | Update project name, framework, or settings | Write |\n| `vercel_delete_project` | Delete a project and its deployments | Write |\n\n### Deployments\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_deployments` | List deployments with pagination and filters | Read |\n| `vercel_get_deployment` | Get deployment details including status and URLs | Read |\n| `vercel_create_deployment` | Create a new deployment | Write |\n| `vercel_cancel_deployment` | Cancel an in-progress deployment | Write |\n| `vercel_delete_deployment` | Delete a deployment | Write |\n\n### Domains\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_domains` | List all domains in the account | Read |\n| `vercel_get_domain` | Get domain details and DNS records | Read |\n| `vercel_add_domain` | Add a domain to a project | Write |\n| `vercel_remove_domain` | Remove a domain from a project | Write |\n| `vercel_verify_domain` | Verify domain ownership | Write |\n\n### Environment Variables\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_env` | List environment variables for a project | Read |\n| `vercel_add_env` | Add an environment variable to a project | Write |\n| `vercel_update_env` | Update an environment variable's value or scope | Write |\n| `vercel_delete_env` | Remove an environment variable | Write |\n\n### Teams & Members\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_team_members` | List all members of a team | Read |\n| `vercel_invite_team_member` | Invite a new member to the team | Write |\n| `vercel_remove_team_member` | Remove a member from the team | Write |\n| `vercel_update_team_member_role` | Change a member's role | Write |\n\n### Secrets\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_secrets` | List all secrets in the account | Read |\n| `vercel_create_secret` | Create a secret for use in environment variables | Write |\n| `vercel_delete_secret` | Delete a secret | Write |\n\n### Logs & Events\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_get_deployment_events` | Get deployment event log | Read |\n| `vercel_get_audit_logs` | Get team audit logs | Read |\n\n## Code Examples\n\n### List all projects\n\n```bash\nclawlink_call_tool --tool \"vercel_list_projects\" \\\n --params '{\n \"team_id\": \"team_id\"\n }'\n```\n\n### Get deployment details\n\n```bash\nclawlink_call_tool --tool \"vercel_get_deployment\" \\\n --params '{\n \"deployment_id\": \"dpl_1234567890\"\n }'\n```\n\n### List deployments for a project\n\n```bash\nclawlink_call_tool --tool \"vercel_list_deployments\" \\\n --params '{\n \"project_name\": \"my-nextjs-app\",\n \"limit\": 10\n }'\n```\n\n### Add an environment variable\n\n```bash\nclawlink_call_tool --tool \"vercel_add_env\" \\\n --params '{\n \"project_name\": \"my-nextjs-app\",\n \"key\": \"DATABASE_URL\",\n \"value\": \"postgres://...\",\n \"environment\": \"production\"\n }'\n```\n\n### Verify a domain\n\n```bash\nclawlink_call_tool --tool \"vercel_verify_domain\" \\\n --params '{\n \"domain\": \"example.com\"\n }'\n```\n\n### Cancel a deployment\n\n```bash\nclawlink_call_tool --tool \"vercel_cancel_deployment\" \\\n --params '{\n \"deployment_id\": \"dpl_1234567890\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Vercel is connected.\n2. Call `clawlink_list_tools --integration vercel` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `vercel`.\n5. If no Vercel tools appear, direct the user to https://claw-link.dev/dashboard?add=vercel.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → describe │\n│ │\n│ Example: List projects → Get deployments → Show status │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ describe → preview → confirm → call │\n│ │\n│ Example: Preview env var change → User approves → Update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Deployment IDs start with `dpl_` and project names are used in deployment URLs.\n- Environment variables can be scoped to `development`, `preview`, or `production` environments.\n- Domain verification requires adding DNS records — check the verification status with `vercel_get_domain`.\n- Deleted deployments cannot be restored.\n- Team operations require the authenticated user to be a team owner or admin.\n- Vercel uses a specific deployment URL format: `https://project.vercel.app`.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration vercel`. |\n| Missing connection | Vercel is not connected. Direct the user to https://claw-link.dev/dashboard?add=vercel. |\n| `Project not found` | The project name does not exist in the account. |\n| `Deployment not found` | The deployment ID does not exist. |\n| `Domain not found` | The domain is not registered with the account. |\n| `Domain not verified` | Domain ownership has not been verified. Add DNS records first. |\n| `Env not found` | The environment variable does not exist in the project. |\n| `Forbidden` | The account lacks permission for this operation. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n## Resources\n\n- [Vercel REST API Documentation](https://vercel.com/docs/rest-api)\n- [Vercel API Reference](https://vercel.com/docs/rest-api)\n- ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=vercel-deployments\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=vercel-deployments)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.6:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"vercel-deployments\",\n \"version\": \"1.0.6\",\n \"publishedAt\": 1780989643913\n}\n\nFile v1.0.6:skill-card.md\n\n## Description:\n\nManage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and operators use this skill to inspect and manage Vercel projects, deployments, domains, environment variables, secrets, audit logs, and team resources from an agent workflow.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill requires installing and allowlisting an external ClawLink plugin that mediates access to Vercel account actions and credentials.\n\nMitigation: Install only when the publisher and ClawLink are trusted, review OAuth scopes before connecting, and know how to revoke the Vercel connection and remove the plugin allowlist entry.\n\nRisk: Write or destructive Vercel operations can change deployments, domains, environment variables, secrets, projects, or team access.\n\nMitigation: Preview write operations, confirm the exact target and effect with the user, and use the least-privileged Vercel account or team role practical.\n\nRisk: Environment variable, secret, and domain changes can affect running production deployments.\n\nMitigation: Check the intended environment or domain status first, prefer read/list/get operations before changes, and confirm production-impacting updates explicitly.\n\n## Reference(s):\n\n- [Vercel REST API Documentation](https://vercel.com/docs/rest-api)\n- [ClawLink OpenClaw Documentation](https://docs.claw-link.dev/openclaw)\n- [ClawLink Verification](https://claw-link.dev/verify)\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/skills/vercel-deployments)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]\n\n**Output Format:** [Markdown with inline shell commands and structured tool-call parameters]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include Vercel resource identifiers, JSON parameters for ClawLink tool calls, previews, confirmations, and error summaries.]\n\n## Skill Version(s):\n\n1.0.6 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.5: 3 files, 5571 bytes\n\nFiles: skill-card.md (2493b), SKILL.md (13530b), _meta.json (137b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: vercel-deployments\ndescription: Manage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API. Use this skill when users want to inspect deployments, manage projects, configure domains, or automate Vercel DevOps workflows.\n---\n\n# Vercel\n\n\n\nManage Vercel projects, deployments, domains, environment variables, and team resources from chat via the Vercel REST API.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Vercel API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Vercel |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Vercel |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Vercel REST │\n│ (User Chat) │ │ (OAuth) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Vercel │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Vercel │\n │ File │ │ Auth │ │ Account │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Vercel again.\"\n\n## Quick Start\n\n```bash\n# List projects\nclawlink_call_tool --tool \"vercel_list_projects\" --params '{}'\n\n# Get deployment details\nclawlink_call_tool --tool \"vercel_get_deployment\" --params '{\"deployment_id\": \"DEPLOYMENT_ID\"}'\n\n# List deployments\nclawlink_call_tool --tool \"vercel_list_deployments\" --params '{\"project_name\": \"my-project\"}'\n```\n\n## Authentication\n\nAll Vercel tool calls are authenticated automatically by ClawLink using the user's connected Vercel account token.\n\n**No API token is required in chat.** ClawLink stores the token securely and injects it into every Vercel API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=vercel and connect Vercel.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `vercel` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration vercel\n```\n\n**Response:** Returns the live tool catalog for Vercel.\n\n### Reconnect\n\nIf Vercel tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=vercel\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration vercel`\n\n## Security & Permissions\n\n- Access is scoped to the Vercel account connected during OAuth setup and the scopes granted.\n- **All write operations (deploy, create project, update settings, add domains) require explicit user confirmation.**\n- Destructive operations (delete deployment, remove domain) are high-impact and must be confirmed.\n- Environment variable changes can affect running deployments — confirm before modifying.\n\n## Tool Reference\n\n### Projects\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_projects` | List all projects in the account/team | Read |\n| `vercel_get_project` | Get project configuration and settings | Read |\n| `vercel_create_project` | Create a new project | Write |\n| `vercel_update_project` | Update project name, framework, or settings | Write |\n| `vercel_delete_project` | Delete a project and its deployments | Write |\n\n### Deployments\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_deployments` | List deployments with pagination and filters | Read |\n| `vercel_get_deployment` | Get deployment details including status and URLs | Read |\n| `vercel_create_deployment` | Create a new deployment | Write |\n| `vercel_cancel_deployment` | Cancel an in-progress deployment | Write |\n| `vercel_delete_deployment` | Delete a deployment | Write |\n\n### Domains\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_domains` | List all domains in the account | Read |\n| `vercel_get_domain` | Get domain details and DNS records | Read |\n| `vercel_add_domain` | Add a domain to a project | Write |\n| `vercel_remove_domain` | Remove a domain from a project | Write |\n| `vercel_verify_domain` | Verify domain ownership | Write |\n\n### Environment Variables\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_env` | List environment variables for a project | Read |\n| `vercel_add_env` | Add an environment variable to a project | Write |\n| `vercel_update_env` | Update an environment variable's value or scope | Write |\n| `vercel_delete_env` | Remove an environment variable | Write |\n\n### Teams & Members\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_team_members` | List all members of a team | Read |\n| `vercel_invite_team_member` | Invite a new member to the team | Write |\n| `vercel_remove_team_member` | Remove a member from the team | Write |\n| `vercel_update_team_member_role` | Change a member's role | Write |\n\n### Secrets\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_secrets` | List all secrets in the account | Read |\n| `vercel_create_secret` | Create a secret for use in environment variables | Write |\n| `vercel_delete_secret` | Delete a secret | Write |\n\n### Logs & Events\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_get_deployment_events` | Get deployment event log | Read |\n| `vercel_get_audit_logs` | Get team audit logs | Read |\n\n## Code Examples\n\n### List all projects\n\n```bash\nclawlink_call_tool --tool \"vercel_list_projects\" \\\n --params '{\n \"team_id\": \"team_id\"\n }'\n```\n\n### Get deployment details\n\n```bash\nclawlink_call_tool --tool \"vercel_get_deployment\" \\\n --params '{\n \"deployment_id\": \"dpl_1234567890\"\n }'\n```\n\n### List deployments for a project\n\n```bash\nclawlink_call_tool --tool \"vercel_list_deployments\" \\\n --params '{\n \"project_name\": \"my-nextjs-app\",\n \"limit\": 10\n }'\n```\n\n### Add an environment variable\n\n```bash\nclawlink_call_tool --tool \"vercel_add_env\" \\\n --params '{\n \"project_name\": \"my-nextjs-app\",\n \"key\": \"DATABASE_URL\",\n \"value\": \"postgres://...\",\n \"environment\": \"production\"\n }'\n```\n\n### Verify a domain\n\n```bash\nclawlink_call_tool --tool \"vercel_verify_domain\" \\\n --params '{\n \"domain\": \"example.com\"\n }'\n```\n\n### Cancel a deployment\n\n```bash\nclawlink_call_tool --tool \"vercel_cancel_deployment\" \\\n --params '{\n \"deployment_id\": \"dpl_1234567890\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Vercel is connected.\n2. Call `clawlink_list_tools --integration vercel` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `vercel`.\n5. If no Vercel tools appear, direct the user to https://claw-link.dev/dashboard?add=vercel.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → describe │\n│ │\n│ Example: List projects → Get deployments → Show status │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ describe → preview → confirm → call │\n│ │\n│ Example: Preview env var change → User approves → Update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Deployment IDs start with `dpl_` and project names are used in deployment URLs.\n- Environment variables can be scoped to `development`, `preview`, or `production` environments.\n- Domain verification requires adding DNS records — check the verification status with `vercel_get_domain`.\n- Deleted deployments cannot be restored.\n- Team operations require the authenticated user to be a team owner or admin.\n- Vercel uses a specific deployment URL format: `https://project.vercel.app`.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration vercel`. |\n| Missing connection | Vercel is not connected. Direct the user to https://claw-link.dev/dashboard?add=vercel. |\n| `Project not found` | The project name does not exist in the account. |\n| `Deployment not found` | The deployment ID does not exist. |\n| `Domain not found` | The domain is not registered with the account. |\n| `Domain not verified` | Domain ownership has not been verified. Add DNS records first. |\n| `Env not found` | The environment variable does not exist in the project. |\n| `Forbidden` | The account lacks permission for this operation. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n## Resources\n\n- [Vercel REST API Documentation](https://vercel.com/docs/rest-api)\n- [Vercel API Reference](https://vercel.com/docs/rest-api)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.5:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"vercel-deployments\",\n \"version\": \"1.0.5\",\n \"publishedAt\": 1780983468552\n}\n\nFile v1.0.5:skill-card.md\n\n## Description:
\nManage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API from OpenClaw chat.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and DevOps teams use this skill to inspect Vercel resources, review deployments, configure domains and environment variables, and perform confirmed project or team administration through ClawLink-backed Vercel tools.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill uses ClawLink OAuth access to a connected Vercel account.
\nMitigation: Install only when the publisher and ClawLink connection are trusted, and review the Vercel OAuth scopes before connecting an account.
\nRisk: Confirmed write actions can affect deployments, domains, environment variables, secrets, projects, and team membership.
\nMitigation: Prefer read and preview steps first, then execute write or destructive actions only after explicit user confirmation matches the intended change.
\nRisk: Environment variable and secret operations may expose or alter sensitive deployment configuration.
\nMitigation: Avoid displaying secret values, confirm the target project and environment scope, and review changes before applying them.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/hith3sh/vercel-deployments)
\n- [Vercel REST API Documentation](https://vercel.com/docs/rest-api)
\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Vercel Connection](https://claw-link.dev/dashboard?add=vercel)
\n\n\n## Skill Output:
\n**Output Type(s):** [Guidance, Shell commands, API calls, Configuration]
\n**Output Format:** [Markdown with inline shell commands and JSON tool parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May include Vercel resource identifiers, previewed write operations, and confirmation-dependent tool calls.]
\n\n## Skill Version(s):
\n1.0.5 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.4: 3 files, 5619 bytes\n\nFiles: skill-card.md (2654b), SKILL.md (13530b), _meta.json (137b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: vercel-deployments\ndescription: Manage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API. Use this skill when users want to inspect deployments, manage projects, configure domains, or automate Vercel DevOps workflows.\n---\n\n# Vercel\n\n\n\nManage Vercel projects, deployments, domains, environment variables, and team resources from chat via the Vercel REST API.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Vercel API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Vercel |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Vercel |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Vercel REST │\n│ (User Chat) │ │ (OAuth) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Vercel │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Vercel │\n │ File │ │ Auth │ │ Account │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Vercel again.\"\n\n## Quick Start\n\n```bash\n# List projects\nclawlink_call_tool --tool \"vercel_list_projects\" --params '{}'\n\n# Get deployment details\nclawlink_call_tool --tool \"vercel_get_deployment\" --params '{\"deployment_id\": \"DEPLOYMENT_ID\"}'\n\n# List deployments\nclawlink_call_tool --tool \"vercel_list_deployments\" --params '{\"project_name\": \"my-project\"}'\n```\n\n## Authentication\n\nAll Vercel tool calls are authenticated automatically by ClawLink using the user's connected Vercel account token.\n\n**No API token is required in chat.** ClawLink stores the token securely and injects it into every Vercel API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=vercel and connect Vercel.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `vercel` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration vercel\n```\n\n**Response:** Returns the live tool catalog for Vercel.\n\n### Reconnect\n\nIf Vercel tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=vercel\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration vercel`\n\n## Security & Permissions\n\n- Access is scoped to the Vercel account connected during OAuth setup and the scopes granted.\n- **All write operations (deploy, create project, update settings, add domains) require explicit user confirmation.**\n- Destructive operations (delete deployment, remove domain) are high-impact and must be confirmed.\n- Environment variable changes can affect running deployments — confirm before modifying.\n\n## Tool Reference\n\n### Projects\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_projects` | List all projects in the account/team | Read |\n| `vercel_get_project` | Get project configuration and settings | Read |\n| `vercel_create_project` | Create a new project | Write |\n| `vercel_update_project` | Update project name, framework, or settings | Write |\n| `vercel_delete_project` | Delete a project and its deployments | Write |\n\n### Deployments\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_deployments` | List deployments with pagination and filters | Read |\n| `vercel_get_deployment` | Get deployment details including status and URLs | Read |\n| `vercel_create_deployment` | Create a new deployment | Write |\n| `vercel_cancel_deployment` | Cancel an in-progress deployment | Write |\n| `vercel_delete_deployment` | Delete a deployment | Write |\n\n### Domains\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_domains` | List all domains in the account | Read |\n| `vercel_get_domain` | Get domain details and DNS records | Read |\n| `vercel_add_domain` | Add a domain to a project | Write |\n| `vercel_remove_domain` | Remove a domain from a project | Write |\n| `vercel_verify_domain` | Verify domain ownership | Write |\n\n### Environment Variables\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_env` | List environment variables for a project | Read |\n| `vercel_add_env` | Add an environment variable to a project | Write |\n| `vercel_update_env` | Update an environment variable's value or scope | Write |\n| `vercel_delete_env` | Remove an environment variable | Write |\n\n### Teams & Members\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_team_members` | List all members of a team | Read |\n| `vercel_invite_team_member` | Invite a new member to the team | Write |\n| `vercel_remove_team_member` | Remove a member from the team | Write |\n| `vercel_update_team_member_role` | Change a member's role | Write |\n\n### Secrets\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_secrets` | List all secrets in the account | Read |\n| `vercel_create_secret` | Create a secret for use in environment variables | Write |\n| `vercel_delete_secret` | Delete a secret | Write |\n\n### Logs & Events\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_get_deployment_events` | Get deployment event log | Read |\n| `vercel_get_audit_logs` | Get team audit logs | Read |\n\n## Code Examples\n\n### List all projects\n\n```bash\nclawlink_call_tool --tool \"vercel_list_projects\" \\\n --params '{\n \"team_id\": \"team_id\"\n }'\n```\n\n### Get deployment details\n\n```bash\nclawlink_call_tool --tool \"vercel_get_deployment\" \\\n --params '{\n \"deployment_id\": \"dpl_1234567890\"\n }'\n```\n\n### List deployments for a project\n\n```bash\nclawlink_call_tool --tool \"vercel_list_deployments\" \\\n --params '{\n \"project_name\": \"my-nextjs-app\",\n \"limit\": 10\n }'\n```\n\n### Add an environment variable\n\n```bash\nclawlink_call_tool --tool \"vercel_add_env\" \\\n --params '{\n \"project_name\": \"my-nextjs-app\",\n \"key\": \"DATABASE_URL\",\n \"value\": \"postgres://...\",\n \"environment\": \"production\"\n }'\n```\n\n### Verify a domain\n\n```bash\nclawlink_call_tool --tool \"vercel_verify_domain\" \\\n --params '{\n \"domain\": \"example.com\"\n }'\n```\n\n### Cancel a deployment\n\n```bash\nclawlink_call_tool --tool \"vercel_cancel_deployment\" \\\n --params '{\n \"deployment_id\": \"dpl_1234567890\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Vercel is connected.\n2. Call `clawlink_list_tools --integration vercel` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `vercel`.\n5. If no Vercel tools appear, direct the user to https://claw-link.dev/dashboard?add=vercel.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → describe │\n│ │\n│ Example: List projects → Get deployments → Show status │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ describe → preview → confirm → call │\n│ │\n│ Example: Preview env var change → User approves → Update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Deployment IDs start with `dpl_` and project names are used in deployment URLs.\n- Environment variables can be scoped to `development`, `preview`, or `production` environments.\n- Domain verification requires adding DNS records — check the verification status with `vercel_get_domain`.\n- Deleted deployments cannot be restored.\n- Team operations require the authenticated user to be a team owner or admin.\n- Vercel uses a specific deployment URL format: `https://project.vercel.app`.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration vercel`. |\n| Missing connection | Vercel is not connected. Direct the user to https://claw-link.dev/dashboard?add=vercel. |\n| `Project not found` | The project name does not exist in the account. |\n| `Deployment not found` | The deployment ID does not exist. |\n| `Domain not found` | The domain is not registered with the account. |\n| `Domain not verified` | Domain ownership has not been verified. Add DNS records first. |\n| `Env not found` | The environment variable does not exist in the project. |\n| `Forbidden` | The account lacks permission for this operation. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n## Resources\n\n- [Vercel REST API Documentation](https://vercel.com/docs/rest-api)\n- [Vercel API Reference](https://vercel.com/docs/rest-api)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.4:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"vercel-deployments\",\n \"version\": \"1.0.4\",\n \"publishedAt\": 1780980577953\n}\n\nFile v1.0.4:skill-card.md\n\n## Description:
\nManage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and DevOps engineers use this skill to inspect Vercel resources, manage deployments, configure domains and environment variables, and perform team or project administration through a connected Vercel account.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill requires OAuth access to a connected Vercel account and may handle sensitive credentials through ClawLink.
\nMitigation: Install only when comfortable connecting the account, verify the active Vercel integration before use, and rely on the connected account scopes granted during OAuth.
\nRisk: Write operations can change deployments, domains, environment variables, secrets, team membership, or projects.
\nMitigation: Preview account-changing actions and execute them only after the user confirms that the proposed change matches their intent.
\nRisk: Destructive actions such as deleting deployments, removing domains, deleting secrets, or deleting projects can have lasting operational impact.
\nMitigation: Treat destructive operations as high-impact, confirm the exact target resource, and report real API errors rather than guessing outcomes.
\n\n\n## Reference(s):
\n- [Vercel REST API Documentation](https://vercel.com/docs/rest-api)
\n- [Vercel API Reference](https://vercel.com/docs/rest-api)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Verification](https://claw-link.dev/verify)
\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/vercel-deployments)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and tool-call JSON examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May guide authenticated Vercel read and write workflows through ClawLink after user confirmation.]
\n\n## Skill Version(s):
\n1.0.4 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.1: 3 files, 5497 bytes\n\nFiles: skill-card.md (2327b), SKILL.md (13530b), _meta.json (137b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: vercel-deployments\ndescription: Manage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API. Use this skill when users want to inspect deployments, manage projects, configure domains, or automate Vercel DevOps workflows.\n---\n\n# Vercel\n\n\n\nManage Vercel projects, deployments, domains, environment variables, and team resources from chat via the Vercel REST API.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Vercel API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Vercel |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Vercel |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Vercel REST │\n│ (User Chat) │ │ (OAuth) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Vercel │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Vercel │\n │ File │ │ Auth │ │ Account │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Vercel again.\"\n\n## Quick Start\n\n```bash\n# List projects\nclawlink_call_tool --tool \"vercel_list_projects\" --params '{}'\n\n# Get deployment details\nclawlink_call_tool --tool \"vercel_get_deployment\" --params '{\"deployment_id\": \"DEPLOYMENT_ID\"}'\n\n# List deployments\nclawlink_call_tool --tool \"vercel_list_deployments\" --params '{\"project_name\": \"my-project\"}'\n```\n\n## Authentication\n\nAll Vercel tool calls are authenticated automatically by ClawLink using the user's connected Vercel account token.\n\n**No API token is required in chat.** ClawLink stores the token securely and injects it into every Vercel API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=vercel and connect Vercel.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `vercel` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration vercel\n```\n\n**Response:** Returns the live tool catalog for Vercel.\n\n### Reconnect\n\nIf Vercel tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=vercel\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration vercel`\n\n## Security & Permissions\n\n- Access is scoped to the Vercel account connected during OAuth setup and the scopes granted.\n- **All write operations (deploy, create project, update settings, add domains) require explicit user confirmation.**\n- Destructive operations (delete deployment, remove domain) are high-impact and must be confirmed.\n- Environment variable changes can affect running deployments — confirm before modifying.\n\n## Tool Reference\n\n### Projects\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_projects` | List all projects in the account/team | Read |\n| `vercel_get_project` | Get project configuration and settings | Read |\n| `vercel_create_project` | Create a new project | Write |\n| `vercel_update_project` | Update project name, framework, or settings | Write |\n| `vercel_delete_project` | Delete a project and its deployments | Write |\n\n### Deployments\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_deployments` | List deployments with pagination and filters | Read |\n| `vercel_get_deployment` | Get deployment details including status and URLs | Read |\n| `vercel_create_deployment` | Create a new deployment | Write |\n| `vercel_cancel_deployment` | Cancel an in-progress deployment | Write |\n| `vercel_delete_deployment` | Delete a deployment | Write |\n\n### Domains\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_domains` | List all domains in the account | Read |\n| `vercel_get_domain` | Get domain details and DNS records | Read |\n| `vercel_add_domain` | Add a domain to a project | Write |\n| `vercel_remove_domain` | Remove a domain from a project | Write |\n| `vercel_verify_domain` | Verify domain ownership | Write |\n\n### Environment Variables\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_env` | List environment variables for a project | Read |\n| `vercel_add_env` | Add an environment variable to a project | Write |\n| `vercel_update_env` | Update an environment variable's value or scope | Write |\n| `vercel_delete_env` | Remove an environment variable | Write |\n\n### Teams & Members\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_team_members` | List all members of a team | Read |\n| `vercel_invite_team_member` | Invite a new member to the team | Write |\n| `vercel_remove_team_member` | Remove a member from the team | Write |\n| `vercel_update_team_member_role` | Change a member's role | Write |\n\n### Secrets\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_secrets` | List all secrets in the account | Read |\n| `vercel_create_secret` | Create a secret for use in environment variables | Write |\n| `vercel_delete_secret` | Delete a secret | Write |\n\n### Logs & Events\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_get_deployment_events` | Get deployment event log | Read |\n| `vercel_get_audit_logs` | Get team audit logs | Read |\n\n## Code Examples\n\n### List all projects\n\n```bash\nclawlink_call_tool --tool \"vercel_list_projects\" \\\n --params '{\n \"team_id\": \"team_id\"\n }'\n```\n\n### Get deployment details\n\n```bash\nclawlink_call_tool --tool \"vercel_get_deployment\" \\\n --params '{\n \"deployment_id\": \"dpl_1234567890\"\n }'\n```\n\n### List deployments for a project\n\n```bash\nclawlink_call_tool --tool \"vercel_list_deployments\" \\\n --params '{\n \"project_name\": \"my-nextjs-app\",\n \"limit\": 10\n }'\n```\n\n### Add an environment variable\n\n```bash\nclawlink_call_tool --tool \"vercel_add_env\" \\\n --params '{\n \"project_name\": \"my-nextjs-app\",\n \"key\": \"DATABASE_URL\",\n \"value\": \"postgres://...\",\n \"environment\": \"production\"\n }'\n```\n\n### Verify a domain\n\n```bash\nclawlink_call_tool --tool \"vercel_verify_domain\" \\\n --params '{\n \"domain\": \"example.com\"\n }'\n```\n\n### Cancel a deployment\n\n```bash\nclawlink_call_tool --tool \"vercel_cancel_deployment\" \\\n --params '{\n \"deployment_id\": \"dpl_1234567890\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Vercel is connected.\n2. Call `clawlink_list_tools --integration vercel` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `vercel`.\n5. If no Vercel tools appear, direct the user to https://claw-link.dev/dashboard?add=vercel.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → describe │\n│ │\n│ Example: List projects → Get deployments → Show status │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ describe → preview → confirm → call │\n│ │\n│ Example: Preview env var change → User approves → Update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Deployment IDs start with `dpl_` and project names are used in deployment URLs.\n- Environment variables can be scoped to `development`, `preview`, or `production` environments.\n- Domain verification requires adding DNS records — check the verification status with `vercel_get_domain`.\n- Deleted deployments cannot be restored.\n- Team operations require the authenticated user to be a team owner or admin.\n- Vercel uses a specific deployment URL format: `https://project.vercel.app`.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration vercel`. |\n| Missing connection | Vercel is not connected. Direct the user to https://claw-link.dev/dashboard?add=vercel. |\n| `Project not found` | The project name does not exist in the account. |\n| `Deployment not found` | The deployment ID does not exist. |\n| `Domain not found` | The domain is not registered with the account. |\n| `Domain not verified` | Domain ownership has not been verified. Add DNS records first. |\n| `Env not found` | The environment variable does not exist in the project. |\n| `Forbidden` | The account lacks permission for this operation. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n## Resources\n\n- [Vercel REST API Documentation](https://vercel.com/docs/rest-api)\n- [Vercel API Reference](https://vercel.com/docs/rest-api)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"vercel-deployments\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1780937001372\n}\n\nFile v1.0.1:skill-card.md\n\n## Description:
\nManage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and DevOps teams use this skill to inspect and manage Vercel projects, deployments, domains, environment variables, secrets, logs, and team resources from an agent workflow.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill brokers access to a connected Vercel account through ClawLink OAuth.
\nMitigation: Install only when ClawLink is trusted, review OAuth scopes during connection, and use the least-privileged Vercel account or team practical.
\nRisk: Write actions can change deployments, domains, environment variables, secrets, or team membership.
\nMitigation: Use preview and explicit confirmation before write actions, and verify the target project, domain, environment, or team member before execution.
\nRisk: Some destructive actions, such as deleting deployments or removing domains, may be hard to reverse.
\nMitigation: Prefer read and describe operations first, confirm destructive intent explicitly, and report real tool errors without inventing outcomes.
\n\n\n## Reference(s):
\n- [Vercel REST API Documentation](https://vercel.com/docs/rest-api)
\n- [ClawLink OpenClaw Documentation](https://docs.claw-link.dev/openclaw)
\n- [ClawLink](https://claw-link.dev)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and structured tool-call guidance]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May include previews, confirmations, and follow-up checks before write operations.]
\n\n## Skill Version(s):
\n1.0.1 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v0.2.1: 3 files, 5442 bytes\n\nFiles: skill-card.md (2340b), SKILL.md (13416b), _meta.json (137b)\n\nFile v0.2.1:SKILL.md\n\n---\nname: vercel-deployments\ndescription: Manage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API. Use this skill when users want to inspect deployments, manage projects, configure domains, or automate Vercel DevOps workflows.\n---\n\n# Vercel\n\nManage Vercel projects, deployments, domains, environment variables, and team resources from chat via the Vercel REST API.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Vercel API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Vercel |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Vercel |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Vercel REST │\n│ (User Chat) │ │ (OAuth) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Vercel │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Vercel │\n │ File │ │ Auth │ │ Account │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Vercel again.\"\n\n## Quick Start\n\n```bash\n# List projects\nclawlink_call_tool --tool \"vercel_list_projects\" --params '{}'\n\n# Get deployment details\nclawlink_call_tool --tool \"vercel_get_deployment\" --params '{\"deployment_id\": \"DEPLOYMENT_ID\"}'\n\n# List deployments\nclawlink_call_tool --tool \"vercel_list_deployments\" --params '{\"project_name\": \"my-project\"}'\n```\n\n## Authentication\n\nAll Vercel tool calls are authenticated automatically by ClawLink using the user's connected Vercel account token.\n\n**No API token is required in chat.** ClawLink stores the token securely and injects it into every Vercel API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=vercel and connect Vercel.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `vercel` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration vercel\n```\n\n**Response:** Returns the live tool catalog for Vercel.\n\n### Reconnect\n\nIf Vercel tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=vercel\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration vercel`\n\n## Security & Permissions\n\n- Access is scoped to the Vercel account connected during OAuth setup and the scopes granted.\n- **All write operations (deploy, create project, update settings, add domains) require explicit user confirmation.**\n- Destructive operations (delete deployment, remove domain) are high-impact and must be confirmed.\n- Environment variable changes can affect running deployments — confirm before modifying.\n\n## Tool Reference\n\n### Projects\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_projects` | List all projects in the account/team | Read |\n| `vercel_get_project` | Get project configuration and settings | Read |\n| `vercel_create_project` | Create a new project | Write |\n| `vercel_update_project` | Update project name, framework, or settings | Write |\n| `vercel_delete_project` | Delete a project and its deployments | Write |\n\n### Deployments\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_deployments` | List deployments with pagination and filters | Read |\n| `vercel_get_deployment` | Get deployment details including status and URLs | Read |\n| `vercel_create_deployment` | Create a new deployment | Write |\n| `vercel_cancel_deployment` | Cancel an in-progress deployment | Write |\n| `vercel_delete_deployment` | Delete a deployment | Write |\n\n### Domains\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_domains` | List all domains in the account | Read |\n| `vercel_get_domain` | Get domain details and DNS records | Read |\n| `vercel_add_domain` | Add a domain to a project | Write |\n| `vercel_remove_domain` | Remove a domain from a project | Write |\n| `vercel_verify_domain` | Verify domain ownership | Write |\n\n### Environment Variables\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_env` | List environment variables for a project | Read |\n| `vercel_add_env` | Add an environment variable to a project | Write |\n| `vercel_update_env` | Update an environment variable's value or scope | Write |\n| `vercel_delete_env` | Remove an environment variable | Write |\n\n### Teams & Members\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_team_members` | List all members of a team | Read |\n| `vercel_invite_team_member` | Invite a new member to the team | Write |\n| `vercel_remove_team_member` | Remove a member from the team | Write |\n| `vercel_update_team_member_role` | Change a member's role | Write |\n\n### Secrets\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_secrets` | List all secrets in the account | Read |\n| `vercel_create_secret` | Create a secret for use in environment variables | Write |\n| `vercel_delete_secret` | Delete a secret | Write |\n\n### Logs & Events\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_get_deployment_events` | Get deployment event log | Read |\n| `vercel_get_audit_logs` | Get team audit logs | Read |\n\n## Code Examples\n\n### List all projects\n\n```bash\nclawlink_call_tool --tool \"vercel_list_projects\" \\\n --params '{\n \"team_id\": \"team_id\"\n }'\n```\n\n### Get deployment details\n\n```bash\nclawlink_call_tool --tool \"vercel_get_deployment\" \\\n --params '{\n \"deployment_id\": \"dpl_1234567890\"\n }'\n```\n\n### List deployments for a project\n\n```bash\nclawlink_call_tool --tool \"vercel_list_deployments\" \\\n --params '{\n \"project_name\": \"my-nextjs-app\",\n \"limit\": 10\n }'\n```\n\n### Add an environment variable\n\n```bash\nclawlink_call_tool --tool \"vercel_add_env\" \\\n --params '{\n \"project_name\": \"my-nextjs-app\",\n \"key\": \"DATABASE_URL\",\n \"value\": \"postgres://...\",\n \"environment\": \"production\"\n }'\n```\n\n### Verify a domain\n\n```bash\nclawlink_call_tool --tool \"vercel_verify_domain\" \\\n --params '{\n \"domain\": \"example.com\"\n }'\n```\n\n### Cancel a deployment\n\n```bash\nclawlink_call_tool --tool \"vercel_cancel_deployment\" \\\n --params '{\n \"deployment_id\": \"dpl_1234567890\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Vercel is connected.\n2. Call `clawlink_list_tools --integration vercel` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `vercel`.\n5. If no Vercel tools appear, direct the user to https://claw-link.dev/dashboard?add=vercel.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → describe │\n│ │\n│ Example: List projects → Get deployments → Show status │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ describe → preview → confirm → call │\n│ │\n│ Example: Preview env var change → User approves → Update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Deployment IDs start with `dpl_` and project names are used in deployment URLs.\n- Environment variables can be scoped to `development`, `preview`, or `production` environments.\n- Domain verification requires adding DNS records — check the verification status with `vercel_get_domain`.\n- Deleted deployments cannot be restored.\n- Team operations require the authenticated user to be a team owner or admin.\n- Vercel uses a specific deployment URL format: `https://project.vercel.app`.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration vercel`. |\n| Missing connection | Vercel is not connected. Direct the user to https://claw-link.dev/dashboard?add=vercel. |\n| `Project not found` | The project name does not exist in the account. |\n| `Deployment not found` | The deployment ID does not exist. |\n| `Domain not found` | The domain is not registered with the account. |\n| `Domain not verified` | Domain ownership has not been verified. Add DNS records first. |\n| `Env not found` | The environment variable does not exist in the project. |\n| `Forbidden` | The account lacks permission for this operation. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n## Resources\n\n- [Vercel REST API Documentation](https://vercel.com/docs/rest-api)\n- [Vercel API Reference](https://vercel.com/docs/rest-api)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v0.2.1:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"vercel-deployments\",\n \"version\": \"0.2.1\",\n \"publishedAt\": 1780840348353\n}\n\nFile v0.2.1:skill-card.md\n\n## Description:
\nManage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and DevOps engineers use this skill to inspect and manage Vercel projects, deployments, domains, environment variables, secrets, and team resources from an agent workflow.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can broker access to a connected Vercel account and may handle sensitive deployment, domain, secret, environment variable, project, and team operations.
\nMitigation: Review the Vercel account, team, and OAuth permissions before connecting; revoke the ClawLink/Vercel connection when it is no longer needed.
\nRisk: Write or destructive actions can change projects, domains, deployments, environment variables, secrets, or team membership.
\nMitigation: Preview and confirm write or destructive actions before execution, and verify the target project, domain, environment, secret, or team member matches the user's intent.
\n\n\n## Reference(s):
\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/vercel-deployments)
\n- [Vercel REST API Documentation](https://vercel.com/docs/rest-api)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Verification](https://claw-link.dev/verify)
\n\n\n## Skill Output:
\n**Output Type(s):** [guidance, shell commands, configuration, API calls]
\n**Output Format:** [Markdown with inline shell commands and JSON parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Requires a connected Vercel account through ClawLink; write and destructive operations require explicit user confirmation.]
\n\n## Skill Version(s):
\n0.2.1 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v0.2.0: 3 files, 5602 bytes\n\nFiles: skill-card.md (2715b), SKILL.md (13416b), _meta.json (137b)\n\nFile v0.2.0:SKILL.md\n\n---\nname: vercel-deployments\ndescription: Manage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API. Use this skill when users want to inspect deployments, manage projects, configure domains, or automate Vercel DevOps workflows.\n---\n\n# Vercel\n\nManage Vercel projects, deployments, domains, environment variables, and team resources from chat via the Vercel REST API.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Vercel API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Vercel |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Vercel |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Vercel REST │\n│ (User Chat) │ │ (OAuth) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Vercel │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Vercel │\n │ File │ │ Auth │ │ Account │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Vercel again.\"\n\n## Quick Start\n\n```bash\n# List projects\nclawlink_call_tool --tool \"vercel_list_projects\" --params '{}'\n\n# Get deployment details\nclawlink_call_tool --tool \"vercel_get_deployment\" --params '{\"deployment_id\": \"DEPLOYMENT_ID\"}'\n\n# List deployments\nclawlink_call_tool --tool \"vercel_list_deployments\" --params '{\"project_name\": \"my-project\"}'\n```\n\n## Authentication\n\nAll Vercel tool calls are authenticated automatically by ClawLink using the user's connected Vercel account token.\n\n**No API token is required in chat.** ClawLink stores the token securely and injects it into every Vercel API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=vercel and connect Vercel.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `vercel` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration vercel\n```\n\n**Response:** Returns the live tool catalog for Vercel.\n\n### Reconnect\n\nIf Vercel tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=vercel\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration vercel`\n\n## Security & Permissions\n\n- Access is scoped to the Vercel account connected during OAuth setup and the scopes granted.\n- **All write operations (deploy, create project, update settings, add domains) require explicit user confirmation.**\n- Destructive operations (delete deployment, remove domain) are high-impact and must be confirmed.\n- Environment variable changes can affect running deployments — confirm before modifying.\n\n## Tool Reference\n\n### Projects\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_projects` | List all projects in the account/team | Read |\n| `vercel_get_project` | Get project configuration and settings | Read |\n| `vercel_create_project` | Create a new project | Write |\n| `vercel_update_project` | Update project name, framework, or settings | Write |\n| `vercel_delete_project` | Delete a project and its deployments | Write |\n\n### Deployments\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_deployments` | List deployments with pagination and filters | Read |\n| `vercel_get_deployment` | Get deployment details including status and URLs | Read |\n| `vercel_create_deployment` | Create a new deployment | Write |\n| `vercel_cancel_deployment` | Cancel an in-progress deployment | Write |\n| `vercel_delete_deployment` | Delete a deployment | Write |\n\n### Domains\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_domains` | List all domains in the account | Read |\n| `vercel_get_domain` | Get domain details and DNS records | Read |\n| `vercel_add_domain` | Add a domain to a project | Write |\n| `vercel_remove_domain` | Remove a domain from a project | Write |\n| `vercel_verify_domain` | Verify domain ownership | Write |\n\n### Environment Variables\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_env` | List environment variables for a project | Read |\n| `vercel_add_env` | Add an environment variable to a project | Write |\n| `vercel_update_env` | Update an environment variable's value or scope | Write |\n| `vercel_delete_env` | Remove an environment variable | Write |\n\n### Teams & Members\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_team_members` | List all members of a team | Read |\n| `vercel_invite_team_member` | Invite a new member to the team | Write |\n| `vercel_remove_team_member` | Remove a member from the team | Write |\n| `vercel_update_team_member_role` | Change a member's role | Write |\n\n### Secrets\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_list_secrets` | List all secrets in the account | Read |\n| `vercel_create_secret` | Create a secret for use in environment variables | Write |\n| `vercel_delete_secret` | Delete a secret | Write |\n\n### Logs & Events\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `vercel_get_deployment_events` | Get deployment event log | Read |\n| `vercel_get_audit_logs` | Get team audit logs | Read |\n\n## Code Examples\n\n### List all projects\n\n```bash\nclawlink_call_tool --tool \"vercel_list_projects\" \\\n --params '{\n \"team_id\": \"team_id\"\n }'\n```\n\n### Get deployment details\n\n```bash\nclawlink_call_tool --tool \"vercel_get_deployment\" \\\n --params '{\n \"deployment_id\": \"dpl_1234567890\"\n }'\n```\n\n### List deployments for a project\n\n```bash\nclawlink_call_tool --tool \"vercel_list_deployments\" \\\n --params '{\n \"project_name\": \"my-nextjs-app\",\n \"limit\": 10\n }'\n```\n\n### Add an environment variable\n\n```bash\nclawlink_call_tool --tool \"vercel_add_env\" \\\n --params '{\n \"project_name\": \"my-nextjs-app\",\n \"key\": \"DATABASE_URL\",\n \"value\": \"postgres://...\",\n \"environment\": \"production\"\n }'\n```\n\n### Verify a domain\n\n```bash\nclawlink_call_tool --tool \"vercel_verify_domain\" \\\n --params '{\n \"domain\": \"example.com\"\n }'\n```\n\n### Cancel a deployment\n\n```bash\nclawlink_call_tool --tool \"vercel_cancel_deployment\" \\\n --params '{\n \"deployment_id\": \"dpl_1234567890\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Vercel is connected.\n2. Call `clawlink_list_tools --integration vercel` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `vercel`.\n5. If no Vercel tools appear, direct the user to https://claw-link.dev/dashboard?add=vercel.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → describe │\n│ │\n│ Example: List projects → Get deployments → Show status │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ describe → preview → confirm → call │\n│ │\n│ Example: Preview env var change → User approves → Update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Deployment IDs start with `dpl_` and project names are used in deployment URLs.\n- Environment variables can be scoped to `development`, `preview`, or `production` environments.\n- Domain verification requires adding DNS records — check the verification status with `vercel_get_domain`.\n- Deleted deployments cannot be restored.\n- Team operations require the authenticated user to be a team owner or admin.\n- Vercel uses a specific deployment URL format: `https://project.vercel.app`.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration vercel`. |\n| Missing connection | Vercel is not connected. Direct the user to https://claw-link.dev/dashboard?add=vercel. |\n| `Project not found` | The project name does not exist in the account. |\n| `Deployment not found` | The deployment ID does not exist. |\n| `Domain not found` | The domain is not registered with the account. |\n| `Domain not verified` | Domain ownership has not been verified. Add DNS records first. |\n| `Env not found` | The environment variable does not exist in the project. |\n| `Forbidden` | The account lacks permission for this operation. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n## Resources\n\n- [Vercel REST API Documentation](https://vercel.com/docs/rest-api)\n- [Vercel API Reference](https://vercel.com/docs/rest-api)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v0.2.0:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"vercel-deployments\",\n \"version\": \"0.2.0\",\n \"publishedAt\": 1780839675023\n}\n\nFile v0.2.0:skill-card.md\n\n## Description:
\nManage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and DevOps teams use this skill to inspect and manage Vercel projects, deployments, domains, environment variables, secrets, and team resources from an agent workflow.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill requires ClawLink OAuth access to a Vercel account, which can expose account, project, team, deployment, domain, environment variable, secret, and audit-log operations within granted scopes.
\nMitigation: Review Vercel OAuth scopes during connection, connect the least-privileged account that fits the task, and avoid production or team-owner access unless those capabilities are required.
\nRisk: Write and destructive Vercel actions can create, update, cancel, remove, or delete operational resources.
\nMitigation: Use the skill's preview and explicit confirmation workflow before any write or destructive action, and verify the target project, deployment, domain, team, and environment before execution.
\nRisk: Environment variable and secret changes can affect running or future deployments and may involve sensitive values.
\nMitigation: Confirm the environment scope and target project before modifying values, avoid exposing secrets in chat, and prefer read-only inspection before changes.
\n\n\n## Reference(s):
\n- [Vercel REST API Documentation](https://vercel.com/docs/rest-api)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Verification](https://claw-link.dev/verify)
\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/vercel-deployments)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown guidance with inline shell commands and JSON tool parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Uses ClawLink OAuth-backed Vercel tool calls; write and destructive actions require preview and confirmation.]
\n\n## Skill Version(s):
\n0.2.0 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v0.1.0: 3 files, 3349 bytes\n\nFiles: skill-card.md (2172b), SKILL.md (5042b), _meta.json (137b)\n\nFile v0.1.0:SKILL.md\n\n---\nname: vercel-deployments\ndescription: Manage projects, deployments, domains, and environment variables in Vercel - powered by ClawLink.\n---\n\n# Vercel\n\nWork with Vercel from chat - inspect projects, deployments, domains, environment variables, and team resources.\n\nPowered by [ClawLink](https://claw-link.dev), an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Vercel API access yourself.\n\n## Quick start\n\n1. Install the verified ClawLink plugin: `openclaw plugins install clawhub:clawlink-plugin`\n2. Start a fresh OpenClaw chat if the plugin was just installed and ClawLink tools are not visible yet\n3. If ClawLink is not configured, call `clawlink_begin_pairing`\n4. Tell the user to open the returned pairing URL, sign in to ClawLink if needed, and approve the device\n5. After the user confirms approval, call `clawlink_get_pairing_status`\n6. Tell the user to connect Vercel at [claw-link.dev/dashboard?add=vercel](https://claw-link.dev/dashboard?add=vercel)\n7. When the user confirms Vercel is connected, call `clawlink_list_integrations` and then `clawlink_list_tools` with the `vercel` integration slug\n\n## Setup details\n\n### Installing the plugin\n\nIf the ClawLink plugin is not installed yet, tell the user to run:\n\n```\nopenclaw plugins install clawhub:clawlink-plugin\n```\n\nIf the current chat started before the plugin was installed and ClawLink tools are still unavailable, tell the user to start a fresh chat so OpenClaw reloads the plugin tool catalog.\n\n### Pairing ClawLink\n\nIf ClawLink reports that the plugin is not configured, the plugin has not been paired with the user's ClawLink account yet.\n\n1. Call `clawlink_begin_pairing`.\n2. Tell the user to open the returned pairing URL in their browser.\n3. The user signs in to ClawLink if needed and approves the OpenClaw device.\n4. After the user confirms approval, call `clawlink_get_pairing_status` to finish local setup.\n\nThe resulting device credential is stored locally in OpenClaw's plugin config and is only sent to `claw-link.dev`. The user should not paste raw credentials into chat.\n\n### Connecting Vercel\n\nTell the user to open https://claw-link.dev/dashboard?add=vercel and connect Vercel there. The page opens the add-connection panel filtered to Vercel. ClawLink's hosted page runs the Vercel provider connection flow. When they confirm it is done, call `clawlink_list_integrations` to verify, then call `clawlink_list_tools` with integration `vercel`.\n\n## Using Vercel tools\n\nClawLink provides tools dynamically based on what the user has connected. You do not need to know tool names or schemas in advance.\n\n### Discovery\n\n1. Call `clawlink_list_integrations` to confirm Vercel is connected.\n2. Call `clawlink_list_tools` with integration `vercel`.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `vercel`.\n5. If no Vercel tools appear, direct the user to https://claw-link.dev/dashboard?add=vercel.\n\n### Execution\n\n1. Call `clawlink_describe_tool` before using an unfamiliar tool, before any write, or when the request is ambiguous.\n2. Use the returned schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups`.\n3. Prefer team, project, deployment, domain, and environment reads before changing project state.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first, then confirm with the user.\n5. Execute with `clawlink_call_tool`.\n6. If it fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## What you can do\n\nTypical Vercel tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog):\n\n- Inspect users, teams, projects, deployments, and attached domains\n- Review environment variables for a project\n- Create projects or deployments after confirmation\n- Attach domains to projects after confirmation\n- Update project settings or add environment variables after confirmation\n\n## Rules\n\n- Always use ClawLink tools for Vercel. Do not ask the user for separate Vercel credentials.\n- Do not claim a capability is missing without checking the live ClawLink catalog in the current turn.\n- Do not invent slash commands or ask the user to paste raw credentials.\n- Ask for confirmation before deployments, project creation, environment-variable changes, domain changes, or settings updates.\n- If Vercel is not connected, direct the user to https://claw-link.dev/dashboard?add=vercel.\n- Never echo or repeat the user's ClawLink credential.\n\n## Resources\n\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n- ClawLink Source: https://github.com/hith3sh/clawlink\n- Vercel REST API: https://vercel.com/docs/rest-api\n\nFile v0.1.0:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"vercel-deployments\",\n \"version\": \"0.1.0\",\n \"publishedAt\": 1779633078213\n}\n\nFile v0.1.0:skill-card.md\n\n## Description:
\nManage projects, deployments, domains, and environment variables in Vercel - powered by ClawLink.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineers use this skill to inspect and manage Vercel projects, deployments, domains, environment variables, and team resources through ClawLink-connected tools.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can guide actions that affect Vercel deployments, domains, project settings, or environment variables.
\nMitigation: Review ClawLink previews and confirm intent before approving deployments, domain changes, project changes, or environment-variable updates.
\nRisk: Vercel access depends on connected ClawLink and Vercel permissions.
\nMitigation: Use least-privilege Vercel access where possible and do not paste raw credentials into chat.
\n\n\n## Reference(s):
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Verification](https://claw-link.dev/verify)
\n- [ClawLink Source](https://github.com/hith3sh/clawlink)
\n- [Vercel REST API](https://vercel.com/docs/rest-api)
\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/vercel-deployments)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and tool-use guidance]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Uses the live ClawLink catalog as the source of truth and asks for confirmation before sensitive Vercel changes.]
\n\n## Skill Version(s):
\n0.1.0 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
","readmeExcerpt":"Skill: Vercel Owner: hith3sh Summary: Manage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API. Use this skill when users want to inspect de... Tags: latest:1.0.6 Version history: v1.0.6 | 2026-06-09T07:20:43.913Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Vercel REST │\n│ (User Chat) │ │ (OAuth) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Vercel │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Vercel │\n │ File │ │ Auth │ │ Account │\n └──────────┘ └──────────┘ └──────────┘"},{"language":"bash","snippet":"openclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart"},{"language":"bash","snippet":"# List projects\nclawlink_call_tool --tool \"vercel_list_projects\" --params '{}'\n\n# Get deployment details\nclawlink_call_tool --tool \"vercel_get_deployment\" --params '{\"deployment_id\": \"DEPLOYMENT_ID\"}'\n\n# List deployments\nclawlink_call_tool --tool \"vercel_list_deployments\" --params '{\"project_name\": \"my-project\"}'"},{"language":"bash","snippet":"clawlink_list_integrations"},{"language":"bash","snippet":"clawlink_list_tools --integration vercel"},{"language":"bash","snippet":"clawlink_call_tool --tool \"vercel_list_projects\" \\\n --params '{\n \"team_id\": \"team_id\"\n }'"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: vercel-deployments\ndescription: Manage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API. Use this skill when users want to inspect deployments, manage projects, configure domains, or automate Vercel DevOps workflows.\n---\n\n# Vercel\n\n\n\nManage Vercel projects, deployments, domains, environment variables, and team resources from chat via the Vercel REST API.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=vercel-deployments) for hosted connection flows and credentials so you do not need to configure Vercel API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Vercel |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Vercel |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Vercel REST │\n│ (User Chat) │ │ (OAuth) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Vercel │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Vercel │\n │ File │ │ Auth │ │ Account │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Vercel again.\"\n\n## Quick Start\n\n```bash\n# List projects\nclawlink_call_tool --tool \"vercel_list_projects\" --params '{}'\n\n# Get deployment details\nclawlink_call_tool --tool \"vercel_get_deployment\" --params '{\"deployment_id\": \"DEPLOYMENT_ID\"}'\n\n# List deployments\nclawlink_call_tool --tool \"v"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"vercel-deployments\",\n \"version\": \"1.0.6\",\n \"publishedAt\": 1780989643913\n}"},{"path":"skill-card.md","content":"## Description:\n\nManage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and operators use this skill to inspect and manage Vercel projects, deployments, domains, environment variables, secrets, audit logs, and team resources from an agent workflow.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill requires installing and allowlisting an external ClawLink plugin that mediates access to Vercel account actions and credentials.\n\nMitigation: Install only when the publisher and ClawLink are trusted, review OAuth scopes before connecting, and know how to revoke the Vercel connection and remove the plugin allowlist entry.\n\nRisk: Write or destructive Vercel operations can change deployments, domains, environment variables, secrets, projects, or team access.\n\nMitigation: Preview write operations, confirm the exact target and effect with the user, and use the least-privileged Vercel account or team role practical.\n\nRisk: Environment variable, secret, and domain changes can affect running production deployments.\n\nMitigation: Check the intended environment or domain status first, prefer read/list/get operations before changes, and confirm production-impacting updates explicitly.\n\n## Reference(s):\n\n- [Vercel REST API Documentation](https://vercel.com/docs/rest-api)\n- [ClawLink OpenClaw Documentation](https://docs.claw-link.dev/openclaw)\n- [ClawLink Verification](https://claw-link.dev/verify)\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/skills/vercel-deployments)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]\n\n**Output Format:** [Markdown with inline shell commands and structured tool-call parameters]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include Vercel resource identifiers, JSON parameters for ClawLink tool calls, previews, confirmations, and error summaries.]\n\n## Skill Version(s):\n\n1.0.6 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Manage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API. Use this skill when users want to inspect de... Skill: Vercel Owner: hith3sh Summary: Manage Vercel projects, deployments, domains, environment variables, and team resources via the Vercel REST API. Use this skill when users want to inspect de... Tags: latest:1.0.6 Version history: v1.0.6 | 2026-06-09T07:20:43.913Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1058,"uniquenessScore":50,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T12:26:32.624Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-09T12:26:32.624Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-09T20:20:46.921Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}