analyzing-network-latency
This skill enables Claude to analyze network latency and optimize request patterns within an application. It helps identify bottlenecks and suggest improvements for faster and more efficient network communication. Use this skill when the user asks to "analyze network latency", "optimize request patterns", or when facing performance issues related to network requests. It focuses on identifying serial requests that can be parallelized, opportunities for request batching, connection pooling improvements, timeout configuration adjustments, and DNS resolution enhancements. The skill provides concrete suggestions for reducing latency and improving overall network performance.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill analyzing-network-latency68
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
Discovery
100%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 is a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes natural trigger terms users would actually say, explicitly states when to use the skill, and carves out a distinct niche in network latency optimization. The description effectively balances comprehensiveness with clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'identifying serial requests that can be parallelized, opportunities for request batching, connection pooling improvements, timeout configuration adjustments, and DNS resolution enhancements.' | 3 / 3 |
Completeness | Clearly answers both what (analyze latency, identify bottlenecks, suggest improvements for specific areas) AND when with explicit 'Use this skill when...' clause containing quoted trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'analyze network latency', 'optimize request patterns', 'performance issues', 'network requests', 'latency', 'network performance' - good coverage of terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on network latency and request patterns - distinct from general performance optimization or other network skills through specific technical focus areas like connection pooling and DNS resolution. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content describes what network latency analysis is rather than instructing Claude how to perform it. It lacks executable code examples, specific tools or libraries to use, concrete analysis techniques, and measurable optimization patterns. The content reads more like a feature description than actionable guidance.
Suggestions
Add concrete code examples showing how to measure latency (e.g., using timing decorators, network profiling tools, or browser DevTools analysis)
Include specific patterns to look for with executable detection code (e.g., regex patterns for identifying serial await chains, code snippets for implementing connection pooling)
Replace abstract 'the skill will' descriptions with actual analysis commands or scripts Claude should run
Add validation steps showing how to measure improvement after applying optimizations (before/after latency comparisons)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what parallelization, connection pooling, and request batching are). The 'How It Works' and 'When to Use' sections repeat information from the description without adding actionable value. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. Examples describe what the skill 'will do' abstractly rather than showing actual analysis techniques, tools, or code patterns Claude should use. | 1 / 3 |
Workflow Clarity | Steps are listed (identify, analyze, suggest) but they're vague and lack validation checkpoints. No concrete methods for how to actually perform latency analysis or what tools/approaches to use. | 2 / 3 |
Progressive Disclosure | Content is organized into sections but everything is inline with no references to detailed materials. The 'Best Practices' section could be expanded into separate documentation, and there are no links to implementation guides or code examples. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.