AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
Conventions for static deploy automation Python CLIs in scripts/static-deploy/.
$ npx skills add Opentrons/opentrons --skill static-deploy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Opentrons/opentrons static-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/Opentrons/opentrons.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/static-deploy .claude/skills/static-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 "static-deploy" agent skill from https://github.com/Opentrons/opentrons/tree/edge/.cursor/skills/static-deploy into .claude/skills/static-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "static-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/Opentrons/opentrons/tree/edge/.cursor/skills/static-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 Opentrons/opentrons --skill static-deploy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Opentrons/opentrons static-deploy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Opentrons/opentrons.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/static-deploy .agents/skills/static-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 "static-deploy" agent skill from https://github.com/Opentrons/opentrons/tree/edge/.cursor/skills/static-deploy into .agents/skills/static-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "static-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 Opentrons/opentrons --skill static-deploy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Opentrons/opentrons static-deploy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Opentrons/opentrons.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/static-deploy .cursor/skills/static-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 "static-deploy" agent skill from https://github.com/Opentrons/opentrons/tree/edge/.cursor/skills/static-deploy into .cursor/skills/static-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "static-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/Opentrons/opentrons.git --path .cursor/skills/static-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 Opentrons/opentrons --skill static-deploy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Opentrons/opentrons static-deploy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Opentrons/opentrons.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/static-deploy .gemini/skills/static-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 "static-deploy" agent skill from https://github.com/Opentrons/opentrons/tree/edge/.cursor/skills/static-deploy into .gemini/skills/static-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "static-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 Opentrons/opentrons static-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 Opentrons/opentrons --skill static-deploy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Opentrons/opentrons.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/static-deploy .github/skills/static-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 "static-deploy" agent skill from https://github.com/Opentrons/opentrons/tree/edge/.cursor/skills/static-deploy into .github/skills/static-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "static-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 Opentrons/opentrons --skill static-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 Opentrons/opentrons static-deploy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Opentrons/opentrons.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/static-deploy .opencode/skills/static-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 "static-deploy" agent skill from https://github.com/Opentrons/opentrons/tree/edge/.cursor/skills/static-deploy into .opencode/skills/static-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "static-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.
static-deployConventions for static deploy automation Python CLIs in scripts/static-deploy/.
Static Deploy is an agent skill from Opentrons/opentrons. Conventions for static deploy automation Python CLIs in scripts/static-deploy/. Use when working with deployment scripts, AWS S3/CloudFront automation, or Python CLIs in the static-deploy directory.
Its SKILL.md is about 810 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 Python, Amazon S3 and Amazon Web Services. The repository describes itself as: Software for writing protocols and running them on the Opentrons Flex and Opentrons OT-2. The licence is Apache-2.0.
Read from SKILL.md and the folder at commit 5bae80d. 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.
Shell commands in SKILL.md call:
uvFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Static Deploy loads about 806 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 372 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 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.
The full file from Opentrons/opentrons at commit 5bae80d, republished under its Apache-2.0 licence (© Opentrons). 372 words, ~806 tokens.
.claude/skills/static-deploy/SKILL.md (or your agent's skills folder).typing everywhere (arg/return types, TypedDict/Protocol/Enum where helpful)dataclasses for config/value objects; avoid global statepathlib.Path, not os.path stringssubprocess.run(..., check=True, text=True) for shelling out; return structured resultsValueError for validation, RuntimeError for runtime failures)rich.console.Console() instance — create once and reusepyproject.toml)uv run python deploy.py ...).PHONY targets) calling uv run ...argparse from stdlib with clear help text and argument validation--dry-run flag for safe testing--aws-profile for local runs; in CI accept env and required inputs via argsint from main() and call raise SystemExit(main())GITHUB_OUTPUT when the env var is setSame code path runs locally and in CI. Only entry points differ:
--aws-profile, etc.)Configuration should be static and deterministic — avoid runtime environment detection.
Use rich.console.Console for all human output:
style="red" for errorsstyle="yellow" for warningsstyle="green" for successstyle="blue" for infostyle="green bold" for major successconsole.rule, Status spinners for long-running steps, Table for summariesconsole.print calls./ for library code, ./tests/ for tests© Opentrons, 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
Just SKILL.md in .cursor/skills/static-deploy of Opentrons/opentrons.
Open the folder on GitHubat commit 5bae80d
Static 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 |
|---|---|---|---|---|---|---|
| Static Deploy this skillOpentrons/opentrons | 521 | — | ~806 | Automated safety check: Pass | Apache-2.0 | |
| AWS Cdk Developmentzxkane/aws-skills | 367 | 2 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Devops Deploysickn33/agentic-awesome-skills | 47k | 2 repos | ~1.9k | Automated safety check: Pass | MIT | |
| AWS Deploymentaws/agent-toolkit-for-aws | 2.8k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| AWS Cdkaws/agent-toolkit-for-aws | 2.8k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Update Quarto in RStudiorstudio/rstudio | 5.1k | — | ~2.8k | Automated safety check: Pass | Custom licence |
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
sickn33/agentic-awesome-skills
DevOps e deploy de aplicacoes — Docker, CI/CD com GitHub Actions, AWS Lambda, SAM, Terraform, infraestrutura como codigo e monitoramento.
aws/agent-toolkit-for-aws
Configures CI/CD pipelines using AWS CodePipeline, CodeBuild, CodeDeploy, CodeConnections, and CodeArtifact.
aws/agent-toolkit-for-aws
Authors, deploys, and troubleshoots AWS infrastructure using CDK with TypeScript or Python.
rstudio/rstudio
Bumps the pinned Quarto version across the RStudio repository, mirrors the release to the rstudio-buildtools S3 bucket, verifies it and opens a PR, on macOS and Linux.
mukul975/Anthropic-Cybersecurity-Skills
Deploy cloud-native deception across AWS, Azure, and GCP using decoy (honey) resources whose only purpose is to generate a high-fidelity alert the instant an attacker touches them: canary IAM access…
Opentrons/opentrons
Conventions for the opentrons-ai-client React/TypeScript frontend — project structure, API integration, state management (Jotai), feature flags, types, and testing.
Opentrons/opentrons
Conventions for the opentrons-ai-server FastAPI service — project structure, uv dependency management, settings, testing, Docker, and deployment.
Opentrons/opentrons
Conventions for the analyses snapshot testing framework in analyses-snapshot-testing/.
Opentrons/opentrons
CSS Modules conventions, Stylelint rules, design tokens (spacing, colors, typography, border-radius), and patterns for the Opentrons monorepo.
Opentrons/opentrons
Authoring and styling guidelines for the Opentrons /docs MkDocs project.
Opentrons/opentrons
E2E testing conventions for Protocol Designer and Labware Library using Playwright + pytest in e2e-testing/.
Works with
Categories
Conventions for static deploy automation Python CLIs in scripts/static-deploy/. Static Deploy is an agent skill from Opentrons/opentrons. Conventions for static deploy automation Python CLIs in scripts/static-deploy/.
Static Deploy fits situations like: working with deployment scripts; AWS S3/CloudFront automation; Python CLIs in the static-deploy directory.
Run `npx skills add Opentrons/opentrons --skill static-deploy -a claude-code`. Or copy the skill folder (.cursor/skills/static-deploy in Opentrons/opentrons) into .claude/skills/static-deploy in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Opentrons/opentrons --skill static-deploy -a codex`. Or copy the skill folder (.cursor/skills/static-deploy in Opentrons/opentrons) into .agents/skills/static-deploy 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 Opentrons/opentrons --skill static-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/static-deploy, .gemini/skills/static-deploy, .github/skills/static-deploy and .opencode/skills/static-deploy in your project.
Going by SKILL.md and its folder, Static Deploy needs the command-line tools its instructions call (uv). Our summary lists: Python 3.
SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
Static 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.
About 806 tokens (SKILL.md is roughly 3.2k 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 Static Deploy: AWS Cdk Development (zxkane/aws-skills, 367 stars), Devops Deploy (sickn33/agentic-awesome-skills, 47k stars), AWS Deployment (aws/agent-toolkit-for-aws, 2.8k stars) and AWS Cdk (aws/agent-toolkit-for-aws, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Opentrons (a GitHub organization) maintains it in Opentrons/opentrons, which has 521 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 6, 2026.
Source: Opentrons/opentrons on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.