Google Analytics Data API Basics
google/skills
Manages Google Analytics reporting data, enables the Analytics Data API via the Cloud CLI, and creates reports using the Google Analytics Data API (v1beta).
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…
$ npx skills add WeaveMindAI/weft --skill weft-deploying -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install WeaveMindAI/weft weft-deploying --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/WeaveMindAI/weft.git skills-src && mkdir -p .claude/skills && cp -r skills-src/tangle/cline/.cline/skills/weft-deploying .claude/skills/weft-deploying && rm -rf skills-srcUse ~/.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/
Install the "weft-deploying" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-deploying into .claude/skills/weft-deploying/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weft-deploying", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-deployingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add WeaveMindAI/weft --skill weft-deploying -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install WeaveMindAI/weft weft-deploying --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WeaveMindAI/weft.git skills-src && mkdir -p .agents/skills && cp -r skills-src/tangle/cline/.cline/skills/weft-deploying .agents/skills/weft-deploying && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "weft-deploying" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-deploying into .agents/skills/weft-deploying/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weft-deploying", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add WeaveMindAI/weft --skill weft-deploying -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install WeaveMindAI/weft weft-deploying --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WeaveMindAI/weft.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/tangle/cline/.cline/skills/weft-deploying .cursor/skills/weft-deploying && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "weft-deploying" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-deploying into .cursor/skills/weft-deploying/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weft-deploying", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/WeaveMindAI/weft.git --path tangle/cline/.cline/skills/weft-deploying--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add WeaveMindAI/weft --skill weft-deploying -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install WeaveMindAI/weft weft-deploying --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WeaveMindAI/weft.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/tangle/cline/.cline/skills/weft-deploying .gemini/skills/weft-deploying && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "weft-deploying" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-deploying into .gemini/skills/weft-deploying/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weft-deploying", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install WeaveMindAI/weft weft-deployingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add WeaveMindAI/weft --skill weft-deploying -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/WeaveMindAI/weft.git skills-src && mkdir -p .github/skills && cp -r skills-src/tangle/cline/.cline/skills/weft-deploying .github/skills/weft-deploying && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "weft-deploying" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-deploying into .github/skills/weft-deploying/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weft-deploying", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add WeaveMindAI/weft --skill weft-deploying -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install WeaveMindAI/weft weft-deploying --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WeaveMindAI/weft.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/tangle/cline/.cline/skills/weft-deploying .opencode/skills/weft-deploying && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "weft-deploying" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-deploying into .opencode/skills/weft-deploying/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weft-deploying", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
weft-deployingRead 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…
Weft Deploying is an agent skill from 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 workflow weft ci add writes, handing it its settings with weft target export, a project's frontends (weft frontend), what a cloud build is and how it fails, rolling back, and connections on a cloud install. The deployer specialist reads it; you read it before dispatching one.
Its SKILL.md is about 4.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design. It works with Google Cloud. The repository describes itself as: A programming language for AI orchestrations.
7 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 6e28f31. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and toml).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
api.shop.comweft-role-dispatcher-123456789.us-central1.run.appFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
WEFT_TOKENBETTER_AUTH_SECRETFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Weft Deploying loads about 4.2k tokens when it runs. Until then it costs about 123 tokens; SKILL.md has 2,682 words of instructions outside code blocks.
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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
Run and by `front/.env` on this machine:front/.env.prod` plus the door's address from `weft infra list-doors --ont export prod --github --front-env front/.env.prod`ued itself**, kept in the project's own `.env`it without ever reading it, by loading `.env` into the`set -a; . ./.env; set +a; weft connect --on prod --node <node> --door own --set-env <field>=<VARIABLE>`.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.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 2,682 words (~4,185 tokens).
“A [target] is one weft install, named in the project's weft.toml:”
Just SKILL.md in tangle/cline/.cline/skills/weft-deploying of WeaveMindAI/weft.
Open the folder on GitHubat commit 6e28f31
Weft Deploying 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Weft Deploying this skillWeaveMindAI/weft | 2k | — | ~4.2k | Automated safety check: Notes | Custom licence | |
| Google Analytics Data API Basicsgoogle/skills | 21k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Omk StitchKaimingWan/oh-my-kiro | 107 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Cloud Cost Optimizationwshobson/agents | 40k | 13 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Agent Readiness Auditdocker/docs | 4.7k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 259 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence |
google/skills
Manages Google Analytics reporting data, enables the Analytics Data API via the Cloud CLI, and creates reports using the Google Analytics Data API (v1beta).
KaimingWan/oh-my-kiro
Google Stitch design-to-code workflow with design system management.
wshobson/agents
Cuts cloud spend across AWS, Azure, GCP and OCI with cost tagging, rightsizing, commitment and spot pricing models, and architecture changes.
docker/docs
Audit a documentation site for agent-friendliness: discovery, markdown delivery, crawlability, semantic structure, machine-readable surfaces, and content legibility.
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
patrickchugh/terravision
Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision.
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…
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…
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…
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…
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…
WeaveMindAI/weft
COMMAND, not reference: Build and run the weft program, then report what came out.
Works with
Categories
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…. Weft Deploying is an agent skill from 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 workflow weft ci add writes, handing it its settings with weft target export, a project's frontends (weft frontend), what a cloud build is and how it fails, rolling back, and connections on a cloud install.
Weft Deploying fits situations like: A program live for real people on their cloud; asks about prod; A deploy failed: targets and logging in; the deploy workflow weft ci add writes.
Run `npx skills add WeaveMindAI/weft --skill weft-deploying -a claude-code`. Or copy the skill folder (tangle/cline/.cline/skills/weft-deploying in WeaveMindAI/weft) into .claude/skills/weft-deploying in your project. Claude Code loads it when a task matches its description.
Run `npx skills add WeaveMindAI/weft --skill weft-deploying -a codex`. Or copy the skill folder (tangle/cline/.cline/skills/weft-deploying in WeaveMindAI/weft) into .agents/skills/weft-deploying in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add WeaveMindAI/weft --skill weft-deploying -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/weft-deploying, .gemini/skills/weft-deploying, .github/skills/weft-deploying and .opencode/skills/weft-deploying in your project.
Going by SKILL.md and its folder, Weft Deploying needs credentials named WEFT_TOKEN and BETTER_AUTH_SECRET. Our summary lists: Docker; A credential in WEFT_TOKEN.
SKILL.md names 2 domains. In commands or code: api.shop.com and weft-role-dispatcher-123456789.us-central1.run.app; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
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.
Weft Deploying has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 4.2k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Weft Deploying: Google Analytics Data API Basics (google/skills, 21k stars), Omk Stitch (KaimingWan/oh-my-kiro, 107 stars), Cloud Cost Optimization (wshobson/agents, 40k stars) and Agent Readiness Audit (docker/docs, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.