tessl i github:wshobson/agents --skill hybrid-cloud-networkingConfigure 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.
Review Score
65%
Validation Score
13/16
Implementation Score
38%
Activation Score
90%
Generated
Validation
Total
13/16Score
Passed| Criteria | Score |
|---|---|
metadata_version | 'metadata' field is not a dictionary |
license_field | 'license' field is missing |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs |
Implementation
Suggestions 4
Score
38%Overall Assessment
This skill provides a broad overview of hybrid cloud networking options across AWS, Azure, and GCP with some useful Terraform examples and architectural patterns. However, it reads more like reference documentation than an actionable skill - it lacks clear workflows with validation steps for actually implementing these connections, and the code examples are incomplete. The content would benefit from being restructured around specific implementation workflows rather than categorized by cloud provider.
Suggestions
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 2/3 | The content is reasonably efficient but includes some unnecessary explanatory text (e.g., bullet point descriptions of what each connection type offers that Claude would already know). The lists of security best practices and cost optimization tips are somewhat generic and could be trimmed. |
Actionability | 2/3 | Provides executable Terraform code examples which is good, but many sections are incomplete (GCP examples missing code, BGP configuration is pseudocode-like, troubleshooting commands are minimal). The code examples lack context like required providers or variable definitions. |
Workflow Clarity | 1/3 | No clear step-by-step workflow for setting up hybrid connectivity. Content is organized as reference material rather than a guided process. Missing validation checkpoints for what are complex, potentially disruptive network operations (e.g., no steps to verify VPN tunnel is up before proceeding). |
Progressive Disclosure | 2/3 | References external files (references/vpn-setup.md, references/direct-connect.md) and related skills, which is good. However, the main file is quite long with content that could be split out (e.g., cloud-specific sections could be separate files). The ASCII diagrams are helpful for quick understanding. |
Activation
Suggestions 1
Score
90%Overall Assessment
This is a solid skill description with excellent completeness and distinctiveness. It includes an explicit 'Use when' clause with relevant trigger scenarios and carves out a clear niche in hybrid cloud connectivity. The main weakness is that the capabilities could be more specific - listing concrete actions like configuring specific connection types or protocols would strengthen it.
Suggestions
| Dimension | Score | Reasoning |
|---|---|---|
Specificity | 2/3 | Names the domain (hybrid cloud connectivity) and mentions VPN and dedicated connections, but lacks specific concrete actions like 'configure IPsec tunnels', 'set up BGP peering', or 'establish Direct Connect/ExpressRoute'. The phrase 'configure secure, high-performance connectivity' is somewhat abstract. |
Completeness | 3/3 | Clearly answers both what (configure VPN and dedicated connections between on-premises and cloud) and when (explicit 'Use when' clause covering hybrid cloud architectures, data center to cloud connections, and cross-premises networking). |
Trigger Term Quality | 3/3 | Good coverage of natural terms users would say: 'VPN', 'hybrid cloud', 'data centers to cloud', 'on-premises', 'cross-premises networking', 'dedicated connections'. These are terms users would naturally use when needing this skill. |
Distinctiveness Conflict Risk | 3/3 | Clear niche focused specifically on hybrid cloud connectivity and VPN/dedicated connections. The combination of 'on-premises', 'hybrid cloud', and 'VPN' creates distinct triggers unlikely to conflict with general cloud or networking skills. |