Agent skill

Deployer

by WeaveMindAI in WeaveMindAI/weft

The only agent that acts on a cloud install. An agent skill from WeaveMindAI/weft.

Custom licenceAuto-check: notes

Install Deployer

skills CLI
$ npx skills add WeaveMindAI/weft --skill deployer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install WeaveMindAI/weft deployer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/WeaveMindAI/weft.git skills-src && mkdir -p .claude/skills && cp -r skills-src/tangle/cline/.cline/skills/deployer .claude/skills/deployer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
deployer
GitHub stars
2k
Token cost
~1.9k tokens
SKILL.md length
1,315 words
Files
1
Skills in repo
36
Repo updated
First seen
Licence
Custom licence

At a glance

The only agent that acts on a cloud install. An agent skill from WeaveMindAI/weft.

  • Works in 4 steps: Read the weft-deploying skill. Putting… → Check the target exists and you can… → Do [the ask], as the skill lays it out.… → …
  • SKILL.md covers Running commands, Rules, Method and Report
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Deployer is an agent skill from WeaveMindAI/weft. The only agent that acts on a cloud install. Dispatched by Tangle with what to do on a named target (deploy, roll back, set up CI, read a failed cloud build); names the target with --on on every command, reads the weft-deploying skill, and reports the deployed version and route addresses, or the exact failure.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: A programming language for AI orchestrations.

Example prompts

  • “/deployer”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Read the weft-deploying skill. Putting weft itself on the cloud, upgrading it or resizing it is never yours: every step of it is the…
  2. Check the target exists and you can reach it: weft target list shows it and whether a key is stored; weft status --on answers. A missing…
  3. Do [the ask], as the skill lays it out. A deploy is weft activate --on while the program is off, and weft resync --on --mode park once its…
  4. Prove it: weft status --on shows the project active on the version you deployed. For each route, call /connect/local/ once with no…

What it can do on your machine

Read from SKILL.md and the folder at commit 6e28f31. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Deployer loads about 1.9k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 1,315 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:31
    ject issued itself and keeps in its own `.env` (the key guarding its own API, a webhook secret) you store without ever r

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,315 words (~1,928 tokens).

“You are the deployer for this weft project. Tangle dispatched you with [the target] (a name from [targets.] in weft.toml) and [the ask]: deploy, roll back, set the project up for its cloud, or find why a cloud deploy failed…”

— opening of SKILL.md by WeaveMindAI, Custom licence
name
deployer

Read the full SKILL.md on GitHub

Files

Just SKILL.md in tangle/cline/.cline/skills/deployer of WeaveMindAI/weft.

Open the folder on GitHubat commit 6e28f31

Compare with similar skills

Deployer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Deployer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Deployer this skillWeaveMindAI/weft2k—~1.9kAutomated safety check: NotesCustom licence
Deploy Setupgarrytan/gstack136k—~11kAutomated safety check: NotesMIT
Deployment Patternsaffaan-m/ECC274k1 repos~2.9kAutomated safety check: PassMIT
Vercel Deploybytedance/deer-flow83k10 repos~797Automated safety check: PassMIT
Land and Deploygarrytan/gstack136k—~18kAutomated safety check: NotesMIT
Deployment and CI/CD Patternsaffaan-m/ECC274k6 repos~2.8kAutomated safety check: PassMIT

Similar skills

  • Deploy Setup

    garrytan/gstack

    Detects where an app deploys, its production URL and health checks, then saves the deploy configuration in CLAUDE.md for /land-and-deploy.

    136k GitHub stars~11k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Deployment iş akışları, CI/CD pipeline kalıpları, Docker konteynerizasyonu, sağlık kontrolleri, rollback stratejileri ve web uygulamaları için üretim hazırlığı kontrol listeleri.

    274k GitHub starsUsed in 1 repo~2.9k tokens
    DevOps & CloudAuto-check passed
  • Vercel Deploy

    bytedance/deer-flow

    Deploys a project to Vercel with one script and no login, then returns a live preview URL and a claim link for moving the deployment into your own Vercel account.

    83k GitHub starsUsed in 10 repos~797 tokens
    DevOps & CloudAuto-check passed
  • Land and Deploy

    garrytan/gstack

    Merges a pull request, waits for CI and the deploy, then verifies production health with canary checks, picking up where /ship leaves off.

    136k GitHub stars~18k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Covers rolling, blue-green and canary deployments, multi-stage Dockerfiles, a GitHub Actions pipeline, health checks and production readiness for web apps.

    274k GitHub starsUsed in 6 repos~2.8k tokens
    DevOps & CloudAuto-check passed
  • Vercel Deployment

    davila7/claude-code-templates

    Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.

    32k GitHub starsUsed in 4 repos~534 tokens
    DevOps & CloudAuto-check passed

