[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PRHF8EKN2B14HPBPB5D18A":3,"skill-same:01M6PRHF8EKN2B14HPBPB5D18A":82},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":14,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6PRHF8EKN2B14HPBPB5D18A","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.","headmktlucca-ui\u002Fneuroads-lp","headmktlucca-ui","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F247379838?v=4","01M6PDVAV6M1W96D1SR1PDF8CS","NeuroAds","01M6PDVAZ4P281GNDKD45CYTF5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fredis-security\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"redis security","redis","security","connections","down","for","mode","users","network exposure","bind","control","Access Control","use","security guidance","Rules","access","tls","firewall","authentication","deployment","2026-11-10 10:12:30",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":44,"description":7},{"author":45,"version":46},"Redis, Inc.","0.1.0","main","7a940b8e5af16c95e5c190a524421d32fc7445a9",".claude\u002Fskills\u002Fredis-security","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui","https:\u002F\u002Fneuroads.com.br","2026-08-12 00:42:44",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add headmktlucca-ui\u002Fneuroads-lp --skill redis-security",{"tool":60,"command":61},"bunx","bunx skills add headmktlucca-ui\u002Fneuroads-lp --skill redis-security",{"tool":63,"command":64},"pnpm","pnpm dlx skills add headmktlucca-ui\u002Fneuroads-lp --skill redis-security","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fredis-security\u002FSKILL.md",true,[68,74,78],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Facls.md","REFERENCE","参考文档",862,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fredis-security\u002Freferences\u002Facls.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fauth.md",1650,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fredis-security\u002Freferences\u002Fauth.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fnetwork.md",902,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fredis-security\u002Freferences\u002Fnetwork.md",[83,108,132,158,176,211],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":97,"publishedAt":39},"01M6PTDCZTXTGSTX4RFK901YSZ","xunit-skill","Generates xUnit.net tests in C#. Covers Fact\u002FTheory, constructor injection, IClassFixture, and FluentAssertions. Use when user mentions \"xUnit\", \"[Fact]\", \"[Theory]\", \"Assert.Equal\", \"C# xUnit\". Triggers on: \"xUnit\", \"[Fact]\", \"[Theory]\", \"Assert.Equal C#\", \"xUnit.net\".","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fxunit-skill\u002FSKILL.md",[89,94],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":95,"categoryName":96,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000023","Skill与智能体开发",[98,99,100,101,102,31,103,104,105,106,107],"xunit","xunit skill","testing","injection","user","tests","triggers","unit","unit-testing","C#",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":116,"publishedAt":39},"01M6PTCB59ZTG5FTMWGPYEMMBP","xcuitest-skill","Generates XCUITest UI tests for iOS\u002FiPadOS apps in Swift. Apple's native testing framework for reliable, fast UI automation. Supports local simulators and TestMu AI cloud real devices. Use when user mentions \"XCUITest\", \"XCTest\", \"iOS UI test\", \"Swift test\", \"XCUIApplication\". Triggers on: \"XCUITest\", \"XCTest UI\", \"iOS UI test\", \"Swift UI test\", \"XCUIApplication\", \"TestMu\".","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fxcuitest-skill\u002FSKILL.md",[114,115],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},{"categoryNo":95,"categoryName":96,"taxonomyType":92,"taxonomyTypeDesc":93},[117,118,100,119,120,121,122,123,31,124,125,126,127,128,103,104,129,130,24,131],"xcuitest","xcuitest skill","automation","test","testing framework","ios","devices","mobile","mobile-testing","ui test","local","apple","apps","native","objective",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":142,"publishedAt":39},"01M6PTATMNTY9NF4J7KSR76YK6","world-builder","Create and manage generative game zones for Dorothy's Pokemon-style world. Use this skill when creating, updating, or designing game worlds via MCP tools.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fworld-builder\u002FSKILL.md",[138,141],{"categoryNo":139,"categoryName":140,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":95,"categoryName":96,"taxonomyType":92,"taxonomyTypeDesc":93},[143,144,145,146,147,148,149,150,31,151,152,153,154,155,156,24,157],"builder","world","world builder","MCP","create","mcp tools","Tools","game","pokemon","manage","style","via","theme","zone","generative",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":166,"publishedAt":39},"01M6PT9Z92JTSQEHE1QR0NNW5F","webdriverio-skill","Generates WebdriverIO (WDIO) automation tests in JavaScript or TypeScript. Supports local and TestMu AI cloud. Use when user mentions \"WebdriverIO\", \"WDIO\", \"wdio.conf\", \"browser.url\", \"$\", \"$$\". Triggers on: \"WebdriverIO\", \"WDIO\", \"wdio\", \"browser.$\".","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwebdriverio-skill\u002FSKILL.md",[164,165],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},{"categoryNo":95,"categoryName":96,"taxonomyType":92,"taxonomyTypeDesc":93},[167,100,168,119,169,170,171,172,102,31,173,127,103,104,174,175],"webdriverio skill","typescript","javascript","browser","cloud","e2e","e2e-testing","URL","conf",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":191,"publishedAt":39},"01M6PT9NVK36ZWCQ69YXK3FR4K","web-design-guidelines","Web platform design and accessibility guidelines. Use when building web interfaces, auditing accessibility, implementing responsive layouts, or reviewing web UI code. Triggers on tasks involving HTML, CSS, web components, WCAG compliance, responsive design, or web performance.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb\u002FSKILL.md",[182,185,186],{"categoryNo":183,"categoryName":184,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":139,"categoryName":140,"taxonomyType":92,"taxonomyTypeDesc":93},{"categoryNo":187,"categoryName":188,"taxonomyType":189,"taxonomyTypeDesc":190},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,104,210],"design","web","guidelines","web design guidelines","web design","css","performance","components","web components","tasks","code","web performance","ui","platform design","html","responsive design","responsive","platform","implementing",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":219,"publishedAt":39},"01M6PT9A3JKRE3X34276F2FW5R","watchos-design-guidelines","Apple Human Interface Guidelines for Apple Watch. Use when building watchOS apps, complications, or workout features. Triggers on tasks involving Watch UI, Digital Crown, glanceable interfaces, or wrist-based interactions.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwatchos\u002FSKILL.md",[217,218],{"categoryNo":139,"categoryName":140,"taxonomyType":92,"taxonomyTypeDesc":93},{"categoryNo":187,"categoryName":188,"taxonomyType":189,"taxonomyTypeDesc":190},[192,194,220,201,204,31,221,222,128,209,223,104,129,224,24,225,226],"watchos design guidelines","workout","human","watch","interface","platform-design","features"]