[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PEKZD1AMDAB0WM56WT5SS4":3,"skill-same:01M6PEKZD1AMDAB0WM56WT5SS4":93},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M6PEKZD1AMDAB0WM56WT5SS4","modeling-nosql-data",null,"This skill enables Claude to design NoSQL data models. It activates when the user requests assistance with NoSQL database design, including schema creation, data modeling for MongoDB or DynamoDB, or defining document structures. Use this skill when the user mentions \"NoSQL data model\", \"design MongoDB schema\", \"create DynamoDB table\", or similar phrases related to NoSQL database architecture. It assists in understanding NoSQL modeling principles like embedding vs. referencing, access pattern optimization, and sharding key selection.","sandraschi\u002Fdocumentation-mcp","sandraschi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34750307?v=4","01M6C42H9WE5EC9CK3N5RGZP8S","Sandra Schipal","01M6PE1X2FZP8KR5GANPPFTHA8",2,"MIT","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fdatabase\u002Fnosql-data-modeler\u002Fskills\u002Fnosql-data-modeler\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"data","nosql","modeling","Modeling NoSQL Data","model","data model","for","embedding","creation","dynamodb","pattern","selection","design","table","access","mongodb","Optimization","database","create","architecture","2026-11-10 10:12:30",false,"---\nname: modeling-nosql-data\ndescription: |\n  This skill enables Claude to design NoSQL data models. It activates when the user requests assistance with NoSQL database design, including schema creation, data modeling for MongoDB or DynamoDB, or defining document structures. Use this skill when the user mentions \"NoSQL data model\", \"design MongoDB schema\", \"create DynamoDB table\", or similar phrases related to NoSQL database architecture. It assists in understanding NoSQL modeling principles like embedding vs. referencing, access pattern optimization, and sharding key selection.\n---\n\n## Overview\n\nThis skill facilitates the design of efficient NoSQL data models, providing guidance on schema creation, denormalization strategies, and query optimization for document and key-value databases. It helps users translate their data requirements into production-ready NoSQL implementations.\n\n## How It Works\n\n1. **Identify Database Type**: Determines the target NoSQL database (e.g., MongoDB, DynamoDB).\n2. **Analyze Data Requirements**: Understands the data entities, attributes, and relationships.\n3. **Design Data Model**: Creates a NoSQL data model based on the identified database type and data requirements, considering embedding vs. referencing and access patterns.\n4. **Suggest Schema Definition**: Provides a schema definition or table structure based on the designed data model.\n\n## When to Use This Skill\n\nThis skill activates when you need to:\n- Design a new NoSQL database schema.\n- Optimize an existing NoSQL data model for performance.\n- Translate relational data models to NoSQL.\n- Choose appropriate sharding keys for a NoSQL database.\n- Generate MongoDB or DynamoDB schema definitions.\n\n## Examples\n\n### Example 1: Designing a MongoDB Schema for an E-commerce Application\n\nUser request: \"Design a MongoDB schema for an e-commerce application, focusing on products and customers.\"\n\nThe skill will:\n1. Analyze the data requirements for products and customers, considering attributes like product name, price, description, customer ID, name, and address.\n2. Design a MongoDB schema with embedded product reviews and customer order history, optimizing for common query patterns.\n\n### Example 2: Creating a DynamoDB Table for a Social Media Platform\n\nUser request: \"Create a DynamoDB table for storing social media posts, considering high read and write throughput.\"\n\nThe skill will:\n1. Analyze the data requirements for social media posts, considering attributes like user ID, timestamp, content, and likes.\n2. Design a DynamoDB table with appropriate primary and secondary indexes for efficient querying based on user ID and timestamp.\n\n## Best Practices\n\n- **Denormalization**: Embed related data when reads are more frequent than writes.\n- **Access Patterns**: Optimize the data model for the most common query patterns.\n- **Sharding**: Choose sharding keys that distribute data evenly across shards.\n\n## Integration\n\nThis skill can be integrated with other plugins for generating code based on the designed data model, such as generating MongoDB queries or DynamoDB API calls.\n","## Overview\n\nThis skill facilitates the design of efficient NoSQL data models, providing guidance on schema creation, denormalization strategies, and query optimization for document and key-value databases. It helps users translate their data requirements into production-ready NoSQL implementations.\n\n## How It Works\n\n1. **Identify Database Type**: Determines the target NoSQL database (e.g., MongoDB, DynamoDB).\n2. **Analyze Data Requirements**: Understands the data entities, attributes, and relationships.\n3. **Design Data Model**: Creates a NoSQL data model based on the identified database type and data requirements, considering embedding vs. referencing and access patterns.\n4. **Suggest Schema Definition**: Provides a schema definition or table structure based on the designed data model.\n\n## When to Use This Skill\n\nThis skill activates when you need to:\n- Design a new NoSQL database schema.\n- Optimize an existing NoSQL data model for performance.\n- Translate relational data models to NoSQL.\n- Choose appropriate sharding keys for a NoSQL database.\n- Generate MongoDB or DynamoDB schema definitions.\n\n## Examples\n\n### Example 1: Designing a MongoDB Schema for an E-commerce Application\n\nUser request: \"Design a MongoDB schema for an e-commerce application, focusing on products and customers.\"\n\nThe skill will:\n1. Analyze the data requirements for products and customers, considering attributes like product name, price, description, customer ID, name, and address.\n2. Design a MongoDB schema with embedded product reviews and customer order history, optimizing for common query patterns.\n\n### Example 2: Creating a DynamoDB Table for a Social Media Platform\n\nUser request: \"Create a DynamoDB table for storing social media posts, considering high read and write throughput.\"\n\nThe skill will:\n1. Analyze the data requirements for social media posts, considering attributes like user ID, timestamp, content, and likes.\n2. Design a DynamoDB table with appropriate primary and secondary indexes for efficient querying based on user ID and timestamp.\n\n## Best Practices\n\n- **Denormalization**: Embed related data when reads are more frequent than writes.\n- **Access Patterns**: Optimize the data model for the most common query patterns.\n- **Sharding**: Choose sharding keys that distribute data evenly across shards.\n\n## Integration\n\nThis skill can be integrated with other plugins for generating code based on the designed data model, such as generating MongoDB queries or DynamoDB API calls.\n",{"name":5,"description":7},"master","be156301b65e301887f327d08190ed4f17ba08d2","docs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fdatabase\u002Fnosql-data-modeler\u002Fskills\u002Fnosql-data-modeler",0,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp","https:\u002F\u002Fgithub.com\u002Fsandraschi","2026-11-09 11:03:27",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add sandraschi\u002Fdocumentation-mcp --skill modeling-nosql-data",{"tool":67,"command":68},"bunx","bunx skills add sandraschi\u002Fdocumentation-mcp --skill modeling-nosql-data",{"tool":70,"command":71},"pnpm","pnpm dlx skills add sandraschi\u002Fdocumentation-mcp --skill modeling-nosql-data","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fdatabase\u002Fnosql-data-modeler\u002Fskills\u002Fnosql-data-modeler\u002FSKILL.md",true,[75,81,87],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"assets\u002FREADME.md","ASSET","资产文件",320,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fdatabase\u002Fnosql-data-modeler\u002Fskills\u002Fnosql-data-modeler\u002Fassets\u002FREADME.md",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002FREADME.md","REFERENCE","参考文档",451,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fdatabase\u002Fnosql-data-modeler\u002Fskills\u002Fnosql-data-modeler\u002Freferences\u002FREADME.md",{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002FREADME.md","SCRIPT","脚本",367,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fdatabase\u002Fnosql-data-modeler\u002Fskills\u002Fnosql-data-modeler\u002Fscripts\u002FREADME.md",[94,117,143,153,177,203],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":104,"publishedAt":49},"01M6PFAWAHEJJCKKVNXEWNK87W","Docs Research","Use MCP Central Docs server to search, ask, and retrieve documentation (FastMCP, standards, packaging).","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fsrc\u002Fdocs_mcp\u002Fskills\u002Fdocs-research\u002FSKILL.md",[100,103],{"categoryNo":101,"categoryName":102,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[105,106,107,108,109,110,111,112,113,114,115,116],"docs research","docs","research","standards","use","packaging","ask","server","search","fastmcp","documentation","MCP",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":49},"01M6PFAN4DAENMY574Q7Q3CB3H","wrappee-drift","Read-only, single-repo audit of a repo's tool coverage against the software it wraps (its current real API\u002Fdocs, not training-data memory) and against comparable\u002Fcompeting wrappers. Trigger when the user says \"wrappee drift\" followed by a repo name, \"capability audit\" followed by a repo name, or asks whether a repo is missing features the wrapped software or a competitor now has. Always scoped to one named repo per invocation -- never trigger this fleet-wide or unprompted; that is explicitly against the SOP. Do NOT trigger for internal fleet-standard compliance (that is drift-scan) or strategic worth\u002Farchive decisions (that is quality-check) -- this is specifically about the gap between the repo's tool list and the wrapped software's\u002Fcompetitors' actual current capabilities.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwrappee-drift\u002FSKILL.md",[],[124,125,126,29,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142],"drift","wrappee drift","api","audit","capabilities","training","memory","features","repo audit","competitors","fleet","now","software","tool list","only","never","coverage","list","read",{"skillNo":144,"name":145,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":152,"publishedAt":49},"01M6PFADA3X031SK3W3T6X0N6H","modules","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwindsurf-mcp-standards\u002Fmodules\u002FSKILL.md",[148,151],{"categoryNo":149,"categoryName":150,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[145],{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":163,"publishedAt":49},"01M6PFA8YA029N68TW0X31FB1W","mcp-standards","Use when developing MCP servers to access comprehensive standards for scaffolding, packaging, sampling, documentation, testing, error handling, monitoring, and CI\u002FCD workflows.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwindsurf-mcp-standards\u002FSKILL.md",[159,162],{"categoryNo":160,"categoryName":161,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[164,116,108,109,165,166,167,168,169,170,35,171,43,172,173,174,115,175,176,110],"mcp standards","monitoring","sampling","scaffolding","servers","cd","error","CI\u002FCD","ci","mcp servers","error handling","workflows","testing",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":185,"publishedAt":49},"01M6PFA1XX344WX57B0DJZY94Q","webapp-cua-test","Run the pre-Tauri CUA click-through test (real browser, dev stack, OCR \"Connected\" wait, sidebar nav walk) for a fleet MCP server repo under D:\\Dev\\repos. Trigger when the user says \"cua webapp test\" or \"webapp clickthrough\" followed by a repo name, asks for an e2e click-through of a webapp, or asks whether a webapp boots and connects in a real browser. Not for the installed NSIS app (that is the nsis-build skill \u002F cua-nsis-test) and not for DOM assertions (Playwright), and not for hunting fake data or dead buttons (fakefind).","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwebapp-cua-test\u002FSKILL.md",[183,184],{"categoryNo":160,"categoryName":161,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[186,187,188,189,190,116,191,192,193,35,194,195,196,197,198,199,200,201,112,202],"webapp","test","webapp cua test","playwright","mcp server","dev","dom","assertions","trigger","click","app","tauri","repo","stack","e2e","ocr","browser",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":210,"publishedAt":49},"01M6PF9WYF6NWJR7WVN38TT0WH","ship","Final release gate for a fleet MCP server repo under D:\\Dev\\repos -- run all quality gates, build the release artifact, verify it, commit, push, and cut a GitHub release. Trigger this whenever the user says \"ship it\", \"ship\" followed by a repo name, \"release\" followed by a repo name, or asks to finalize and publish work that's already been done in a repo. This is the terminal step after assfix\u002Fnsis-build, not a substitute for them -- if the repo hasn't been assessed recently, say so before shipping rather than shipping blind.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fship\u002FSKILL.md",[209],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[205,198,35,194,211,212,213,214,215,216,217,112,218,191,219,220,221,190,222,116],"gates","ship it","artifact","done","say","work","publish","push","shipping","quality gates","commit","github"]