AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
A skill your agent uses when the user invokes /loom deploy or /loom-deploy to prepare, run, inspect, validate, stop, bootstrap, or repair deployment through Loom MCP.
Install Loom Deploy
$ npx skills add valkor-ai/loom --skill loom-deploy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install valkor-ai/loom loom-deploy --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/valkor-ai/loom.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/claude-code/skills/loom-deploy .claude/skills/loom-deploy && 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 "loom-deploy" agent skill from https://github.com/valkor-ai/loom/tree/main/plugins/claude-code/skills/loom-deploy into .claude/skills/loom-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loom-deploy", 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/valkor-ai/loom/tree/main/plugins/claude-code/skills/loom-deployType 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 valkor-ai/loom --skill loom-deploy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install valkor-ai/loom loom-deploy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/valkor-ai/loom.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/claude-code/skills/loom-deploy .agents/skills/loom-deploy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "loom-deploy" agent skill from https://github.com/valkor-ai/loom/tree/main/plugins/claude-code/skills/loom-deploy into .agents/skills/loom-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loom-deploy", 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 valkor-ai/loom --skill loom-deploy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install valkor-ai/loom loom-deploy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/valkor-ai/loom.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/claude-code/skills/loom-deploy .cursor/skills/loom-deploy && 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 "loom-deploy" agent skill from https://github.com/valkor-ai/loom/tree/main/plugins/claude-code/skills/loom-deploy into .cursor/skills/loom-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loom-deploy", 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/valkor-ai/loom.git --path plugins/claude-code/skills/loom-deploy--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 valkor-ai/loom --skill loom-deploy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install valkor-ai/loom loom-deploy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/valkor-ai/loom.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/claude-code/skills/loom-deploy .gemini/skills/loom-deploy && 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 "loom-deploy" agent skill from https://github.com/valkor-ai/loom/tree/main/plugins/claude-code/skills/loom-deploy into .gemini/skills/loom-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loom-deploy", 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 valkor-ai/loom loom-deployInstalls 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 valkor-ai/loom --skill loom-deploy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/valkor-ai/loom.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/claude-code/skills/loom-deploy .github/skills/loom-deploy && 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 "loom-deploy" agent skill from https://github.com/valkor-ai/loom/tree/main/plugins/claude-code/skills/loom-deploy into .github/skills/loom-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loom-deploy", 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 valkor-ai/loom --skill loom-deploy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install valkor-ai/loom loom-deploy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/valkor-ai/loom.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/claude-code/skills/loom-deploy .opencode/skills/loom-deploy && 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 "loom-deploy" agent skill from https://github.com/valkor-ai/loom/tree/main/plugins/claude-code/skills/loom-deploy into .opencode/skills/loom-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loom-deploy", 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.
Facts
- Skill name
loom-deploy- GitHub stars
- 1.2k
- Token cost
- ~546 tokens
- SKILL.md length
- 252 words
- Files
- 1
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when the user invokes /loom deploy or /loom-deploy to prepare, run, inspect, validate, stop, bootstrap, or repair deployment through Loom MCP.
- The user invokes /loom deploy
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- /loom-deploy to prepare
- Repair deployment through Loom MCP
What it does
Loom Deploy is an agent skill from valkor-ai/loom. Use when the user invokes /loom deploy or /loom-deploy to prepare, run, inspect, validate, stop, bootstrap, or repair deployment through Loom MCP.
Its SKILL.md is about 550 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 DevOps & Cloud, covering Deployment. It works with Model Context Protocol. The repository describes itself as: Loop engineering for agentic software delivery. The licence is Apache-2.0.
When your agent uses it
- The user invokes /loom deploy
- /loom-deploy to prepare
- Repair deployment through Loom MCP
Example prompts
- “/loom-deploy”
What it can do on your machine
Read from SKILL.md and the folder at commit a30a7e6. 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
Loom Deploy loads about 546 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 252 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.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
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
The full file from valkor-ai/loom at commit a30a7e6, republished under its Apache-2.0 licence (© valkor-ai). 252 words, ~546 tokens.
Download SKILL.mdSave it as
.claude/skills/loom-deploy/SKILL.md (or your agent's skills folder).- name
- loom-deploy
- description
- Use when the user invokes /loom deploy or /loom-deploy to prepare, run, inspect, validate, stop, bootstrap, or repair deployment through Loom MCP.
loom-deploy
Deployment is controlled by Loom MCP deploy tools. Use the matching loom.deploy* tool and follow its structured action result. For user_gate with preResponseContract, execute the contract before any visible response: call loom.inspectRequest, then call loom.readFieldGroup for only required requestReadPlan.groups, and present the returned deployment decision.
During active_operation, call only the observation tools named by the result, obey observationPolicy, obey forbiddenActions, and do not report completion while finalResponsePolicy forbids it. During asset repair, edit only the returned generated deployment assets or the returned modelRepairRef, then call the returned retryTool; never edit generated source-model/topology/facts snapshots directly. Do not retry asset repair through loom.deployRun. During deploy execution repair, edit only the returned application/runtime files and submit through the returned repair submit tool.
Do not infer stack topology, generated file paths, preview URLs, ports, or repair scope outside the current MCP result.
Reference Loading
The current MCP deploy result remains the authority. Load no reference by default; load deploy references only when the MCP result supplies an exact reference load plan.
Protocol:
- After a deploy MCP result, look for
next.deployReferenceProfile.referenceLoadPlanordetails.deployReferenceProfile.referenceLoadPlan. - Each
referenceLoadPlanentry containsrefId,path, andreason. Resolvepathrelative to this skill'sreferences/directory. - Read only the listed paths. Do not infer extra files from
refId, stack names, failure text, or thereferences/directory. - Use references as implementation guidance for generated or repaired deployment files; do not paste reference prose into deployment artifacts, repair results, or final chat output.
- If the current deploy action has no
deployReferenceProfile, leave deploy references unread.
© valkor-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/claude-code/skills/loom-deploy of valkor-ai/loom.
Open the folder on GitHubat commit a30a7e6
Compare with similar skills
Loom Deploy 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 |
|---|---|---|---|---|---|---|
| Loom Deploy this skillvalkor-ai/loom | 1.2k | — | ~546 | Automated safety check: Pass | Apache-2.0 | |
| AWS Cdk Developmentzxkane/aws-skills | 367 | 2 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Prepare Cloudflare Production DeploymentLubomirGeorgiev/cloudflare-workers-nextjs-saas-template | 786 | — | ~5.9k | Automated safety check: Notes | MIT | |
| Deploy Observabilityaliyun/alibabacloud-observability-mcp-server | 166 | — | ~2.6k | Automated safety check: Notes | None | |
| Release Allpaperboytm/spool | 592 | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Deploynoskillish/bankmcp | 276 | — | ~744 | Automated safety check: Pass | MIT |
Similar skills
Prepare Cloudflare Production Deployment
LubomirGeorgiev/cloudflare-workers-nextjs-saas-template
Source-of-truth runbook for preparing this Vinext Cloudflare Workers SaaS template for production deployment.
Deploy Observability
aliyun/alibabacloud-observability-mcp-server
Deploy, start, and update the Alibaba Cloud Observability MCP Server (阿里云可观测 MCP Server).
Release All
paperboytm/spool
Publish the complete Spool CLI release train: synchronized versions, npm packages, the GitHub release, and the matching production web deployment.
Deploy
noskillish/bankmcp
Deploy BankMCP™ to a small server so it works in claude.ai and on the phone: Railway or Fly.io, volume, domain, setup page, connector.
- Official
Hcls Deploy Agent
aws-samples/amazon-bedrock-agents-healthcare-lifesciences
A skill your agent uses when a developer wants to deploy an HCLS agent to Amazon Bedrock AgentCore, configure Gateway tools as MCP endpoints, set up authentication with Cognito, configure memory, or…
More from valkor-ai/loom
All 17 skills in this repoThreejs Gameplay Systems
valkor-ai/loom
Build and iterate playable Three.js game systems: starter scaffold, architecture, design briefs, core loops, level and encounter design, entities, input, camera, collision and physics, scoring…
Threejs 3D Generator
valkor-ai/loom
Generate, texture, rig, animate, stylize, convert, and download 3D assets for Three.js games via the Tripo API.
Threejs Image Generator
valkor-ai/loom
Generate and edit 2D image assets for Three.js games with Google's Gemini image API: concept sheets, image-to-3D inputs, texture and material references, sky and background plates, decals, logos…
Threejs Game Director
valkor-ai/loom
Entrypoint for building, upgrading, and finishing Three.js browser games.
Threejs Audio Generator
valkor-ai/loom
Generate, convert, clean, and integrate audio for Three.js browser games with ElevenLabs: sound effects, looping ambience, UI sounds, impact/weapon/vehicle audio, creature and boss stingers…
Threejs QA Release
valkor-ai/loom
Verify and release Three.js browser games: playtest QA, automated bot playtests, mobile and responsive checks, production builds, static-hosting base paths, debug gating, bundle review, screenshots…
Related
Works with
Categories
Questions about Loom Deploy
What does Loom Deploy do?
A skill your agent uses when the user invokes /loom deploy or /loom-deploy to prepare, run, inspect, validate, stop, bootstrap, or repair deployment through Loom MCP. Loom Deploy is an agent skill from valkor-ai/loom. Use when the user invokes /loom deploy or /loom-deploy to prepare, run, inspect, validate, stop, bootstrap, or repair deployment through Loom MCP.
When should I use Loom Deploy?
Loom Deploy fits situations like: the user invokes /loom deploy; /loom-deploy to prepare; repair deployment through Loom MCP.
How do I install Loom Deploy in Claude Code?
Run `npx skills add valkor-ai/loom --skill loom-deploy -a claude-code`. Or copy the skill folder (plugins/claude-code/skills/loom-deploy in valkor-ai/loom) into .claude/skills/loom-deploy in your project. Claude Code loads it when a task matches its description.
How do I install Loom Deploy in Codex?
Run `npx skills add valkor-ai/loom --skill loom-deploy -a codex`. Or copy the skill folder (plugins/claude-code/skills/loom-deploy in valkor-ai/loom) into .agents/skills/loom-deploy in your project. Codex loads it when a task matches its description.
Can I use Loom Deploy 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 valkor-ai/loom --skill loom-deploy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/loom-deploy, .gemini/skills/loom-deploy, .github/skills/loom-deploy and .opencode/skills/loom-deploy in your project.
What does Loom Deploy need to run?
SKILL.md names no scripts, command-line tools or credentials: Loom Deploy is instructions for the agent only.
Does Loom Deploy 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 Loom Deploy safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Loom Deploy use?
Loom Deploy is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Loom Deploy use?
About 546 tokens (SKILL.md is roughly 2.2k 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 Loom Deploy?
Skills that share tags, products or a category with Loom Deploy: AWS Cdk Development (zxkane/aws-skills, 367 stars), Prepare Cloudflare Production Deployment (LubomirGeorgiev/cloudflare-workers-nextjs-saas-template, 786 stars), Deploy Observability (aliyun/alibabacloud-observability-mcp-server, 166 stars) and Release All (paperboytm/spool, 592 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Loom Deploy?
valkor-ai (a GitHub organization) maintains it in valkor-ai/loom, which has 1,198 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 6, 2026.
Source: valkor-ai/loom on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.