[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE268FHYN3X9P4RY9ZT1TM":3,"skill-same:01M6AE268FHYN3X9P4RY9ZT1TM":77},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M6AE268FHYN3X9P4RY9ZT1TM","qdrant-scaling-data-volume",null,"Guides Qdrant data volume scaling decisions. Use when someone asks 'data doesn't fit on one node', 'too much data', 'need more storage', 'vertical or horizontal scaling', 'tenant scaling', 'time window rotation', or 'data growth exceeds capacity'.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41028,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fqdrant-scaling\u002Fscaling-data-volume\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"data","Qdrant","qdrant scaling","qdrant scaling data volume","volume","scaling","time","when","tenant","window","rotation","more","guides","fit","storage","use","growth","read","decisions","capacity","2026-11-10 10:12:30",false,"---\nname: qdrant-scaling-data-volume\ndescription: \"Guides Qdrant data volume scaling decisions. Use when someone asks 'data doesn't fit on one node', 'too much data', 'need more storage', 'vertical or horizontal scaling', 'tenant scaling', 'time window rotation', or 'data growth exceeds capacity'.\"\nallowed-tools:\n  - Read\n  - Grep\n  - Glob\n---\n\n# Scaling Data Volume\n\nThis document covers data volume scaling scenarios,\nwhere the total size of the dataset exceeds the capacity of a single node.\n\n## Tenant Scaling\n\nIf the use case is multi-tenant, meaning that each user only has access to a subset of the data,\nand we never need to query across all the data, then we can use multi-tenancy patterns to scale.\n\nThe recommended way is to use multi-tenant workloads with payload partitioning, per-tenant indexes, and tiered multitenancy.\n\nLearn more [Tenant Scaling](tenant-scaling\u002FSKILL.md)\n\n## Sliding Time Window\n\nSome use-cases are based on a sliding time window, where only the most recent data is relevant.\nFor example an index for social media posts, where only the last 6 months of data require fast search.\n\nLearn more [Sliding Time Window](sliding-time-window\u002FSKILL.md)\n\n## Global Search\n\nMost general use-cases require global search across all data.\nIn these situations, we might need to fall back to vertical scaling,\nand then horizontal scaling when we reach the limits of vertical scaling.\n\n\n### Vertical Scaling\n\nWhen data doesn't fit in a single node, the first approach is to scale the node itself — more RAM, better disk, quantization, mmap.\nExhaust vertical options before going horizontal, as horizontal scaling adds permanent operational complexity.\n\nLearn more [Vertical Scaling](vertical-scaling\u002FSKILL.md)\n\n### Horizontal Scaling\n\nWhen a single node can't hold the data even with quantization and mmap, distribute data across multiple nodes via sharding.\n\nLearn more [Horizontal Scaling](horizontal-scaling\u002FSKILL.md)\n","# Scaling Data Volume\n\nThis document covers data volume scaling scenarios,\nwhere the total size of the dataset exceeds the capacity of a single node.\n\n## Tenant Scaling\n\nIf the use case is multi-tenant, meaning that each user only has access to a subset of the data,\nand we never need to query across all the data, then we can use multi-tenancy patterns to scale.\n\nThe recommended way is to use multi-tenant workloads with payload partitioning, per-tenant indexes, and tiered multitenancy.\n\nLearn more [Tenant Scaling](tenant-scaling\u002FSKILL.md)\n\n## Sliding Time Window\n\nSome use-cases are based on a sliding time window, where only the most recent data is relevant.\nFor example an index for social media posts, where only the last 6 months of data require fast search.\n\nLearn more [Sliding Time Window](sliding-time-window\u002FSKILL.md)\n\n## Global Search\n\nMost general use-cases require global search across all data.\nIn these situations, we might need to fall back to vertical scaling,\nand then horizontal scaling when we reach the limits of vertical scaling.\n\n\n### Vertical Scaling\n\nWhen data doesn't fit in a single node, the first approach is to scale the node itself — more RAM, better disk, quantization, mmap.\nExhaust vertical options before going horizontal, as horizontal scaling adds permanent operational complexity.\n\nLearn more [Vertical Scaling](vertical-scaling\u002FSKILL.md)\n\n### Horizontal Scaling\n\nWhen a single node can't hold the data even with quantization and mmap, distribute data across multiple nodes via sharding.\n\nLearn more [Horizontal Scaling](horizontal-scaling\u002FSKILL.md)\n",{"name":5,"description":7,"allowed-tools":49},[50,51,52],"Read","Grep","Glob","main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fqdrant-scaling\u002Fscaling-data-volume",5335,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-11 11:59:04",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add github\u002Fawesome-copilot --skill qdrant-scaling-data-volume",{"tool":69,"command":70},"bunx","bunx skills add github\u002Fawesome-copilot --skill qdrant-scaling-data-volume",{"tool":72,"command":73},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill qdrant-scaling-data-volume","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fqdrant-scaling\u002Fscaling-data-volume\u002FSKILL.md",true,[],[78,110,138,166,200,217],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":92,"publishedAt":44},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[84,89],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":90,"categoryName":91,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000023","Skill与智能体开发",[93,94,95,96,97,31,98,99,41,100,101,102,103,104,105,106,39,107,108,109],"supabase","rls","supabase rls","supabase rls policies","project","review","change","write","security","isolation","tables","as","tests","prove","users","functions","with",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":117,"publishedAt":44},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[116],{"categoryNo":90,"categoryName":91,"taxonomyType":87,"taxonomyTypeDesc":88},[118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":148,"publishedAt":44},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[145],{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师",[149,150,151,152,153,154,124,97,155,156,157,158,159,160,161,39,162,163,164,165],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":170,"sourceHtmlUrl":171,"categories":172,"keywords":177,"publishedAt":44},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[173,176],{"categoryNo":174,"categoryName":175,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},[178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,31,193,194,195,196,197,124,198,199],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":204,"licenseFileUrl":205,"sourceHtmlUrl":206,"categories":207,"keywords":213,"publishedAt":44},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[208,209,212],{"categoryNo":174,"categoryName":175,"taxonomyType":87,"taxonomyTypeDesc":88},{"categoryNo":210,"categoryName":211,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":90,"categoryName":91,"taxonomyType":87,"taxonomyTypeDesc":88},[214,121,187,215,216],"resemble detect","https","identity",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":204,"licenseFileUrl":221,"sourceHtmlUrl":222,"categories":223,"keywords":228,"publishedAt":44},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[224,227],{"categoryNo":225,"categoryName":226,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":90,"categoryName":91,"taxonomyType":87,"taxonomyTypeDesc":88},[229,230,231,232,150,98,9,120,233,234,215,235,236,237,238,239,240,241,242,243,244,245,105,246,247,248,249],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]