CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

49

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

20%

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

The body reads as a descriptive overview rather than executable guidance: it re-explains concepts Claude knows, offers no code or concrete commands, and ignores its own bundled scripts and assets. The workflow has a step list but lacks validation checkpoints.

Suggestions

Replace the prose Best Practices explanations and vague Instructions with concrete, copy-paste-ready commands or code snippets (e.g. curl/timing examples, the analyze_request_patterns.py invocation).

Tighten the body by removing the description restatement in Overview and the conceptual explanations of batching/pooling that Claude already knows.

Link the bundled scripts and the latency_analysis_template.html asset from the body so progressive disclosure actually routes readers to those files, and add an explicit validation step in the Instructions workflow.

DimensionReasoningScore

Conciseness

The body is padded: the Overview restates the description, the Best Practices section explains connection pooling/batching/parallelization concepts Claude already knows, and the Examples are verbose prose, matching the verbose/padded anchor.

1 / 3

Actionability

There is no executable code or concrete command anywhere; the Instructions are abstract directives ('Identify all network requests', 'Measure latency', 'Recommend timeout configurations'), describing rather than instructing.

1 / 3

Workflow Clarity

A 6-step Instructions sequence exists and a separate Error Handling list is provided, but no validation checkpoints are integrated into the workflow and the steps remain implicit-directional rather than verified.

2 / 3

Progressive Disclosure

Sections provide some organization, but the body never references the real bundle files (scripts/analyze_request_patterns.py and other scripts, the assets template), keeping in prose what should be split out and leaving the bundle unlinked.

2 / 3

Total

6

/

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 strong: it answers both what and when, uses natural trigger phrases, and carves out a distinct niche. Its only weakness is specificity, where it lists a couple of broad actions rather than a comprehensive set of concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain ('network latency') and two actions ('Analyze network latency and optimize request patterns') but stops short of the comprehensive multi-action list the score-3 anchor requires (e.g. extract, fill, merge).

2 / 3

Completeness

It states both what it does ('Analyze network latency and optimize request patterns for faster communication') and an explicit 'Use when diagnosing slow network performance or optimizing API calls' trigger clause, satisfying both halves.

3 / 3

Trigger Term Quality

Explicit natural phrases users would say are listed ('analyze network latency', 'optimize API calls', 'reduce network delays'), giving good coverage matching the score-3 anchor.

3 / 3

Distinctiveness Conflict Risk

The network-latency niche plus distinct trigger phrases make it clearly distinguishable and unlikely to fire for the wrong skill, matching the clear-niche anchor.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.