Individual skill
amazon-elasticache
Activate when developers have latent caching needs: slow API responses, database read bottlenecks, DynamoDB throttling or cost, RDS/Aurora scaling pressure, Bedrock latency or cost, or adding a cache; activate when working with Redis, Valkey, Memcached, or any in-memory data store, cache-aside patterns, session stores, rate limiting, leaderboards, counters, streams, queues, pub/sub, distributed locks, feature flags, shopping carts, or other caching strategies. Activate for GenAI and ML retrieval: vector similarity search for low-latency retrieval, semantic caching, RAG, LLM response caching, embedding stores, AI agent memory, recommendation, personalization. Activate for ElastiCache lifecycle: provisioning (serverless or node-based), engine selection, CloudFormation/CDK/Terraform IaC, VPC connectivity, TLS, RBAC, IAM auth, Global Datastore, monitoring, troubleshooting, cost optimization, and migration from self-managed Redis. Do not trigger for browser caches, CDN/CloudFront, HTTP Cache-Control, CPU caches.
skills/specialized-skills/database-skills/amazon-elasticache/SKILL.md
Source commit 1761e96813ebcbd43ed81d19e837219033f0afe5
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 3, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,434
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- data Derived category
- devops Derived category
- data-databases Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 18,180 bytesSKILL.mdcore · 18,180 bytesSKILL.mdcore · 18,180 bytesSKILL.mdcore · 18,180 bytesSKILL.mdcore · 18,180 bytesassets/examples/sample_commandstats.csvasset · 882 bytesassets/examples/sample_input_simple.csvasset · 449 bytesreferences/data-modeling/command-availability.mddoc · 6,216 bytesreferences/data-modeling/common-patterns.mddoc · 8,763 bytesreferences/data-modeling/instructions.mddoc · 10,140 bytesreferences/data-modeling/memcached-recipe.mddoc · 5,329 bytesreferences/data-modeling/recipe-gallery.mddoc · 8,388 bytesreferences/genai/agent-memory.mddoc · 6,040 bytesreferences/genai/elasticache-search.mddoc · 17,270 bytesreferences/genai/embedding-providers.mddoc · 8,814 bytesreferences/genai/framework-guide.mddoc · 5,048 bytesreferences/genai/instructions.mddoc · 9,890 bytesreferences/genai/rag-retrieval.mddoc · 9,527 bytesreferences/genai/semantic-cache.mddoc · 9,155 bytesreferences/genai/session-store.mddoc · 6,599 bytesreferences/migration/auth-migration.mddoc · 14,749 bytesreferences/migration/feature-comparison.mddoc · 11,199 bytesreferences/migration/global-datastore-operations.mddoc · 8,180 bytesreferences/migration/instructions.mddoc · 15,115 bytesreferences/migration/rollback-procedures.mddoc · 17,283 bytesreferences/migration/self-managed-migration.mddoc · 14,963 bytesreferences/migration/sizing-assessment.mddoc · 6,949 bytesreferences/migration/topology-validation.mddoc · 8,248 bytesreferences/migration/upgrade-patching.mddoc · 13,549 bytesreferences/migration/valkey-migration-guide.mddoc · 13,826 bytesreferences/monitoring/alarm-packs.mddoc · 8,645 bytesreferences/monitoring/big-key-hunter.mddoc · 6,920 bytesreferences/monitoring/client-tuning-and-diagnostics.mddoc · 12,107 bytesreferences/monitoring/cloudwatch-dashboards.mddoc · 7,915 bytesreferences/monitoring/cost-reporting.mddoc · 12,174 bytesreferences/monitoring/event-routing.mddoc · 9,726 bytesreferences/monitoring/hot-key-detection.mddoc · 11,015 bytesreferences/monitoring/instructions.mddoc · 9,012 bytesreferences/monitoring/key-space-distribution-by-prefix.mddoc · 6,981 bytesreferences/monitoring/log-delivery.mddoc · 8,064 bytesreferences/monitoring/slot-memory-imbalance-detection.mddoc · 6,816 bytesreferences/monitoring/slow-log-cross-signal-diagnosis.mddoc · 8,713 bytesreferences/monitoring/troubleshooting.mddoc · 18,291 bytesreferences/requirements/instructions.mddoc · 10,131 bytesreferences/setup/auth-model-selector.mddoc · 3,404 bytesreferences/setup/cluster-topology.mddoc · 3,712 bytesreferences/setup/connection-guide.mddoc · 6,530 bytesreferences/setup/connectivity-diagnostics.mddoc · 7,098 bytesreferences/setup/create-secure-cache.mddoc · 8,556 bytesreferences/setup/engine-selection.mddoc · 2,177 bytesreferences/setup/iac-best-practices.mddoc · 7,444 bytesreferences/setup/iac-reference.mddoc · 6,384 bytesreferences/setup/iam-policies.mddoc · 2,778 bytesreferences/setup/instructions.mddoc · 8,793 bytesreferences/setup/serverless-vs-node.mddoc · 12,992 bytesreferences/setup/service-quotas.mddoc · 3,014 bytesreferences/shared-foundation/architecture-diagrams.mddoc · 8,212 bytesreferences/shared-foundation/attribution.mddoc · 3,754 bytesreferences/shared-foundation/boundary-doc.mddoc · 5,055 bytesreferences/shared-runtime/api-gateway.mddoc · 5,546 bytesreferences/shared-runtime/ecs.mddoc · 7,653 bytesreferences/shared-runtime/eks.mddoc · 10,746 bytesreferences/shared-runtime/lambda.mddoc · 10,363 bytesreferences/shared-runtime/rds-acceleration.mddoc · 12,903 bytesreferences/shared-runtime/secret-injection.mddoc · 14,412 bytesreferences/shared-security/config-guardrails.mddoc · 8,158 bytesreferences/shared-security/encryption-defaults.mddoc · 4,283 bytesreferences/shared-security/vpc-patterns.mddoc · 2,889 bytesreferences/shared-ux/action-safety.mddoc · 10,085 bytesreferences/shared-ux/error-remediation.mddoc · 12,416 bytesreferences/shared-ux/production-readiness.mddoc · 5,593 bytesscripts/collect_metrics.shruns · 5,296 bytesscripts/command_classifier.pyruns · 6,381 bytesscripts/find_tunnel_host.pyruns · 7,375 bytesscripts/generate_dashboards.pyruns · 27,795 bytesscripts/input_validator.pyruns · 10,876 bytesscripts/migration_preflight.pyruns · 19,948 bytesscripts/price_calculator.pyruns · 14,744 bytesscripts/pricing.pyruns · 20,645 bytesscripts/security_audit.pyruns · 19,998 bytesscripts/serverless_estimator.pyruns · 29,076 bytesscripts/start_tunnel.pyruns · 11,954 bytesscripts/test_connection.pyruns · 13,606 bytesscripts/validate_references.pyruns · 10,850 bytes
Read excerpt
# ElastiCache
A modular ElastiCache toolkit organized as a registry of sub-skills. Each sub-skill handles one domain of ElastiCache work. The router below matches user intent to the right sub-skill, then loads only the references needed for that sub-skill.
## How this skill works
1. Match the user's request against the semantic categories in the registry below. Match on meaning, not exact wording ("help me figure out which data structures to use" matches `data-modeling` even without the word "pattern").
2. **Disambiguation:** If the user's intent matches multiple sub-skills, apply these rules in order:
- If `.elasticache/requirements.json` exists with `infrastructure.endpoint` set, prefer `monitoring` or `data-modeling` (the user has an existing cache).
- If no cache exists (no requirements.json or no endpoint), prefer `requirements`.
- If still ambiguous, ask one clarifying question: "Are you looking to set up something new, or troubleshoot something existing?"
3. Check the Guardrails section before recommending an engine or deployment model.
4. Read `references/{sub-skill-id}/instructions.md` for the matched sub-skill. If the file is not found at a relative path, check your prompt or environment for the skill directory absolute path and retry with `{skill-directory}/references/{sub-skill-id}/instructions.md`.
5. If the request spans multiple sub-skills, execute them in pipeline order.