Skip to content
Contact
Engineering

Deploy to Vercel

Vercel

Prepare Vercel deployment from current project configuration and explicit target authorization.

SKILL.md

---
name: knoveya-deploy-to-vercel
description: "Prepare Vercel deployment from current project configuration and explicit target authorization. Use for matching engineering work."
---

# Deploy to Vercel

## Scope

Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.

## Workflow

Prepare Vercel deployment from current project configuration and explicit target authorization.

Before acting, inspect the relevant artifact and ask only for information that materially changes the result. Use existing tools and conventions; do not install dependencies, publish, send messages, deploy, or mutate external data unless the user has authorized that operation.

## Acceptance check

Build verification and environment boundaries precede any production mutation.

## Example task

Create a preview only for the approved project and review the result.

## Report

State what changed, the evidence checked, and what remains unverified. Do not claim a successful operation or completed test without observing it.
View all

How to use

Copy the full block, including its frontmatter, into a new folder named knoveya-deploy-to-vercel as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-deploy-to-vercel/SKILL.md; check the current documentation for another agent's supported location. Do not overwrite an existing skill.

This is an independent Knoveya skill. No files are installed by this website.

Example

Create a preview only for the approved project and review the result.

Verify

Build verification and environment boundaries precede any production mutation.

Test the skill on a small, authorized example. File validation alone does not prove that an agent will make good decisions.

Limits

The skill supplies instructions, not tool access or expertise guarantees. Inspect generated work and preserve the user's approval boundaries.