How do I install the Policyengine Vercel Deployment skill?

Run npx skillmds@latest add tomevault-io/policyengine-vercel-deployment in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Policyengine Vercel Deployment safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Policyengine Vercel Deployment?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Policyengine Vercel Deployment free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Policyengine Vercel Deployment?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Policyengine Vercel Deployment by tomevault-io

Name: Policyengine Vercel Deployment
Author: tomevault-io

File contents

PolicyEngine Vercel Deployment

Standard patterns for deploying frontend apps (interactive tools, dashboards, static sites) to Vercel under the PolicyEngine team.

Deployment

Team and scope

All PE apps deploy under the policy-engine Vercel team:

vercel link --scope policy-engine
vercel --prod --yes --scope policy-engine

Naming convention

Projects use the pattern policyengine--{repo-name}:

policyengine--marriage.vercel.app
policyengine--aca-calc.vercel.app
policyengine--state-legislative-tracker.vercel.app

Vercel auto-assigns a random production URL (e.g., marriage-zeta-beryl.vercel.app). Use that in apps.json as the source URL since custom aliases may have deployment protection issues.

First deploy

cd my-project

# Link to team (creates .vercel/)
vercel link --scope policy-engine

# Deploy
vercel --prod --yes

Subsequent deploys

vercel --prod --yes --scope policy-engine

Environment variables

For apps with API backends (e.g., Modal):

# Set env var (Next.js uses NEXT_PUBLIC_* prefix)
vercel env add NEXT_PUBLIC_API_URL production

# Must force-redeploy after changing env vars
vercel --prod --force --yes --scope policy-engine

Next.js apps access env vars via process.env.NEXT_PUBLIC_API_URL.

Verify deployment

curl -s -o /dev/null -w "%{http_code}" https://your-app.vercel.app/
# Should return 200

Common issues

Deployed to personal account: If vercel --prod goes to your personal account, delete .vercel/ and re-link:

rm -rf .vercel
vercel link --scope policy-engine
vercel --prod --yes

Deployment protection (401): Team deployment protection may block unauthenticated access to alias URLs. Use the auto-assigned production URL instead, or configure in Vercel dashboard > Settings > Deployment Protection.

Generic project names: Never use generic names like app or site — they can steal domains from other projects. Always use descriptive names.

vercel.json

Must be at repo root. For Next.js static exports, configure rewrites as needed:

{
  "rewrites": [{ "source": "/(.*)", "destination": "/index.html" }]
}

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: policyengine-vercel-deploymentdescription: Deploying PolicyEngine frontend apps to Vercel - naming, scope, team settings Use when this capability is needed.---# PolicyEngine Vercel DeploymentStandard patterns for deploying frontend apps (interactive tools, dashboards, static sites) to Vercel under the PolicyEngine team.## Deployment### Team and scopeAll PE apps deploy under the `policy-engine` Vercel team:```bashvercel link --scope policy-enginevercel --prod --yes --scope policy-engine```### Naming conventionProjects use the pattern `policyengine--{repo-name}`:```policyengine--marriage.vercel.apppolicyengine--aca-calc.vercel.apppolicyengine--state-legislative-tracker.vercel.app```Vercel auto-assigns a random production URL (e.g., `marriage-zeta-beryl.vercel.app`). Use that in apps.json as the source URL since custom aliases may have deployment protection issues.### First deploy```bashcd my-project# Link to team (creates .vercel/)vercel link --scope policy-engine# Deployvercel --prod --yes```### Subsequent deploys```bashvercel --prod --yes --scope policy-engine```### Environment variablesFor apps with API backends (e.g., Modal):```bash# Set env var (Next.js uses NEXT_PUBLIC_* prefix)vercel env add NEXT_PUBLIC_API_URL production# Must force-redeploy after changing env varsvercel --prod --force --yes --scope policy-engine```Next.js apps access env vars via `process.env.NEXT_PUBLIC_API_URL`.### Verify deployment```bashcurl -s -o /dev/null -w "%{http_code}" https://your-app.vercel.app/# Should return 200```### Common issues**Deployed to personal account:** If `vercel --prod` goes to your personal account, delete `.vercel/` and re-link:```bashrm -rf .vercelvercel link --scope policy-enginevercel --prod --yes```**Deployment protection (401):** Team deployment protection may block unauthenticated access to alias URLs. Use the auto-assigned production URL instead, or configure in Vercel dashboard > Settings > Deployment Protection.**Generic project names:** Never use generic names like `app` or `site` — they can steal domains from other projects. Always use descriptive names.### vercel.jsonMust be at repo root. For Next.js static exports, configure rewrites as needed:```json{ "rewrites": [{ "source": "/(.*)", "destination": "/index.html" }]}```---> Converted and distributed by [TomeVault](https://tomevault.io/claim/policyengine) — claim your Tome and manage your conversions.

Frequently asked questions

Policyengine Vercel Deployment