[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE6DM9FSN5207F8ZYFYCXV":3,"skill-same:01M6AE6DM9FSN5207F8ZYFYCXV":114},{"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":31,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M6AE6DM9FSN5207F8ZYFYCXV","salesforce-flow-design",null,"Salesforce Flow architecture decisions, flow type selection, bulk safety validation, and fault handling standards. Use this skill when designing or reviewing Record-Triggered, Screen, Autolaunched, Scheduled, or Platform Event flows to ensure correct type selection, no DML\u002FGet Records in loops, proper fault connectors on all data-changing elements, and appropriate automation density checks before deployment.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41046,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsalesforce-flow-design\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"flow","salesforce flow design","design","salesforce","standards","when","scheduled","flows","event","loops","bulk","screen","platform","get","selection","correct","Safety","data","validation","deployment","connectors","architecture","automation","2026-11-10 10:12:30",false,"---\nname: salesforce-flow-design\ndescription: 'Salesforce Flow architecture decisions, flow type selection, bulk safety validation, and fault handling standards. Use this skill when designing or reviewing Record-Triggered, Screen, Autolaunched, Scheduled, or Platform Event flows to ensure correct type selection, no DML\u002FGet Records in loops, proper fault connectors on all data-changing elements, and appropriate automation density checks before deployment.'\n---\n\n# Salesforce Flow Design and Validation\n\nApply these checks to every Flow you design, build, or review.\n\n## Step 1 — Confirm Flow Is the Right Tool\n\nBefore designing a Flow, verify that a lighter-weight declarative option cannot solve the problem:\n\n| Requirement | Best tool |\n|---|---|\n| Calculate a field value with no side effects | Formula field |\n| Prevent a bad record save with a user message | Validation rule |\n| Sum or count child records on a parent | Roll-up Summary field |\n| Complex multi-object logic, callouts, or high volume | Apex (Queueable \u002F Batch) — not Flow |\n| Everything else | Flow ✓ |\n\nIf you are building a Flow that could be replaced by a formula field or validation rule, ask the user to confirm the requirement is genuinely more complex.\n\n## Step 2 — Select the Correct Flow Type\n\n| Use case | Flow type | Key constraint |\n|---|---|---|\n| Update a field on the same record before it is saved | Before-save Record-Triggered | Cannot send emails, make callouts, or change related records |\n| Create\u002Fupdate related records, emails, callouts | After-save Record-Triggered | Runs after commit — avoid recursion traps |\n| Guide a user through a multi-step UI process | Screen Flow | Cannot be triggered by a record event automatically |\n| Reusable background logic called from another Flow | Autolaunched (Subflow) | Input\u002Foutput variables define the contract |\n| Logic invoked from Apex `@InvocableMethod` | Autolaunched (Invocable) | Must declare input\u002Foutput variables |\n| Time-based batch processing | Scheduled Flow | Runs in batch context — respect governor limits |\n| Respond to events (Platform Events \u002F CDC) | Platform Event–Triggered | Runs asynchronously — eventual consistency |\n\n**Decision rule**: choose before-save when you only need to change the triggering record's own fields. Move to after-save the moment you need to touch related records, send emails, or make callouts.\n\n## Step 3 — Bulk Safety Checklist\n\nThese patterns are governor limit failures at scale. Check for all of them before the Flow is activated.\n\n### DML in Loops — Automatic Fail\n\n```\nLoop element\n  └── Create Records \u002F Update Records \u002F Delete Records  ← ❌ DML inside loop\n```\n\nFix: collect records inside the loop into a collection variable, then run the DML element **outside** the loop.\n\n### Get Records in Loops — Automatic Fail\n\n```\nLoop element\n  └── Get Records  ← ❌ SOQL inside loop\n```\n\nFix: perform the Get Records query **before** the loop, then loop over the collection variable.\n\n### Correct Bulk Pattern\n\n```\nGet Records — collect all records in one query\n└── Loop over the collection variable\n    └── Decision \u002F Assignment (no DML, no Get Records)\n└── After the loop: Create\u002FUpdate\u002FDelete Records — one DML operation\n```\n\n### Transform vs Loop\nWhen the goal is reshaping a collection (e.g. mapping field values from one object to another), use the **Transform** element instead of a Loop + Assignment pattern. Transform is bulk-safe by design and produces cleaner Flow graphs.\n\n## Step 4 — Fault Path Requirements\n\nEvery element that can fail at runtime must have a fault connector. Flows without fault paths surface raw system errors to users.\n\n### Elements That Require Fault Connectors\n- Create Records\n- Update Records\n- Delete Records\n- Get Records (when accessing a required record that might not exist)\n- Send Email\n- HTTP Callout \u002F External Service action\n- Apex action (invocable)\n- Subflow (if the subflow can throw a fault)\n\n### Fault Handler Pattern\n```\nFault connector → Log Error (Create Records on a logging object or fire a Platform Event)\n               → Screen element with user-friendly message (Screen Flows)\n               → Stop \u002F End element (Record-Triggered Flows)\n```\n\nNever connect a fault path back to the same element that faulted — this creates an infinite loop.\n\n## Step 5 — Automation Density Check\n\nBefore deploying, verify there are no overlapping automations on the same object and trigger event:\n\n- Other active Record-Triggered Flows on the same `Object` + `When to Run` combination\n- Legacy Process Builder rules still active on the same object\n- Workflow Rules that fire on the same field changes\n- Apex triggers that also run on the same `before insert` \u002F `after update` context\n\nOverlapping automations can cause unexpected ordering, recursion, and governor limit failures. Document the automation inventory for the object before activating.\n\n## Step 6 — Screen Flow UX Guidelines\n\n- Every path through a Screen Flow must reach an **End** element — no orphan branches.\n- Provide a **Back** navigation option on multi-step flows unless back-navigation would corrupt data.\n- Use `lightning-input` and SLDS-compliant components for all user inputs — do not use HTML form elements.\n- Validate required inputs on the screen before the user can advance — use Flow validation rules on the screen.\n- Handle the **Pause** element if the flow may need to await user action across sessions.\n\n## Step 7 — Deployment Safety\n\n```\nDeploy as Draft    →   Test with 1 record   →   Test with 200+ records   →   Activate\n```\n\n- Always deploy as **Draft** first and test thoroughly before activation.\n- For Record-Triggered Flows: test with the exact entry conditions (e.g. `ISCHANGED(Status)` — ensure the test data actually triggers the condition).\n- For Scheduled Flows: test with a small batch in a sandbox before enabling in production.\n- Check the Automation Density score for the object — more than 3 active automations on a single object increases order-of-execution risk.\n\n## Quick Reference — Flow Anti-Patterns Summary\n\n| Anti-pattern | Risk | Fix |\n|---|---|---|\n| DML element inside a Loop | Governor limit exception | Move DML outside the loop |\n| Get Records inside a Loop | SOQL governor limit exception | Query before the loop |\n| No fault connector on DML\u002Femail\u002Fcallout element | Unhandled exception surfaced to user | Add fault path to every such element |\n| Updating the triggering record in an after-save flow with no recursion guard | Infinite trigger loops | Add an entry condition or recursion guard variable |\n| Looping directly on `$Record` collection | Incorrect behaviour at scale | Assign to a collection variable first, then loop |\n| Process Builder still active alongside a new Flow | Double-execution, unexpected ordering | Deactivate Process Builder before activating the Flow |\n| Screen Flow with no End element on all branches | Runtime error or stuck user | Ensure every branch resolves to an End element |\n","# Salesforce Flow Design and Validation\n\nApply these checks to every Flow you design, build, or review.\n\n## Step 1 — Confirm Flow Is the Right Tool\n\nBefore designing a Flow, verify that a lighter-weight declarative option cannot solve the problem:\n\n| Requirement | Best tool |\n|---|---|\n| Calculate a field value with no side effects | Formula field |\n| Prevent a bad record save with a user message | Validation rule |\n| Sum or count child records on a parent | Roll-up Summary field |\n| Complex multi-object logic, callouts, or high volume | Apex (Queueable \u002F Batch) — not Flow |\n| Everything else | Flow ✓ |\n\nIf you are building a Flow that could be replaced by a formula field or validation rule, ask the user to confirm the requirement is genuinely more complex.\n\n## Step 2 — Select the Correct Flow Type\n\n| Use case | Flow type | Key constraint |\n|---|---|---|\n| Update a field on the same record before it is saved | Before-save Record-Triggered | Cannot send emails, make callouts, or change related records |\n| Create\u002Fupdate related records, emails, callouts | After-save Record-Triggered | Runs after commit — avoid recursion traps |\n| Guide a user through a multi-step UI process | Screen Flow | Cannot be triggered by a record event automatically |\n| Reusable background logic called from another Flow | Autolaunched (Subflow) | Input\u002Foutput variables define the contract |\n| Logic invoked from Apex `@InvocableMethod` | Autolaunched (Invocable) | Must declare input\u002Foutput variables |\n| Time-based batch processing | Scheduled Flow | Runs in batch context — respect governor limits |\n| Respond to events (Platform Events \u002F CDC) | Platform Event–Triggered | Runs asynchronously — eventual consistency |\n\n**Decision rule**: choose before-save when you only need to change the triggering record's own fields. Move to after-save the moment you need to touch related records, send emails, or make callouts.\n\n## Step 3 — Bulk Safety Checklist\n\nThese patterns are governor limit failures at scale. Check for all of them before the Flow is activated.\n\n### DML in Loops — Automatic Fail\n\n```\nLoop element\n  └── Create Records \u002F Update Records \u002F Delete Records  ← ❌ DML inside loop\n```\n\nFix: collect records inside the loop into a collection variable, then run the DML element **outside** the loop.\n\n### Get Records in Loops — Automatic Fail\n\n```\nLoop element\n  └── Get Records  ← ❌ SOQL inside loop\n```\n\nFix: perform the Get Records query **before** the loop, then loop over the collection variable.\n\n### Correct Bulk Pattern\n\n```\nGet Records — collect all records in one query\n└── Loop over the collection variable\n    └── Decision \u002F Assignment (no DML, no Get Records)\n└── After the loop: Create\u002FUpdate\u002FDelete Records — one DML operation\n```\n\n### Transform vs Loop\nWhen the goal is reshaping a collection (e.g. mapping field values from one object to another), use the **Transform** element instead of a Loop + Assignment pattern. Transform is bulk-safe by design and produces cleaner Flow graphs.\n\n## Step 4 — Fault Path Requirements\n\nEvery element that can fail at runtime must have a fault connector. Flows without fault paths surface raw system errors to users.\n\n### Elements That Require Fault Connectors\n- Create Records\n- Update Records\n- Delete Records\n- Get Records (when accessing a required record that might not exist)\n- Send Email\n- HTTP Callout \u002F External Service action\n- Apex action (invocable)\n- Subflow (if the subflow can throw a fault)\n\n### Fault Handler Pattern\n```\nFault connector → Log Error (Create Records on a logging object or fire a Platform Event)\n               → Screen element with user-friendly message (Screen Flows)\n               → Stop \u002F End element (Record-Triggered Flows)\n```\n\nNever connect a fault path back to the same element that faulted — this creates an infinite loop.\n\n## Step 5 — Automation Density Check\n\nBefore deploying, verify there are no overlapping automations on the same object and trigger event:\n\n- Other active Record-Triggered Flows on the same `Object` + `When to Run` combination\n- Legacy Process Builder rules still active on the same object\n- Workflow Rules that fire on the same field changes\n- Apex triggers that also run on the same `before insert` \u002F `after update` context\n\nOverlapping automations can cause unexpected ordering, recursion, and governor limit failures. Document the automation inventory for the object before activating.\n\n## Step 6 — Screen Flow UX Guidelines\n\n- Every path through a Screen Flow must reach an **End** element — no orphan branches.\n- Provide a **Back** navigation option on multi-step flows unless back-navigation would corrupt data.\n- Use `lightning-input` and SLDS-compliant components for all user inputs — do not use HTML form elements.\n- Validate required inputs on the screen before the user can advance — use Flow validation rules on the screen.\n- Handle the **Pause** element if the flow may need to await user action across sessions.\n\n## Step 7 — Deployment Safety\n\n```\nDeploy as Draft    →   Test with 1 record   →   Test with 200+ records   →   Activate\n```\n\n- Always deploy as **Draft** first and test thoroughly before activation.\n- For Record-Triggered Flows: test with the exact entry conditions (e.g. `ISCHANGED(Status)` — ensure the test data actually triggers the condition).\n- For Scheduled Flows: test with a small batch in a sandbox before enabling in production.\n- Check the Automation Density score for the object — more than 3 active automations on a single object increases order-of-execution risk.\n\n## Quick Reference — Flow Anti-Patterns Summary\n\n| Anti-pattern | Risk | Fix |\n|---|---|---|\n| DML element inside a Loop | Governor limit exception | Move DML outside the loop |\n| Get Records inside a Loop | SOQL governor limit exception | Query before the loop |\n| No fault connector on DML\u002Femail\u002Fcallout element | Unhandled exception surfaced to user | Add fault path to every such element |\n| Updating the triggering record in an after-save flow with no recursion guard | Infinite trigger loops | Add an entry condition or recursion guard variable |\n| Looping directly on `$Record` collection | Incorrect behaviour at scale | Assign to a collection variable first, then loop |\n| Process Builder still active alongside a new Flow | Double-execution, unexpected ordering | Deactivate Process Builder before activating the Flow |\n| Screen Flow with no End element on all branches | Runtime error or stuck user | Ensure every branch resolves to an End element |\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fsalesforce-flow-design",5340,"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 13:41:32",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add github\u002Fawesome-copilot --skill salesforce-flow-design",{"tool":76,"command":77},"bunx","bunx skills add github\u002Fawesome-copilot --skill salesforce-flow-design",{"tool":79,"command":80},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill salesforce-flow-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsalesforce-flow-design\u002FSKILL.md",true,[84,90,94,98,102,106,110],{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"agents\u002Fopenai.yaml","REFERENCE","参考文档",394,"https:\u002F\u002Fgithub.com\u002Fpydantic\u002Fpydantic-ai\u002Fblob\u002Fmain\u002Fpydantic_ai_slim\u002Fpydantic_ai\u002F.agents\u002Fskills\u002Fmigrating-langchain-to-pydantic-ai\u002Fagents\u002Fopenai.yaml",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002FCONCEPT-MAPPING.md",16626,"https:\u002F\u002Fgithub.com\u002Fpydantic\u002Fpydantic-ai\u002Fblob\u002Fmain\u002Fpydantic_ai_slim\u002Fpydantic_ai\u002F.agents\u002Fskills\u002Fmigrating-langchain-to-pydantic-ai\u002Freferences\u002FCONCEPT-MAPPING.md",{"path":95,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002FDEEP-AGENTS-MAPPING.md",25057,"https:\u002F\u002Fgithub.com\u002Fpydantic\u002Fpydantic-ai\u002Fblob\u002Fmain\u002Fpydantic_ai_slim\u002Fpydantic_ai\u002F.agents\u002Fskills\u002Fmigrating-langchain-to-pydantic-ai\u002Freferences\u002FDEEP-AGENTS-MAPPING.md",{"path":99,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002FLOGFIRE-VERIFICATION.md",10433,"https:\u002F\u002Fgithub.com\u002Fpydantic\u002Fpydantic-ai\u002Fblob\u002Fmain\u002Fpydantic_ai_slim\u002Fpydantic_ai\u002F.agents\u002Fskills\u002Fmigrating-langchain-to-pydantic-ai\u002Freferences\u002FLOGFIRE-VERIFICATION.md",{"path":103,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002FSEMANTIC-GAPS.md",22149,"https:\u002F\u002Fgithub.com\u002Fpydantic\u002Fpydantic-ai\u002Fblob\u002Fmain\u002Fpydantic_ai_slim\u002Fpydantic_ai\u002F.agents\u002Fskills\u002Fmigrating-langchain-to-pydantic-ai\u002Freferences\u002FSEMANTIC-GAPS.md",{"path":107,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002FVERIFICATION-AND-CUTOVER.md",12619,"https:\u002F\u002Fgithub.com\u002Fpydantic\u002Fpydantic-ai\u002Fblob\u002Fmain\u002Fpydantic_ai_slim\u002Fpydantic_ai\u002F.agents\u002Fskills\u002Fmigrating-langchain-to-pydantic-ai\u002Freferences\u002FVERIFICATION-AND-CUTOVER.md",{"path":111,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002FWORKAROUND-RECIPES.md",18431,"https:\u002F\u002Fgithub.com\u002Fpydantic\u002Fpydantic-ai\u002Fblob\u002Fmain\u002Fpydantic_ai_slim\u002Fpydantic_ai\u002F.agents\u002Fskills\u002Fmigrating-langchain-to-pydantic-ai\u002Freferences\u002FWORKAROUND-RECIPES.md",[115,145,173,200,233,250],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":125,"publishedAt":55},"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",[121,124],{"categoryNo":122,"categoryName":123,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[126,127,128,129,130,37,131,132,133,134,135,136,137,138,139,140,141,142,143,144],"supabase","rls","supabase rls","supabase rls policies","project","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":152,"publishedAt":55},"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",[151],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,170,171,172],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"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":177,"sourceHtmlUrl":178,"categories":179,"keywords":183,"publishedAt":55},"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",[180],{"categoryNo":181,"categoryName":182,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师",[184,185,186,187,188,189,159,130,51,190,191,192,193,194,195,141,196,197,198,199],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"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":15,"licenseFileUrl":204,"sourceHtmlUrl":205,"categories":206,"keywords":211,"publishedAt":55},"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",[207,210],{"categoryNo":208,"categoryName":209,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":181,"categoryName":182,"taxonomyType":29,"taxonomyTypeDesc":30},[212,213,214,215,216,217,218,219,220,221,222,223,224,225,226,37,227,228,229,230,44,159,231,232],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","methods","controls",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":237,"licenseFileUrl":238,"sourceHtmlUrl":239,"categories":240,"keywords":246,"publishedAt":55},"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",[241,242,245],{"categoryNo":208,"categoryName":209,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":243,"categoryName":244,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[247,156,221,248,249],"resemble detect","https","identity",{"skillNo":251,"name":252,"nameZh":6,"description":253,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":237,"licenseFileUrl":254,"sourceHtmlUrl":255,"categories":256,"keywords":261,"publishedAt":55},"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",[257,260],{"categoryNo":258,"categoryName":259,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[262,263,264,265,185,131,9,155,266,267,248,268,269,270,271,272,273,274,275,276,277,278,139,279,280,281,282],"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"]