Cache Layer

Cache layers, TTLs, invalidation, and consistency. Use when speeding reads or debugging stale data.

Security Scan

The skill is an instruction-only, workflow-oriented helper for caching (TTLs, invalidation, consistency) and its requirements and instructions are coherent with that purpose.

Purpose & Capability

Name and description match the SKILL.md content: it provides a staged workflow for cache design, implementation, and operation. There are no unrelated permissions, binaries, or env vars requested.

Instruction Scope

Runtime instructions are procedural guidance and questions for the user; they do not instruct the agent to read files, access credentials, call external endpoints, or perform broad system operations.

Install Mechanism

No install spec and no code files — instruction-only skill. Nothing is written to disk or downloaded during install.

Credentials

The skill requests no environment variables, credentials, or config paths; requested access is proportional (none) to the stated task.

Persistence & Privilege

always is false and the skill is user-invocable. It does not request permanent presence or elevated privileges beyond normal skill invocation.

Assessment

This skill is a pure guidance/workflow helper and appears safe and coherent with its purpose. Because it is instruction-only, it won't execute code or access secrets by itself — still: review any recommendations before applying them, avoid pasting secrets into prompts, and if you want to prevent autonomous invocation, disable model invocation for this skill in your agent settings.

Structured guidance for cache layers (TTLs, invalidation, consistency): confirm triggers, propose the stages below, and adapt if the user wants a lighter pass.

When to Offer This Workflow

Trigger conditions:

• User mentions caching, cache invalidation, or closely related work
• They want a structured workflow rather than ad-hoc tips
• They are preparing a review, rollout, or stakeholder communication

Initial offer: Explain the four stages briefly and ask whether to follow this workflow or work freeform. If they decline, continue in their preferred style.

Workflow Stages

Stage 1: Clarify context & goals

Anchor on what to cache and TTL rationale. Ask what success looks like, constraints, and what must not break. Capture unknowns early.

Stage 2: Design or plan the approach

Translate goals into a concrete plan around invalidation patterns. Compare alternatives and explicit trade-offs; avoid implicit assumptions.

Stage 3: Implement, validate, and harden

Execute with verification loops tied to consistency and thundering herds. Prefer small steps, measurable checks, and rollback points where risk is high.

Stage 4: Operate, communicate, and iterate

Close the loop with monitoring hit rate and staleness: monitoring, documentation, stakeholder updates, and lessons learned for the next cycle.

Checklist Before Completion

• Goals and constraints are explicit for cache layers
• Risks and trade-offs are stated, not hand-waved
• Verification steps match the change’s impact (tests, canary, peer review)
• Operational follow-through is covered (monitoring, docs, owners)

Tips for Effective Guidance

• Be procedural: stage-by-stage, with clear exit criteria
• Ask for missing context (environment, scale, deadlines) before prescribing
• Prefer checklists and concrete examples over generic platitudes
• If the user declines the workflow, switch to freeform help without lecturing

Handling Deviations

• If the user wants to skip a stage: confirm and continue with what they need.
• If context is missing: ask targeted questions before strong recommendations.
• Prefer concrete examples, trade-offs, and verification steps over generic advice.

Quality Bar

• Each recommendation should be actionable (what to do next).
• Call out failure modes relevant to cache layers (security, scale, UX, or ops).
• Keep tone direct and respectful of the user’s time.