response-time-analyzer
Response Time Analyzer - Auto-activating skill for Performance Testing. Triggers on: response time analyzer, response time analyzer Part of the Performance Testing skill category.
36
Quality
3%
Does it follow best practices?
Impact
100%
1.00xAverage 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/response-time-analyzer/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 provides almost no useful information for skill selection. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The repetitive trigger terms and absence of a 'Use when...' clause make it nearly impossible for Claude to appropriately select this skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Measures API response times, identifies latency bottlenecks, generates performance reports, compares baseline metrics'
Include a 'Use when...' clause with natural trigger terms like 'Use when analyzing response times, measuring latency, performance testing APIs, identifying slow endpoints, or benchmarking service speed'
Remove the redundant duplicate trigger term and expand to include variations users would naturally say: 'latency analysis', 'slow response', 'API performance', 'timing metrics'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Response Time Analyzer') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of measuring, analyzing, reporting, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. The 'Triggers on' section is not a proper 'Use when...' clause and only repeats the skill name. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'response time analyzer' repeated twice, which is redundant and unlikely to match natural user language. Missing common variations like 'latency', 'performance metrics', 'slow response', 'API timing', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Response Time Analyzer' and 'Performance Testing' provide some domain specificity, the lack of concrete actions means it could overlap with other performance-related skills. The category mention helps slightly but isn't sufficient for 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 is a hollow template with no actual content about response time analysis. It contains only meta-descriptions of what a skill should do without any concrete guidance, code examples, tool usage, or actionable instructions for analyzing response times in performance testing contexts.
Suggestions
Add concrete code examples for measuring response times (e.g., k6 scripts, JMeter configurations, or custom timing code)
Include specific metrics to capture (p50, p95, p99 latencies) and how to interpret them
Provide a clear workflow: collect data -> analyze -> identify bottlenecks -> report findings
Add example output formats showing what a response time analysis report should contain
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. It explains what the skill does in abstract terms without any concrete information about response time analysis. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The content only describes capabilities in vague terms like 'provides step-by-step guidance' without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for analyzing response times. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed materials, no examples, no actual content to organize. The sections are empty placeholders. | 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.