CtrlK
BlogDocsLog inGet started
Tessl Logo

network-engineer

Expert network engineer specializing in modern cloud networking, security architectures, and performance optimization. Masters multi-cloud connectivity, service mesh, zero-trust networking, SSL/TLS, global load balancing, and advanced troubleshooting. Handles CDN optimization, network automation, and compliance. Use PROACTIVELY for network design, connectivity issues, or performance optimization.

48

Quality

52%

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 ./skills/network-engineer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

20%Weight 40%Scale 1-3

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

The body reads as a verbose persona/role definition enumerating well-known concepts and tools rather than actionable, token-efficient guidance, with a sequenced workflow that lacks validation checkpoints.

Suggestions

Cut the catalog-style capability lists (product/service enumerations Claude already knows) and replace them with a few concrete decision rules or command snippets for the highest-value network tasks.

Add explicit validation/verification checkpoints to the Response Approach workflow — e.g. validate connectivity at each OSI layer and re-test after any change — since network changes are risky.

Split the large capability taxonomy into a one-level reference file (e.g. references/CAPABILITIES.md) and keep SKILL.md as a concise overview with a clear pointer, improving progressive disclosure.

DimensionReasoningScore

Conciseness

The body is padded with enumerated lists of product names and concepts Claude already knows (e.g. "AWS networking: VPC, subnets, route tables, NAT gateways" and "Modern protocols: HTTP/2, HTTP/3 (QUIC), WebSockets, gRPC"), which the rubric penalizes as unnecessary explanation of known concepts.

1 / 3

Actionability

It describes categories and lists tool names but provides almost no concrete, executable guidance — no commands, config snippets, or specific decision rules — and steps like "Analyze network requirements" and "Test thoroughly" are vague platitudes, matching the describes-rather-than-instructs anchor.

1 / 3

Workflow Clarity

The 9-step "Response Approach" provides a clear sequence, but network configuration is a risky/batch context and there are no explicit validation checkpoints or validate→fix→retry feedback loops, which caps the score at 2.

2 / 3

Progressive Disclosure

It is a single ~157-line file with no bundle references, and the large capability taxonomy that should be split out is all inline; the section organization prevents a score of 1 but it is not a concise overview pointing to one-level references.

2 / 3

Total

6

/

12

Passed

Description

85%Weight 40%Scale 1-3

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, complete, and clearly distinct, but its trigger phrasing leans on the system directive "PROACTIVELY" and omits common natural-language variations users would actually say.

DimensionReasoningScore

Specificity

The description enumerates many concrete capability domains — "multi-cloud connectivity, service mesh, zero-trust networking, SSL/TLS, global load balancing" plus "CDN optimization, network automation, and compliance" — matching the anchor for multiple specific concrete actions rather than only naming a domain and some actions.

3 / 3

Completeness

It answers both what (detailed capabilities) and when via the explicit "Use PROACTIVELY for network design, connectivity issues, or performance optimization" trigger clause, satisfying the anchor for clearly answering both what AND when.

3 / 3

Trigger Term Quality

It includes relevant triggers ("Use PROACTIVELY for network design, connectivity issues, or performance optimization") but "PROACTIVELY" is a system directive rather than a user utterance, and common natural variations a user would say (e.g. "troubleshoot my network", "set up a load balancer", "VPN not working") are missing.

2 / 3

Distinctiveness Conflict Risk

The network-engineering niche is clearly bounded with distinct triggers (network design, connectivity issues, performance optimization) and is unlikely to be selected for the wrong skill.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
rmyndharis/antigravity-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.