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
Quality
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 with minimal useful content. It names the skill and category but provides no concrete actions, no meaningful trigger terms (just a duplicate), and no guidance on when Claude should select this skill. The description fails to help Claude distinguish this skill from others or understand its capabilities.
Suggestions
Add specific actions the skill performs, e.g., 'Measures network latency, tests ping times, analyzes connection delays, and reports network performance metrics.'
Include a 'Use when...' clause with natural trigger terms like 'Use when the user asks about ping times, network speed, connection latency, response times, or network performance testing.'
Remove the duplicate trigger term and expand to include variations users would naturally say: 'ping', 'latency test', 'network delay', 'connection speed', 'response time'.
| 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 the 'when' guidance is just a duplicate trigger phrase. There is no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('network latency tester' repeated twice) and overly specific. Missing natural variations users would say like 'ping', 'latency', 'network speed', 'connection delay', 'response time', or 'network performance'. | 1 / 3 |
Distinctiveness Conflict Risk | The skill name 'Network Latency Tester' is somewhat specific to a niche (network performance), but the lack of concrete actions means it could overlap with other network or performance testing skills without clear differentiation. | 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 content is essentially an empty template with no actual instructional value. It contains only meta-descriptions of what a skill should do rather than any concrete guidance on network latency testing. There is no executable code, no specific tools mentioned (despite tags referencing k6 and jmeter), and no actionable workflows.
Suggestions
Add concrete code examples for network latency testing using specific tools like ping, traceroute, k6, or custom scripts with actual executable commands
Include a clear workflow with numbered steps: e.g., 1) Select target endpoints, 2) Run baseline test with specific command, 3) Analyze results, 4) Compare against thresholds
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific techniques for measuring latency (TCP handshake timing, DNS resolution, HTTP response times)
Add example output formats showing what latency test results look like and how to interpret them
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude already understands conceptually. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific tools, no examples of actual network latency testing. The content only describes what the skill claims to do without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps, no sequence, no validation checkpoints - just vague claims about 'step-by-step guidance' without actually providing any steps. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials. No references to external files, no organized sections with actual content, just empty placeholder sections. | 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
0c08951
- 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.