vercel-automation
Automate Vercel Operations
Vercel administration often requires switching between dashboards, logs, and API details. This skill guides Claude, Codex, and Claude Code through Rube MCP workflows.
This skill is part of a pack
Install the whole pack to get every skill the task needs, in one command.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "vercel-automation" from https://skillstore.io/skills/sickn33-vercel-automation.md and its manifest at https://skillstore.io/api/skills/sickn33-vercel-automation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "vercel-automation". Check why the latest preview deployment failed.
Expected outcome:
The response identifies the latest failed preview deployment, summarizes the key log error, shows the event sequence, and lists recommended fixes.
Using "vercel-automation". Add a production environment variable for the billing project.
Expected outcome:
The response confirms the target project, requested variable name, target environment, and required approval before any write action is taken.
Using "vercel-automation". Review DNS records for my custom domain.
Expected outcome:
The response lists record types, names, values, and likely configuration issues without changing DNS until the user approves.
Security Audit
Medium RiskMost static external command findings are false positives caused by markdown backticks around tool names, parameters, and examples. The real risks are the external Rube MCP endpoint, Vercel OAuth trust boundary, and write-capable Vercel workflows that can affect production deployments, DNS, project settings, and environment variables.
Confirmed security concerns (2)
Capability review items (1)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (66)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-vercel-automation/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-vercel-automation?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-vercel-automation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-vercel-automation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-vercel-automation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). vercel-automation security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-vercel-automation/audits/4BibTeX citation
@techreport{sickn33-sickn33-vercel-automation-2026,
author = {sickn33},
title = {vercel-automation security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-vercel-automation/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "vercel-automation security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-vercel-automation/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-vercel-automation:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Debug Deployment Failures
Inspect recent deployments, logs, runtime events, and checks to find why a build failed.
Prepare Release Changes
Trigger a preview or production deployment after checking the project and target environment.
Review Domain And Team State
Check domain configuration, DNS records, team membership, and project settings before an operational change.
Try These Prompts
Search current Rube tool schemas first. List recent Vercel deployments for project <project name> with status, target, created time, and URL.
Find the latest failed deployment for <project name>. Review build logs, runtime logs if relevant, and deployment events. Summarize likely causes and next steps.
For project <project name>, list current environment variables. Prepare to add <key> for <targets>, but wait for my confirmation before making changes.
Inspect domain configuration and DNS records for <domain>. Propose any deployment, DNS, or project updates needed, then wait for explicit approval.
Best Practices
- Start each workflow by searching current Rube tool schemas.
- Require explicit confirmation before production, DNS, or environment variable changes.
- Use project IDs, deployment IDs, and record IDs from Vercel lookups instead of guessing.
Avoid
- Adding the external MCP server without reviewing permissions and data flow.
- Deleting environment variables or editing DNS records without confirmation.
- Assuming old Vercel tool schema names are still current.