tracking-application-response-times
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill tracking-application-response-timesTrack and optimize application response times across API endpoints, database queries, and service calls. Use when monitoring performance or identifying bottlenecks. Trigger with phrases like "track response times", "monitor API performance", or "analyze latency".
Validation
81%| Criteria | Description | Result |
|---|---|---|
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 |
Total | 13 / 16 Passed | |
Implementation
7%This skill is almost entirely descriptive rather than instructive. It explains what response time tracking conceptually involves but provides zero executable guidance - no code snippets, no specific commands, no tool configurations, no actual implementation details. The content reads like marketing copy rather than a technical skill that Claude can act upon.
Suggestions
Replace abstract descriptions with concrete, executable code examples showing how to actually track response times (e.g., specific APM tool commands, database query instrumentation code, metric collection scripts)
Add specific tool configurations and commands - if using a particular APM tool, show the exact setup; if using custom instrumentation, provide working code
Remove explanatory content Claude already knows (what percentiles are, generic best practices) and replace with project-specific configurations and thresholds
Add validation steps with concrete checks (e.g., 'Verify metrics are being collected: `curl localhost:9090/metrics | grep response_time`')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with unnecessary explanations Claude already knows (what response times are, what percentiles mean, generic best practices). Heavy padding with vague descriptions like 'empowers Claude to proactively monitor' and 'provides detailed metrics and insights' that add no actionable value. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance anywhere. Everything is abstract description ('Configure monitoring', 'Collect response time metrics') without showing HOW to do any of it. No actual implementation details, API calls, or tool usage examples. | 1 / 3 |
Workflow Clarity | Steps are vague and non-actionable ('Configure monitoring for API endpoints'). No validation checkpoints, no feedback loops for error recovery. The 'Instructions' section lists abstract goals rather than concrete steps with verification points. | 1 / 3 |
Progressive Disclosure | Content is organized into sections with headers, but it's a monolithic document with no references to external files. The structure exists but content that could be split (examples, error handling, resources) is all inline without clear navigation to detailed materials. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
100%This is an excellent skill description that hits all the marks. It provides specific capabilities across three technical domains, includes explicit trigger guidance with natural user phrases, and clearly defines both what the skill does and when to use it. The description is concise yet comprehensive, making it easy for Claude to select appropriately from a large skill set.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Track and optimize application response times across API endpoints, database queries, and service calls' - covers three distinct technical domains with clear actions. | 3 / 3 |
Completeness | Clearly answers both what (track/optimize response times across endpoints, queries, service calls) AND when (explicit 'Use when monitoring performance or identifying bottlenecks' plus 'Trigger with phrases' clause). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'track response times', 'monitor API performance', 'analyze latency', plus domain terms like 'API endpoints', 'database queries', 'bottlenecks', and 'performance'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on response time/latency monitoring with specific triggers that distinguish it from general monitoring, logging, or other performance skills. The combination of 'response times', 'latency', and 'API performance' creates a distinct profile. | 3 / 3 |
Total | 12 / 12 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.