[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CTKBA3ZEM3E4KPPVCMNAJB":3,"skill-same:01M7CTKBA3ZEM3E4KPPVCMNAJB":49},{"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},"01M7CTKBA3ZEM3E4KPPVCMNAJB","redis-core",null,"Core Redis modeling guidance — choose the right data structure (String, Hash, List, Set, Sorted Set, JSON, Stream, Vector Set) and use consistent colon-separated key names. Use when designing a Redis data model, caching objects, deciding between Hash and JSON, building counters, leaderboards, membership sets, or session stores, or when reviewing\u002Fcleaning up Redis key naming.","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-core\u002Fskills\u002Fredis-core\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: redis-core\ndescription: Core Redis modeling guidance — choose the right data structure (String, Hash, List, Set, Sorted Set, JSON, Stream, Vector Set) and use consistent colon-separated key names. Use when designing a Redis data model, caching objects, deciding between Hash and JSON, building counters, leaderboards, membership sets, or session stores, or when reviewing\u002Fcleaning up Redis key naming.\nlicense: MIT\nmetadata:\n  author: Redis, Inc.\n  version: \"0.1.0\"\n---\n\n# Redis Core\n\nFoundational guidance for modeling data in Redis. Covers data-type selection and key-name conventions — the two decisions that most directly drive memory, performance, and maintainability.\n\n## When to apply\n\n- Caching objects, sessions, or per-user state.\n- Counters, leaderboards, recent-items lists, unique-membership sets.\n- Reviewing or refactoring Redis key names.\n- Deciding between a Redis Hash and a JSON document for an entity.\n\n## 1. Choose the right data structure\n\nPick the type that matches the *access pattern*, not just the shape of the data.\n\n| Use case | Recommended type | Why |\n|---|---|---|\n| Simple values, counters | String | Atomic `INCR`\u002F`DECR`, `SET`\u002F`GET` |\n| Object with independently updated fields | Hash | Per-field reads\u002Fwrites, no whole-object rewrite |\n| Queue, recent-N items | List | O(1) push\u002Fpop at ends |\n| Unique items, membership checks | Set | O(1) `SADD`\u002F`SISMEMBER`\u002F`SCARD` |\n| Rankings, score-based ranges | Sorted Set | Score-ordered; `ZADD`\u002F`ZRANGE`\u002F`ZRANK` |\n| Nested \u002F hierarchical data | JSON | Path-level updates, nested arrays, RQE indexing |\n| Event log, fan-out messaging | Stream | Persistent, consumer groups |\n| Vector similarity | Vector Set | Native vector storage with HNSW |\n\n**Common anti-pattern:** stuffing a flat object into a serialized string. Updating one field means fetch + parse + mutate + rewrite. Use a Hash instead.\n\nSee [references\u002Fchoose-data-structure.md](references\u002Fchoose-data-structure.md) for full rationale and Python\u002FJava examples.\n\n## 2. Use consistent key names\n\nUse `colon-separated` segments with a stable hierarchy:\n\n```\n{entity}:{id}:{attribute}\nuser:1001:profile\nuser:1001:settings\norder:2024:items\nsession:abc123\narticle:987:likes\ngame:space-invaders:leaderboard\n```\n\nRules of thumb:\n\n- **Lowercase, colon-separated.** No spaces, no mixed casing (`User_1001_Profile` is bad).\n- **Keep keys short but readable** — keys live in memory and appear in every command.\n- **Don't use full URLs or long strings as keys.** Extract a short identifier, or use a hash digest of the URL.\n- **Prefix for multi-tenancy** (`tenant:42:user:7:cart`) so scans and ACLs can target a tenant cleanly.\n- **Be consistent.** Pick one convention per service and apply it across all keys.\n\nSee [references\u002Fkey-naming.md](references\u002Fkey-naming.md) for cleanup examples and edge cases.\n\n## References\n\n- [Redis: Choosing the right data type](https:\u002F\u002Fredis.io\u002Fdocs\u002Flatest\u002Fdevelop\u002Fdata-types\u002Fcompare-data-types\u002F)\n- [Redis: Keys](https:\u002F\u002Fredis.io\u002Fdocs\u002Flatest\u002Fdevelop\u002Fuse\u002Fkeyspace\u002F)\n","# Redis Core\n\nFoundational guidance for modeling data in Redis. Covers data-type selection and key-name conventions — the two decisions that most directly drive memory, performance, and maintainability.\n\n## When to apply\n\n- Caching objects, sessions, or per-user state.\n- Counters, leaderboards, recent-items lists, unique-membership sets.\n- Reviewing or refactoring Redis key names.\n- Deciding between a Redis Hash and a JSON document for an entity.\n\n## 1. Choose the right data structure\n\nPick the type that matches the *access pattern*, not just the shape of the data.\n\n| Use case | Recommended type | Why |\n|---|---|---|\n| Simple values, counters | String | Atomic `INCR`\u002F`DECR`, `SET`\u002F`GET` |\n| Object with independently updated fields | Hash | Per-field reads\u002Fwrites, no whole-object rewrite |\n| Queue, recent-N items | List | O(1) push\u002Fpop at ends |\n| Unique items, membership checks | Set | O(1) `SADD`\u002F`SISMEMBER`\u002F`SCARD` |\n| Rankings, score-based ranges | Sorted Set | Score-ordered; `ZADD`\u002F`ZRANGE`\u002F`ZRANK` |\n| Nested \u002F hierarchical data | JSON | Path-level updates, nested arrays, RQE indexing |\n| Event log, fan-out messaging | Stream | Persistent, consumer groups |\n| Vector similarity | Vector Set | Native vector storage with HNSW |\n\n**Common anti-pattern:** stuffing a flat object into a serialized string. Updating one field means fetch + parse + mutate + rewrite. Use a Hash instead.\n\nSee [references\u002Fchoose-data-structure.md](references\u002Fchoose-data-structure.md) for full rationale and Python\u002FJava examples.\n\n## 2. Use consistent key names\n\nUse `colon-separated` segments with a stable hierarchy:\n\n```\n{entity}:{id}:{attribute}\nuser:1001:profile\nuser:1001:settings\norder:2024:items\nsession:abc123\narticle:987:likes\ngame:space-invaders:leaderboard\n```\n\nRules of thumb:\n\n- **Lowercase, colon-separated.** No spaces, no mixed casing (`User_1001_Profile` is bad).\n- **Keep keys short but readable** — keys live in memory and appear in every command.\n- **Don't use full URLs or long strings as keys.** Extract a short identifier, or use a hash digest of the URL.\n- **Prefix for multi-tenancy** (`tenant:42:user:7:cart`) so scans and ACLs can target a tenant cleanly.\n- **Be consistent.** Pick one convention per service and apply it across all keys.\n\nSee [references\u002Fkey-naming.md](references\u002Fkey-naming.md) for cleanup examples and edge cases.\n\n## References\n\n- [Redis: Choosing the right data type](https:\u002F\u002Fredis.io\u002Fdocs\u002Flatest\u002Fdevelop\u002Fdata-types\u002Fcompare-data-types\u002F)\n- [Redis: Keys](https:\u002F\u002Fredis.io\u002Fdocs\u002Flatest\u002Fdevelop\u002Fuse\u002Fkeyspace\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-core\u002Fskills\u002Fredis-core",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-core",{"tool":41,"command":42},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill redis-core",{"tool":44,"command":45},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill redis-core","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fredis-agent-skills\u002Fredis-core\u002Fskills\u002Fredis-core\u002FSKILL.md",true,[],[50,57,62,69,74,81],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"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":58,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":70,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]