agentleFS
Sign inStart free
danielarif26danielarif26/agentic-os-starter/skills/deploy-verify/SKILL.md

deploy-verify

Skill1 starsChanged 4 months agoMITView on GitHub

Verify a Vercel deployment actually went live and serves the correct production domain. Self-improving: reads its own run history before checking and logs the outcome after. Use when the user asks "did you deploy?", "is it live?", "verify the deploy", "check vercel", or after any Vercel deploy. Part of the Agentic OS (Level 1 backbone).

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read vercel.json alias/domain BEFORE hitting a URL — don't assume the domain.

    line 19
  2. Distinctive:

    Never claim "deployed" without an actual HTTP check.

    line 44
  3. Distinctive:

    Never trigger a new deploy — this skill only *verifies*.

    line 45

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “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-verify

Confirms a Vercel deploy is live + on the right domain. Loop-engineered: it learns from past runs.

Loop (do this every time)

  1. Before checking — read the last ~5 entries of <vault>/agentic-os/runs/deploy-verify.md (if it exists). Honor each lesson:. Known lessons for this repo family:
    • Read vercel.json alias/domain BEFORE hitting a URL — don't assume the domain.
    • Vercel Hobby can BLOCK deploys unless the commit author matches the account owner email (check your git identity). If deploy is stuck, check git log -1 --format='%ae' first.
  2. Verify:
    • Determine the intended production domain from vercel.json (alias) or the project config — never guess.
    • curl -sI -o /dev/null -w '%{http_code} %{url_effective}\n' https://<domain>/ → expect 2xx.
    • Optionally query Vercel API for the latest deployment readyState (want READY, not ERROR/BUILDING).
    • Spot-check one localized/inner page too (user runs multilingual sites).

  3. After checking — append a record (newest on top) to <vault>/agentic-os/runs/deploy-verify.md:

    ## <ISO-datetime> — deploy-verify — <PASS|FAIL|PARTIAL>
- input: <domain checked>
- output: <http code + readyState>
- lesson: <what to remember next time>

Output to user

Terse verdict: LIVE ✅ <domain> (200, READY) or NOT LIVE ❌ <reason> → <fix>.

Never

  • Never claim "deployed" without an actual HTTP check.
  • Never trigger a new deploy — this skill only verifies.

Download now (ZIP)

  • Other versions9 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 9

    1. wolverin0/claude-skills★ 41same name
    2. kirillgreen/skills★ 23same name
    3. kensaurus/cursor-kenji★ 9same name
    4. kensaurus/skills★ 9same name
    5. jaywedgeworth22/BotFleet★ 4same name
    6. Simple-With-Us/BotFleet★ 4same name
    7. jonmumm/skills★ 2same name
    8. EtanHey/golems★ 0same name
    9. kimkon1011/orgiast-claude-rules★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use session-start.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • bitwize-music-studioSkill

      session-start

      Runs the session startup procedure - verifies setup, loads config and state, checks skill models, and reports project status. Use at the beginning of a fresh session.

      Also in 3 projects that use this

  • In this repository6 other files it gives its agents.

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