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'.

Quality

33%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/performance/cache-performance-optimizer/skills/optimizing-cache-performance/SKILL.md

Quality

Discovery

67%

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 covers caching-specific capabilities reasonably well and includes explicit trigger guidance, but suffers from overly broad trigger terms that would cause conflicts with other performance-related skills. The phrasing is awkward ('Execute this skill enables AI assistant') and uses third-person inconsistently, and the generic triggers like 'optimize' and 'performance' undermine its ability to be selected precisely.

Suggestions

Narrow trigger terms to caching-specific language: add terms like 'cache miss', 'TTL', 'Redis', 'Memcached', 'cache invalidation', 'cache eviction' and remove overly generic terms like 'optimize' and 'performance' that would conflict with other skills.

Remove the awkward preamble 'Execute this skill enables AI assistant' and rewrite in clean third-person voice, e.g., 'Analyzes and improves application caching strategies...'

Differentiate from general performance optimization skills by specifying the scope more precisely, e.g., 'Use when the user asks about cache hit rates, cache key design, TTL tuning, or cache invalidation — not for general application performance tuning.'

Dimension	Reasoning	Score
Specificity	Names the domain (caching strategies) and lists some specific actions like optimizing cache hit rates, TTL configurations, cache key design, and invalidation strategies. However, the description is somewhat padded with filler and doesn't clearly enumerate distinct concrete actions.	2 / 3
Completeness	Explicitly answers both 'what' (analyze and improve caching strategies, optimize hit rates, TTL, cache key design, invalidation) and 'when' (Use when optimizing performance, with explicit trigger phrases). Both components are present and stated.	3 / 3
Trigger Term Quality	Includes some relevant trigger terms like 'optimize', 'performance', 'speed up', and 'cache performance', but misses many natural variations users might say such as 'caching', 'cache miss', 'TTL', 'Redis', 'Memcached', 'cache invalidation', or 'slow response times'.	2 / 3
Distinctiveness Conflict Risk	The caching focus provides some distinctiveness, but the broad trigger terms 'optimize', 'performance', and 'speed up' would easily conflict with other performance-related skills (database optimization, code profiling, network optimization, etc.).	2 / 3
	Total	9 / 12 Passed

Implementation

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

This skill is almost entirely boilerplate with no actionable technical content. It describes what caching optimization is at a high level but provides zero concrete guidance — no Redis/Memcached commands, no example configurations, no TTL calculation strategies, no cache key design patterns, no invalidation code examples. Multiple sections are generic templates that add no value.

Suggestions

Replace vague descriptions with concrete, executable examples: show actual Redis CONFIG commands, specific TTL values for common patterns (e.g., session data: 30min, API responses: 5min), and real cache key design patterns (e.g., `user:{id}:profile` vs `user_profile_{id}`).

Add a concrete diagnostic workflow with validation steps: e.g., '1. Run `redis-cli INFO stats` to get hit/miss ratio. 2. If hit rate < 80%, analyze key patterns with `redis-cli --bigkeys`. 3. Check TTL distribution with `DEBUG OBJECT key`.'

Remove all boilerplate sections that provide no skill-specific value (Prerequisites, Instructions, Output, Error Handling, Resources, Integration) — these waste tokens on generic content Claude already knows.

Add specific code examples for common optimizations: cache-aside pattern implementation, write-through vs write-behind comparison code, and invalidation strategy implementations (event-driven, TTL-based, versioned keys).

Dimension	Reasoning	Score
Conciseness	Extremely verbose with sections that explain things Claude already knows ('This skill empowers Claude to...', 'How It Works' restates the obvious). Multiple boilerplate sections (Prerequisites, Instructions, Output, Error Handling, Resources) add no actionable value and waste tokens. The 'When to Use This Skill' section repeats the description.	1 / 3
Actionability	No concrete code, commands, configuration examples, or specific technical guidance anywhere. The examples describe what the skill 'will do' in vague terms rather than showing actual cache configurations, Redis commands, key design patterns, or TTL values. Best Practices are generic platitudes without executable specifics.	1 / 3
Workflow Clarity	The workflow steps are abstract descriptions ('Analyze cache configuration', 'Recommend optimizations') with no concrete sequence, validation checkpoints, or feedback loops. The 'Instructions' section is completely generic boilerplate ('Invoke this skill when trigger conditions are met') that provides zero workflow guidance.	1 / 3
Progressive Disclosure	No bundle files exist, yet the content is a monolithic wall of vague text with no references to external resources. The content that is present is poorly organized — multiple sections (Prerequisites, Instructions, Output, Error Handling, Resources) are generic filler that could be removed entirely rather than structured into separate files.	1 / 3
	Total	4 / 12 Passed

Validation

81%

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 — 9 / 11 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	9 / 11 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3a2d27d

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.