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

29%

Does it follow best practices?

Impact

—

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

Content

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 generic boilerplate with no actionable, concrete guidance for cache optimization. It reads like a template that was never filled in with real content — there are no code examples, no specific configuration values, no tool commands, and no validation steps. Every section describes what the skill 'will do' in abstract terms rather than providing executable instructions Claude can follow.

Suggestions

Replace the abstract descriptions with concrete, executable code examples showing actual cache optimization patterns (e.g., Redis CONFIG SET, key naming conventions, TTL calculation logic).

Add specific validation steps such as commands to measure cache hit rates before and after optimization (e.g., `redis-cli INFO stats | grep keyspace`), creating a feedback loop.

Remove all boilerplate sections that add no value (Prerequisites, Instructions, Output, Error Handling, Resources, Integration) — these are generic filler that wastes tokens.

Provide concrete cache key design patterns with before/after examples showing how to improve hit rates, and specific TTL recommendations for common data access patterns.

Dimension	Reasoning	Score
Conciseness	The content is extremely verbose and padded with generic filler that Claude already knows. Sections like 'Overview', 'How It Works', 'When to Use', 'Integration', 'Prerequisites', 'Instructions', 'Output', 'Error Handling', and 'Resources' are all boilerplate with no substantive, skill-specific information. The entire file could be reduced to a fraction of its size.	1 / 3
Actionability	There is no concrete, executable guidance anywhere in the skill. No code examples, no specific commands, no actual TTL values, no cache key patterns, no configuration snippets. The 'Examples' section describes what the skill 'will do' in vague terms rather than showing how. Instructions like 'Invoke this skill when the trigger conditions are met' and 'Provide necessary context and parameters' are completely non-actionable.	1 / 3
Workflow Clarity	The multi-step processes described are vague and lack any validation checkpoints. Steps like 'Analyze the Redis configuration' and 'Recommend optimal TTL values' provide no concrete sequence, no specific tools or commands, and no feedback loops for verifying that optimizations actually improved performance.	1 / 3
Progressive Disclosure	The content is a monolithic wall of generic text with no references to external files and no meaningful structure. Multiple sections contain near-empty boilerplate ('The skill produces structured output relevant to the task') that adds no value. There are no bundle files to reference, but the content itself is poorly organized with redundant sections.	1 / 3
	Total	4 / 12 Passed

Description

59%

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 has a reasonable core covering caching-specific capabilities and includes explicit 'Use when' guidance, but suffers from overly generic trigger terms that would cause frequent false matches with other performance-related skills. The opening 'Execute this skill enables AI assistant' is unnecessary filler, and the use of third-person 'it' is acceptable but awkward. The biggest weakness is the conflict risk from broad triggers like 'optimize' and 'performance'.

Suggestions

Narrow the trigger terms to caching-specific phrases like 'cache hit rate', 'TTL', 'cache invalidation', 'Redis caching', 'cache key design', 'cache miss' instead of generic terms like 'optimize' and 'performance'.

Remove the filler opening 'Execute this skill enables AI assistant to' and start directly with the actions, e.g., 'Analyzes and improves application caching strategies...'

Add more specific file types, technologies, or scenarios (e.g., 'Redis', 'Memcached', 'CDN caching', 'HTTP cache headers') to improve distinctiveness and trigger accuracy.

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 the actions could be more concrete (e.g., what does 'analyze' or 'improve' actually produce?).	2 / 3
Completeness	The description answers both 'what does this do' (analyze and improve caching strategies, optimize hit rates, TTL, cache key design, invalidation) and 'when should Claude use it' with an explicit 'Use when' clause and trigger phrases. Both components are present and explicit.	3 / 3
Trigger Term Quality	Includes some relevant keywords like 'optimize', 'performance', 'speed up', 'cache', 'caching', and 'cache hit rates'. However, it misses common variations users might say such as 'caching layer', 'Redis', 'Memcached', 'cache miss', 'latency', or 'response time'. The triggers 'optimize' and 'performance' are overly generic and would match many unrelated skills.	2 / 3
Distinctiveness Conflict Risk	The trigger terms 'optimize', 'performance', and 'speed up' are extremely generic and would conflict with many other performance-related skills (database optimization, query optimization, frontend performance, etc.). While the description body mentions caching specifically, the trigger clause is far too broad.	1 / 3
	Total	8 / 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: 83ac5c7

Reviewed: 4 days 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.