Support project-scoped Cloudflare skills installation in Wrangler

[samzong]

Problem

Wrangler's automatic Cloudflare skills installer currently targets detected agents' global skills directories. This is useful for quick setup, but it is a poor fit for repositories that already manage project-scoped skills.

Many teams keep repository-specific agent guidance under paths such as .claude/skills or .agents/skills, often vendored as a submodule or generated from an internal skills package. In that setup, accepting Wrangler's prompt or running wrangler --install-skills installs Cloudflare skills globally, making them visible in unrelated projects as well.

That creates a few problems:

• Cloudflare-specific guidance leaks into every agent session, even outside Cloudflare projects.
• Teams with carefully curated project skills cannot keep Wrangler's skills scoped to the repository that needs them.
• Developers must clean global agent directories manually after trying the installer.
• The current install target is surprising because the command is usually run from a specific project, but the side effect is global.

Expected behavior

Wrangler should support a project-scoped install mode for Cloudflare skills, or at least a custom target directory, so teams can keep Cloudflare guidance local to the repository that uses Wrangler.

Possible UX options:

• wrangler --install-skills --skills-scope=project
• wrangler --install-skills --skills-dir ./.agents/skills
• wrangler --install-skills --skills-dir ./.claude/skills
• Prompt choice: Install globally / Install in this project / Skip

For project-scoped installs, Wrangler could install into a repo-local skills directory and avoid touching global agent state.

Current implementation note

The current Wrangler implementation appears to call rosieInstall("cloudflare/skills", { global: true, agent: agentNames, lockfile: false }) from packages/wrangler/src/agents-skills-install.ts.

The underlying rosie-skills API appears to already expose options such as global?: boolean and cwd?: string, so project-scoped installation may be possible without changing the skills content repository itself.

Related work

• Interruptive interactive prompts for unrelated commands for ai skills installs with wrangler@>=4.94.0 #14116 discusses interruptive prompts from the same skills installer.
• Fully remove the Wrangler automatic skills installation #14224 proposes fully removing the automatic skills installation.

If automatic installation stays, having an explicit project-scoped path would make the feature much safer for teams that already manage repository-specific skills.