hybrid-cloud-networking
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 skill description with a clear 'Use when' clause and good trigger term coverage for hybrid cloud networking scenarios. 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, managing routing). 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 routing' 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 | Has a clear niche focused specifically on on-premises-to-cloud connectivity via VPN and dedicated connections. The trigger terms are distinct enough to avoid conflict with general networking, cloud-only, or security-only 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 serves as a broad reference catalog for hybrid cloud networking across four cloud providers, with some useful Terraform examples and CLI commands. Its main weaknesses are the lack of a clear sequential workflow with validation checkpoints for what is a complex, multi-step infrastructure operation, and the uneven actionability—some providers get executable code while others get only bullet-point descriptions. The content would benefit from being restructured as a workflow with provider-specific details split into separate reference files.
Suggestions
Add a clear end-to-end workflow section (e.g., 'Setting Up Hybrid Connectivity') with numbered steps and explicit validation checkpoints like 'Verify tunnel status before configuring route propagation'.
Move per-provider details (AWS, Azure, GCP, OCI) into separate reference files and keep only a summary comparison table in the main SKILL.md.
Add executable code examples for GCP and OCI connectivity (currently only bullet-point descriptions) to match the actionability level of the AWS and Azure sections.
Remove explanatory bullet points that describe what VPN/Direct Connect/ExpressRoute are (Claude already knows this) and replace with configuration-specific guidance.
| 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 | The Terraform code blocks for AWS VPN and Azure VPN are executable and concrete, and the CLI troubleshooting commands are copy-paste ready. However, many sections (GCP, OCI, routing, security, cost optimization) are bullet-point lists of vague guidance rather than concrete, executable instructions. The BGP configuration is pseudocode rather than actual router config. | 2 / 3 |
Workflow Clarity | There is no clear sequenced 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. For a skill involving complex, potentially destructive network configuration, there are no validation checkpoints, verification steps, or feedback loops (e.g., verify tunnel is up before proceeding to route propagation). | 1 / 3 |
Progressive Disclosure | There is one reference to a separate file ('references/direct-connect.md') and related skills are linked 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 per-provider reference files. The structure is present but not well-leveraged. | 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.
- Repository
- wshobson/agents
- Commit
70444e5
- Reviewed
Table of Contents
Is this your skill?
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.