Name: network-engineer
Rating: 21.6 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

network-engineer

Expert network engineer specializing in modern cloud networking, security architectures, and performance optimization.

Quality

10%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/network-engineer/SKILL.md

The canonical home for this skill is network-engineer in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

10%Scale 1-5

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

This skill reads as a persona description or job posting rather than actionable instructions for performing network engineering tasks. It extensively catalogs technologies and concepts Claude already knows without providing any concrete code, commands, configuration examples, or specific procedures. The content would need a fundamental restructuring to become a useful skill.

Suggestions

Replace the extensive capability lists with concrete, executable examples: specific Terraform snippets for VPC setup, actual tcpdump/curl commands for troubleshooting, real configuration blocks for load balancers or TLS.

Add validation and verification steps with actual commands (e.g., 'Verify connectivity: `curl -v https://endpoint`', 'Check certificate chain: `openssl s_client -connect host:443`').

Remove sections that describe what Claude already knows (Capabilities catalog, Knowledge Base, Behavioral Traits) and replace with decision trees or checklists for specific scenarios.

Either create the referenced `resources/implementation-playbook.md` with detailed procedures, or inline the most critical workflows directly in SKILL.md with proper structure.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~200+ lines, mostly listing technologies and concepts Claude already knows. The 'Capabilities' section is essentially a resume/catalog of networking topics rather than actionable instructions. Behavioral traits, knowledge base, and example interactions sections add no value for task execution.	1 / 5
Actionability	Contains zero executable code, commands, or concrete examples. Everything is abstract description — lists of technologies, vague behavioral traits, and generic response approaches like 'Analyze network requirements' with no specifics on how to do so.	1 / 5
Workflow Clarity	The 'Response Approach' section provides a rough 9-step sequence but steps are entirely vague ('Implement connectivity solutions with proper configuration and testing'). No validation checkpoints, no feedback loops, no concrete commands or verification steps.	2 / 5
Progressive Disclosure	References `resources/implementation-playbook.md` but no bundle files exist, making this a dead reference. The massive amount of content inlined in SKILL.md (capability lists, behavioral traits, knowledge base) should either be removed or placed in separate reference files. No clear navigation structure.	2 / 5
	Total	6 / 20 Passed

Description

11%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.

This description reads as a persona or role statement ('Expert network engineer specializing in...') rather than a functional skill description. It uses first-person-adjacent framing, lists no concrete actions, includes no 'Use when...' trigger guidance, and relies on broad domain labels that would easily conflict with other skills. It fails to help Claude distinguish when to select this skill over others.

Suggestions

Replace the persona framing with concrete actions: e.g., 'Configures VPCs, subnets, and routing tables; sets up firewalls and security groups; diagnoses network latency and connectivity issues; designs load balancing architectures.'

Add an explicit 'Use when...' clause with natural trigger terms: e.g., 'Use when the user asks about VPCs, subnets, DNS, firewalls, load balancers, network security, cloud networking, or connectivity troubleshooting.'

Include specific cloud provider names and technical terms users would naturally mention, such as 'AWS', 'Azure', 'GCP', 'VPN', 'CDN', 'CIDR', 'NAT gateway', or 'security groups' to improve trigger term quality and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description uses entirely vague language with no concrete actions. 'Specializing in modern cloud networking, security architectures, and performance optimization' names broad domains but lists zero specific actions like 'configure VPNs', 'analyze latency', or 'set up firewall rules'.	1 / 5
Completeness	The 'what' is extremely vague (no concrete actions described), and there is no 'when' clause at all. It reads as a persona description rather than a functional skill description. Missing both what it does and when Claude should use it.	1 / 5
Trigger Term Quality	Contains a few domain keywords like 'cloud networking', 'security architectures', and 'performance optimization', but these are broad and abstract. Missing natural user phrases like 'VPC', 'firewall', 'load balancer', 'DNS', 'subnet', 'routing', 'latency', or specific cloud provider terms users would actually say.	2 / 5
Distinctiveness Conflict Risk	Very broad terms like 'security architectures' and 'performance optimization' could overlap with many other skills (e.g., application security, database optimization, general cloud skills). 'Cloud networking' provides some domain narrowing but is still quite broad.	2 / 5
	Total	6 / 20 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/network-engineer/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.