tracking-application-response-times

Track 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".

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/performance/response-time-tracker/skills/tracking-application-response-times/SKILL.md

Quality

Content

20%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body reads as a feature brochure rather than executable guidance: it explains performance concepts Claude already knows and gives abstract instructions with no code, commands, or links to the bundled analysis script. The strong description is undercut by a weak, non-actionable body.

Suggestions

Replace abstract Instructions with concrete, executable steps — e.g. invoke `python scripts/analyze_response_times.py <metrics_dir> --output report.txt` and show expected output, rather than "Configure monitoring" and "Collect response time metrics".

Cut the Overview, Integration, and Resources marketing prose ("empowers Claude to proactively monitor...", "APM tool documentation") to assume Claude's competence and respect the context budget.

Add validation/feedback-loop checkpoints to the workflow (verify metrics file exists, re-run analysis after a fix, compare P95 against SLO before reporting) and link the bundled analyze_response_times.py under a scripts section so progressive disclosure is actually wired.

Dimension	Reasoning	Score
Conciseness	The body is padded with marketing prose Claude does not need ("empowers Claude to proactively monitor and improve application performance") and generic Overview/Integration/Resources sections, with no executable content earning its tokens.	1 / 3
Actionability	Instructions are abstract ("Configure monitoring for API endpoints", "Collect response time metrics") with no concrete code or commands; the bundled analyze_response_times.py script is never referenced or invoked.	1 / 3
Workflow Clarity	Steps are listed (How It Works, Instructions) so a sequence exists, but they are vague and lack validation/verification checkpoints for a monitoring/analysis workflow, which caps clarity at 2.	2 / 3
Progressive Disclosure	Sections are organized, but the body never signals or links the bundled scripts/analyze_response_times.py file, and references/ and assets/ are empty stubs — structure is present but references are not wired in.	2 / 3
	Total	6 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong across all dimensions: it states concrete capabilities, supplies natural trigger phrases, covers both what and when, and occupies a distinct niche. It is concise and free of fluff.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions and targets — "Track and optimize application response times across API endpoints, database queries, and service calls" — matching the anchor that lists several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (track and optimize response times across named layers) and when ("Use when monitoring performance or identifying bottlenecks") with explicit triggers.	3 / 3
Trigger Term Quality	Provides natural user phrasing via "Trigger with phrases like 'track response times', 'monitor API performance', or 'analyze latency'", giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The response-time/performance-monitoring niche with specific trigger phrases is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/performance/response-time-tracker/skills/tracking-application-response-times/SKILL.md
Commit: 0540a62

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.