CtrlK
BlogDocsLog inGet started
Tessl Logo

hybrid-cloud-networking

Configure secure, high-performance connectivity between on-premises and cloud environments using VPN, Direct Connect, and ExpressRoute.

52

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/hybrid-cloud-networking/SKILL.md

The canonical home for this skill is hybrid-cloud-networking in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is action-rich with concrete Terraform and CLI examples, but it has a generic Instructions section, no sequenced validation workflow for risky infra changes, and references that point to non-existent files. Tightening the fluff, adding validation checkpoints, and creating the referenced files would raise the score.

Suggestions

Replace the generic "Instructions" bullets with a concrete sequenced workflow: design → apply Terraform → validate connectivity (e.g. ping/BGP status) → monitor, with explicit validate-before-proceed checkpoints.

Create the referenced files (references/vpn-setup.md, references/direct-connect.md) or remove the broken references; fix the inconsistent "resources/implementation-playbook.md" path to the real directory.

Move the per-cloud connectivity reference detail into the reference files and keep SKILL.md as a concise overview with one inline quick-start example.

DimensionReasoningScore

Conciseness

The body is mostly concrete and avoids explaining concepts Claude already knows, but the generic "Instructions" section ("Clarify goals... Apply relevant best practices...") is fluff and substantial per-cloud reference material is inlined rather than split out.

3 / 5

Actionability

It provides concrete, executable Terraform HCL and bash troubleshooting commands for the common cases, with only minor gaps (examples lack provider config and some referenced variables).

4 / 5

Workflow Clarity

The "Instructions" section is generic principles rather than a sequenced workflow, and infrastructure configuration carries destructive/risk potential without explicit validate-then-proceed checkpoints, which caps this at 3.

3 / 5

Progressive Disclosure

Section headers organize the content and references are signaled, but referenced files (resources/implementation-playbook.md, references/direct-connect.md, references/vpn-setup.md) do not exist, the path is inconsistent ("resources/" vs "references/"), and reference-grade per-cloud detail is inlined.

3 / 5

Total

13

/

20

Passed

Description

61%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinct, naming concrete connectivity technologies, but it lacks any explicit "when to use" trigger guidance, capping completeness. Third-person voice is used correctly. Adding a "Use when..." clause would lift the two completeness-anchored dimensions.

Suggestions

Append an explicit trigger clause, e.g. "Use when connecting on-premises data centers to AWS, Azure, or GCP via VPN, Direct Connect, or ExpressRoute."

Add natural synonyms users say ("hybrid cloud", "site-to-site VPN", "cloud connectivity") to broaden trigger coverage.

Enumerate more concrete actions (e.g. "configure, validate, and troubleshoot") to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain and three concrete connectivity technologies (VPN, Direct Connect, ExpressRoute), but offers only a single action verb ("Configure") rather than multiple distinct actions, so it is not comprehensive.

3 / 5

Completeness

It gives a clear "what" but has no "Use when..." or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Natural trigger terms users would say are present ("VPN", "Direct Connect", "ExpressRoute", "on-premises", "cloud"), though common synonyms like "hybrid cloud" and "site-to-site VPN" are missing.

4 / 5

Distinctiveness Conflict Risk

The hybrid-cloud connectivity niche with named provider technologies is mostly distinct, with only minor overlap risk against a general cloud-networking skill.

4 / 5

Total

14

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.