Configure secure, high-performance connectivity between on-premises infrastructure and cloud platforms using VPN and dedicated connections. Use when building hybrid cloud architectures, connecting data centers to cloud, or implementing secure cross-premises networking.
71
63%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/cloud-infrastructure/skills/hybrid-cloud-networking/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description with a clear 'Use when' clause and good trigger term coverage for hybrid cloud networking scenarios. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., configuring IPsec tunnels, setting up Direct Connect/ExpressRoute, managing route tables). Overall it performs well for skill selection purposes.
Suggestions
Add more specific concrete actions such as 'configure IPsec tunnels, set up AWS Direct Connect or Azure ExpressRoute, manage BGP peering and route tables' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (hybrid cloud connectivity) and mentions VPN and dedicated connections, but doesn't list multiple specific concrete actions beyond 'configure'. It lacks specifics like 'set up IPsec tunnels, configure BGP peering, establish AWS Direct Connect or Azure ExpressRoute, manage routing tables'. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure secure, high-performance connectivity using VPN and dedicated connections) and 'when' (explicit 'Use when' clause covering hybrid cloud architectures, connecting data centers to cloud, and secure cross-premises networking). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'VPN', 'dedicated connections', 'hybrid cloud', 'data centers to cloud', 'on-premises', 'cross-premises networking'. These are terms a user would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around on-premises-to-cloud connectivity with specific triggers like VPN, dedicated connections, and hybrid cloud. This is unlikely to conflict with general cloud or general networking skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill covers a broad topic across four cloud providers but sacrifices depth and actionability for breadth. It provides some useful Terraform snippets and CLI commands but lacks clear end-to-end workflows with validation steps, which is critical for complex networking operations. The content would benefit from being restructured into a concise overview with provider-specific details in separate reference files, and adding explicit step-by-step setup procedures with verification checkpoints.
Suggestions
Add a clear end-to-end workflow with numbered steps and validation checkpoints (e.g., '1. Deploy VPN gateway → 2. Configure customer gateway → 3. Verify tunnel status with `aws ec2 describe-vpn-connections` → 4. Test connectivity with ping/traceroute → 5. Configure BGP → 6. Verify route propagation').
Move provider-specific details (Azure, GCP, OCI) into separate reference files (e.g., `references/azure-connectivity.md`) and keep SKILL.md as a concise overview with links, improving progressive disclosure.
Replace the BGP pseudocode block with actual executable configuration (e.g., a real router config snippet or Terraform `aws_dx_bgp_peer` resource) to improve actionability.
Remove bullet-point descriptions of what each connection type is (e.g., 'IPSec VPN over internet', 'Dedicated network connection') since Claude already knows these concepts—focus on when to choose each and how to configure them.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanatory content (e.g., bullet-point descriptions of what VPN and Direct Connect are, which Claude already knows), and the 'When to Use' section is somewhat redundant with the purpose. However, it's not egregiously verbose—most sections carry useful configuration details. | 2 / 3 |
Actionability | Provides some executable Terraform code for AWS VPN and Azure VPN gateway, plus CLI troubleshooting commands. However, many sections (GCP, OCI, BGP configuration, security best practices, cost optimization) are high-level bullet lists without concrete, executable examples. The BGP config is pseudocode rather than actual router configuration. | 2 / 3 |
Workflow Clarity | There is no clear sequential workflow for setting up hybrid connectivity end-to-end. Steps are not numbered in a process flow, there are no validation checkpoints (e.g., verify tunnel is up before proceeding), and no feedback loops for error recovery. For a complex, multi-step networking operation, this is a significant gap. | 1 / 3 |
Progressive Disclosure | There is one reference to 'references/direct-connect.md' and links to related skills at the bottom, showing some awareness of progressive disclosure. However, the main file is quite long (~200+ lines) with inline content for multiple cloud providers that could be split into separate reference files. The structure is reasonable but could be better organized. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
27a7ed9
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.