[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B5D8BRA66G07045DF7WDYA":3,"skill-same:01M7B5D8BRA66G07045DF7WDYA":74},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7B5D8BRA66G07045DF7WDYA","sap-cloud-integration",null,"SAP Cloud Integration (CPI, part of SAP Integration Suite) runtime-specific guidance for building and troubleshooting iFlows. Use when writing or reviewing CPI Groovy scripts, choosing headers vs. exchange properties, designing exception subprocesses, JMS retry, idempotency or data store patterns, or diagnosing adapter errors (SFTP, HTTP\u002FOAuth, SOAP, IDoc, OData, AS2, Cloud Connector) from Message Processing Log (MPL) text. Not for SAP PI\u002FPO, ABAP development, or generic Java\u002FGroovy outside CPI.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41162,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsap-cloud-integration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sap-cloud-integration\ndescription: 'SAP Cloud Integration (CPI, part of SAP Integration Suite) runtime-specific guidance for building and troubleshooting iFlows. Use when writing or reviewing CPI Groovy scripts, choosing headers vs. exchange properties, designing exception subprocesses, JMS retry, idempotency or data store patterns, or diagnosing adapter errors (SFTP, HTTP\u002FOAuth, SOAP, IDoc, OData, AS2, Cloud Connector) from Message Processing Log (MPL) text. Not for SAP PI\u002FPO, ABAP development, or generic Java\u002FGroovy outside CPI.'\n---\n\n# SAP Cloud Integration (CPI)\n\nThis skill supplies CPI runtime behavior that general models often get wrong: what survives a JMS or ProcessDirect hop, how End events change the monitored status, which Camel and `SAP_` headers the runtime reads, how scripts should touch large payloads, and how specific adapter error texts map to root causes.\n\n## Required references\n\nRead the matching reference before answering. Resolve paths relative to this file.\n\n| Task | Read first |\n|---|---|\n| Write, review, or optimize a Groovy script | [references\u002Fgroovy-scripting.md](references\u002Fgroovy-scripting.md) |\n| Decide header vs. property, write Simple expressions, use `SAP_`\u002F`Camel` names | [references\u002Fheaders-properties-expressions.md](references\u002Fheaders-properties-expressions.md) |\n| Exception subprocess, End events, retry, JMS, idempotency, data store | [references\u002Ferror-handling-reliability.md](references\u002Ferror-handling-reliability.md) |\n| Diagnose an MPL error or adapter failure | [references\u002Fadapter-troubleshooting.md](references\u002Fadapter-troubleshooting.md) |\n| Need SAP's own wording, a field not covered here, or a source link for the user | [references\u002Fsap-documentation-index.md](references\u002Fsap-documentation-index.md) |\n\n## Rules that change the answer\n\n1. **Exchange properties stay inside one iFlow.** They are not propagated over ProcessDirect. They are not stored in a JMS queue unless the JMS receiver's *Transfer Exchange Properties* option is on, which SAP does not recommend because of size limits. Pass what a downstream iFlow needs as a header or in the body. Headers that leave the tenant must not carry secrets.\n2. **An Exception Subprocess that ends with a Message End event reports the message as Completed.** Use an Error End event when the failure must stay visible in monitoring. For synchronous senders, also set `CamelHttpResponseCode`.\n3. **Check `message.getBodySize()` before reading a body with `getBody(String)`.** Treat `-1` (size unknown) as too large. For large payloads, use a streaming parser or a streaming splitter. Line-by-line reading only helps for line-delimited formats; minified JSON or XML is often a single line. Never attach payloads to the MPL unconditionally: gate attachments behind an externalized flag and cap their size. Tenants can write at most 1 GB of MPL attachments per 24 hours.\n4. **Use `SAP_ApplicationID` for business keys.** It makes messages searchable in Monitor. Do not build custom correlation stores for this.\n5. **Reliable delivery needs JMS (or a data store) for retry, and duplicate protection on the receiver side.** An Idempotent Process Call skips messages already processed successfully, but if a receiver commits and the acknowledgment is lost, a retry can still duplicate the effect (at least once). A failed synchronous call is not redelivered by the runtime; the caller must retry. To stop retrying after N attempts, route on `SAPJMSRetries`. The JMS sender sets it only for *Non-Exclusive* queues.\n6. **Read credentials through the Security Material APIs** (`SecureStoreService`), never from externalized parameters or headers. Trust a server certificate chain only after verifying its fingerprints against an independent source, never just because a TLS test returned it, and never disable certificate validation as a fix.\n7. **Diagnose from the exact MPL text.** Separate evidence (error text, HTTP status, step ID) from hypotheses, and give one concrete check per hypothesis (Connectivity Test, trace, keystore entry, Cloud Connector log).\n\n## Output contract\n\n- Code is complete and runnable in a CPI Script step: imports, null handling, guarded `messageLog`.\n- Generated code contains no author names, credits, or promotional URLs.\n- Say which iFlow step the code or setting belongs to and what to configure there (adapter field, End event, externalized parameter).\n- Include test steps for the tenant (trace level, expected MPL status and properties).\n- End with *Static analysis — not tested on a tenant* unless the user confirms a successful test run on their tenant; deployment alone is not enough.\n- If a field name, limit, or behavior is not in these references and you are unsure, say so and point to the matching page in [references\u002Fsap-documentation-index.md](references\u002Fsap-documentation-index.md). Do not invent adapter fields, headers, or SAP Note numbers.\n- Before designing a new integration between SAP products, check SAP Business Accelerator Hub for prepackaged integration content and SAP Architecture Center for a reference architecture. Extend standard content rather than rebuilding it.\n\n## Authoritative sources\n\n- SAP Integration Suite documentation: https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002Fintegration-suite (overview: https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002Fintegration-suite\u002Fsap-integration-suite\u002Fwhat-is-sap-integration-suite)\n- Markdown source of the same documentation, for searching its text only: https:\u002F\u002Fgithub.com\u002FSAP-docs\u002Fbtp-integration-suite\n- Prepackaged integration content: https:\u002F\u002Fapi.sap.com\u002Fintegrations\u002Fdiscoverintegrations\n- Reference architectures: https:\u002F\u002Farchitecture.learning.sap.com\u002F\n\nWhen you cite a source to the user, link the public SAP page (SAP Help Portal, SAP Business Accelerator Hub, SAP Architecture Center, or another official SAP site), not the GitHub Markdown source. When these sources and this skill disagree, the SAP documentation wins. Tell the user about the difference.\n","# SAP Cloud Integration (CPI)\n\nThis skill supplies CPI runtime behavior that general models often get wrong: what survives a JMS or ProcessDirect hop, how End events change the monitored status, which Camel and `SAP_` headers the runtime reads, how scripts should touch large payloads, and how specific adapter error texts map to root causes.\n\n## Required references\n\nRead the matching reference before answering. Resolve paths relative to this file.\n\n| Task | Read first |\n|---|---|\n| Write, review, or optimize a Groovy script | [references\u002Fgroovy-scripting.md](references\u002Fgroovy-scripting.md) |\n| Decide header vs. property, write Simple expressions, use `SAP_`\u002F`Camel` names | [references\u002Fheaders-properties-expressions.md](references\u002Fheaders-properties-expressions.md) |\n| Exception subprocess, End events, retry, JMS, idempotency, data store | [references\u002Ferror-handling-reliability.md](references\u002Ferror-handling-reliability.md) |\n| Diagnose an MPL error or adapter failure | [references\u002Fadapter-troubleshooting.md](references\u002Fadapter-troubleshooting.md) |\n| Need SAP's own wording, a field not covered here, or a source link for the user | [references\u002Fsap-documentation-index.md](references\u002Fsap-documentation-index.md) |\n\n## Rules that change the answer\n\n1. **Exchange properties stay inside one iFlow.** They are not propagated over ProcessDirect. They are not stored in a JMS queue unless the JMS receiver's *Transfer Exchange Properties* option is on, which SAP does not recommend because of size limits. Pass what a downstream iFlow needs as a header or in the body. Headers that leave the tenant must not carry secrets.\n2. **An Exception Subprocess that ends with a Message End event reports the message as Completed.** Use an Error End event when the failure must stay visible in monitoring. For synchronous senders, also set `CamelHttpResponseCode`.\n3. **Check `message.getBodySize()` before reading a body with `getBody(String)`.** Treat `-1` (size unknown) as too large. For large payloads, use a streaming parser or a streaming splitter. Line-by-line reading only helps for line-delimited formats; minified JSON or XML is often a single line. Never attach payloads to the MPL unconditionally: gate attachments behind an externalized flag and cap their size. Tenants can write at most 1 GB of MPL attachments per 24 hours.\n4. **Use `SAP_ApplicationID` for business keys.** It makes messages searchable in Monitor. Do not build custom correlation stores for this.\n5. **Reliable delivery needs JMS (or a data store) for retry, and duplicate protection on the receiver side.** An Idempotent Process Call skips messages already processed successfully, but if a receiver commits and the acknowledgment is lost, a retry can still duplicate the effect (at least once). A failed synchronous call is not redelivered by the runtime; the caller must retry. To stop retrying after N attempts, route on `SAPJMSRetries`. The JMS sender sets it only for *Non-Exclusive* queues.\n6. **Read credentials through the Security Material APIs** (`SecureStoreService`), never from externalized parameters or headers. Trust a server certificate chain only after verifying its fingerprints against an independent source, never just because a TLS test returned it, and never disable certificate validation as a fix.\n7. **Diagnose from the exact MPL text.** Separate evidence (error text, HTTP status, step ID) from hypotheses, and give one concrete check per hypothesis (Connectivity Test, trace, keystore entry, Cloud Connector log).\n\n## Output contract\n\n- Code is complete and runnable in a CPI Script step: imports, null handling, guarded `messageLog`.\n- Generated code contains no author names, credits, or promotional URLs.\n- Say which iFlow step the code or setting belongs to and what to configure there (adapter field, End event, externalized parameter).\n- Include test steps for the tenant (trace level, expected MPL status and properties).\n- End with *Static analysis — not tested on a tenant* unless the user confirms a successful test run on their tenant; deployment alone is not enough.\n- If a field name, limit, or behavior is not in these references and you are unsure, say so and point to the matching page in [references\u002Fsap-documentation-index.md](references\u002Fsap-documentation-index.md). Do not invent adapter fields, headers, or SAP Note numbers.\n- Before designing a new integration between SAP products, check SAP Business Accelerator Hub for prepackaged integration content and SAP Architecture Center for a reference architecture. Extend standard content rather than rebuilding it.\n\n## Authoritative sources\n\n- SAP Integration Suite documentation: https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002Fintegration-suite (overview: https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002Fintegration-suite\u002Fsap-integration-suite\u002Fwhat-is-sap-integration-suite)\n- Markdown source of the same documentation, for searching its text only: https:\u002F\u002Fgithub.com\u002FSAP-docs\u002Fbtp-integration-suite\n- Prepackaged integration content: https:\u002F\u002Fapi.sap.com\u002Fintegrations\u002Fdiscoverintegrations\n- Reference architectures: https:\u002F\u002Farchitecture.learning.sap.com\u002F\n\nWhen you cite a source to the user, link the public SAP page (SAP Help Portal, SAP Business Accelerator Hub, SAP Architecture Center, or another official SAP site), not the GitHub Markdown source. When these sources and this skill disagree, the SAP documentation wins. Tell the user about the difference.\n",{"name":5,"description":7},"main","222eba62d518c27317e917c92e3ec1a7e6729455","skills\u002Fsap-cloud-integration",5360,"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-15 04:42:30",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add github\u002Fawesome-copilot --skill sap-cloud-integration",{"tool":40,"command":41},"bunx","bunx skills add github\u002Fawesome-copilot --skill sap-cloud-integration",{"tool":43,"command":44},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill sap-cloud-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsap-cloud-integration\u002FSKILL.md",true,[48,54,58,62,66,70],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"README.md","REFERENCE","参考文档",2868,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsap-cloud-integration\u002FREADME.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fadapter-troubleshooting.md",7956,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsap-cloud-integration\u002Freferences\u002Fadapter-troubleshooting.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Ferror-handling-reliability.md",6400,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsap-cloud-integration\u002Freferences\u002Ferror-handling-reliability.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fgroovy-scripting.md",7110,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsap-cloud-integration\u002Freferences\u002Fgroovy-scripting.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fheaders-properties-expressions.md",4308,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsap-cloud-integration\u002Freferences\u002Fheaders-properties-expressions.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fsap-documentation-index.md",8972,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsap-cloud-integration\u002Freferences\u002Fsap-documentation-index.md",[75,82,92,128,156,186],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7B5CYRGSG571NH7EJWT5066","on-device-delegate","Saves cloud-model context by briefing one bounded, read-heavy sub-task (more than about 25 KB of prose, or many files that no single command can answer) to the local-coding plugin's on-device worker, which runs on the local MAI Code 1.1 Flash model. Use for log and test triage, summarizing many files, or extracting facts from large inputs. When the user names this skill, call the skill tool in the same response as your first other tool call, never as a separate step.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fon-device-delegate\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":91},"01M74CBQ0M3ZKGQH8XKQZ2FHB1","scout-issue","Use when a developer wants to find the best GitHub issues to contribute to in a repository. Invoke with \u002Fscout-issue or ask to find good first issues, beginner-friendly issues, or open source work. Asks about experience level, technical skills, time, and contribution type, then searches GitHub issues, scores them, and presents ranked recommendations with match analysis.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fscout-issue\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fscout-issue\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":106,"publishedAt":127},"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",[98,103],{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":104,"categoryName":105,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000023","Skill与智能体开发",[107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126],"supabase","rls","supabase rls","supabase rls policies","functions","with","tables","write","read","change","review","when","project","security","isolation","as","tests","prove","use","users","2026-11-10 10:12:30",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":135,"publishedAt":127},"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",[134],{"categoryNo":104,"categoryName":105,"taxonomyType":101,"taxonomyTypeDesc":102},[136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,155],"audit","skill distribution audit","distribution","comparison","investigate","output","drift","collection","version","manifest","helper","template","discovery","for","installer","deterministic","SET","duplicate","reconcile","release",{"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":160,"sourceHtmlUrl":161,"categories":162,"keywords":168,"publishedAt":127},"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",[163],{"categoryNo":164,"categoryName":165,"taxonomyType":166,"taxonomyTypeDesc":167},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[169,170,171,172,173,174,175,176,125,177,178,179,180,181,182,183,119,149,184,185],"migration","logicapps custom code net10 migration","code","custom","local","debugging","Legacy","apps","package","upgrades","worker","azure","workflows","applications","deployment","standalone","projects",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":190,"sourceHtmlUrl":191,"categories":192,"keywords":197,"publishedAt":127},"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",[193,196],{"categoryNo":194,"categoryName":195,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":164,"categoryName":165,"taxonomyType":166,"taxonomyTypeDesc":167},[198,199,200,201,202,203,204,205,206,118,207,208,209,149,210,211,212,213,214,215,216,217,218,219],"search","api","winmd api search","capabilities","platform","events","camera","full","features","access","explore","notifications","networking","file","ml","ui","enumeration","file access","desktop","windows","controls","methods"]