Vercel Staging Workflow

Set up a staging/production workflow for Vercel projects using GitHub Actions and stable URL aliases. Use when asked to create a staging environment, set up...

This skill appears to do what it says: it provides a GitHub Action that polls Vercel for the latest READY deployment and sets a stable staging alias. Before installing, ensure you: (1) create a permanent Vercel API token with the minimum necessary scope and understand which projects it can modify; (2) store the token and IDs as GitHub secrets (do not hardcode them in the workflow); (3) set STAGING_ALIAS to a safe staging subdomain (do not accidentally use your production/custom domain); (4) verify the action's HTTP responses/logs after the first run and consider adding error handling or response checks if you need stricter guarantees; (5) be aware SKILL.md suggests a local step using the vercel CLI to obtain project.json — that step requires the vercel CLI on your machine but is optional if you obtain the projectId from the dashboard. If you need more assurance, test in a non-critical repo first.

Type: OpenClaw Skill Name: vercel-staging-workflow Version: 1.0.0 The skill bundle provides a legitimate utility for automating Vercel staging aliases via GitHub Actions. It uses standard Vercel API endpoints (api.vercel.com) and follows documented practices for CI/CD integration, such as using GitHub Secrets for sensitive tokens. No evidence of data exfiltration, malicious execution, or prompt injection was found in SKILL.md or the references/github-action-template.yml file.