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.
56
63%
Does it follow best practices?
Impact
—
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 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.
The skill provides broad coverage of hybrid cloud networking across four providers with some useful Terraform examples and CLI commands, but suffers from a lack of clear workflow sequencing and validation steps for what is inherently a complex, multi-step process. Many sections are descriptive bullet lists rather than actionable instructions, and the content is somewhat verbose with explanations Claude doesn't need. The referenced bundle file doesn't exist, undermining progressive disclosure.
Suggestions
Add a clear end-to-end workflow with numbered steps and explicit validation checkpoints (e.g., 'Verify tunnel status with `aws ec2 describe-vpn-connections` before proceeding to route configuration').
Replace descriptive bullet lists for GCP, OCI, and BGP sections with executable Terraform or CLI code examples, matching the level of detail given to AWS and Azure VPN.
Remove explanatory text about what VPN/Direct Connect/ExpressRoute are (Claude knows this) and trim the 'When to Use' and 'Cost Optimization' sections to essential, non-obvious guidance only.
Either provide the referenced `references/direct-connect.md` bundle file or remove the reference; consider splitting provider-specific details into separate reference files to reduce the monolithic structure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill covers four cloud providers which adds necessary breadth, but includes some unnecessary explanatory text (e.g., bullet-point descriptions of what VPN and Direct Connect are, which Claude already knows). The 'When to Use' section and some bullet lists could be tightened significantly. | 2 / 3 |
Actionability | Provides some executable Terraform code for AWS VPN and Azure VPN, plus CLI troubleshooting commands, but many sections (GCP, OCI, BGP configuration, security best practices, cost optimization) are purely descriptive bullet lists without concrete code or commands. The BGP config is pseudocode rather than executable. | 2 / 3 |
Workflow Clarity | There is no clear multi-step workflow with sequencing or validation checkpoints. Setting up hybrid cloud connectivity is inherently a multi-step, risky process, yet the skill presents disconnected sections without a coherent sequence, no verification steps (e.g., test tunnel connectivity after setup), and no feedback loops for error recovery. | 1 / 3 |
Progressive Disclosure | References `references/direct-connect.md` and related skills, showing some intent for progressive disclosure, but no bundle files exist to support these references. The main file is quite long and monolithic—detailed provider-specific configurations could be split into separate reference files. The reference to a non-existent bundle file is a negative signal. | 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
112197c
- 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.