analyzing-network-latency

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill 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".

57%

Overall

Validation — 81%

Implementation — 20%

Activation — 90%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

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

	Total	13 / 16 Passed

Implementation

20%

This skill is highly verbose and abstract, explaining concepts Claude already understands while failing to provide any concrete, executable guidance. It describes what the skill 'will do' rather than providing actual commands, code snippets, or specific tools for network latency analysis. The content would benefit from dramatic reduction and replacement of descriptions with actionable examples.

Suggestions

Replace abstract descriptions with concrete commands (e.g., `curl -w '@curl-format.txt' -o /dev/null -s https://example.com` for latency measurement)

Remove sections explaining what Claude 'will do' and instead provide executable code examples for connection pooling, request batching, etc.

Add specific tool usage examples with actual output formats (e.g., how to interpret traceroute output, specific curl timing metrics)

Consolidate the redundant 'Overview', 'How It Works', and 'When to Use' sections into a single brief introduction

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive padding explaining concepts Claude already knows. Sections like 'Overview', 'How It Works', and 'When to Use This Skill' repeat the same information multiple times and explain obvious concepts like what parallelization and connection pooling are.	1 / 3
Actionability	No concrete code, commands, or executable examples provided. The entire skill describes what Claude 'will do' abstractly rather than providing specific tools, commands, or code snippets for actually measuring latency or implementing optimizations.	1 / 3
Workflow Clarity	The 'Instructions' section provides a numbered sequence of steps, but lacks validation checkpoints, specific commands for each step, and no feedback loops for error recovery. The steps are too abstract to be actionable.	2 / 3
Progressive Disclosure	Content is organized into sections but is monolithic with no references to external files. The 'Resources' section mentions guides but provides no actual links. Content that could be split (examples, error handling) is all inline.	2 / 3
	Total	6 / 12 Passed

Activation

90%

This is a well-structured description with explicit trigger guidance and clear 'when to use' clauses. The main weakness is that the capability description could be more specific about concrete actions and techniques. The trigger terms are natural and the scope is distinct enough to avoid conflicts with other skills.

Suggestions

Expand specificity by listing concrete actions like 'measure round-trip times, identify bottlenecks, batch API requests, implement request caching, analyze connection pooling'

Dimension	Reasoning	Score
Specificity	Names the domain (network latency, request patterns) and some actions (analyze, optimize), but lacks comprehensive concrete actions like specific techniques or outputs (e.g., 'measure round-trip times', 'batch requests', 'implement caching').	2 / 3
Completeness	Clearly answers both what (analyze network latency, optimize request patterns) and when (diagnosing slow network performance, optimizing API calls) with explicit trigger phrases provided.	3 / 3
Trigger Term Quality	Includes good natural trigger terms users would say: 'analyze network latency', 'optimize API calls', 'reduce network delays', 'slow network performance'. These cover common variations of how users would phrase such requests.	3 / 3
Distinctiveness Conflict Risk	Clear niche focused on network latency and API request optimization with distinct triggers. Unlikely to conflict with general performance or code optimization skills due to specific network/API focus.	3 / 3
	Total	11 / 12 Passed

Reviewed

14 days ago

Table of Contents

Validation Implementation Activation

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.