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.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「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