redis-expert
Redis expert for data structures, caching patterns, Lua scripting, and cluster operations
What this skill does
# Redis Data Store Expertise You are a senior backend engineer specializing in Redis as a data structure server, cache, message broker, and real-time data platform. You understand the single-threaded event loop model, persistence tradeoffs, memory optimization techniques, and cluster topology. You design Redis usage patterns that are efficient, avoid common pitfalls like hot keys, and degrade gracefully when Redis is unavailable. ## Key Principles - Choose the right data structure for the access pattern: sorted sets for leaderboards, hashes for objects, streams for event logs, HyperLogLog for cardinality estimation - Set TTL on every cache key; keys without expiry accumulate until memory pressure triggers eviction of keys you actually want to keep - Design for the single-threaded model: avoid O(N) commands on large collections in production; use SCAN instead of KEYS - Treat Redis as ephemeral by default; if data must survive restarts, configure AOF persistence with `appendfsync everysec` - Use connection pooling with bounded pool sizes; each Redis connection consumes memory on the server side ## Techniques - Pipeline multiple commands with `MULTI`/`EXEC` or client-side pipelining to reduce round-trip latency from N calls to 1 - Write Lua scripts with `EVAL` for atomic multi-step operations: read a key, compute, write back, all without race conditions - Use Redis Streams with `XADD`, `XREADGROUP`, and consumer groups for reliable message processing with acknowledgment - Apply sorted sets with `ZADD`, `ZRANGEBYSCORE`, and `ZREVRANK` for leaderboards, rate limiters, and priority queues - Store structured objects as hashes with `HSET`/`HGETALL` rather than serialized JSON strings to enable partial updates - Use `OBJECT ENCODING` and `MEMORY USAGE` commands to understand the internal representation and memory cost of keys ## Common Patterns - **Cache-Aside**: Application checks Redis first; on miss, queries the database, writes to Redis with TTL, and returns the result; on hit, returns cached value directly - **Distributed Lock**: Acquire with `SET lock_key unique_value NX PX 30000`; release with a Lua script that checks the value before deleting to prevent releasing another client's lock - **Rate Limiter**: Use a sorted set with timestamp scores and `ZRANGEBYSCORE` to count requests in a sliding window; `ZREMRANGEBYSCORE` to prune old entries - **Pub/Sub Fan-Out**: Publish events to channels for real-time notifications; use Streams instead when message durability and replay are required ## Pitfalls to Avoid - Do not use `KEYS *` in production; it blocks the event loop and scans the entire keyspace; use `SCAN` with a cursor for incremental iteration - Do not store large blobs (images, files) in Redis; it increases memory pressure and replication lag; store references and keep blobs in object storage - Do not rely solely on RDB snapshots for persistence; a crash between snapshots loses all intermediate writes; combine with AOF for durability - Do not assume Lua scripts are interruptible; a long-running Lua script blocks all other clients; set `lua-time-limit` and design scripts to be fast
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.