huiferhuifer/CloudSaver/skills/redis-audit/SKILL.md

redis-audit

Skill2 starsChanged 5 months agoApache-2.0View on GitHub

Redis cost optimization expert. Analyzes memory usage, connection management, command patterns, hot keys, and provides optimization strategies. Trigger when user mentions Redis costs, memory optimization, or Redis audit.

In this repository8 other files it gives its agents.
- cloudflare-auditSkill
- cost-audit-masterSkill
- cost-monitorSkill
- d1-cost-optimizerSkill
- index-optimizerSkill
- query-rewriterSkill
- spend-cap-managerSkill
- supabase-auditSkill

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Check connection count and timeout settings.
line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Redis Cost Optimization Expert

Cost Factors

Factor	Impact	Optimization
Memory	Primary cost	Compression, TTLs
Connections	Resource usage	Pooling
Commands	CPU usage	Batching, pipelines
Network	Egress	Compression

Audit Workflow

Step 1: Check Memory Usage

redis-cli INFO memory

Analyze fragmentation, peak memory, and eviction stats. See cases/memory-optimization.md for optimization.

Step 2: Monitor Connections

redis-cli INFO clients

Check connection count and timeout settings. See cases/connection-optimization.md for pooling strategies.

Step 3: Identify Hot Keys

redis-cli --hotkeys

Find keys with disproportionate access patterns. See cases/hot-key-optimization.md for sharding strategies.

Step 4: Analyze Slow Commands

redis-cli SLOWLOG GET 10

Identify expensive operations and optimize queries.

Matching Cases

Problem	Case File	Solution
High memory	`cases/memory-optimization.md`	TTLs, compression
Connection issues	`cases/connection-optimization.md`	Pooling
Hot keys	`cases/hot-key-optimization.md`	Sharding

Benchmark Reference

Optimization	Before	After	Improvement
Memory compression	1GB	300MB	70%
Connection pooling	500 conns	50 conns	90%
Key sharding	100K ops/key	10K ops/key	90%

Output Format

## Redis Cost Audit Report

### 1. Current Usage
- Memory: X MB / X MB (X%)
- Connections: X / X (X%)
- Commands/sec: X
- Hit rate: X%

### 2. Performance Issues
- Slow commands: X
- Hot keys: X
- Memory fragmentation: X

### 3. Recommendations (by priority)
1. [P0] Apply case: <case-name> → Expected improvement: XX%

### 4. Cost Projection
- Current: $X/month
- After optimization: $X/month
- Savings: $X/month (XX%)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free