[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE1SZEBSVDMYR13PFM0PY6":3,"skill-same:01M6AE1SZEBSVDMYR13PFM0PY6":122},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6AE1SZEBSVDMYR13PFM0PY6","qdrant-indexing-performance-optimization",null,"Diagnoses and fixes slow Qdrant indexing and data ingestion. Use when someone reports 'uploads are slow', 'indexing takes forever', 'optimizer is stuck', 'HNSW build time too long', or 'data uploaded but search is bad'. Also use when optimizer status shows errors, segments won't merge, or indexing threshold questions arise.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41133,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fqdrant-performance-optimization\u002Findexing-performance-optimization\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"Optimization","Qdrant","indexing","qdrant indexing performance optimization","performance optimization","performance","ingestion","when","fixes","errors","long","bad","optimizer","time","build","uploads","reports","use","HNSW","data","data ingestion","search","status","merge","2026-11-10 10:12:30",false,"---\nname: qdrant-indexing-performance-optimization\ndescription: \"Diagnoses and fixes slow Qdrant indexing and data ingestion. Use when someone reports 'uploads are slow', 'indexing takes forever', 'optimizer is stuck', 'HNSW build time too long', or 'data uploaded but search is bad'. Also use when optimizer status shows errors, segments won't merge, or indexing threshold questions arise.\"\n---\n\n# What to Do When Qdrant Indexing Is Too Slow\n\nQdrant does NOT build HNSW indexes immediately. Small segments use brute-force until they exceed `indexing_threshold_kb` (default: 20 MB). Search during this window is slower by design, not a bug.\n\n- Understand the indexing optimizer [Indexing optimizer](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Foptimizer\u002F?s=indexing-optimizer)\n\n\n## Uploads\u002FIngestion Too Slow\n\nUse when: upload or upsert API calls are slow.\nIdentify bottleneck: client-side (network, batching) vs server-side (CPU, disk I\u002FO)\n\nFor client-side, optimize batching and parallelism:\n\n- Use batch upserts (64-256 points per request) [Points API](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fpoints\u002F?s=upload-points)\n- Use 2-4 parallel upload streams\n\nFor server-side, optimize Qdrant configuration and indexing strategy:\n\n- Create more shards (3-12), each shard has an independent update worker [Sharding](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Fdistributed_deployment\u002F?s=sharding)\n- Create payload indexes before HNSW builds (needed for filterable vector index) [Payload index](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Findexing\u002F?s=payload-index)\n\nSuitable for initial bulk load of large datasets:\n\n- Disable HNSW during bulk load (set `indexing_threshold_kb` very high, restore after) [Collection params](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fcollections\u002F?s=update-collection-parameters)\n- Setting `m=0` to disable HNSW is legacy, use high `indexing_threshold_kb` instead\n\nCareful, fast unindexed upload might temporarily use more RAM and degrade search performance until optimizer catches up.\n\nSee https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Ftutorials-develop\u002Fbulk-upload\u002F\n\n\n## Optimizer Stuck or Taking Too Long\n\nUse when: optimizer running for hours, not finishing.\n\n- Check actual progress via optimizations endpoint (v1.17+) [Optimization monitoring](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Foptimizer\u002F?s=optimization-monitoring)\n- Large merges and HNSW rebuilds legitimately take hours on big datasets\n- Check CPU and disk I\u002FO (HNSW is CPU-bound, merging is I\u002FO-bound, HDD is not viable)\n- If `optimizer_status` shows an error, check logs for disk full or corrupted segments\n\n\n## HNSW Build Time Too High\n\nUse when: HNSW index build dominates total indexing time.\n\n- Reduce `m` (default 16, good for most cases, 32+ rarely needed) [HNSW params](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Findexing\u002F?s=vector-index)\n- Reduce `ef_construct` (100-200 sufficient) [HNSW config](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fcollections\u002F?s=indexing-vectors-in-hnsw)\n- Keep `max_indexing_threads` proportional to CPU cores [Configuration](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Fconfiguration\u002F)\n- Use GPU for indexing [GPU indexing](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Frunning-with-gpu\u002F)\n\n## HNSW index for multi-tenant collections\n\nIf you have a multi-tenant use case where all data is split by some payload field (e.g. `tenant_id`), you can avoid building a global HNSW index and instead rely on `payload_m` to build HNSW index only for subsets of data.\nSkipping global HNSW index can significantly reduce indexing time.\n\nSee [Multi-tenant collections](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fmultitenancy\u002F) for details.\n\n## Additional Payload Indexes Are Too Slow\n\nQdrant builds extra HNSW links for all payload indexes to ensure that quality of filtered vector search does not degrade.\nSome payload indexes (e.g. `text` fields with long texts) can have a very high number of unique values per point, which can lead to long HNSW build time.\n\nYou can disable building extra HNSW links for specific payload index and instead rely on slightly slower query-time strategies like ACORN.\n\nRead more about disabling extra HNSW links in [documentation](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Findexing\u002F?s=disable-the-creation-of-extra-edges-for-payload-fields)\n\nRead more about ACORN in [documentation](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fsearch\u002Fsearch\u002F?s=acorn-search-algorithm)\n\n\n## What NOT to Do\n\n- Do not create payload indexes AFTER HNSW is built (breaks filterable vector index)\n- Do not use `m=0` for bulk uploads into an existing collection, it might drop the existing HNSW and cause long reindexing \n- Do not upload one point at a time (per-request overhead dominates)\n","# What to Do When Qdrant Indexing Is Too Slow\n\nQdrant does NOT build HNSW indexes immediately. Small segments use brute-force until they exceed `indexing_threshold_kb` (default: 20 MB). Search during this window is slower by design, not a bug.\n\n- Understand the indexing optimizer [Indexing optimizer](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Foptimizer\u002F?s=indexing-optimizer)\n\n\n## Uploads\u002FIngestion Too Slow\n\nUse when: upload or upsert API calls are slow.\nIdentify bottleneck: client-side (network, batching) vs server-side (CPU, disk I\u002FO)\n\nFor client-side, optimize batching and parallelism:\n\n- Use batch upserts (64-256 points per request) [Points API](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fpoints\u002F?s=upload-points)\n- Use 2-4 parallel upload streams\n\nFor server-side, optimize Qdrant configuration and indexing strategy:\n\n- Create more shards (3-12), each shard has an independent update worker [Sharding](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Fdistributed_deployment\u002F?s=sharding)\n- Create payload indexes before HNSW builds (needed for filterable vector index) [Payload index](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Findexing\u002F?s=payload-index)\n\nSuitable for initial bulk load of large datasets:\n\n- Disable HNSW during bulk load (set `indexing_threshold_kb` very high, restore after) [Collection params](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fcollections\u002F?s=update-collection-parameters)\n- Setting `m=0` to disable HNSW is legacy, use high `indexing_threshold_kb` instead\n\nCareful, fast unindexed upload might temporarily use more RAM and degrade search performance until optimizer catches up.\n\nSee https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Ftutorials-develop\u002Fbulk-upload\u002F\n\n\n## Optimizer Stuck or Taking Too Long\n\nUse when: optimizer running for hours, not finishing.\n\n- Check actual progress via optimizations endpoint (v1.17+) [Optimization monitoring](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Foptimizer\u002F?s=optimization-monitoring)\n- Large merges and HNSW rebuilds legitimately take hours on big datasets\n- Check CPU and disk I\u002FO (HNSW is CPU-bound, merging is I\u002FO-bound, HDD is not viable)\n- If `optimizer_status` shows an error, check logs for disk full or corrupted segments\n\n\n## HNSW Build Time Too High\n\nUse when: HNSW index build dominates total indexing time.\n\n- Reduce `m` (default 16, good for most cases, 32+ rarely needed) [HNSW params](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Findexing\u002F?s=vector-index)\n- Reduce `ef_construct` (100-200 sufficient) [HNSW config](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fcollections\u002F?s=indexing-vectors-in-hnsw)\n- Keep `max_indexing_threads` proportional to CPU cores [Configuration](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Fconfiguration\u002F)\n- Use GPU for indexing [GPU indexing](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Frunning-with-gpu\u002F)\n\n## HNSW index for multi-tenant collections\n\nIf you have a multi-tenant use case where all data is split by some payload field (e.g. `tenant_id`), you can avoid building a global HNSW index and instead rely on `payload_m` to build HNSW index only for subsets of data.\nSkipping global HNSW index can significantly reduce indexing time.\n\nSee [Multi-tenant collections](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fmultitenancy\u002F) for details.\n\n## Additional Payload Indexes Are Too Slow\n\nQdrant builds extra HNSW links for all payload indexes to ensure that quality of filtered vector search does not degrade.\nSome payload indexes (e.g. `text` fields with long texts) can have a very high number of unique values per point, which can lead to long HNSW build time.\n\nYou can disable building extra HNSW links for specific payload index and instead rely on slightly slower query-time strategies like ACORN.\n\nRead more about disabling extra HNSW links in [documentation](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Findexing\u002F?s=disable-the-creation-of-extra-edges-for-payload-fields)\n\nRead more about ACORN in [documentation](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fsearch\u002Fsearch\u002F?s=acorn-search-algorithm)\n\n\n## What NOT to Do\n\n- Do not create payload indexes AFTER HNSW is built (breaks filterable vector index)\n- Do not use `m=0` for bulk uploads into an existing collection, it might drop the existing HNSW and cause long reindexing \n- Do not upload one point at a time (per-request overhead dominates)\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fqdrant-performance-optimization\u002Findexing-performance-optimization",5354,"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-14 05:37:52",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add github\u002Fawesome-copilot --skill qdrant-indexing-performance-optimization",{"tool":64,"command":65},"bunx","bunx skills add github\u002Fawesome-copilot --skill qdrant-indexing-performance-optimization",{"tool":67,"command":68},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill qdrant-indexing-performance-optimization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fqdrant-performance-optimization\u002Findexing-performance-optimization\u002FSKILL.md",true,[72,78,82,86,90,94,98,102,106,110,114,118],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Flark-doc-create.md","REFERENCE","参考文档",5461,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-doc\u002Freferences\u002Flark-doc-create.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Flark-doc-fetch.md",8566,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-doc\u002Freferences\u002Flark-doc-fetch.md",{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Flark-doc-md.md",5104,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-doc\u002Freferences\u002Flark-doc-md.md",{"path":87,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Flark-doc-media-download.md",2169,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-doc\u002Freferences\u002Flark-doc-media-download.md",{"path":91,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Flark-doc-media-insert.md",6944,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-doc\u002Freferences\u002Flark-doc-media-insert.md",{"path":95,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Flark-doc-media-preview.md",1647,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-doc\u002Freferences\u002Flark-doc-media-preview.md",{"path":99,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Flark-doc-update.md",12548,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-doc\u002Freferences\u002Flark-doc-update.md",{"path":103,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Flark-doc-whiteboard.md",5155,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-doc\u002Freferences\u002Flark-doc-whiteboard.md",{"path":107,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Flark-doc-xml.md",8250,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-doc\u002Freferences\u002Flark-doc-xml.md",{"path":111,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fstyle\u002Flark-doc-create-workflow.md",3728,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-doc\u002Freferences\u002Fstyle\u002Flark-doc-create-workflow.md",{"path":115,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Fstyle\u002Flark-doc-style.md",6897,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-doc\u002Freferences\u002Fstyle\u002Flark-doc-style.md",{"path":119,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fstyle\u002Flark-doc-update-workflow.md",4722,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Flark-doc\u002Freferences\u002Fstyle\u002Flark-doc-update-workflow.md",[123,156,184,214,247,264],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":137,"publishedAt":43},"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",[129,134],{"categoryNo":130,"categoryName":131,"taxonomyType":132,"taxonomyTypeDesc":133},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":135,"categoryName":136,"taxonomyType":132,"taxonomyTypeDesc":133},"01JBSEEDCAT000000000000023","Skill与智能体开发",[138,139,140,141,142,26,143,144,145,146,147,148,149,150,151,152,36,153,154,155],"supabase","rls","supabase rls","supabase rls policies","project","review","change","read","write","security","isolation","tables","as","tests","prove","users","functions","with",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":163,"publishedAt":43},"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",[162],{"categoryNo":135,"categoryName":136,"taxonomyType":132,"taxonomyTypeDesc":133},[164,165,166,167,168,169,170,171,172,173,174,175,176,177,178,179,180,181,182,183],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":188,"sourceHtmlUrl":189,"categories":190,"keywords":196,"publishedAt":43},"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",[191],{"categoryNo":192,"categoryName":193,"taxonomyType":194,"taxonomyTypeDesc":195},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[197,198,199,200,201,202,170,142,203,204,205,206,207,208,209,36,210,211,212,213],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":218,"sourceHtmlUrl":219,"categories":220,"keywords":225,"publishedAt":43},"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",[221,224],{"categoryNo":222,"categoryName":223,"taxonomyType":132,"taxonomyTypeDesc":133},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":192,"categoryName":193,"taxonomyType":194,"taxonomyTypeDesc":195},[226,40,227,228,229,230,231,232,233,234,235,236,237,238,239,26,240,241,242,243,244,170,245,246],"winmd api search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":248,"name":249,"nameZh":6,"description":250,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":251,"licenseFileUrl":252,"sourceHtmlUrl":253,"categories":254,"keywords":260,"publishedAt":43},"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",[255,256,259],{"categoryNo":222,"categoryName":223,"taxonomyType":132,"taxonomyTypeDesc":133},{"categoryNo":257,"categoryName":258,"taxonomyType":132,"taxonomyTypeDesc":133},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":135,"categoryName":136,"taxonomyType":132,"taxonomyTypeDesc":133},[261,167,234,262,263],"resemble detect","https","identity",{"skillNo":265,"name":266,"nameZh":6,"description":267,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":251,"licenseFileUrl":268,"sourceHtmlUrl":269,"categories":270,"keywords":275,"publishedAt":43},"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",[271,274],{"categoryNo":272,"categoryName":273,"taxonomyType":132,"taxonomyTypeDesc":133},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":135,"categoryName":136,"taxonomyType":132,"taxonomyTypeDesc":133},[276,277,278,279,198,143,9,166,280,281,262,282,283,284,285,286,287,288,289,290,291,292,151,293,294,295,296],"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"]