Agent skill

Ship Prod

A skill your agent uses when deploying qaskills.sh to production, verifying whether a deploy landed, or when a push to main did not show up on the live site, e.g.

MITAuto-check passedDevOps & Cloud

Install Ship Prod

skills CLI

$ npx skills add PramodDutta/qaskills --skill ship-prod -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install PramodDutta/qaskills ship-prod --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/PramodDutta/qaskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/ship-prod .claude/skills/ship-prod && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "ship-prod" agent skill from https://github.com/PramodDutta/qaskills/tree/main/.claude/skills/ship-prod into .claude/skills/ship-prod/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-prod", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/PramodDutta/qaskills/tree/main/.claude/skills/ship-prod

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add PramodDutta/qaskills --skill ship-prod -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install PramodDutta/qaskills ship-prod --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PramodDutta/qaskills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/ship-prod .agents/skills/ship-prod && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ship-prod" agent skill from https://github.com/PramodDutta/qaskills/tree/main/.claude/skills/ship-prod into .agents/skills/ship-prod/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-prod", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add PramodDutta/qaskills --skill ship-prod -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install PramodDutta/qaskills ship-prod --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PramodDutta/qaskills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/ship-prod .cursor/skills/ship-prod && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ship-prod" agent skill from https://github.com/PramodDutta/qaskills/tree/main/.claude/skills/ship-prod into .cursor/skills/ship-prod/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-prod", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/PramodDutta/qaskills.git --path .claude/skills/ship-prod

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add PramodDutta/qaskills --skill ship-prod -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install PramodDutta/qaskills ship-prod --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PramodDutta/qaskills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/ship-prod .gemini/skills/ship-prod && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "ship-prod" agent skill from https://github.com/PramodDutta/qaskills/tree/main/.claude/skills/ship-prod into .gemini/skills/ship-prod/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-prod", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install PramodDutta/qaskills ship-prod

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add PramodDutta/qaskills --skill ship-prod -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/PramodDutta/qaskills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/ship-prod .github/skills/ship-prod && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "ship-prod" agent skill from https://github.com/PramodDutta/qaskills/tree/main/.claude/skills/ship-prod into .github/skills/ship-prod/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-prod", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add PramodDutta/qaskills --skill ship-prod -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install PramodDutta/qaskills ship-prod --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PramodDutta/qaskills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/ship-prod .opencode/skills/ship-prod && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ship-prod" agent skill from https://github.com/PramodDutta/qaskills/tree/main/.claude/skills/ship-prod into .opencode/skills/ship-prod/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ship-prod", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: ship-prod
GitHub stars: 233
Token cost: ~1k tokens
SKILL.md length: 341 words
Files: 1
Skills in repo: 11
Repo updated: Oct 4, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when deploying qaskills.sh to production, verifying whether a deploy landed, or when a push to main did not show up on the live site, e.g.

Deploying qaskills.sh to production
SKILL.md covers Fixed facts, Preflight, Deploy and Verify (required, every deploy), plus 3 more sections
Calls git, npx and vercel; reaches qaskills.sh
Verifying whether a deploy landed

What it does

Ship Prod is an agent skill from PramodDutta/qaskills. Use when deploying qaskills.sh to production, verifying whether a deploy landed, or when a push to main did not show up on the live site, e.g. "deploy", "ship it", "push this live", "is prod updated?", "the site still shows the old version".

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud. It works with Vercel and Git. The repository describes itself as: QA Skills Directory QA Skills is a curated directory of testing-specific skills for AI coding agents (Claude Code, Cursor, Copilot, etc.). The licence is MIT.

When your agent uses it

Deploying qaskills.sh to production
Verifying whether a deploy landed
A push to main did not show up on the live site

Example prompts

“deploy”
“ship it”
“push this live”
“/ship-prod”

Requirements

Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit 1d2a092. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
- npx
- vercel
- curl
- pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- qaskills.sh
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ship Prod loads about 1k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 341 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~63
When it runs · the whole SKILL.md, loaded when a task matches: ~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from PramodDutta/qaskills at commit 1d2a092, republished under its MIT licence (© PramodDutta). 341 words, ~1,044 tokens.

