aws-network-monitoring

Installs, configures, and troubleshoots Network Flow Monitor agents on EC2 instances to monitor network path health. Covers agent installation, IAM permissions, monitoring network paths, and troubleshooting agents reporting no metrics, HTTP 403 errors, or connectivity failures.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/specialized-skills/operations-skills/aws-network-monitoring/SKILL.md

Quality

Content

72%

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

A well-structured, lean overview that excels at progressive disclosure with real, one-level-deep references and clear navigation. The body itself is a routing hub, so it lacks executable commands and an explicit validated workflow, which are instead delegated to the reference files.

Suggestions

Add a brief inline minimal example or the single most-used command (e.g., the SSM Distributor install/activate invocation) so the body is actionable without opening a reference.

Surface a short validated end-to-end sequence with an explicit verification checkpoint (e.g., confirm metrics appear after activation) in the body or a quick-start section.

Dimension	Reasoning	Score
Conciseness	The body is lean — overview, routing table, files table, and short security notes — and assumes Claude's competence without explaining general concepts; every section earns its place. It is not a 2 because there is no padded explanation of Claude-known material.	3 / 3
Actionability	The body provides some concrete specifics (policy names like 'CloudWatchNetworkFlowMonitorAgentPublishPolicy', VPC endpoint patterns, SSM document name) but no executable code or command blocks, deferring execution to references; this matches 'some concrete guidance but incomplete'.	2 / 3
Workflow Clarity	The routing table provides a decision flow, but the body contains no explicit multi-step sequence with validation checkpoints for the install/activate/publish process; it is not a 1 because routing structure exists, and not a 3 because no validation checkpoints are shown.	2 / 3
Progressive Disclosure	A clear overview hub with a routing table and a files table pointing to three real one-level-deep references (verified to exist: agent-install-ec2.md, agent-permissions.md, troubleshooting.md), matching the well-signaled, appropriately-split anchor.	3 / 3
	Total	10 / 12 Passed

Description

82%

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

A specific, third-person description with strong concrete actions and natural trigger terms for a well-defined AWS niche. Its only weakness is the absence of an explicit 'Use when...' clause, which caps completeness.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when installing, configuring, or troubleshooting Network Flow Monitor agents on EC2, or when users report HTTP 403, missing metrics, or connectivity failures from these agents.'

Consider adding common phrasing variations like 'network flow monitor' or 'NFM agent' to broaden trigger-term recall.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Installs, configures, and troubleshoots', 'agent installation, IAM permissions, monitoring network paths', 'troubleshooting agents reporting no metrics, HTTP 403 errors, or connectivity failures'), matching the 'multiple specific concrete actions' anchor.	3 / 3
Completeness	The 'what' is clearly stated (install/configure/troubleshoot NFM agents to monitor network path health), but there is no explicit 'Use when...' trigger clause, which the guidelines cap at 2; it is not a 1 because the capability description is strong.	2 / 3
Trigger Term Quality	Natural user complaint terms ('no metrics', 'HTTP 403 errors', 'connectivity failures') plus the product name 'Network Flow Monitor agents on EC2 instances' give good coverage of phrasing a user would actually say; not merely technical jargon.	3 / 3
Distinctiveness Conflict Risk	The narrow niche 'Network Flow Monitor agents on EC2 instances' with distinctive triggers (HTTP 403, no metrics) is unlikely to conflict with other skills, matching the clear-niche anchor.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: aws/agent-toolkit-for-aws
Path: skills/specialized-skills/operations-skills/aws-network-monitoring/SKILL.md
Commit: 222ce56

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.