Is caching-strategies safe to install?

SaferSkills independently audited caching-strategies (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

src/auto_skill_mcp/skill_data/caching-strategies/SKILL.md · 1 file

src/auto_skill_mcp/skill_data/caching-strategies/SKILL.md1.4 KB · Markdown

name: caching-strategies

description: Cache effectively — in-memory, distributed, HTTP caching — with proper invalidation.

metadata:

category: general

tags: [cache, performance, redis, memory, invalidation]

Caching Strategies

Cache Levels

Level	Storage	Speed	Use Case
L1 (in-memory)	Application RAM	<1ms	Hot data, repeated queries
L2 (distributed)	Redis/Memcached	1-5ms	Shared across instances
L3 (HTTP/CDN)	Browser/CDN	10-100ms	Static assets, API responses

Caching Patterns

Cache-aside: read from cache, miss → read DB → write to cache → return
Write-through: write to cache first, then DB
Write-behind: write to cache, async write to DB
Cache invalidation: the hardest problem — use TTLs, version keys, or event-driven purges

HTTP Caching

Use Cache-Control headers: public, private, max-age, no-cache, no-store
Use ETags for conditional requests
Set appropriate TTLs: static assets (1 year with hash in URL), API responses (seconds to minutes)

Rules

Cache the result of expensive operations (DB queries, API calls, computation)
Never cache sensitive data (PII, auth tokens)
Always set a TTL (even if long) — prevent stale data
Monitor cache hit rates — low hit rate means wrong cache strategy
Have a cache warming strategy for critical data

caching-strategies— agent skill

Is caching-strategies safe to install?

Caching Strategies

Cache Levels

Caching Patterns

HTTP Caching

Rules

Audit the pieces. Scan the whole. Decide.