> optimizing-cache-performance
Execute this skill enables AI assistant to analyze and improve application caching strategies. it optimizes cache hit rates, ttl configurations, cache key design, and invalidation strategies. use this skill when the user requests to "optimize cache performance"... Use when optimizing performance. Trigger with phrases like 'optimize', 'performance', or 'speed up'.
curl "https://skillshub.wtf/jeremylongshore/claude-code-plugins-plus-skills/optimizing-cache-performance?format=md"Cache Performance Optimizer
Analyze and optimize caching strategies for Redis, Memcached, and in-memory caches by tuning hit rates, TTL configurations, key design, and invalidation policies.
Overview
This skill empowers Claude to diagnose and resolve caching-related performance issues. It guides users through a comprehensive optimization process, ensuring efficient use of caching resources.
How It Works
- Identify Caching Implementation: Locates the caching implementation within the project (e.g., Redis, Memcached, in-memory caches).
- Analyze Cache Configuration: Examines the existing cache configuration, including TTL values, eviction policies, and key structures.
- Recommend Optimizations: Suggests improvements to cache hit rates, TTLs, key design, invalidation strategies, and memory usage.
When to Use This Skill
This skill activates when you need to:
- Improve application performance by optimizing caching mechanisms.
- Identify and resolve caching-related bottlenecks.
- Review and improve cache key design for better hit rates.
Examples
Example 1: Optimizing Redis Cache
User request: "Optimize Redis cache performance."
The skill will:
- Analyze the Redis configuration, including TTLs and memory usage.
- Recommend optimal TTL values based on data access patterns.
Example 2: Improving Cache Hit Rate
User request: "Improve cache hit rate in my application."
The skill will:
- Analyze cache key design and identify potential areas for improvement.
- Suggest more effective cache key structures to increase hit rates.
Best Practices
- TTL Management: Set appropriate TTL values to balance data freshness and cache hit rates.
- Key Design: Use consistent and well-structured cache keys for efficient retrieval.
- Invalidation Strategies: Implement proper cache invalidation strategies to avoid serving stale data.
Integration
This skill can integrate with code analysis tools to automatically identify caching implementations and configuration. It can also work with monitoring tools to track cache hit rates and performance metrics.
Prerequisites
- Appropriate file access permissions
- Required dependencies installed
Instructions
- Invoke this skill when the trigger conditions are met
- Provide necessary context and parameters
- Review the generated output
- Apply modifications as needed
Output
The skill produces structured output relevant to the task.
Error Handling
- Invalid input: Prompts for correction
- Missing dependencies: Lists required components
- Permission errors: Suggests remediation steps
Resources
- Project documentation
- Related skills and commands
> 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".