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".
43
44%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/performance/network-latency-analyzer/skills/analyzing-network-latency/SKILL.mdQuality
Discovery
89%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 solid description with strong completeness and trigger term coverage, explicitly stating both what the skill does and when to use it with natural trigger phrases. The main weakness is that the capability description could be more specific about concrete actions performed (e.g., measuring latency, batching requests, caching strategies) rather than staying at a somewhat abstract level.
Suggestions
Add more specific concrete actions to improve specificity, e.g., 'Measures round-trip times, identifies bottlenecks, batches API requests, and implements retry strategies for faster communication.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (network latency, request patterns) and some actions (analyze, optimize), but doesn't list multiple concrete specific actions. 'Analyze network latency' and 'optimize request patterns' are somewhat vague—it doesn't specify what concrete techniques or outputs are involved (e.g., measure round-trip times, batch API requests, implement connection pooling). | 2 / 3 |
Completeness | Clearly answers both 'what' (analyze network latency and optimize request patterns) and 'when' (diagnosing slow network performance, optimizing API calls) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would say: 'analyze network latency', 'optimize API calls', 'reduce network delays', 'slow network performance'. These cover common variations of how users would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | The focus on network latency and request pattern optimization is a clear niche. The specific trigger terms ('network latency', 'API calls', 'network delays') are distinct and unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 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 almost entirely abstract description with no actionable, executable content. It explains what network latency analysis is and describes what the skill 'will do' rather than providing concrete instructions, code examples, or specific commands Claude can execute. The content is heavily padded with redundant sections that restate the same high-level concepts.
Suggestions
Replace abstract descriptions with concrete, executable code examples (e.g., Python scripts using aiohttp for parallel requests, connection pooling with requests.Session, actual curl/traceroute commands for diagnosis).
Consolidate redundant sections (Overview, How It Works, When to Use, Examples) into a single concise workflow with specific commands and validation checkpoints at each step.
Add concrete before/after code examples showing specific optimizations (e.g., converting serial requests to asyncio.gather, implementing request batching with actual code).
Remove sections that describe concepts Claude already knows (what connection pooling is, what batching means) and replace with specific implementation patterns and tool-specific commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and padded with unnecessary context. The 'Overview' restates the title, 'How It Works' describes abstract steps Claude already knows, 'When to Use' repeats the description, and 'Examples' describe what the skill 'will do' rather than providing concrete guidance. Multiple sections (Resources, Integration, Output) add no actionable value. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples anywhere. Everything is abstract description ('identify all network requests', 'analyze the latency') with no specific tools, scripts, code snippets, or copy-paste-ready commands. The examples describe what the skill 'will do' rather than showing how to actually do it. | 1 / 3 |
Workflow Clarity | The 'Instructions' section lists steps but they are vague and lack any validation checkpoints, feedback loops, or concrete commands. Steps like 'Identify all network requests' and 'Measure latency for each request type' provide no specifics on how to accomplish them. No error recovery or verification steps are integrated into the workflow. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no bundle files and no references to external resources. Content is poorly organized with redundant sections (Overview, How It Works, When to Use, Examples all overlap significantly). The 'Resources' section lists topics but provides no actual links or file references. | 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
6e9558f
- 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.