caching
Diagnose Stale Data and Plan Cache Policies
Conflicting cache policies can delay updates and expose personalized content through shared caches. This skill guides HTTP freshness, revalidation, and invalidation decisions across cache layers.
使用我的智能体安装
将此请求复制给你的智能体，其中包含权威 Skill 页面和清单。
Review the Skillstore skill "caching" from https://skillstore.io/skills/shreyam1008-caching.md and its manifest at https://skillstore.io/api/skills/shreyam1008-caching/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智能体仍应展示其计划，并按安全策略请求必要确认。
Agent 可读资源
当 AI Agent、爬虫或脚本需要干净上下文，而不是读取完整页面时，请使用这些链接。
测试它
正在使用“caching”。 Our content-hashed JavaScript files change URLs on every release. How should we cache them?
预期结果:
- Use a one-year freshness window and immutable caching for content-hashed assets.
- Serve each changed asset under a new URL.
- Keep HTML freshness short or require revalidation so clients receive updated asset references.
正在使用“caching”。 Users still see old HTML after deployment. Which cache should we check?
预期结果:
- Inspect Cache-Control, ETag, Age, and CDN cache-hit headers on the HTML response.
- Check whether a service worker returns an older Cache Storage entry.
- Identify the stale layer before applying a CDN purge or service worker cache update.
正在使用“caching”。 Can we use the same shared cache policy for a public catalog and account details?
预期结果:
- Allow shared caching only for public, non-personalized catalog responses within acceptable freshness limits.
- Use private caching for suitable personalized responses and no-store for sensitive data.
- Apply explicit service worker exclusions and account cleanup because Cache Storage does not enforce HTTP no-store.
安全审计
安全All 21 static findings are false positives: Markdown formatting, documentation links, and a conceptual cache description do not establish execution or reconnaissance. The skill provides caching guidance and explicitly addresses sensitive data, shared caches, and service worker exclusions. No evidence found of prompt injection, credential exfiltration, or other intent-level security threats.
风险因素
分享与引用此报告
分享版本化评估报告、中性徽章、嵌入卡片和引用。Skillstore 只报告证据，不判断该 Skill 是否安全。
复制报告链接
https://skillstore.io/skills/shreyam1008-caching/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/shreyam1008-caching?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/shreyam1008-caching?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/shreyam1008-caching/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/shreyam1008-caching.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学术引用 (APA · BibTeX · CFF)
APA 引用
shreyam1008. (2026). caching security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/shreyam1008-caching/audits/1BibTeX 引用
@techreport{shreyam1008-shreyam1008-caching-2026,
author = {shreyam1008},
title = {caching security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/shreyam1008-caching/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "caching security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "shreyam1008"
date-released: "2026-10-02"
url: "https://skillstore.io/skills/shreyam1008-caching/audits/1"
identifiers:
- type: other
value: "skillstore:shreyam1008-caching:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 评分
评分依据 证据置信度: 中你能构建什么
Resolve stale releases
Investigate stale HTML and asset references across browser, service worker, and CDN caches after a deployment.
Protect personalized API responses
Separate public data from personalized or sensitive responses and choose appropriate cache storage and revalidation policies.
Plan CDN freshness and invalidation
Define shared-cache freshness windows and compare content versioning with purge strategies for deployment and data updates.
试试这些提示
Explain max-age, s-maxage, no-cache, and no-store for my [resource type]. Recommend a policy based on [freshness requirement] and [data sensitivity].
Review cache policies for [hashed assets], [HTML], and [API responses]. Use [current headers] to identify freshness, revalidation, and privacy issues.
Diagnose stale content after [deployment or mutation]. Use [response headers], [service worker behavior], and [CDN observations] to prioritize checks for each cache layer.
Design caching for [application] with [freshness limits] and [account boundaries]. Address hashed URLs, CDN invalidation, conditional requests, and service worker exclusions.
最佳实践
- Classify resources by URL stability, acceptable staleness, and data sensitivity before choosing cache directives.
- Use content-hashed asset URLs and keep HTML fresh enough to discover new versions.
- Inspect every relevant cache layer and explicitly exclude sensitive data from service worker storage.
避免
- Applying public shared-cache policies to personalized or sensitive responses.
- Treating no-cache as a prohibition on storage or assuming Cache Storage enforces no-store.
- Using immutable caching for changing resources whose URLs remain unchanged.
常见问题
Which AI tools support this skill?
Does this skill configure my CDN automatically?
What is the difference between no-cache and no-store?
When should I use immutable caching?
Does HTTP no-store prevent service worker Cache Storage entries?
Does this skill include complete TanStack Query or service worker workflows?
开发者详情
作者
shreyam1008许可证
MIT
Skillstore 修订
r1
版本提示
作者未声明版本。
引用
bbec03cf10354f3aaccd6dd24eda4ac9ceeceac5
维护新鲜度
2026/10/2
使用量
0 次下载 · 0 次浏览
文件结构
📄 SKILL.md