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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill response-time-analyzerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It relies entirely on the skill name without explaining capabilities, use cases, or natural trigger terms. The redundant trigger terms and lack of concrete actions make it nearly impossible for Claude to intelligently select this skill over alternatives.
Suggestions
Add specific capabilities: 'Measures API response times, analyzes latency percentiles (p50, p95, p99), identifies slow endpoints, generates performance reports'
Include a 'Use when...' clause with natural triggers: 'Use when the user mentions response times, latency issues, slow APIs, performance bottlenecks, or needs to benchmark endpoint speed'
Add varied trigger terms users would naturally say: 'latency', 'slow response', 'API performance', 'endpoint timing', 'performance metrics', 'load testing results'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Response Time Analyzer') without describing any concrete actions. There are no specific capabilities listed like 'measure latency', 'analyze percentiles', or 'generate performance reports'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is circular (triggers on its own name). There is no explicit 'Use when...' clause with meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('response time analyzer' listed twice) and overly specific to the skill name itself. Missing natural user terms like 'latency', 'slow response', 'performance metrics', 'API timing', or 'load testing'. | 1 / 3 |
Distinctiveness Conflict Risk | The 'Performance Testing' category provides some context, and 'response time' is somewhat specific. However, without concrete actions, it could overlap with other performance-related skills like load testers, APM tools, or general monitoring skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is an empty template that provides no actual value. It contains only generic placeholder text describing what a skill should do without any concrete guidance on response time analysis. Claude already knows everything stated here, making this skill entirely redundant.
Suggestions
Add concrete code examples for response time analysis using tools like k6 or JMeter (e.g., measuring percentiles, setting thresholds)
Include a clear workflow for analyzing response times: collect data → identify outliers → calculate percentiles → compare against baselines → report findings
Provide specific metrics to track (p50, p95, p99, mean, standard deviation) with example output formats
Add validation steps for determining if response times meet acceptable thresholds and how to diagnose failures
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about response time analysis. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific techniques for analyzing response times. The content only describes what the skill claims to do without actually teaching anything actionable. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps for how to actually analyze response times, no validation checkpoints, and no process to follow. | 1 / 3 |
Progressive Disclosure | The content is a shallow placeholder with no real structure. It mentions 'Related Skills' but provides no actual references to detailed documentation or examples. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.