agentsclimarketplace
Sign in

Cloudflare deploy

Skill yigityildiz0/universal-ai-skill-library/skills/common/cloudflare-deploy

Prepare, preview, deploy, and verify a Cloudflare application with environment-aware configuration, migrations, secrets, domains, observability, and.From its SKILL.md

Install
npx -y skills add yigityildiz0/universal-ai-skill-library --skill cloudflare-deploy

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

3 things to look at

  • 22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 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.
  • 1 stars1 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.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.9 KB, 342 tokens by cl100k_base, as published. Nobody here has run it

Deploy to Cloudflare

Deployment is an external mutation. A request to prepare configuration does not by itself authorize a production deploy.

Preflight

  1. Identify project type, installed package manager/Wrangler version, account/project, target environment, branch, config files, bindings, compatibility date/flags, build command/output, routes/domains, secrets names, and data migrations.
  2. Preserve dirty work and verify build/test/lint/typecheck locally.
  3. Compare current config and generated deployment plan with current official docs and installed CLI help.
  4. Confirm who owns DNS, secrets, databases/storage, billing, and rollback.

Do not install/upgrade Wrangler automatically. Never print or copy secret values. Do not create/delete resources, apply migrations, change routes/DNS, or deploy to production outside explicit scope.

Plan and execute

Use separate preview/staging and production configuration. Make data migrations forward/backward compatible, back up critical data, and define a rollback that accounts for schema changes. For AI bindings/gateway, use the project's validated configuration; model/provider/fallback changes require separate review of capability, privacy, region, and cost.

Run the exact deployment command only after preflight passes. Capture version/deployment ID and output without secrets.

Verify

Test health, representative routes, auth, bindings, cache, logs/metrics, errors, latency, headers, redirects, and version identity from the deployed environment. Verify domain/DNS only when in scope. Roll back when predefined checks fail and report any irreversible migration.

Return target, commands, build/tests, resources/migrations, deployment ID/URL, smoke evidence, observability, cost/limits, and rollback status.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,834. 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.