network-engineer

I took a look at your network-engineer skill and wanted to share some thoughts.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 76/100, solidly in C territory. The grading is based on Anthropic's skill best practices across five pillars. Your Utility scores perfectly at 20/20 — the comprehensive network engineering coverage is genuinely useful. The weak spot is Progressive Disclosure Architecture at 14/30 — that's where you'll get the biggest wins.

What's Working Well

• Utility is chef's kiss — You've got solid problem-solving power covering cloud architectures, security, and performance. The JSON templates for communication and status reporting are practical and specific.
• Strong workflow clarity — Your numbered steps and phased approach actually guide people through complex tasks. The checklists for validation are effective.
• Good trigger discoverability — Terms like "network engineer," "cloud architecture," and "hybrid networks" are baked into the description, making it findable.
• Dense but organized — For a 253-line file, you've kept consistent terminology and structure throughout. The headers work.

The Big One: Missing Layered Architecture

This is holding you back for a -8 point swing. Right now, you've got one monolithic SKILL.md with everything inlined. What you need is a references directory with detailed guides that the main skill references rather than contains.

Here's the concrete fix:

network-engineer/
├── SKILL.md (trimmed to ~100 lines, just overview + triggers)
├── references/
│   ├── cloud-architectures.md (detailed AWS/GCP/Azure patterns)
│   ├── security-frameworks.md (detailed compliance/hardening)
│   ├── performance-tuning.md (detailed optimization str...