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
56%
Does it follow best practices?
Impact
98%
1.05xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/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 explicit 'Use when' triggers and good natural keywords covering the hybrid cloud connectivity domain. Its main weakness is that the capability description could be more specific about concrete actions (e.g., configuring IPsec tunnels, setting up Direct Connect/ExpressRoute, configuring 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 route tables and BGP peering' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (hybrid cloud connectivity) and some actions ('configure secure, high-performance connectivity using VPN and dedicated connections'), but doesn't list multiple specific concrete actions like setting up IPsec tunnels, configuring BGP peering, setting up AWS Direct Connect or Azure ExpressRoute, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure secure connectivity between on-premises and cloud using VPN and dedicated connections) and 'when' (explicit 'Use when' clause covering hybrid cloud architectures, data center to cloud connections, and cross-premises networking). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'VPN', 'dedicated connections', 'hybrid cloud', 'data centers to cloud', 'on-premises', 'cross-premises networking'. These cover common variations of how users would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly carved out niche focusing specifically on on-premises-to-cloud connectivity via VPN and dedicated connections. Unlikely to conflict with general networking, cloud-only, or security skills due to the specific hybrid/cross-premises focus. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a broad reference document or study guide than an actionable skill for Claude. It covers three cloud providers at a surface level with generic best practices Claude already knows, lacks a clear end-to-end workflow with validation steps, and is significantly too verbose. The Terraform examples provide some concrete value but are isolated snippets without a cohesive implementation workflow.
Suggestions
Add a clear sequential workflow (e.g., 'Setting up AWS Site-to-Site VPN') with numbered steps, validation checkpoints (verify tunnel status, test connectivity), and error recovery guidance.
Remove generic knowledge Claude already has (what VPN is, what Direct Connect is, basic security advice like 'implement encryption') and focus on project-specific configurations, gotchas, and non-obvious details.
Split per-cloud-provider content into separate reference files and keep SKILL.md as a concise overview with decision criteria and links to detailed guides.
Replace the BGP pseudocode with actual executable configuration (e.g., a real router config snippet or complete Terraform BGP resource) and add post-deployment verification commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is very verbose, covering three cloud providers with extensive bullet-point descriptions of connection types (bandwidth, latency, cost) that Claude already knows. The 'When to Use' section, 'Cost Optimization' tips, and 'Security Best Practices' are largely generic knowledge that doesn't need to be spelled out. Much of this could be cut by 50%+ without losing actionable value. | 1 / 3 |
Actionability | There are some concrete Terraform code blocks (AWS VPN, Azure VPN gateway, dual tunnels) and CLI commands for troubleshooting, which is good. However, many sections are just bullet-point lists of general advice rather than executable guidance (e.g., Security Best Practices, Cost Optimization, Route Propagation). The BGP configuration is pseudocode rather than actual router config. | 2 / 3 |
Workflow Clarity | There is no clear sequential workflow for setting up hybrid connectivity end-to-end. The content is organized as a reference catalog of options rather than a step-by-step process. There are no validation checkpoints, no verification steps after deploying VPN connections, and no feedback loops for error recovery—critical for networking operations where misconfigurations can cause outages. | 1 / 3 |
Progressive Disclosure | There are references to external files (references/vpn-setup.md, references/direct-connect.md) and related skills, which is good. However, the main file itself is a monolithic wall of content covering three cloud providers in detail when much of this could be split into per-provider reference files. The inline content is too long for an overview document. | 2 / 3 |
Total | 6 / 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.
47823e3
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.