agentsclimarketplace
Sign in

Deploy skills chakshugautam deploy

Skill bg-szy/TOP-SKILLS/skills/marketplace/deploy__skills-chakshugautam-deploy

Enforces local testing before any deployment. MUST be used before running vercel, git push, or any deployment command. Prevents deploying untested code.From its SKILL.md

Install
npx -y skills add bg-szy/TOP-SKILLS --skill deploy__skills-chakshugautam-deploy

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.6 KB, 364 tokens by cl100k_base, as published. Nobody here has run it

Deploy Skill

NEVER deploy without completing ALL steps below.

Required Workflow

Before ANY deployment (vercel, git push to main, etc.):

1. Build Locally

pnpm build
  • Must complete with zero errors
  • Check output for warnings

2. Start Local Dev Server

pnpm dev
  • Server must start successfully

3. Test in Browser

  • Open the local URL in Chrome DevTools MCP
  • Test ALL changed functionality manually:
    • Click buttons, verify they work
    • Test keyboard input if applicable
    • Submit forms, verify responses
    • Check for console errors

4. Verify Tests Pass (if tests exist)

pnpm test

5. Only Then Deploy

After ALL above steps pass:

vercel --prod

Rules

  1. NO SHORTCUTS - Every step must be completed
  2. NO ASSUMPTIONS - "It worked before" is not verification
  3. TEST AFTER CHANGES - Any code change requires re-testing
  4. LOCAL FIRST - Never deploy to see if something works

Common Mistakes to Avoid

  • Deploying immediately after build without browser testing
  • Assuming dependency changes don't break anything
  • Skipping keyboard/interaction testing
  • Deploying to "check if it works on Vercel"

When User Says "Deploy"

  1. Ask: "Have you verified locally? Let me run through the checklist."
  2. Run build
  3. Start dev server
  4. Test in browser via Chrome DevTools MCP
  5. Only after confirming everything works, deploy

What ships with it: 1 file

13.5 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.