Wrangler

What it does

The skill begins by checking the project and its configuration before selecting CLI operations. It distinguishes local development, previews, deployment and resource management, and asks the agent to retrieve documentation appropriate to the installed tooling. This can prevent a valid command from acting on the wrong environment or editing generated configuration instead of its source.

Best for

Maintaining a Worker that already uses Wrangler, diagnosing a deployment problem or checking an existing project's scripts and bindings. Supply the repository and identify the intended account, environment and resource before any operation that changes remote state.

Tradeoffs and requirements

The source specifically directs new projects and other configuration styles toward a different Cloudflare CLI workflow. It is therefore not a universal starting point for every Cloudflare task. CLI access may expose remote data or billable resources, and a successful command does not prove that the deployed application works.

Unknown; inspect source requirements and supporting scripts.

Install from the source

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code; this catalog never runs it.

npx skills add https://github.com/cloudflare/skills/tree/49a31e0b3229ccdffe4944be9c61bc7481d1d432/skills/wrangler --skill wrangler

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

• Network Access — review the source context.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

86/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

63/100

63

Originality

80/100

80

Static Safety

60/100

60

Suggested workflow

Inspect the lockfile, scripts and active configuration, choose the correct project version, test locally, then use the established deployment path. Pair with the relevant runtime skill for application-specific behavior.

How to judge the result

Confirm the target environment and bindings, inspect the actual command result and check the deployed endpoint. Keep local and remote data operations clearly distinguished in the final evidence.