analyzing-network-latency

Analyze network latency and optimize request patterns for faster communication. Use when diagnosing slow network performance or optimizing API calls. Trigger with phrases like "analyze network latency", "optimize API calls", or "reduce network delays".

Quality

51%

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/performance/network-latency-analyzer/skills/analyzing-network-latency/SKILL.md

Quality

Content

12%

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

The body is a verbose, abstract restatement of network-optimization concepts Claude already knows, with no executable commands or code and no links to the bundled script. Cross-file structure is broken: the body never references the bundle, and the bundle READMEs claim files that do not exist.

Suggestions

Collapse the redundant How It Works / Examples / Best Practices / Instructions sections into one concise workflow, and drop explanations of known concepts like what connection pooling is.

Add concrete, copy-paste-ready commands (e.g. curl timing, ping/traceroute invocations, a call to scripts/analyze_request_patterns.py) so the guidance is executable rather than descriptive.

Wire the body to the bundle with one-level-deep references (e.g. 'See scripts/analyze_request_patterns.py') and fix scripts/README.md so it only lists files that actually exist.

Dimension	Reasoning	Score
Conciseness	The ~94-line body restates the same few techniques (parallelization, batching, pooling, timeouts) across How It Works, Examples, Best Practices, and Instructions, and the Best Practices section explains concepts Claude already knows (e.g. "Connection Pooling: Reuse existing HTTP connections to avoid the overhead"), matching the score-1 anchor of padding with unnecessary context.	1 / 3
Actionability	No executable code or concrete commands appear anywhere; Instructions are abstract ("Measure latency for each request type", "Analyze patterns for serial vs parallel execution") and the allowed curl/ping/traceroute tools are never示范, nor is the bundled analyze_request_patterns.py script ever invoked — describing rather than instructing, per the score-1 anchor.	1 / 3
Workflow Clarity	A 6-step sequence is listed (Identify → Measure → Analyze → Identify opportunities → Recommend → Provide plan) and an Error Handling section exists, but there are no explicit validation checkpoints or feedback loops integrated into the workflow, capping it at 2 per the missing-checkpoint anchor.	2 / 3
Progressive Disclosure	The body is a monolithic wall of text with zero references to any bundle file, while the bundle itself is largely phantom — scripts/README.md marks 5 scripts present but only 1 exists, and assets/README.md lists a non-existent file — matching the score-1 anchor of poor cross-file organization and navigation.	1 / 3
	Total	5 / 12 Passed

Description

90%

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 well-crafted and closely models the good reference examples: it states concrete actions, includes an explicit 'Use when' trigger clause with natural phrases, and occupies a clear niche. Its only weakness is modest action specificity (two high-level actions rather than a fuller list).

Dimension	Reasoning	Score
Specificity	Names the domain and two actions ("Analyze network latency and optimize request patterns") but stops at two high-level actions rather than listing multiple concrete operations like the score-3 anchor ("Extract text and tables..., fill forms, merge documents").	2 / 3
Completeness	Clearly answers both what ("Analyze network latency and optimize request patterns for faster communication") and when with explicit triggers ("Use when diagnosing slow network performance or optimizing API calls. Trigger with phrases like..."), matching the score-3 example structure.	3 / 3
Trigger Term Quality	Provides natural phrases users would actually say — "analyze network latency", "optimize API calls", "reduce network delays" — alongside the "Use when diagnosing slow network performance" clause, matching the score-3 anchor's coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	Network-latency diagnosis is a clear niche with distinct triggers ("analyze network latency", "reduce network delays") unlikely to fire for unrelated skills; "optimize API calls" is slightly broad but the latency framing keeps it distinguishable, so it is not the score-2 overlap case.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/performance/network-latency-analyzer/skills/analyzing-network-latency/SKILL.md
Commit: 15940c5

Reviewed: 4 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.