optimizing-cache-performance

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill 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'.

43%

Overall

Validation — 81%

Implementation — 7%

Activation — 67%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata' field is not a dictionary	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Implementation

This skill content is almost entirely generic boilerplate with no actionable guidance. It describes what cache optimization involves at a high level but provides zero concrete code, commands, configuration examples, or specific techniques. Claude already knows what caching is and what TTLs are - this skill adds no new knowledge or executable instructions.

Suggestions

Replace abstract descriptions with concrete code examples showing how to analyze Redis/Memcached configurations (e.g., `redis-cli INFO stats` output parsing, specific config file locations to check)

Add executable commands or scripts for measuring cache hit rates and identifying problematic keys (e.g., `redis-cli --stat`, memory analysis commands)

Provide specific TTL recommendations with rationale (e.g., 'session data: 30min, user profiles: 1hr, static config: 24hr') rather than generic 'set appropriate TTL values'

Remove all generic sections (Prerequisites, Instructions, Output, Error Handling, Resources) that contain no skill-specific content

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive padding explaining what the skill does rather than how to do it. Sections like 'Overview', 'How It Works', 'When to Use', 'Integration', 'Prerequisites', 'Instructions', 'Output', 'Error Handling', and 'Resources' are generic boilerplate that add no actionable value.	1 / 3
Actionability	No concrete code, commands, or executable guidance provided. Examples describe what 'the skill will' do abstractly rather than showing actual commands, configuration snippets, or analysis techniques Claude should use.	1 / 3
Workflow Clarity	No clear sequence of steps with validation checkpoints. The 'How It Works' section lists vague phases without specific commands, tools, or verification steps. No feedback loops for error recovery.	1 / 3
Progressive Disclosure	Content is organized into sections with headers, but it's a monolithic document with no references to external files. The structure exists but contains mostly filler content that doesn't warrant the organization.	2 / 3
	Total	5 / 12 Passed

Activation

67%

The description adequately covers caching optimization with explicit trigger guidance, but suffers from overly broad trigger terms that could cause conflicts with other performance skills. The capabilities listed are somewhat abstract rather than concrete actions, and the description uses awkward phrasing ('Execute this skill enables AI assistant') that reduces clarity.

Suggestions

Make trigger terms more cache-specific: add 'caching', 'cache miss', 'TTL', 'redis', 'memcached' and remove overly generic terms like 'optimize' and 'performance' that would conflict with other skills.

Rewrite opening to use proper third person voice: 'Analyzes and improves application caching strategies' instead of 'Execute this skill enables AI assistant to analyze'.

Add more concrete actions: 'audit cache hit/miss ratios', 'recommend TTL values', 'design cache key schemas' instead of abstract concepts.

Dimension	Reasoning	Score
Specificity	Names the domain (caching) and lists some actions (optimize cache hit rates, TTL configurations, cache key design, invalidation strategies), but these are somewhat abstract concepts rather than concrete executable actions like 'analyze cache metrics' or 'generate TTL recommendations'.	2 / 3
Completeness	Explicitly answers both what (analyze and improve caching strategies, optimize hit rates, TTL, key design, invalidation) and when (Use when optimizing performance, trigger phrases provided), meeting the requirement for explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes some relevant keywords ('optimize', 'performance', 'speed up', 'cache performance') but misses common variations users might say like 'caching', 'slow', 'latency', 'redis', 'memcached', or 'cache miss'.	2 / 3
Distinctiveness Conflict Risk	The generic triggers 'optimize', 'performance', and 'speed up' could easily conflict with other performance-related skills (database optimization, code profiling, etc.). The caching-specific terms help but the broad triggers create overlap risk.	2 / 3
	Total	9 / 12 Passed

Reviewed

16 days ago

Table of Contents

Validation Implementation Activation

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.