More from WeaveMindAI/weft

All 36 skills in this repo
  • Weft Cloud Install

    WeaveMindAI/weft

    Read when the user wants weft itself on their Google Cloud for the first time, or to upgrade or resize the weft already there: getting the user's GitHub and Google Cloud accounts and CLIs ready, the…

    2k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Weft Consumers

    WeaveMindAI/weft

    Read when the user wants their own website, app, bot or extension to list, show, answer, skip or cancel what a program is waiting on, fetch a file it carries, or show what one of its nodes is…

    2k GitHub stars~3.8k tokensUpdated yesterday
    Auto-check passed
  • Weft Deploying

    WeaveMindAI/weft

    Read when the user wants weft or a program live for real people on their cloud, asks about prod, a target, --on, a domain or GCP, or a deploy failed: targets and logging in, domains, the deploy…

    2k GitHub stars~4.2k tokensUpdated yesterday
    Auto-check: notes
  • Weft Metering

    WeaveMindAI/weft

    Read when the user asks what a run costs, or when a node is wired to a paid API weft does not already price: the three pieces of a custom paid service, a meter to copy, and the rules that keep a…

    2k GitHub stars~4k tokensUpdated yesterday
    Auto-check passed
  • Weft Sdp

    WeaveMindAI/weft

    Read when growing a program stage by stage: carving a run, supplying starting values, baking a trigger and firing it without activating, reusing completed work with a seed, freezing an accepted…

    2k GitHub stars~4k tokensUpdated yesterday
    Auto-check passed
  • Weft Frontend

    WeaveMindAI/weft

    Read when the user wants a page, app or site for the program, and before dispatching the frontend-builder: the verified scaffold commands, the default stack (pnpm, SvelteKit, PostgreSQL, BetterAuth…

    2k GitHub stars~8k tokensUpdated yesterday
    Auto-check: notes

Questions about Deployer

What does Deployer do?

The only agent that acts on a cloud install. An agent skill from WeaveMindAI/weft. Deployer is an agent skill from WeaveMindAI/weft. The only agent that acts on a cloud install.

How do I install Deployer in Claude Code?

Run `npx skills add WeaveMindAI/weft --skill deployer -a claude-code`. Or copy the skill folder (tangle/cline/.cline/skills/deployer in WeaveMindAI/weft) into .claude/skills/deployer in your project. Claude Code loads it when a task matches its description.

How do I install Deployer in Codex?

Run `npx skills add WeaveMindAI/weft --skill deployer -a codex`. Or copy the skill folder (tangle/cline/.cline/skills/deployer in WeaveMindAI/weft) into .agents/skills/deployer in your project. Codex loads it when a task matches its description.

Can I use Deployer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add WeaveMindAI/weft --skill deployer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deployer, .gemini/skills/deployer, .github/skills/deployer and .opencode/skills/deployer in your project.

What does Deployer need to run?

SKILL.md names no scripts, command-line tools or credentials: Deployer is instructions for the agent only.

Does Deployer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Deployer safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Deployer use?

Deployer has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Deployer use?

About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Deployer?

Skills that share tags, products or a category with Deployer: Deploy Setup (garrytan/gstack, 136k stars), Deployment Patterns (affaan-m/ECC, 274k stars), Vercel Deploy (bytedance/deer-flow, 83k stars) and Land and Deploy (garrytan/gstack, 136k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Deployer?

WeaveMindAI (a GitHub organization) maintains it in WeaveMindAI/weft, which has 1,994 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on October 6, 2026.

Source: WeaveMindAI/weft on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.