Tracking Application Response TimesSAFE

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: tracking-application-response-times
description: 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".
version: 1.22.0
allowed-tools: Read, Write, Edit, Grep, Glob, Bash(monitoring:*), Bash(metrics:*)
license: MIT
author: Jeremy Longshore <[email protected]>
tags:
- performance
- api
- database
- monitoring
compatibility: Designed for Claude Code
---
# Response Time Tracker

Track and analyze response times across API endpoints, database queries, and service calls with P50/P95/P99 percentile reporting and SLO compliance monitoring.

## Overview

This skill empowers Claude to proactively monitor and improve application performance by tracking response times across various layers. It provides detailed metrics and insights to identify and resolve performance bottlenecks.

## How It Works

1. **Initiate Tracking**: The user requests response time tracking.
2. **Configure Monitoring**: The plugin automatically begins monitoring API endpoints, database queries, external service calls, frontend rendering, and background jobs.
3. **Report Metrics**: The plugin generates reports including P50, P95, P99 percentiles, average, and maximum response times.

## When to Use This Skill

This skill activates when you need to:

- Identify performance bottlenecks in your application.
- Monitor service level objectives (SLOs) related to response times.
- Receive alerts about performance degradation.

## Examples

### Example 1: Diagnosing Slow API Endpoint

User request: "Track response times for the user authentication API endpoint."

The skill will:

1. Activate the response-time-tracker plugin.
2. Monitor the specified API endpoint and report response time metrics, highlighting potential bottlenecks.

### Example 2: Monitoring Database Query Performance

User request: "Monitor database query performance for the product catalog."

The skill will:

1. Activate the response-time-tracker plugin.
2. Track the execution time of database queries related to the product catalog and provide performance insights.

## Best Practices

- **Granularity**: Track response times at a granular level (e.g., individual API endpoints, specific database queries) for more precise insights.
- **Alerting**: Configure alerts for significant deviations from baseline performance to proactively address potential issues.
- **Contextualization**: Correlate response time data with other metrics (e.g., CPU usage, memory consumption) to identify root causes.

## Integration

This skill can be integrated with other monitoring and alerting tools to provide a comprehensive view of application performance. It can also be used in conjunction with optimization tools to automatically address identified bottlenecks.

## Prerequisites

- Access to application monitoring infrastructure
- Response time data collection in ${CLAUDE_SKILL_DIR}/metrics/response-times/
- APM tools or custom instrumentation
- Performance SLO definitions

## Instructions

1. Configure monitoring for API endpoints and database queries
2. Collect response time metrics (P50, P95, P99 percentiles)
3. Analyze trends and identify performance degradation
4. Compare against performance baselines and SLOs
5. Identify bottlenecks and root causes
6. Generate optimization recommendations

## Output

- Response time reports with percentile metrics
- Performance trend visualizations
- Bottleneck identification analysis
- SLO compliance status
- Optimization recommendations with priorities

## Error Handling

If response time tracking fails:

- Verify monitoring agent installation
- Check instrumentation configuration
- Validate metric export endpoints
- Ensure data storage availability
- Review sampling configuration

## Resources

- APM tool documentation
- Response time monitoring best practices
- Percentile-based SLO definitions
- Performance optimization guides

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.