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.
Instalar con mi Agente
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
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.Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.
Recursos legibles por agentes
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Pruébalo
Usando "caching". Our content-hashed JavaScript files change URLs on every release. How should we cache them?
Resultado esperado:
- 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.
Usando "caching". Users still see old HTML after deployment. Which cache should we check?
Resultado esperado:
- 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.
Usando "caching". Can we use the same shared cache policy for a public catalog and account details?
Resultado esperado:
- 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.
Auditoría de seguridad
SeguroAll 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.
Factores de riesgo
⚙️ Comandos externos (19)
🌐 Acceso a red (1)
Compartir y citar este informe
Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.
Copiar enlace del informe
https://skillstore.io/skills/shreyam1008-caching/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/shreyam1008-caching?utm_source=security_passport_badge)Insignia 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>Tarjeta para insertar
<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>Citas académicas (APA · BibTeX · CFF)
Cita APA
shreyam1008. (2026). caching security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/shreyam1008-caching/audits/1Cita BibTeX
@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"
Puntuación de Skillstore
Por qué esta puntuación Confianza de la evidencia: MedioLo que puedes crear
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.
Prueba estos prompts
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.
Mejores prácticas
- 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.
Evitar
- 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.
Preguntas frecuentes
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?
Detalles del desarrollador
Autor
shreyam1008Licencia
MIT
Revisión de Skillstore
r1
Aviso de versión
El autor no declaró una versión.
Repositorio
https://github.com/shreyam1008/shre-skills/tree/ba9787f41c2fe1be1062eeb6322bc339a1026383/skills/cachingRef.
bbec03cf10354f3aaccd6dd24eda4ac9ceeceac5
Actualidad del mantenimiento
2/10/2026
Uso
0 descargas · 0 vistas
Estructura de archivos
📄 SKILL.md