跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 prompt-caching

Prompt Caching

LLM 提示的缓存策略,包括 Anthropic 提示

910 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

LLM 提示的缓存策略,包括 Anthropic 提示

何时用

页:1 使用具有稳定系统提示或上下文的 Claude API

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Prompt Caching、Capabilities、Prerequisites、Scope、Ecosystem、Primary_tools。 其中含规范建议的小节:边界情况。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Caching strategies for LLM prompts including Anthropic prompt

Prompt CachingCapabilitiesPrerequisitesScopeEcosystemPrimary_toolsPatternsAnthropic Prompt CachingResponse CachingCache Augmented Generation (CAG)Sharp EdgesCache miss causes latency spike with additional overhead

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
prompt-caching
description
Caching strategies for LLM prompts including Anthropic prompt
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「prompt-caching」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-a4753c4251f2cffa-%E5%BF%AB%E9%80%9F%E7%BC%93%E5%AD%98.html
请存为 .cursor/skills/prompt-caching/SKILL.md 或 .claude/skills/prompt-caching/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/sickn33/agentic-awesome-skills' --list

npx skills add 'https://github.com/sickn33/agentic-awesome-skills' --skill 'prompt-caching'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: prompt-caching description: Caching strategies for LLM prompts including Anthropic prompt caching, response caching, and CAG (Cache Augmented Generation) risk: none source: vibeship-spawner-skills (Apache 2.0) date_added: 2026-02-27 --- # Prompt Caching Caching strategies for LLM prompts including Anthropic prompt caching, response caching, and CAG (Cache Augmented Generation) ## Capabilities - prompt-cache - response-cache - kv-cache - cag-patterns - cache-invalidation ## Prerequisites - Knowledge: Caching fundamentals, LLM API usage, Hash functions - Skills_recommended: context-window-management ## Scope - Does_not_cover: CDN caching, Database query caching, Static asset caching - Boundaries: Focus is LLM-specific caching, Covers prompt and response caching ## Ecosystem ### Primary_tools - Anthropic Prompt Caching - Native prompt caching in Claude API - Redis - In-memory cache for responses (ioredis on servers; @upstash/redis over HTTP on serverless, see `upstash-redis`) - OpenAI Caching - Automatic caching in OpenAI API ## Patterns ### Anthropic Prompt Caching Use Claude's native prompt caching for repeated prefixes **When to use**: Using Claude API with stable system prompts or context import Anthropic from '@anthropic-ai/sdk'; const client = new Anthropic(); // Cache the stable parts of your prompt async function queryWithCaching(userQuery: string) { const response = await client.messages.create({ model: "claude-sonnet-4-20250514", max_tokens: 1024, system: [ { type: "text", text: LONG_SYSTEM_PROMPT, // Your detailed instructions cache_control: { type: "ephemeral" } // Cache this! }, { type: "text", text: KNOWLEDGE_BASE, // Large static context cache_control: { type: "ephemeral" } } ], messages: [ { role: "user", content: userQuery } // Dynamic part ] }); // Check cache usage console.log(`Cache read: ${response.usage.cache_read_input_tokens}`); console.log(`Cache write: ${response.usage.cache_creation_input_tokens}`); return response; } // Cost savings: 90% reduction on cached tokens // Latency savings: Up to 2x faster ### Response Caching Cache full LLM responses for identical or similar queries **When to use**: Same queries asked repeatedly import { createHash } from 'crypto'; import Redis from 'ioredis'; const redis = new Redis(process.env.REDIS_URL); // Serverless/edge alternative without a persistent connection: // import { Redis } from '@upstash/redis'; const redis = Redis.fromEnv(); // then use redis.set(key, value, { ex: ttl }) class ResponseCache { private ttl = 3600; // 1 hour default // Exact match caching async getCached(prompt: string): Promise { const key = this.hashPrompt(prompt); return await redis.get(`response:${key}`); } async setCached(prompt: string, response: string): Promise { const key = this.hashPrompt(prompt); await redis.set(`response:${key}`, response, 'EX', this.ttl); } private hashPrompt(prompt: string): string { return createHash('sha256').update(prompt).digest('hex'); } // Semantic similarity caching async getSemanticallySimilar( prompt: string, threshold: number = 0.95 ): Promise { const embedding = await embed(prompt); const similar = await this.vectorCache.search(embedding, 1); if (similar.length && similar[0].similarity > threshold) { return await redis.get(`response:${similar[0].id}`); } return null; } // Temperature-aware caching async getCachedWithParams( prompt: string, params: { temperature: number; model: string } ): Promise { // Only cache low-temperature responses if (params.temperature > 0.5) return null; const key = this.hashPrompt( `${prompt}|${params.model}|${params.temperature}` ); return await redis.get(`response:${key}`); } } ### Cache Augmented Generation (CAG) Pre-cache documents in prompt instead of RAG retrieval **When to use**: Document corpus is stable and fits in context // CAG: Pre-compute document context, cache in prompt // Better than RAG when: // - Documents are stable // - Total fits in context window // - Latency is critical class CAGSystem { private cachedContext: string | null = null; private lastUpdate: number = 0; async buildCachedContext(documents: Document[]): Promise { // Pre-process and format documents const formatted = documents.map(d => `## ${d.title}\n${d.content}` ).join('\n\n'); // Store with timestamp this.cachedContext = formatted; this.lastUpdate = Date.now(); } async query(userQuery: string): Promise { // Use cached context directly in prompt const response = await client.messages.create({ model: "claude-sonnet-4-20250514", max_tokens: 1024, system: [ { type: "text", text: "You are a helpful assistant with access to the following documentation.", cache_control: { type: "ephemeral" } }, { type: "text", text: this.cachedContext!, // Pre-cached docs cache_control: { type: "ephemeral" } } ], messages: [{ role: "user", content: userQuery }] }); return response.content[0].text; } // Periodic refresh async refreshIfNeeded(documents: Document[]): Promise { const stale = Date.now() - this.lastUpdate > 3600000; // 1 hour if (stale) { await this.buildCachedContext(documents); } } } // CAG vs RAG decision matrix: // | Factor | CAG Better | RAG Better | // |------------------|------------|------------| // | Corpus size | < 100K tokens | > 100K tokens | // | Update frequency | Low | High | // | Latency needs | Critical | Flexible | // | Query specificity| General | Specific | ## Sharp Edges ### Cache miss causes latency spike with additional overhead Severity: HIGH Situation: Slow response when cache miss, slower than no caching Symptoms: - Slow responses on cache miss - Cache hit rate below 50% - Higher latency than uncached Why this breaks: Cache check adds latency. Cache write adds more latency. Miss + overhead > no caching. Recommended fix: // Optimize for cache misses, not just hits class OptimizedCache { async queryWithCache(prompt: string): Promise { const cacheKey = this.hash(prompt); // Non-blocking cache check const cachedPromise = this.cache.get(cacheKey); const llmPromise = this.queryLLM(prompt); // Race: use cache if available before LLM returns const cached = await Promise.race([ cachedPromise, sleep(50).then(() => null) // 50ms cache timeout ]); if (cached) { // Cancel LLM request if possible return cached; } // Cache miss: continue with LLM const response = await llmPromise; // Async cache write (don't block response) this.cache.set(cacheKey, response).catch(console.error); return response; } } // Alternative: Probabilistic caching // Only cache if query matches known high-frequency patterns class SelectiveCache { private patterns: Map = new Map(); shouldCache(prompt: string): boolean { const pattern = this.extractPattern(prompt); const frequency = this.patterns.get(pattern) || 0; // Only cache high-frequency patterns return frequency > 10; } recordQuery(prompt: string): void { const pattern = this.extractPattern(prompt); this.patterns.set(pattern, (this.patterns.get(pattern) || 0) + 1); } } ### Cached responses become incorrect over time Severity: HIGH Situation: Users get outdated or wrong information from cache Symptoms: - Users report wrong information - Answers don't match current data - Complaints about outdated responses Why this breaks: Source data changed. No cache invalidation. Long TTLs for dynamic data. Recommended fix: // Implement proper cache invalidation class InvalidatingCache { // Version-based invalidation private cacheVersion = 1; getCacheKey(prompt: string): string { return `v${this.cacheVersion}:${this.hash(prompt)}`; } invalidateAll(): void { this.cacheVersion++; // Old keys automatically become orphaned } // Content-hash invalidation async setWithContentHash( key: string, response: string, sourceContent: string ): Promise { const contentHash = this.hash(sourceContent); await this.cache.set(key, { response, contentHash, timestamp: Date.now() }); } async getIfValid( key: string, currentSourceContent: string ): Promise { const cached = await this.cache.get(key); if (!cached) return null; // Check if source content changed const currentHash = this.hash(currentSourceContent); if (cached.contentHash !== currentHash) { await this.cache.delete(key); return null; } return cached.response; } // Event-based invalidation onSourceUpdate(sourceId: string): void { // Invalidate all caches that used this source this.invalidateByTag(`source:${sourceId}`); } } ### Prompt caching doesn't work due to prefix changes Severity: MEDIUM Situation: Cache misses despite similar prompts Symptoms: - Cache hit rate lower than expected - Cache creation tokens high, read low - Similar prompts not hitting cache Why this breaks: Anthropic caching requires exact prefix match. Timestamps or dynamic content in prefix. Different message order. Recommended fix: // Structure prompts for optimal caching class CacheOptimizedPrompts { // WRONG: Dynamic content in cached prefix buildPromptBad(query: string): SystemMessage[] { return [ { type: "text", text: `You are helpful. Current time: ${new Date()}`, // BREAKS CACHE! cache_control: { type: "ephemeral" } } ]; } // RIGHT: Static prefix, dynamic at end buildPromptGood(query: string): SystemMessage[] { return [ { type: "text", text: STATIC_SYSTEM_PROMPT, // Never changes cache_control: { type: "ephemeral" } }, { type: "text", text: STATIC_KNOWLEDGE_BASE, // Rarely changes cache_control: { type: "ephemeral" } } // Dynamic content goes in messages, NOT system ]; } // Prefix ordering matters buildWithConsistentOrder(components: string[]): SystemMessage[] { // Sort components for consistent ordering const sorted = [...components].sort(); return sorted.map((c, i) => ({ type: "text", text: c, cache_control: i === sorted.length - 1 ? { type: "ephemeral" } : undefined // Only cache the full prefix })); } } ## Validation Checks ### Caching High Temperature Responses Severity: WARNING Message: Caching with high temperature. Responses are non-deterministic. Fix action: Only cache responses with temperature <= 0.5 ### Cache Without TTL Severity: WARNING Message: Cache without TTL. May serve stale data indefinitely. Fix action: Set appropriate TTL based on data freshness requirements ### Dynamic Content in Cached Prefix Severity: WARNING Message: Dynamic content in cached prefix. Will cause cache misses. Fix action: Move dynamic content outside of cache_control blocks ### No Cache Metrics Severity: INFO Message: Cache without hit/miss tracking. Can't measure effectiveness. Fix action: Add cache hit/miss metrics and logging ## Collaboration ### Delegation Triggers - context window|token -> context-window-management (Need context optimization) - rag|retrieval -> rag-implementation (Need retrieval system) - memory -> conversation-memory (Need memory persistence) ### High-Performance LLM System Skills: prompt-caching, context-window-management, rag-implementation Workflow: ``` 1. Analyze query patterns 2. Implement prompt caching for stable prefixes 3. Add response caching for frequent queries 4. Consider CAG for stable document sets 5. Monitor and optimize hit rates ``` ## Related Skills Works well with: `context-window-management`, `rag-implementation`, `conversation-memory` ## When to Use - User mentions or implies: prompt caching - User mentions or implies: cache prompt - User mentions or implies: response cache - User mentions or implies: cag - User mentions or implies: cache augmented ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…