network-latency-tester
Network Latency Tester - Auto-activating skill for Performance Testing. Triggers on: network latency tester, network latency tester Part of the Performance Testing skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill network-latency-testerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with no substantive content. It names a category ('Performance Testing') and repeats the skill name as triggers, but provides zero information about what the skill actually does, what commands or tools it uses, or when Claude should select it. This would be nearly useless for skill selection among multiple options.
Suggestions
Add specific actions the skill performs, e.g., 'Measures network latency, tests connection speed, diagnoses network delays, and reports round-trip times to specified hosts.'
Replace the duplicate trigger term with natural user phrases: 'ping test', 'check latency', 'network speed', 'connection delay', 'response time', 'slow network'.
Add an explicit 'Use when...' clause: 'Use when the user wants to test network performance, measure ping times, diagnose slow connections, or check latency to servers.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Network Latency Tester') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of measuring, testing, analyzing, or reporting latency. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('network latency tester, network latency tester'). Missing natural variations users would say like 'ping', 'latency test', 'network speed', 'response time', 'connection delay', or 'network performance'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Network Latency Tester' is somewhat specific to network performance testing, but without concrete actions or clear triggers, it could overlap with general network tools or other performance testing skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder with no substantive guidance. It describes what a network latency tester skill would do in abstract terms but provides absolutely no actionable content - no tools to use (ping, traceroute, iperf, etc.), no code examples, no measurement techniques, and no interpretation guidance for results.
Suggestions
Add concrete code examples for network latency testing using tools like ping, traceroute, iperf3, or Python libraries (e.g., pythonping, scapy)
Define a clear workflow: 1) Select target endpoints, 2) Run baseline measurements, 3) Execute tests, 4) Analyze results with specific thresholds
Include specific commands with expected output formats, e.g., `ping -c 10 example.com` and how to interpret the statistics
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific examples of how to actually test network latency. The content only describes what the skill supposedly does without providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, and no validation checkpoints for performing network latency testing. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative document with no references to detailed materials, no links to examples, and no structured navigation to additional resources. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
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 |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.