valkey
Skill156 starsChanged 7 months agoApache-2.0View on GitHub
Guidance for Valkey-specific behavior. Use when changing Valkey connections, commands, dashboard data, metrics, key browser behavior, monitoring, cluster routing, response normalization, or unsupported capability handling.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- valkey-io/valkey-skillstheir own version, first seen Jul 4, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- valkey-io/valkey-skills★ 8same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when changing Valkey connection, command, dashboard, metrics, key-browser, monitoring, or cluster behavior.
- Distinctive: line 15
Treat unsupported commands and unavailable server capabilities as expected errors when they can happen in real deployments.
- Distinctive: line 16
Keep raw Valkey transport details out of React components.
- Distinctive: line 21
Do not reuse a response shape across domains just because the transport is the same.
- Distinctive: line 28
Prefer explicit route/address handling for per-node dashboard and metrics queries.
- Distinctive: line 30
Avoid fanout surprises: check whether a Glide command returns a string, record keyed by address, or key/value rows.
- Distinctive: line 36
Never log passwords, IAM tokens, credentials, connection strings with secrets, or raw secure-storage payloads.
- Distinctive: line 41
Add focused regression tests for parser changes, response normalization, cluster routing, and unsupported-command fallbacks.
- Very specific: line 43
Test undefined and null states separately when Valkey data can be absent or explicitly null.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Valkey Skill
Use this skill when changing Valkey connection, command, dashboard, metrics, key-browser, monitoring, or cluster behavior.
Client Behavior
- Distinguish standalone and cluster clients. Cluster calls may return fanout records or routed single-node responses.
- Route explicitly when querying a specific cluster node.
- Normalize Valkey command responses at backend, middleware, or parser boundaries before frontend components consume them.
- Treat unsupported commands and unavailable server capabilities as expected errors when they can happen in real deployments.
- Keep raw Valkey transport details out of React components.
Data Domains
- Dashboard info, memory metrics, CPU metrics, key browser data, command output, hot keys, slow logs, large replies, large requests, and monitor output are separate domains.
- Do not reuse a response shape across domains just because the transport is the same.
- Shared parsing/formatting logic that is useful across apps belongs in
common/. - Preserve useful command semantics, but expose typed domain-shaped data to UI and selectors.
Cluster Handling
- Be careful with node IDs, cluster IDs, connection IDs, and sanitized host keys. Do not treat them as interchangeable.
- Prefer explicit route/address handling for per-node dashboard and metrics queries.
- Account for cluster endpoint discovery versus direct node connections.
- Avoid fanout surprises: check whether a Glide command returns a string, record keyed by address, or key/value rows.
Errors And Logging
- Return expected Valkey/domain errors as values where practical, then pattern-match at the UX/retry/logging boundary.
- Throw only for programmer errors, impossible states, startup/config failures, or framework-required exception flows.
- Never log passwords, IAM tokens, credentials, connection strings with secrets, or raw secure-storage payloads.
- Redact connection details in errors and debug logs.
Testing
- Add focused regression tests for parser changes, response normalization, cluster routing, and unsupported-command fallbacks.
- Mock both standalone and cluster response shapes when behavior depends on the client type.
- Test
undefinedandnullstates separately when Valkey data can be absent or explicitly null.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.