Download SKILL.mdSave it as .claude/skills/ship-prod/SKILL.md (or your agent's skills folder).

name: ship-prod
description: Use when deploying qaskills.sh to production, verifying whether a deploy landed, or when a push to main did not show up on the live site, e.g. "deploy", "ship it", "push this live", "is prod updated?", "the site still shows the old version".

Ship Prod

Deploys COMMITTED HEAD only, to the correct Vercel project, then proves the deploy landed. git push to main does not reliably auto-deploy; this skill is the deploy path.

Fixed facts

Project: qaskills.sh, project ID prj_rDKli4AyhHoXZXV8NHrs92Ncbf4f, org team_DGM6VSs6vhASlhktmHkSqPwn, account luckydutta96
A decoy project qaskills exists WITHOUT the domain. Never deploy there. Never accept interactive "link this directory?" defaults.
Build command lives in root vercel.json (shared build && web build); Node is pinned to 24.x via engines in packages/web/package.json (Vercel stopped building 20.x on 2026-10-01; the Neon HTTP driver is verified on 24)
vercel --prod uploads the WORKING TREE, not git HEAD
.vercel/project.json is gitignored, so fresh worktrees are unlinked: explicit env IDs required there

Preflight

bash

cd /Users/promode/qaskills
vercel whoami                              # must be luckydutta96; else STOP, user must vercel login
git status --short                         # empty => clean path; anything => worktree path
git log -1 --oneline --stat | head -15     # confirm HEAD is exactly what you intend to ship
pnpm --filter @qaskills/shared build && pnpm --filter @qaskills/web build   # never ship a red build

Deploy

Clean tree (no modified or untracked files that could ship):

bash

cd /Users/promode/qaskills && npx vercel --prod --yes

Dirty tree (default assumption; the working tree here usually carries WIP):

bash

DEPLOY_DIR=$(mktemp -d)/qaskills-deploy
git -C /Users/promode/qaskills worktree add "$DEPLOY_DIR" HEAD
cd "$DEPLOY_DIR"
VERCEL_ORG_ID=team_DGM6VSs6vhASlhktmHkSqPwn \
VERCEL_PROJECT_ID=prj_rDKli4AyhHoXZXV8NHrs92Ncbf4f \
npx vercel --prod --yes
cd /Users/promode/qaskills
git worktree remove "$DEPLOY_DIR" --force

Capture the deployment URL the CLI prints; it goes in the final summary.

Verify (required, every deploy)

bash

npx vercel ls | head -5                                         # newest deployment: Ready, Production
curl -s -o /dev/null -w '%{http_code}\n' https://qaskills.sh    # 200
# The specific change, visible live. Examples:
curl -s -o /dev/null -w '%{http_code}\n' https://qaskills.sh/blog/<new-slug>   # new article: 200
curl -s https://qaskills.sh/<changed-page> | grep -c '<expected-marker>'       # code change: >= 1

All three must pass before saying "deployed". If the domain still serves old content while the new deployment is Ready, the alias did not move: npx vercel promote <deployment-url>.

Rollback

bash

npx vercel ls                       # find the previous Ready production deployment
npx vercel promote <previous-url>   # fast path: point the domain back

For a code-level revert, git revert <sha> on main, then run this skill again.

Failure modes

Symptom	Cause	Fix
CLI asks to link / offers project `qaskills`	Unlinked dir, interactive defaults	Abort; re-run with both VERCEL_* env vars set
`Error: not authorized` / wrong scope	Logged into another account	`vercel whoami`; user runs `vercel login` as luckydutta96
Vercel build fails, local build green	Env-dependent code at import time	Lazy-init pattern (see CLAUDE.md); no secrets required at build
Deploy Ready but site unchanged	Domain alias on older deployment, or you shipped stale HEAD	`vercel promote`; confirm intended commit was in HEAD
WIP appeared on prod	Deployed dirty working tree directly	Roll back via promote, then redeploy via worktree

Red flags

"The push probably triggered a deploy"
Deploying from a dirty root without the worktree
Answering Vercel's interactive prompts with defaults
Declaring success without the three verification commands' output
Touching Vercel project settings (Node version, env vars, domains) without user approval

Files

Just SKILL.md in .claude/skills/ship-prod of PramodDutta/qaskills.

Open the folder on GitHubat commit 1d2a092

Compare with similar skills

Ship Prod next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ship Prod compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Ship Prod this skillPramodDutta/qaskills	233	—	~1k	Automated safety check: Pass	MIT	5 days ago
Project Toolingalinaqi/maggy	707	—	~2.5k	Automated safety check: Notes	MIT	15 days ago
Vercel CI Integrationjeremylongshore/tons-of-skills-marketplace	2.8k	—	~1.9k	Automated safety check: Pass	MIT	today
Vercel Deploy Integrationjeremylongshore/tons-of-skills-marketplace	2.8k	—	~1.7k	Automated safety check: Pass	MIT	today
DeployHouseofmvps/ultraship	123	—	~4.1k	Automated safety check: Pass	MIT	3 mo ago
Olore Vercel Latestolorehq/olore	104	—	~620	Automated safety check: Pass	MIT	today

Similar skills

Project Tooling
alinaqi/maggy
gh, vercel, supabase, render CLI and deployment platform setup
707 GitHub stars~2.5k tokensUpdated 15 days ago
DevOps & CloudAuto-check: notes
Vercel CI Integration
jeremylongshore/tons-of-skills-marketplace
Configure Vercel CI/CD with GitHub Actions, preview deployments, and automated testing.
2.8k GitHub stars~1.9k tokensUpdated today
DevOps & CloudAuto-check passed
Vercel Deploy Integration
jeremylongshore/tons-of-skills-marketplace
Deploy and manage Vercel production deployments with promotion, rollback, and multi-region strategies.
2.8k GitHub stars~1.7k tokensUpdated today
DevOps & CloudAuto-check passed
Deploy
Houseofmvps/ultraship
Pre-flight checks then deploy. An agent skill from Houseofmvps/ultraship.
123 GitHub stars~4.1k tokensUpdated 3 mo ago
DevOps & CloudAuto-check passed
Olore Vercel Latest
olorehq/olore
Local vercel documentation reference (latest). An agent skill from olorehq/olore.
104 GitHub stars~620 tokensUpdated today
DevOps & CloudAuto-check passed
Deploy to Vercel
vercel-labs/agent-skills
Official
Deploys applications to Vercel as previews by default, picking a deploy method from the project's link state, git remote and team.
32k GitHub starsUsed in 11 repos~2.9k tokens
DevOps & CloudAuto-check: notes

More from PramodDutta/qaskills

All 11 skills in this repo

Add Seed Skills
PramodDutta/qaskills
A skill your agent uses when adding or editing QA skills in seed-skills/ or getting them onto the live qaskills.sh catalog, e.g.
233 GitHub stars~1.4k tokensUpdated 5 days ago
Auto-check: notes
Publish SEO Batch
PramodDutta/qaskills
A skill your agent uses when publishing SEO blog articles to qaskills.sh, e.g.
233 GitHub stars~2.2k tokensUpdated 5 days ago
Auto-check passed
API Testing REST
PramodDutta/qaskills
Comprehensive RESTful API testing patterns covering HTTP methods, status codes, request/response validation, authentication, error handling, and contract testing.
233 GitHub stars~4.9k tokensUpdated 5 days ago
Auto-check passed
Claude Code QA
PramodDutta/qaskills
The complete QA skill for Claude Code — turn Claude into an expert QA engineer that picks the right test type, writes reliable Playwright, Cypress, and pytest tests, eliminates flaky tests, enforces…
233 GitHub stars~2.3k tokensUpdated 5 days ago
Auto-check passed
Cypress E2E
PramodDutta/qaskills
End-to-end testing skill using Cypress for web applications, covering custom commands, network intercepts, fixtures, cy.session, and component testing patterns.
233 GitHub stars~3.4k tokensUpdated 5 days ago
Auto-check passed
E2E Testing Claude Code
PramodDutta/qaskills
Make Claude Code write and maintain end-to-end tests like a senior SDET — Playwright and Cypress flows with stable locators, the Page Object Model, fixtures, reused auth state, network mocking, and…
233 GitHub stars~1.4k tokensUpdated 5 days ago
Auto-check passed

Works with

Questions about Ship Prod

What does Ship Prod do?

A skill your agent uses when deploying qaskills.sh to production, verifying whether a deploy landed, or when a push to main did not show up on the live site, e.g. Ship Prod is an agent skill from PramodDutta/qaskills.g.

When should I use Ship Prod?

Ship Prod fits situations like: deploying qaskills.sh to production; verifying whether a deploy landed; A push to main did not show up on the live site.

How do I install Ship Prod in Claude Code?

Run `npx skills add PramodDutta/qaskills --skill ship-prod -a claude-code`. Or copy the skill folder (.claude/skills/ship-prod in PramodDutta/qaskills) into .claude/skills/ship-prod in your project. Claude Code loads it when a task matches its description.

How do I install Ship Prod in Codex?

Run `npx skills add PramodDutta/qaskills --skill ship-prod -a codex`. Or copy the skill folder (.claude/skills/ship-prod in PramodDutta/qaskills) into .agents/skills/ship-prod in your project. Codex loads it when a task matches its description.

Can I use Ship Prod in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PramodDutta/qaskills --skill ship-prod -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ship-prod, .gemini/skills/ship-prod, .github/skills/ship-prod and .opencode/skills/ship-prod in your project.

What does Ship Prod need to run?

Going by SKILL.md and its folder, Ship Prod needs the command-line tools its instructions call (git, npx, vercel, curl and pnpm). Our summary lists: Node.js.

Does Ship Prod access the network?

SKILL.md names 1 domain. In commands or code: qaskills.sh; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Ship Prod safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ship Prod use?

Ship Prod is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ship Prod use?

About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ship Prod?

Skills that share tags, products or a category with Ship Prod: Project Tooling (alinaqi/maggy, 707 stars), Vercel CI Integration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Vercel Deploy Integration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Deploy (Houseofmvps/ultraship, 123 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ship Prod?

PramodDutta (a GitHub user) maintains it in PramodDutta/qaskills, which has 233 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 4, 2026.

Source: PramodDutta/qaskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Ship Prod

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Ship Prod

Fixed facts

Preflight

Deploy

Verify (required, every deploy)

Rollback

Failure modes

Red flags

Files

Compare with similar skills

Similar skills

More from PramodDutta/qaskills

Related

Questions about Ship Prod