agentleFS
Sign inStart free
prinxprinx/agents/skills/deploy-vercel/SKILL.md

deploy-vercel

Skill0 starsChanged 4 months agoMITView on GitHub

Use when an approved, human-requested deployment specifically targets Vercel.

  • Installs packages

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the project has never been deployed to Vercel:

    line 16
  2. Distinctive:

    Ask: Do you have a Vercel account?

    line 18
  3. Distinctive:

    Ask: Is the project on GitHub?

    line 19
  4. Very specific:

    If the project is not on GitHub, suggest installing the Vercel CLI: npm i -g vercel.

    line 20
  5. Very specific:

    CLI: run vercel --prod (or vercel for preview).

    line 31
  6. Very specific:

    Never print tokens. If vercel login is needed, ask the user to run it themselves.

    line 32
  7. Distinctive:

    Ask the user to visit the URL and confirm it works.

    line 36
  8. Distinctive:

    If it fails, check: build logs in Vercel dashboard, environment variables set correctly, framework settings.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Deploy Vercel

Guide the user through deploying to Vercel. Keep it simple, one step at a time.

Gate check

Confirm the generic deploy gate: explicit human request, QA PASS, review APPROVE, and a successful build.

Setup (first time only)

If the project has never been deployed to Vercel:

  1. Ask: Do you have a Vercel account? If no, guide them to create one at vercel.com (free tier is enough).
  2. Ask: Is the project on GitHub? If yes, guide them to connect Vercel to their GitHub repo through the Vercel dashboard (Import Project). This is the simplest path — no CLI needed for basic deploys.
  3. If the project is not on GitHub, suggest installing the Vercel CLI: npm i -g vercel. Then run vercel login (opens browser for auth — no token handling needed).
  4. Confirm the Vercel project name and environment (production or preview).
  5. Save the deployment process to .agents/skills/deploy-project/SKILL.md with:
    • Platform: Vercel
    • Method: GitHub push-to-deploy (or vercel --prod for CLI)
    • Project name
    • Any required environment variables (names only, never values)

Deploy

  • GitHub connected: tell the user to push to their deploy branch. Vercel auto-deploys. Report the expected Vercel URL format: https://<project-name>.vercel.app.
  • CLI: run vercel --prod (or vercel for preview). Report the URL from the output.
  • Never print tokens. If vercel login is needed, ask the user to run it themselves.

After deploy

  • Ask the user to visit the URL and confirm it works.
  • If it fails, check: build logs in Vercel dashboard, environment variables set correctly, framework settings.
  • Offer to set up monitoring (load monitoring skill).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free