[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BYNKZMA3SN45FG8SD09QSP":3,"skill-same:01M6BYNKZMA3SN45FG8SD09QSP":65},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M6BYNKZMA3SN45FG8SD09QSP","resolving-merge-conflicts",null,"Use when you need to resolve an in-progress git merge\u002Frebase conflict.","Vortex375\u002Fseraph","Vortex375","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5016523?v=4","01M6BYMHA5FQE4EMD6BSZ13M46","Benjamin Schmitz","01M6BYMHEYGQ7DM3Q8A7KBNZ48",2,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fresolving-merge-conflicts\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"resolving merge conflicts","merge","merge conflicts","conflicts","git merge","git","rebase","use","conflict","progress","you","when","2026-11-10 10:12:30",false,"---\nname: qdrant-deployment-options\ndescription: \"Guides Qdrant deployment selection. Use when someone asks 'how to deploy Qdrant', 'Docker vs Cloud', 'local mode', 'embedded Qdrant', 'Qdrant EDGE', 'which deployment option', 'self-hosted vs cloud', or 'need lowest latency deployment'. Also use when choosing between deployment types for a new project.\"\n---\n\n# Which Qdrant Deployment Do I Need?\n\nStart with what you need: managed ops or full control? Network latency acceptable or not? Production or prototyping? The answer narrows to one of four options.\n\n\n## Getting Started or Prototyping\n\nUse when: building a prototype, running tests, CI\u002FCD pipelines, or learning Qdrant.\n\n- Use local mode (Python only): zero-dependency, in-memory or disk-persisted, no server needed [Local mode](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fquickstart\u002F)\n- Local mode data format is NOT compatible with server. Do not use for production or benchmarking.\n- For a real server locally, use Docker [Quick start](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fquickstart\u002F?s=download-and-run)\n\n\n## Going to Production (Self-Hosted)\n\nUse when: you need full control over infrastructure, data residency, or custom configuration.\n\n- Docker is the default deployment. Full Qdrant Open Source feature set, minimal setup. [Quick start](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fquickstart\u002F?s=download-and-run)\n- You own operations: upgrades, backups, scaling, monitoring\n- Must set up distributed mode manually for multi-node clusters [Distributed deployment](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Fdistributed_deployment\u002F)\n- Consider Hybrid Cloud if you want Qdrant Cloud management on your infrastructure [Hybrid Cloud](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fhybrid-cloud\u002F)\n\n\n## Going to Production (Zero-Ops)\n\nUse when: you want managed infrastructure with zero-downtime updates, automatic backups, and resharding without operating clusters yourself.\n\n- Qdrant Cloud handles upgrades, scaling, backups, and monitoring [Qdrant Cloud](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fcloud-quickstart\u002F)\n- Supports multi-version upgrades automatically\n- Provides features not available in self-hosted: `\u002Fsys_metrics`, managed resharding, pre-configured alerts\n\n\n## Need Lowest Possible Latency\n\nUse when: network round-trip to a server is unacceptable. Edge devices, in-process search, or latency-critical applications.\n\n- Qdrant EDGE: in-process bindings to Qdrant shard-level functions, no network overhead [Qdrant EDGE](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fedge\u002Fedge-quickstart\u002F)\n- Same data format as server. Can sync with server via shard snapshots.\n- Single-node feature set only. No distributed mode.\n\n\n## What NOT to Do\n\n- Use local mode for production or benchmarking (not optimized, incompatible data format)\n- Self-host without monitoring and backup strategy (you will lose data or miss outages)\n- Choose EDGE when you need distributed search (single-node only)\n- Pick Hybrid Cloud unless you have data residency requirements (unnecessary Kubernetes complexity when Qdrant Cloud works)\n","# Which Qdrant Deployment Do I Need?\n\nStart with what you need: managed ops or full control? Network latency acceptable or not? Production or prototyping? The answer narrows to one of four options.\n\n\n## Getting Started or Prototyping\n\nUse when: building a prototype, running tests, CI\u002FCD pipelines, or learning Qdrant.\n\n- Use local mode (Python only): zero-dependency, in-memory or disk-persisted, no server needed [Local mode](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fquickstart\u002F)\n- Local mode data format is NOT compatible with server. Do not use for production or benchmarking.\n- For a real server locally, use Docker [Quick start](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fquickstart\u002F?s=download-and-run)\n\n\n## Going to Production (Self-Hosted)\n\nUse when: you need full control over infrastructure, data residency, or custom configuration.\n\n- Docker is the default deployment. Full Qdrant Open Source feature set, minimal setup. [Quick start](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fquickstart\u002F?s=download-and-run)\n- You own operations: upgrades, backups, scaling, monitoring\n- Must set up distributed mode manually for multi-node clusters [Distributed deployment](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Fdistributed_deployment\u002F)\n- Consider Hybrid Cloud if you want Qdrant Cloud management on your infrastructure [Hybrid Cloud](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fhybrid-cloud\u002F)\n\n\n## Going to Production (Zero-Ops)\n\nUse when: you want managed infrastructure with zero-downtime updates, automatic backups, and resharding without operating clusters yourself.\n\n- Qdrant Cloud handles upgrades, scaling, backups, and monitoring [Qdrant Cloud](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fcloud-quickstart\u002F)\n- Supports multi-version upgrades automatically\n- Provides features not available in self-hosted: `\u002Fsys_metrics`, managed resharding, pre-configured alerts\n\n\n## Need Lowest Possible Latency\n\nUse when: network round-trip to a server is unacceptable. Edge devices, in-process search, or latency-critical applications.\n\n- Qdrant EDGE: in-process bindings to Qdrant shard-level functions, no network overhead [Qdrant EDGE](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fedge\u002Fedge-quickstart\u002F)\n- Same data format as server. Can sync with server via shard snapshots.\n- Single-node feature set only. No distributed mode.\n\n\n## What NOT to Do\n\n- Use local mode for production or benchmarking (not optimized, incompatible data format)\n- Self-host without monitoring and backup strategy (you will lose data or miss outages)\n- Choose EDGE when you need distributed search (single-node only)\n- Pick Hybrid Cloud unless you have data residency requirements (unnecessary Kubernetes complexity when Qdrant Cloud works)\n",{"name":36,"description":37},"qdrant-deployment-options","Guides Qdrant deployment selection. Use when someone asks 'how to deploy Qdrant', 'Docker vs Cloud', 'local mode', 'embedded Qdrant', 'Qdrant EDGE', 'which deployment option', 'self-hosted vs cloud', or 'need lowest latency deployment'. Also use when choosing between deployment types for a new project.","main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd",".agents\u002Fskills\u002Fresolving-merge-conflicts",0,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph","https:\u002F\u002Fgithub.com\u002FVortex375","2026-11-08 18:46:14",{"source":8,"skillName":36,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add Vortex375\u002Fseraph --skill qdrant-deployment-options",{"tool":51,"command":52},"bunx","bunx skills add Vortex375\u002Fseraph --skill qdrant-deployment-options",{"tool":54,"command":55},"pnpm","pnpm dlx skills add Vortex375\u002Fseraph --skill qdrant-deployment-options","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fresolving-merge-conflicts\u002FSKILL.md",true,[59],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"agents\u002Fopenai.yaml","REFERENCE","参考文档",113,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fresolving-merge-conflicts\u002Fagents\u002Fopenai.yaml",[66,88,113,138,154,173],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":82,"publishedAt":31},"01M6BYS1QVW7F887EXS5RR34TA","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[72,77],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[83,84,85,30,26,86,87],"writing","for","writing for agents","editing","documents",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":31},"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",[],[90,95,96,97,98,99,100,101,30,102,103,84,104,105,106,107,108,109,26,110,111,112],"provisioning","ci","generate","infrastructure","dashboard","can","running","invoke","party","credentials","human","provisioning infrastructure","migration","up","only","interactive","Bash","secrets",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":31},"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",[],[115,120,121,122,100,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137],"at","map","agent session","time","true","shared","more","tickets","as","clear","issue","session","one at a time","work","decision","plan","chunk","tracker",{"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":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":31},"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",[],[145,146,147,124,148,149,150,151,152,153],"wait what","wait","re","last","it","pitch","message","stop","land",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":31},"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",[],[156,161,162,163,164,165,166,167,168,169,170,171,124,172],"machine","roles","grill","ready","write","verify","issues","state","move","prs","state machine","briefs",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":31},"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",[],[180,127,181,182,183,124,184,185,128,186,137,187,135,188,189],"to tickets","spec","links","break","native","ticket","conversation","text","SET","file"]