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.
36
3%
Does it follow best practices?
Impact
100%
1.04xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/10-performance-testing/network-latency-tester/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder that restates the skill name without providing any meaningful detail about capabilities, actions, or usage triggers. It lacks concrete verbs, natural user keywords, and explicit guidance on when Claude should select this skill. It would be nearly indistinguishable from other performance testing skills in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Measures network latency, runs ping and traceroute tests, monitors packet loss, and generates latency reports.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about network latency, ping times, response time, packet loss, network speed testing, or traceroute.'
Remove the duplicated trigger term and replace with diverse natural keywords users would actually say, such as 'ping', 'latency test', 'network delay', 'response time', 'jitter', 'network performance'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Network Latency Tester') but provides no concrete actions. There is no indication of what the skill actually does—no verbs describing specific capabilities like measuring latency, running ping tests, generating reports, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'when should Claude use it' clause. The 'Triggers on' line is just the skill name repeated, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'network latency tester' repeated twice. There are no natural keyword variations a user might say, such as 'ping', 'latency', 'network speed', 'response time', 'packet loss', 'traceroute', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Network Latency Tester' is somewhat specific to a niche (network latency testing), which provides some distinctiveness. However, without concrete actions or clear triggers, it could overlap with other network or performance testing skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no actual technical content. It contains only generic boilerplate descriptions that repeat the phrase 'network latency tester' without providing any actionable guidance, code examples, tool recommendations, or workflows for performing network latency testing. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples for network latency testing (e.g., using ping, traceroute, k6, or Python scripts with specific latency measurement patterns).
Define a clear multi-step workflow for conducting latency tests, including setup, execution, result collection, and validation/analysis steps.
Remove all boilerplate sections ('Purpose', 'When to Use', 'Example Triggers') that provide no technical value and replace with actionable content like tool configurations, threshold definitions, and output interpretation guidance.
Include specific tool recommendations with copy-paste ready commands or configurations (e.g., k6 scripts for HTTP latency testing, or iperf3 commands for network-level latency measurement).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific technical content, and every section restates the same vague idea about 'network latency tester' without any substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no tools, no configurations, no examples of actual network latency testing. Every bullet point is abstract and descriptive rather than instructive. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but delivers none. | 1 / 3 |
Progressive Disclosure | There are no references to external files, no bundle files, and the content is a monolithic block of generic placeholder text with no meaningful structure or navigation to deeper content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
3efb53b
- 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.