agentleFS
Sign inStart free
thoitiettxl-cyberthoitiettxl-cyber/Claw-II/skills/vercel-deploy-claimable/SKILL.md

vercel-deploy-claimable

Skill2 starsChanged 7 months agoMITView on GitHub

Prepare or execute a claimable Vercel deployment for a local web project by packaging source, inferring framework, and optionally calling an imported deploy helper that returns preview and claim URLs. Use when the user explicitly wants a Vercel deployment or a deployment-ready package/assessment.

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, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If packaging would otherwise mutate the source tree, use a staging copy first or stop and report.

    line 63
  2. Very specific:

    If a static HTML rename workaround is needed, stage a copy under .ops/staging/ instead of mutating source in place.

    line 68
  3. Distinctive:

    Only with explicit approval, invoke the helper.

    line 70
  4. Very specific:

    If the workflow exposes a critical install path (for example /install.sh), test that path explicitly after deploy instead of assuming …

    line 71
  5. Distinctive:

    When the installer host is already canonical/fixed, prefer a static bootstrap over a dynamic serverless endpoint for the install path.

    line 72
  6. Distinctive:

    treat as failed deploy; do not invent success.

    line 84
  7. Distinctive:

    no fabricated deploy result

    line 93
  8. Distinctive:

    no unsafe in-place source mutation for packaging convenience

    line 94

≈ “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

Vercel Deploy Claimable

Indexed Reference Map

  • @[SKILL.md#L1-L96] Frontmatter, scope, KB notes, trigger rules, SOP, error handling, output contract.
  • @[references/INDEX.md#L1-L12] Reading order and file map.
  • @[references/QUICK_REFERENCE.md#L1-L20] Trigger boundary, approval split, and stop conditions.
  • @[references/CORE_API.md#L1-L33] Packaging/deploy contract, helper behavior, mutation risk, and output semantics.
  • @[references/PATTERNS.md#L1-L18] Staging-first and deployment safety patterns.
  • @[references/EXAMPLES.md#L1-L28] Representative deploy requests and handling.
  • @[references/AI_WORKFLOW.md#L1-L13] Bounded orchestration flow.
  • @[scripts/deploy.sh#L1-L249] Imported external deploy helper.

Scope

  • In-scope:
    • assess whether a local project is a suitable target for claimable Vercel deploy
    • prepare a deployment package or staging copy for review
    • execute the imported deploy helper only when external deployment is explicitly approved
  • Out-of-scope:
    • silent deployment without approval
    • mutating the source project in place just to satisfy deploy packaging assumptions
    • claiming a deployment succeeded without actual preview/claim URLs

KB Mode Notes

  • Reading order:
    1. references/INDEX.md
    2. references/QUICK_REFERENCE.md
    3. references/CORE_API.md
    4. references/PATTERNS.md
    5. references/EXAMPLES.md
    6. references/AI_WORKFLOW.md
    7. scripts/deploy.sh
  • Coverage Matrix:
    • trigger boundary + approval split -> QUICK_REFERENCE.md
    • packaging/deploy contract + helper behavior -> CORE_API.md
    • staging and source-protection patterns -> PATTERNS.md
    • representative use cases -> EXAMPLES.md
    • orchestration order -> AI_WORKFLOW.md
  • Portability note:
    • Local governance forbids blind network deploys and in-place source mutation; re-check endpoint trust, packaging path, and rollback discipline before porting.

Trigger Rules

  • Positive:
    • The user explicitly wants to deploy a project/site to Vercel.
    • The user wants a preview deployment, live preview URL, or claimable deployment link.
    • The task needs a deployment-readiness assessment or package before deploy.
  • Negative:
    • The user only wants build/debug help without deployment.
    • The source tree must remain untouched and no staging path is available.
    • External deployment/network write is not approved.
  • Escalation:
    • Actual deployment is an external write and requires explicit approval.
    • If packaging would otherwise mutate the source tree, use a staging copy first or stop and report.

SOP

  1. Confirm the target project path and whether the user wants assessment/package-only or real deploy.
  2. Inspect the project minimally for deploy suitability and likely framework signals.
  3. If a static HTML rename workaround is needed, stage a copy under .ops/staging/ instead of mutating source in place.
  4. Prepare package/deploy notes and surface expected behavior.
  5. Only with explicit approval, invoke the helper.
  6. If the workflow exposes a critical install path (for example /install.sh), test that path explicitly after deploy instead of assuming success from the preview URL alone.
  7. When the installer host is already canonical/fixed, prefer a static bootstrap over a dynamic serverless endpoint for the install path.
  8. Return preview URL + claim URL only if deployment actually succeeded.
  9. Otherwise return assessment/package-only status truthfully.

Error Handling

  • Missing project path or unsupported input:
    • report the exact missing requirement.
  • Packaging would mutate source:
    • switch to staging copy or stop.
  • Network/deploy failure:
    • report the real stderr/response class and keep the project untouched.
  • Missing preview/claim URL:
    • treat as failed deploy; do not invent success.

Output Contract

  • Deliverables:
    • project path assessed
    • staging/package path if created
    • preview URL + claim URL only on real success
  • Validation:
    • no silent deployment
    • no fabricated deploy result
    • no unsafe in-place source mutation for packaging convenience
  • Compliance Verdict:
    • PASS when assessment/deploy status is reported truthfully with real artifacts/URLs.

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