How do I install the Deploy skill?

Run npx skillmds@latest add jacbk/deploy-2 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.

What does the Deploy skill do?

Publish a completed Persona portfolio safely through Vercel or GitHub Pages. It is listed under DevOps & Infra on SkillMD.

Is Deploy 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 Deploy?

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 Deploy free to use?

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

Who published Deploy?

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

Deploy by jacbk — Agent Skill

Name: Deploy
Author: jacbk

File contents

Deploy a Persona portfolio

Use this only after the portfolio is complete. Never publish the untouched Persona starter page.

Preflight

Run git remote -v. Do not publish to JacbK/Persona.
Run npm run check and fix every failure.
Check mobile layout, links, images, metadata, favicon, and social preview.
Search for placeholders and private material:

rg -n "TODO|Lorem ipsum|Your Name" src public
git status --short

Confirm that profile.yaml, resumes, and uploaded materials are safe to make public.

Ask before publishing

Offer:

Vercel — recommended for Next.js.
GitHub Pages — free static hosting.
Not now.

Publishing changes external state, so wait for the user's choice.

Vercel

The simplest path is Vercel's Git integration:

Push the portfolio to the user's own GitHub repository.
Import that repository at https://vercel.com/new.
Keep the detected Next.js settings.
Deploy and verify the live URL.

For CLI deployment, use the user's installed and authenticated Vercel CLI. Do not request, print, or store a token in project files.

vercel
vercel --prod

The included .github/workflows/deploy-vercel.yml is manual. It requires VERCEL_TOKEN, VERCEL_ORG_ID, and VERCEL_PROJECT_ID repository secrets.

GitHub Pages

GitHub Pages needs a static export. Persona's manual workflow handles this in a disposable CI checkout:

Push to the user's own GitHub repository.
In repository Settings → Pages, choose GitHub Actions.
Run Deploy portfolio to GitHub Pages from the Actions tab.
Verify the Pages URL, including images and internal links.

The workflow removes the local-only config UI and APIs only from its temporary build workspace. Do not delete working source files just to deploy.

Other hosts

Use the host's current official Next.js adapter or documentation. Do not guess output directories; Next.js server and static-export deployments use different outputs.

Safety rules

Never deploy while origin points to the Persona template repository.
Never put access tokens in profile.yaml, source files, shell history, or agent configuration committed to Git.
Do not edit global agent or MCP settings as part of deployment.
Keep deployment workflows manual until the user deliberately enables automatic production deploys.
After publishing, test the real URL on desktop and mobile.

---name: deploy-2description: Publish a completed Persona portfolio safely through Vercel or GitHub Pages.---# Deploy a Persona portfolioUse this only after the portfolio is complete. Never publish the untouched Persona starter page.## Preflight1. Run `git remote -v`. Do not publish to `JacbK/Persona`.2. Run `npm run check` and fix every failure.3. Check mobile layout, links, images, metadata, favicon, and social preview.4. Search for placeholders and private material:```bashrg -n "TODO|Lorem ipsum|Your Name" src publicgit status --short```5. Confirm that `profile.yaml`, resumes, and uploaded materials are safe to make public.## Ask before publishingOffer:- Vercel — recommended for Next.js.- GitHub Pages — free static hosting.- Not now.Publishing changes external state, so wait for the user's choice.## VercelThe simplest path is Vercel's Git integration:1. Push the portfolio to the user's own GitHub repository.2. Import that repository at `https://vercel.com/new`.3. Keep the detected Next.js settings.4. Deploy and verify the live URL.For CLI deployment, use the user's installed and authenticated Vercel CLI. Do not request, print, or store a token in project files.```bashvercelvercel --prod```The included `.github/workflows/deploy-vercel.yml` is manual. It requires `VERCEL_TOKEN`, `VERCEL_ORG_ID`, and `VERCEL_PROJECT_ID` repository secrets.## GitHub PagesGitHub Pages needs a static export. Persona's manual workflow handles this in a disposable CI checkout:1. Push to the user's own GitHub repository.2. In repository Settings → Pages, choose GitHub Actions.3. Run **Deploy portfolio to GitHub Pages** from the Actions tab.4. Verify the Pages URL, including images and internal links.The workflow removes the local-only config UI and APIs only from its temporary build workspace. Do not delete working source files just to deploy.## Other hostsUse the host's current official Next.js adapter or documentation. Do not guess output directories; Next.js server and static-export deployments use different outputs.## Safety rules- Never deploy while `origin` points to the Persona template repository.- Never put access tokens in `profile.yaml`, source files, shell history, or agent configuration committed to Git.- Do not edit global agent or MCP settings as part of deployment.- Keep deployment workflows manual until the user deliberately enables automatic production deploys.- After publishing, test the real URL on desktop and mobile.

Frequently asked questions

Deploy