tracking-application-response-times
This skill enables Claude to track and optimize application response times. It uses the response-time-tracker plugin to monitor API endpoints, database queries, external service calls, frontend rendering, and background job execution. The plugin calculates P50, P95, and P99 percentiles, average and maximum response times. Use this skill when you need to identify performance bottlenecks, monitor SLOs, or receive alerts about performance degradation. Trigger this skill with phrases like "track response times", "optimize latency", or "monitor application performance".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill tracking-application-response-times66
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 capabilities (monitoring various application components, calculating percentile metrics), clear use cases (identifying bottlenecks, monitoring SLOs, performance alerts), and explicit trigger phrases. The description uses proper third-person voice and maintains a clear, focused scope on response time tracking.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'monitor API endpoints, database queries, external service calls, frontend rendering, and background job execution' and 'calculates P50, P95, and P99 percentiles, average and maximum response times.' | 3 / 3 |
Completeness | Clearly answers both what ('track and optimize application response times', monitoring various components, calculating percentiles) AND when ('when you need to identify performance bottlenecks, monitor SLOs, or receive alerts') with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'track response times', 'optimize latency', 'monitor application performance', plus technical terms like 'P50, P95, P99', 'SLOs', and 'performance bottlenecks' that users in this domain would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on response time tracking and performance monitoring with distinct triggers like 'response times', 'latency', 'P50/P95/P99 percentiles', and 'SLOs' that are unlikely to conflict with general monitoring or other performance skills. | 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 is overly verbose and lacks actionable guidance. It describes what the plugin does conceptually but provides no concrete syntax, configuration examples, or actual commands to invoke the response-time-tracker plugin. The examples are abstract descriptions rather than executable demonstrations.
Suggestions
Add concrete plugin invocation syntax showing exactly how to call the response-time-tracker plugin with specific parameters
Include an example of actual output format (JSON schema or sample metrics report) so Claude knows what to expect
Remove explanatory content about what response times and percentiles are - Claude already knows this
Replace abstract 'the skill will' descriptions with actual code/command examples that are copy-paste ready
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what response times are, what percentiles mean, generic best practices). Phrases like 'empowers Claude' and 'proactively monitor' add no value. The entire document could be reduced to a fraction of its size. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples. The examples describe what 'the skill will' do in abstract terms rather than showing actual plugin invocation syntax, configuration options, or output formats. Nothing is copy-paste ready. | 1 / 3 |
Workflow Clarity | Steps are listed (Initiate, Configure, Report) but lack specifics on how to actually invoke the plugin, what parameters to pass, or how to interpret/validate results. No validation checkpoints or error handling guidance. | 2 / 3 |
Progressive Disclosure | Content is organized into sections but everything is inline in one file. For a skill of this complexity, the structure is acceptable, but the content itself is padded rather than appropriately split between overview and detailed reference. | 2 / 3 |
Total | 6 / 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 | |
- 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.