[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BYPF2WSHB031VDFQJ59NA2":3,"skill-same:01M6BYPF2WSHB031VDFQJ59NA2":67},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M6BYPF2WSHB031VDFQJ59NA2","openspec-apply-change",null,"Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.","Vortex375\u002Fseraph","Vortex375","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5016523?v=4","01M6BYMHA5FQE4EMD6BSZ13M46","Benjamin Schmitz","01M6BYMHEYGQ7DM3Q8A7KBNZ48",2,"MIT","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenspec-apply-change\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"change","openspec apply change","openspec","openspec apply","apply","cli","implement","tasks","start","continue","work","user","use","implementation","implementing","when","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":40,"description":41,"allowed-tools":42},"qdrant-scaling-data-volume","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'.",[43,44,45],"Read","Grep","Glob","main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd",".claude\u002Fskills\u002Fopenspec-apply-change",0,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph","https:\u002F\u002Fgithub.com\u002FVortex375","2026-11-08 18:46:14",{"source":8,"skillName":40,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add Vortex375\u002Fseraph --skill qdrant-scaling-data-volume",{"tool":59,"command":60},"bunx","bunx skills add Vortex375\u002Fseraph --skill qdrant-scaling-data-volume",{"tool":62,"command":63},"pnpm","pnpm dlx skills add Vortex375\u002Fseraph --skill qdrant-scaling-data-volume","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenspec-apply-change\u002FSKILL.md",true,[],[68,91,116,140,156,175],{"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":72,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":85,"publishedAt":35},"01M6BYS1QVW7F887EXS5RR34TA","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","AGPL-3.0","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[75,80],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[86,87,88,34,31,89,90],"writing","for","writing for agents","editing","documents",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":35},"01M6BYRZNREK0C7V6Y43AKDJWW","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fwizard\u002FSKILL.md",[],[93,98,99,100,101,102,103,104,34,105,106,87,107,108,109,110,111,112,31,113,114,115],"provisioning","ci","generate","infrastructure","dashboard","can","running","invoke","party","credentials","human","provisioning infrastructure","migration","up","only","interactive","Bash","secrets",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":35},"01M6BYRY92S448X31PTG25TCJC","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[118,123,124,125,103,126,127,128,129,130,131,132,133,134,135,29,136,137,138,139],"at","map","agent session","time","true","shared","more","tickets","as","clear","issue","session","one at a time","decision","plan","chunk","tracker",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":35},"01M6BYRWXMYWB6PD7E9PAD44M4","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[147,148,149,127,150,151,152,153,154,155],"wait what","wait","re","last","it","pitch","message","stop","land",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":35},"01M6BYRTS6JNDYB7BZVAWK7JJ9","triage","Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Ftriage\u002FSKILL.md",[],[158,163,164,165,166,167,168,169,170,171,172,173,127,174],"machine","roles","grill","ready","write","verify","issues","state","move","prs","state machine","briefs",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":35},"01M6BYRRRCDHNXH2YBDTYJPG36","to-tickets","Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[182,130,183,184,185,127,186,187,131,188,139,189,137,190,191],"to tickets","spec","links","break","native","ticket","conversation","text","SET","file"]