[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CTKTTPFDFE7QP7Q165Q9WB":3,"skill-same:01M7CTKTTPFDFE7QP7Q165Q9WB":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CTKTTPFDFE7QP7Q165Q9WB","redis-security",null,"Redis security guidance covering authentication (requirepass and ACL users), TLS, ACL-based least-privilege access control, restricting network exposure via bind and protected-mode, firewall rules, and disabling dangerous commands. Use when deploying Redis to production, defining ACL users for an application, configuring TLS connections, locking down a Redis instance behind a firewall, or auditing a Redis deployment for security hardening.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fredis-agent-skills\u002Fredis-security\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: redis-security\ndescription: Redis security guidance covering authentication (requirepass and ACL users), TLS, ACL-based least-privilege access control, restricting network exposure via bind and protected-mode, firewall rules, and disabling dangerous commands. Use when deploying Redis to production, defining ACL users for an application, configuring TLS connections, locking down a Redis instance behind a firewall, or auditing a Redis deployment for security hardening.\nlicense: MIT\nmetadata:\n  author: Redis, Inc.\n  version: \"0.1.0\"\n---\n\n# Redis Security\n\nProduction hardening for Redis: authentication, ACL-based access control, and network exposure. Cover all three together — any one of them on its own leaves an exploitable gap.\n\n## When to apply\n\n- Deploying or reviewing a Redis instance destined for production.\n- Setting up application credentials beyond a shared password.\n- Auditing a Redis deployment against a security checklist.\n- Receiving \"Redis exposed to the internet\" findings from a scanner.\n\n## 1. Always authenticate (and use TLS)\n\nNever run a production Redis without a password. Pair authentication with TLS so credentials and data aren't sent in clear text.\n\n```\n# redis.conf\nrequirepass your-strong-password\ntls-port 6380\ntls-cert-file \u002Fpath\u002Fto\u002Fredis.crt\ntls-key-file  \u002Fpath\u002Fto\u002Fredis.key\n```\n\n```python\nr = redis.Redis(\n    host=\"localhost\",\n    port=6380,\n    password=\"your-strong-password\",\n    ssl=True,\n    ssl_cert_reqs=\"required\",\n)\n```\n\nIf you can use ACL users (next section) instead of the single `requirepass`, do — `requirepass` is effectively the legacy \"default user\" shortcut.\n\nSee [references\u002Fauth.md](references\u002Fauth.md).\n\n## 2. ACLs for least-privilege access\n\nThe `default` user with a shared password is fine for development. For production, give each application a dedicated ACL user with only the commands and key patterns it actually needs.\n\n```\n# Cache-only reader\nACL SETUSER app_readonly on >password ~cache:* +get +mget +scan\n\n# Writer that can't run dangerous ops\nACL SETUSER app_writer   on >password ~*        +@all -@dangerous\n\n# Admin (use sparingly, never for application traffic)\nACL SETUSER admin        on >strong-password ~* +@all\n```\n\nUseful command categories:\n\n| Category | What it covers |\n|---|---|\n| `@read` | Read commands (`GET`, `MGET`, `HGET`, ...) |\n| `@write` | Write commands (`SET`, `DEL`, `XADD`, ...) |\n| `@dangerous` | `FLUSHALL`, `DEBUG`, `KEYS`, etc. |\n| `@admin` | Administrative commands |\n\nIf app credentials leak, a tight ACL bounds the blast radius — the attacker can't `FLUSHALL` your DB just because they grabbed a cache reader's password.\n\nSee [references\u002Facls.md](references\u002Facls.md).\n\n## 3. Restrict network access\n\nThe most common Redis breach is a public-internet Redis with no auth. Avoid that with three layers:\n\n```\n# redis.conf — bind to specific interfaces, keep protected-mode on\nbind 127.0.0.1 192.168.1.100\nprotected-mode yes\n```\n\n```bash\n# Firewall — allow only application subnets\niptables -A INPUT -p tcp --dport 6379 -s 192.168.1.0\u002F24 -j ACCEPT\niptables -A INPUT -p tcp --dport 6379 -j DROP\n```\n\nAnti-pattern: `bind 0.0.0.0` + `protected-mode no` — exposes Redis to the whole network without protection.\n\nOptional but recommended: rename or disable destructive commands so a compromised client can't trash the DB:\n\n```\nrename-command FLUSHALL \"\"\nrename-command DEBUG \"\"\nrename-command CONFIG \"\"\n```\n\nSee [references\u002Fnetwork.md](references\u002Fnetwork.md).\n\n## References\n\n- [Redis: Security](https:\u002F\u002Fredis.io\u002Fdocs\u002Flatest\u002Foperate\u002Foss_and_stack\u002Fmanagement\u002Fsecurity\u002F)\n- [Redis: ACL](https:\u002F\u002Fredis.io\u002Fdocs\u002Flatest\u002Foperate\u002Foss_and_stack\u002Fmanagement\u002Fsecurity\u002Facl\u002F)\n","# Redis Security\n\nProduction hardening for Redis: authentication, ACL-based access control, and network exposure. Cover all three together — any one of them on its own leaves an exploitable gap.\n\n## When to apply\n\n- Deploying or reviewing a Redis instance destined for production.\n- Setting up application credentials beyond a shared password.\n- Auditing a Redis deployment against a security checklist.\n- Receiving \"Redis exposed to the internet\" findings from a scanner.\n\n## 1. Always authenticate (and use TLS)\n\nNever run a production Redis without a password. Pair authentication with TLS so credentials and data aren't sent in clear text.\n\n```\n# redis.conf\nrequirepass your-strong-password\ntls-port 6380\ntls-cert-file \u002Fpath\u002Fto\u002Fredis.crt\ntls-key-file  \u002Fpath\u002Fto\u002Fredis.key\n```\n\n```python\nr = redis.Redis(\n    host=\"localhost\",\n    port=6380,\n    password=\"your-strong-password\",\n    ssl=True,\n    ssl_cert_reqs=\"required\",\n)\n```\n\nIf you can use ACL users (next section) instead of the single `requirepass`, do — `requirepass` is effectively the legacy \"default user\" shortcut.\n\nSee [references\u002Fauth.md](references\u002Fauth.md).\n\n## 2. ACLs for least-privilege access\n\nThe `default` user with a shared password is fine for development. For production, give each application a dedicated ACL user with only the commands and key patterns it actually needs.\n\n```\n# Cache-only reader\nACL SETUSER app_readonly on >password ~cache:* +get +mget +scan\n\n# Writer that can't run dangerous ops\nACL SETUSER app_writer   on >password ~*        +@all -@dangerous\n\n# Admin (use sparingly, never for application traffic)\nACL SETUSER admin        on >strong-password ~* +@all\n```\n\nUseful command categories:\n\n| Category | What it covers |\n|---|---|\n| `@read` | Read commands (`GET`, `MGET`, `HGET`, ...) |\n| `@write` | Write commands (`SET`, `DEL`, `XADD`, ...) |\n| `@dangerous` | `FLUSHALL`, `DEBUG`, `KEYS`, etc. |\n| `@admin` | Administrative commands |\n\nIf app credentials leak, a tight ACL bounds the blast radius — the attacker can't `FLUSHALL` your DB just because they grabbed a cache reader's password.\n\nSee [references\u002Facls.md](references\u002Facls.md).\n\n## 3. Restrict network access\n\nThe most common Redis breach is a public-internet Redis with no auth. Avoid that with three layers:\n\n```\n# redis.conf — bind to specific interfaces, keep protected-mode on\nbind 127.0.0.1 192.168.1.100\nprotected-mode yes\n```\n\n```bash\n# Firewall — allow only application subnets\niptables -A INPUT -p tcp --dport 6379 -s 192.168.1.0\u002F24 -j ACCEPT\niptables -A INPUT -p tcp --dport 6379 -j DROP\n```\n\nAnti-pattern: `bind 0.0.0.0` + `protected-mode no` — exposes Redis to the whole network without protection.\n\nOptional but recommended: rename or disable destructive commands so a compromised client can't trash the DB:\n\n```\nrename-command FLUSHALL \"\"\nrename-command DEBUG \"\"\nrename-command CONFIG \"\"\n```\n\nSee [references\u002Fnetwork.md](references\u002Fnetwork.md).\n\n## References\n\n- [Redis: Security](https:\u002F\u002Fredis.io\u002Fdocs\u002Flatest\u002Foperate\u002Foss_and_stack\u002Fmanagement\u002Fsecurity\u002F)\n- [Redis: ACL](https:\u002F\u002Fredis.io\u002Fdocs\u002Flatest\u002Foperate\u002Foss_and_stack\u002Fmanagement\u002Fsecurity\u002Facl\u002F)\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"Redis, Inc.","0.1.0","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fredis-agent-skills\u002Fredis-security",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill redis-security",{"tool":41,"command":42},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill redis-security",{"tool":44,"command":45},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill redis-security","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fredis-agent-skills\u002Fredis-security\u002FSkill.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"metadata.json","REFERENCE","参考文档",430,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fredis-agent-skills\u002Fredis-security\u002Fmetadata.json",[56,63,68,75,80,87],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":64,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":76,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":88,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]