Vercel Functions 部署

# Vercel Functions Deployment

Deploy a reviewed Vercel Functions revision and inspect its runtime logs.

## Required Aident Actions

- <action-tag>composio:vercel_tools:vercel_get_project2</action-tag> (required inputs: idOrName): Tool to find a project by ID or name with comprehensive details. Use when you need complete project metadata including configuration, deployments, security settings, and analytics.
- <action-tag>composio:vercel_tools:vercel_create_new_deployment</action-tag> (required inputs: name): Tool to create a new deployment. Use when you need to deploy files or a Git commit to a Vercel project.
- <action-tag>composio:vercel_tools:vercel_get_deployment_logs2</action-tag> (required inputs: projectId, deploymentId): Tool to retrieve runtime logs for a specific Vercel deployment by project and deployment ID. Use when you need to debug or monitor deployment execution with detailed runtime information.
- <action-tag>composio:vercel_tools:vercel_get_deployment</action-tag> (required inputs: idOrUrl): Tool to get a deployment by ID or URL. Use when you need to retrieve detailed information about a specific deployment.

Use Aident Loadout to read the current Action schema before constructing inputs. Check the required integration connection in Aident Vault. If an Action is billable or mutating, run Aident preflight, show the affected target and quoted cost or risk, and wait for explicit user confirmation before execution.

## Workflow

1. Confirm the requested outcome, source material, destination, audience, constraints, and acceptance criteria.
2. Apply the source-derived guidance below to create a concrete plan. Resolve ambiguity before invoking an Action.
3. Select only the Aident Actions whose documented effect directly advances the requested outcome. Do not invoke every listed Action by default.
4. Inspect the current schema and prepare the minimum valid input for each selected Action.
5. Preflight each selected Action. Execute it only after any required confirmation, in dependency order, and carry returned IDs or asset URLs into later steps.
6. Verify the returned IDs, URLs, statuses, or artifacts against the acceptance criteria. Report partial completion precisely and do not repeat paid or mutating calls blindly.

## Source-Derived Guidance

- Confirm runtime, route, environment target, and exact Git revision.
- Capture the deployment ID and inspect logs for startup or invocation errors.

## Execution Boundaries

- Treat upstream provider-specific commands as background knowledge only. Execute the workflow through the exact Aident Actions above.
- Never request raw credentials in chat. Use Aident Vault connection flows for required accounts.
- Preserve user-provided wording, brand constraints, rights restrictions, and target identifiers. Do not invent authorization.
- Read current state before a mutation, state the exact target, and include a rollback or recovery step in the result.
- After Vercel accepts a deployment, pass its returned ID to composio:vercel_tools:vercel_get_deployment at moderate intervals until READY or a terminal failure. Do not report the deployment as successful while it is queued or building.
- Stop when a required integration is disconnected, preflight rejects the input, the target is ambiguous, or the user declines a required confirmation.

## Output

Return the execution plan, selected Action names, confirmed targets, Aident result identifiers or asset URLs, verification evidence, and any remaining blocked step.

## Attribution

This Skill adapts the reviewed upstream workflow. See [UPSTREAM.md](UPSTREAM.md) for the pinned source and [LICENSE.txt](LICENSE.txt) for the preserved license.