hx-redis-advisor

Guides Redis planning, deployment, and validation on HX-9 within HX architecture authority rules.

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/HX-Infratstructure/HX-Eco-System --skill hx-redis-advisor-hx-infratstructure
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hx-redis-advisor
Source: https://github.com/HX-Infratstructure/HX-Eco-System/tree/main/skills/redis/hx-redis-advisor
Command: npx skills add https://github.com/HX-Infratstructure/HX-Eco-System --skill hx-redis-advisor-hx-infratstructure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Applying generic Redis tutorials, vendor quickstarts, or cloud-first guidance to a governed infrastructure build often conflicts with established architecture decisions. This Skill keeps Redis work on HX-9 aligned with HX authority order, native systemd deployment standards, and the official smoke-test validation chain. ## Core Features & Use Cases - Authority-ordered Redis guidance: Reconciles official Redis documentation and the reviewed redis/agent-skills repository against HX control documents, classifying every recommendation as ACCEPT, ADAPT, REFERENCE_ONLY, REJECT_FOR_HX, or OWNER_DECISION_REQUIRED. - HX-9 deployment boundary enforcement: Covers native Ubuntu/systemd installation, shared-host memory sizing with PostgreSQL, persistence, eviction, key/TTL modeling, Search/vector/RAG, Streams, and the Redis MCP companion without allowing containers or cluster topologies by default. - Validation discipline: Enforces the B3 Redis core and B4 Redis MCP smoke-test proof chain, forbidding unexecuted PASS claims. - Use Case: When planning the HX-9 Redis build, an agent loads this Skill to verify the current upstream Redis release, classify upstream clustering or TLS advice against HX decisions, and confirm exactly which smoke tests prove the deployment. ## Quick Start Ask the agent to plan the HX-9 Redis installation and validation steps using the HX Redis Advisor before running any commands.

Frequently Asked Questions about hx-redis-advisor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy Redis on HX-9 in the HX Eco-System?▼

Deploy Redis natively on Ubuntu with systemd, following the HX-9 runbook once it exists. Establish host state, package source, and memory boundaries with PostgreSQL first, then prove the build with the B3 Redis smoke test and B4 Redis MCP test.

How does the skill handle official Redis Agent Skills guidance?▼

The reviewed redis/agent-skills repository is treated as subordinate vendor expertise. Each upstream skill is classified as ACCEPT, ADAPT, REFERENCE_ONLY, or REJECT_FOR_HX, so cloud-only, clustering, and hardening advice never overrides HX architecture decisions.

Can I use Docker or Redis Cluster for the HX-9 Redis deployment?▼

No. Containers are rejected unless the owner explicitly changes the native Linux standard, and Cluster, Sentinel, or replication topologies require an owner decision since they are outside the current HX BASE scope.

What smoke tests validate the HX-9 Redis build?▼

Validation follows the B3 and B4 chain. B3 proves PING, a bounded SET/GET of the exact smoke token, DELETE, and cleanup via the Redis smoke test; B4 then proves the Redis MCP companion after an accepted B3 PASS.

Is a Redis pipeline atomic when modeling data operations?▼

No. A pipeline only reduces round trips and is not inherently atomic. The skill requires distinguishing non-transactional pipelining from MULTI/EXEC transactions and Lua or Functions when correctness matters.

What are the limitations of this Redis advisory skill?▼

It never substitutes for a missing HX-9 runbook or server record, never selects runtime versions or security policies autonomously, and never reports PASS without executed smoke-test evidence. Unresolved architecture choices return OWNER_DECISION_REQUIRED.