Monitor CI
nrwl/nx
Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.
Establishes VPC peering connections between two VPCs for direct private network connectivity.
Install Connecting Vpcs With Peering
$ npx skills add aws/agent-toolkit-for-aws --skill connecting-vpcs-with-peering -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aws/agent-toolkit-for-aws connecting-vpcs-with-peering --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/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/specialized-skills/networking-and-content-delivery-skills/connecting-vpcs-with-peering .claude/skills/connecting-vpcs-with-peering && 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 "connecting-vpcs-with-peering" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/networking-and-content-delivery-skills/connecting-vpcs-with-peering into .claude/skills/connecting-vpcs-with-peering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connecting-vpcs-with-peering", 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/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/networking-and-content-delivery-skills/connecting-vpcs-with-peeringType 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 aws/agent-toolkit-for-aws --skill connecting-vpcs-with-peering -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aws/agent-toolkit-for-aws connecting-vpcs-with-peering --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/specialized-skills/networking-and-content-delivery-skills/connecting-vpcs-with-peering .agents/skills/connecting-vpcs-with-peering && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "connecting-vpcs-with-peering" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/networking-and-content-delivery-skills/connecting-vpcs-with-peering into .agents/skills/connecting-vpcs-with-peering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connecting-vpcs-with-peering", 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 aws/agent-toolkit-for-aws --skill connecting-vpcs-with-peering -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aws/agent-toolkit-for-aws connecting-vpcs-with-peering --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/specialized-skills/networking-and-content-delivery-skills/connecting-vpcs-with-peering .cursor/skills/connecting-vpcs-with-peering && 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 "connecting-vpcs-with-peering" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/networking-and-content-delivery-skills/connecting-vpcs-with-peering into .cursor/skills/connecting-vpcs-with-peering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connecting-vpcs-with-peering", 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/aws/agent-toolkit-for-aws.git --path skills/specialized-skills/networking-and-content-delivery-skills/connecting-vpcs-with-peering--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 aws/agent-toolkit-for-aws --skill connecting-vpcs-with-peering -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aws/agent-toolkit-for-aws connecting-vpcs-with-peering --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/specialized-skills/networking-and-content-delivery-skills/connecting-vpcs-with-peering .gemini/skills/connecting-vpcs-with-peering && 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 "connecting-vpcs-with-peering" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/networking-and-content-delivery-skills/connecting-vpcs-with-peering into .gemini/skills/connecting-vpcs-with-peering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connecting-vpcs-with-peering", 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 aws/agent-toolkit-for-aws connecting-vpcs-with-peeringInstalls 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 aws/agent-toolkit-for-aws --skill connecting-vpcs-with-peering -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/specialized-skills/networking-and-content-delivery-skills/connecting-vpcs-with-peering .github/skills/connecting-vpcs-with-peering && 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 "connecting-vpcs-with-peering" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/networking-and-content-delivery-skills/connecting-vpcs-with-peering into .github/skills/connecting-vpcs-with-peering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connecting-vpcs-with-peering", 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 aws/agent-toolkit-for-aws --skill connecting-vpcs-with-peering -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aws/agent-toolkit-for-aws connecting-vpcs-with-peering --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/specialized-skills/networking-and-content-delivery-skills/connecting-vpcs-with-peering .opencode/skills/connecting-vpcs-with-peering && 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 "connecting-vpcs-with-peering" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/networking-and-content-delivery-skills/connecting-vpcs-with-peering into .opencode/skills/connecting-vpcs-with-peering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connecting-vpcs-with-peering", 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
connecting-vpcs-with-peering- GitHub stars
- 2.8k
- Token cost
- ~472 tokens
- SKILL.md length
- 195 words
- Files
- 2 (incl. references)
- Skills in repo
- 138
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Establishes VPC peering connections between two VPCs for direct private network connectivity.
- Managing VPC peering — it validates CIDR overlap
- SKILL.md covers Overview, Create a VPC peering connection and Troubleshooting
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Updates all route tables in both VPCs
What it does
Connecting Vpcs With Peering is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. Establishes VPC peering connections between two VPCs for direct private network connectivity. Always use this skill when creating or managing VPC peering — it validates CIDR overlap, updates all route tables in both VPCs, configures DNS resolution, and provides security group guidance that are critical for correct connectivity.
Its SKILL.md is about 470 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/vpc-peering-connection.md`).
It sits in DevOps & Cloud. The repository describes itself as: Official, AWS-supported MCP servers, skills, and plugins to help AI agents build on AWS. The licence is Apache-2.0.
When your agent uses it
- Managing VPC peering — it validates CIDR overlap
- Updates all route tables in both VPCs
- Configures DNS resolution
- Provides security group guidance that are critical for correct connectivity
Example prompts
- “Use the connecting-vpcs-with-peering skill to establish VPC peering connections between two VPCs for direct private network connectivity”
- “/connecting-vpcs-with-peering”
What it can do on your machine
Read from SKILL.md and the folder at commit 2cb0fa1. 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
Connecting Vpcs With Peering loads about 472 tokens when it runs, and up to ~2.4k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 195 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 aws/agent-toolkit-for-aws at commit 2cb0fa1, republished under its Apache-2.0 licence (© aws). 195 words, ~472 tokens.
Download SKILL.mdSave it as
.claude/skills/connecting-vpcs-with-peering/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- connecting-vpcs-with-peering
- description
- Establishes VPC peering connections between two VPCs for direct private network connectivity. Always use this skill when creating or managing VPC peering — it validates CIDR overlap, updates all route tables in both VPCs, configures DNS resolution, and provides security group guidance that are critical for correct connectivity.
- version
- 1
Connecting VPCs with Peering
Overview
Domain expertise for establishing private network connectivity between two VPCs using VPC peering. Covers the full lifecycle: creating the peering connection, accepting it, updating route tables in both VPCs, configuring DNS resolution, and adjusting security groups for cross-VPC traffic. Supports same-region, cross-region, and cross-account peering scenarios.
Create a VPC peering connection
To establish a VPC peering connection between two VPCs, follow the procedure exactly. See VPC peering connection procedure.
The procedure requires the requester and accepter VPC IDs at minimum. It validates both VPCs exist, checks for CIDR overlap, creates and accepts the peering, updates all route tables, and configures DNS resolution.
Troubleshooting
Peering stuck in pending state
Cross-account connections require manual acceptance from the accepter account. Same-account connections with auto_accept: true should transition automatically.
Route creation fails
Check for existing routes with the same destination CIDR. Replace existing routes instead of creating new ones.
DNS resolution not working
Both VPCs must have DNS resolution and DNS hostnames enabled in their VPC settings, not just the peering connection options.
Cross-region connectivity issues
Verify routes are added in both regions and security groups allow traffic from the peer VPC's CIDR blocks.
© aws, 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
SKILL.md and 1 other file (references) in skills/specialized-skills/networking-and-content-delivery-skills/connecting-vpcs-with-peering of aws/agent-toolkit-for-aws.
- SKILL.md
- references/vpc-peering-connection.md
Open the folder on GitHubat commit 2cb0fa1
Compare with similar skills
Connecting Vpcs With Peering 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 |
|---|---|---|---|---|---|---|
| Connecting Vpcs With Peering this skillaws/agent-toolkit-for-aws | 2.8k | — | ~472 | Automated safety check: Pass | Apache-2.0 | |
| Monitor CInrwl/nx | 29k | 6 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Terraform and OpenTofu Guideagentscope-ai/QwenPaw | 36k | 6 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 8 repos | ~4.3k | Automated safety check: Pass | None | |
| Analyze GitHub Action Logswithastro/astro | 63k | 1 repos | ~1.3k | Automated safety check: Pass | Custom licence | |
| Openclaw Live Updateropenclaw/openclaw | 392k | — | ~3.7k | Automated safety check: Pass | MIT |
Similar skills
Terraform and OpenTofu Guide
agentscope-ai/QwenPaw
Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.
- Official
Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
- Official
Analyze GitHub Action Logs
withastro/astro
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
Openclaw Live Updater
openclaw/openclaw
Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.
Docs Learn PR Preview
netdata/netdata
Use only when the user explicitly asks to build, run, preview, inspect, or validate learn.netdata.cloud locally using the contents of a PR or documentation branch before merge.
More from aws/agent-toolkit-for-aws
All 138 skills in this repo- Official
Agent Advisor
aws/agent-toolkit-for-aws
Entry point for AI-agent work on AWS: pick a runtime, plan a migration for existing workloads, and build an executable POC — one phased flow.
- Official
Agents Build
aws/agent-toolkit-for-aws
A skill your agent uses to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments, or resource removal.
- Official
Launch With AWS
aws/agent-toolkit-for-aws
Migrates vibe-coded web applications to AWS. An agent skill from aws/agent-toolkit-for-aws.
- Official
Processing S3 Uploads With Step Functions
aws/agent-toolkit-for-aws
Deploy an event-driven workflow that routes S3 uploads to either Lambda or Fargate via Step Functions based on file size.
- Official
AWS Marketplace Metering
aws/agent-toolkit-for-aws
Deploys, queries, and debugs AWS Marketplace usage-based (PAYG) metering — the pipeline (ResolveCustomer, BatchMeterUsage, EventBridge via SAM) and querying/debugging metering records, statuses…
- Official
Agents Pay
aws/agent-toolkit-for-aws
A skill your agent uses when THIS agent needs to pay for x402-protected content at runtime: hitting a paywall mid-task, settling it via AgentCore Payments, and applying operator-defined spend limits.
Related
Categories
Questions about Connecting Vpcs With Peering
What does Connecting Vpcs With Peering do?
Establishes VPC peering connections between two VPCs for direct private network connectivity. Connecting Vpcs With Peering is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. Establishes VPC peering connections between two VPCs for direct private network connectivity.
When should I use Connecting Vpcs With Peering?
Connecting Vpcs With Peering fits situations like: managing VPC peering — it validates CIDR overlap; updates all route tables in both VPCs; configures DNS resolution; provides security group guidance that are critical for correct connectivity.
How do I install Connecting Vpcs With Peering in Claude Code?
Run `npx skills add aws/agent-toolkit-for-aws --skill connecting-vpcs-with-peering -a claude-code`. Or copy the skill folder (skills/specialized-skills/networking-and-content-delivery-skills/connecting-vpcs-with-peering in aws/agent-toolkit-for-aws) into .claude/skills/connecting-vpcs-with-peering in your project. Claude Code loads it when a task matches its description.
How do I install Connecting Vpcs With Peering in Codex?
Run `npx skills add aws/agent-toolkit-for-aws --skill connecting-vpcs-with-peering -a codex`. Or copy the skill folder (skills/specialized-skills/networking-and-content-delivery-skills/connecting-vpcs-with-peering in aws/agent-toolkit-for-aws) into .agents/skills/connecting-vpcs-with-peering in your project. Codex loads it when a task matches its description.
Can I use Connecting Vpcs With Peering 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 aws/agent-toolkit-for-aws --skill connecting-vpcs-with-peering -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/connecting-vpcs-with-peering, .gemini/skills/connecting-vpcs-with-peering, .github/skills/connecting-vpcs-with-peering and .opencode/skills/connecting-vpcs-with-peering in your project.
What does Connecting Vpcs With Peering need to run?
SKILL.md names no scripts, command-line tools or credentials: Connecting Vpcs With Peering is instructions for the agent only.
Does Connecting Vpcs With Peering 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 Connecting Vpcs With Peering 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 Connecting Vpcs With Peering use?
Connecting Vpcs With Peering 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 Connecting Vpcs With Peering use?
About 472 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2k tokens, read only when the agent opens those files.
What are the alternatives to Connecting Vpcs With Peering?
Skills that share tags, products or a category with Connecting Vpcs With Peering: Monitor CI (nrwl/nx, 29k stars), Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 36k stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Analyze GitHub Action Logs (withastro/astro, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Connecting Vpcs With Peering?
aws (a GitHub organization, an official publisher) maintains it in aws/agent-toolkit-for-aws, which has 2,835 GitHub stars. The repository holds 138 skills in this directory. The repository was last updated on October 9, 2026.
Source: aws/agent-toolkit-for-aws on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.