> 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 res
curl "https://skillshub.wtf/jeremylongshore/claude-code-plugins-plus-skills/response-time-tracker?format=md"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
- Initiate Tracking: The user requests response time tracking.
- Configure Monitoring: The plugin automatically begins monitoring API endpoints, database queries, external service calls, frontend rendering, and background jobs.
- 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:
- Activate the response-time-tracker plugin.
- 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:
- Activate the response-time-tracker plugin.
- 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.
> related_skills --same-repo
> fathom-cost-tuning
Optimize Fathom API usage and plan selection. Trigger with phrases like "fathom cost", "fathom pricing", "fathom plan".
> fathom-core-workflow-b
Sync Fathom meeting data to CRM and build automated follow-up workflows. Use when integrating Fathom with Salesforce, HubSpot, or custom CRMs, or creating automated post-meeting email summaries. Trigger with phrases like "fathom crm sync", "fathom salesforce", "fathom follow-up", "fathom post-meeting workflow".
> fathom-core-workflow-a
Build a meeting analytics pipeline with Fathom transcripts and summaries. Use when extracting insights from meetings, building CRM sync, or creating automated meeting follow-up workflows. Trigger with phrases like "fathom analytics", "fathom meeting pipeline", "fathom transcript analysis", "fathom action items sync".
> fathom-common-errors
Diagnose and fix Fathom API errors including auth failures and missing data. Use when API calls fail, transcripts are empty, or webhooks are not firing. Trigger with phrases like "fathom error", "fathom not working", "fathom api failure", "fix fathom".