Skill

openrouter-caching-strategy

Implement response caching to reduce costs and latency. Use when dealing with repeated queries or high-volume scenarios. Trigger with phrases like 'openrouter cache', 'cache responses', 'openrouter caching', 'reduce api calls'.

From openrouter-pack

Install

Run in your terminal

npx claudepluginhub nickloveinvesting/nick-love-plugins --plugin openrouter-pack

Tool Access

This skill is limited to using the following tools:

ReadWriteEditGrep

Supporting Assets

View in Repository

references/cache-invalidation.md

references/caching-strategies.md

references/cost-savings-analysis.md

references/errors.md

references/examples.md

references/in-memory-caching.md

references/redis-caching.md

references/semantic-caching.md

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

evaluation-methodology

1 file

Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.

plugin-eval

32.9k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 20, 2026

Actions

View Source View Plugin View on GitHub View README

Instructions

Generate cache keys: Hash the model ID, messages array, and key parameters (temperature, max_tokens) into a deterministic cache key

Implement exact-match caching: Store responses keyed by the hash; return cached responses for identical requests (works best with temperature: 0)

Add TTL-based expiration: Set cache entries to expire after a configurable period (e.g., 1 hour for factual queries, 5 minutes for dynamic content)

Consider semantic caching: For fuzzy matching, use embedding similarity to find cached responses for semantically similar (but not identical) prompts

Track cache hit rates: Log cache hits vs misses to measure cost savings and tune your caching strategy

Error Handling

Error

Cause

Fix

Stale cached responses

TTL too long for dynamic content

Reduce TTL or add cache invalidation triggers

Cache key collisions

Hash function not including all relevant parameters

Include model, messages, temperature, max_tokens, and tools in the key

Memory pressure

In-memory cache growing unbounded

Set max cache size with LRU eviction; use Redis for large caches

See ${CLAUDE_SKILL_DIR}/references/errors.md for full error reference.

Openrouter Caching Strategy

Overview

This skill shows how to implement caching layers for OpenRouter responses to reduce costs, lower latency, and handle repeated queries efficiently.

Prerequisites

OpenRouter integration
Cache storage (in-memory, Redis, or filesystem)

Instructions

Generate cache keys: Hash the model ID, messages array, and key parameters (temperature, max_tokens) into a deterministic cache key
Implement exact-match caching: Store responses keyed by the hash; return cached responses for identical requests (works best with temperature: 0)
Add TTL-based expiration: Set cache entries to expire after a configurable period (e.g., 1 hour for factual queries, 5 minutes for dynamic content)
Consider semantic caching: For fuzzy matching, use embedding similarity to find cached responses for semantically similar (but not identical) prompts
Track cache hit rates: Log cache hits vs misses to measure cost savings and tune your caching strategy

Output

Cache hit rate metrics showing percentage of requests served from cache
Cost savings report comparing cached vs uncached request costs
Latency improvement measurements (cached responses return in <5ms vs 500ms+ for API calls)

Error Handling

Error	Cause	Fix
Stale cached responses	TTL too long for dynamic content	Reduce TTL or add cache invalidation triggers
Cache key collisions	Hash function not including all relevant parameters	Include model, messages, temperature, max_tokens, and tools in the key
Memory pressure	In-memory cache growing unbounded	Set max cache size with LRU eviction; use Redis for large caches

See ${CLAUDE_SKILL_DIR}/references/errors.md for full error reference.

Examples

See ${CLAUDE_SKILL_DIR}/references/examples.md for runnable code samples.

openrouter-caching-strategy

openrouter-caching-strategy

Openrouter Caching Strategy

Overview

Prerequisites

Instructions

Output

Error Handling

Examples

Resources

Openrouter Caching Strategy

Overview

Prerequisites

Instructions

Output

Error Handling

Examples

Resources