[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DZ494KEPWQ7GRWEVMGGFWM":3,"skill-same:01M6DZ494KEPWQ7GRWEVMGGFWM":97},{"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":23,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6DZ494KEPWQ7GRWEVMGGFWM","dump-collect",null,"Configure and collect crash dumps for modern .NET applications. USE FOR: enabling automatic crash dumps for CoreCLR or NativeAOT, capturing dumps from running .NET processes, setting up dump collection in Docker or Kubernetes, using dotnet-dump collect or createdump. DO NOT USE FOR: analyzing or debugging dumps, post-mortem investigation with lldb\u002Fwindbg\u002Fdotnet-dump analyze, profiling or tracing, or for .NET Framework processes.","managedcode\u002Fdotnet-skills","managedcode","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F78253589?v=4","01M6DYDJR3EG8KB5G4PC65XCTT","Managed Code","01M6DYDJX0ZT432N04NYJW89DN",512,"MIT","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FOfficial-DotNet-Diagnostics\u002Fskills\u002Fdump-collect\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"collect","dump","dump collect","running","docker","post-mortem","for","lldb","with","post","do","up","crash","use","profiling","analyze","configure","investigation","collection","applications","analyzing","tracing","framework","debugging","dotnet","kubernetes","2026-11-10 10:12:30",false,"---\nname: dump-collect\ndescription: \"Configure and collect crash dumps for modern .NET applications. USE FOR: enabling automatic crash dumps for CoreCLR or NativeAOT, capturing dumps from running .NET processes, setting up dump collection in Docker or Kubernetes, using dotnet-dump collect or createdump. DO NOT USE FOR: analyzing or debugging dumps, post-mortem investigation with lldb\u002Fwindbg\u002Fdotnet-dump analyze, profiling or tracing, or for .NET Framework processes.\"\nlicense: MIT\n---\n\n# .NET Crash Dump Collection\n\nThis skill configures and collects crash dumps for modern .NET applications (CoreCLR and NativeAOT) on Linux, macOS, and Windows — including containers.\n\n## Stop Signals\n\n? **Read before starting any workflow.**\n\n- **Stop after dumps are enabled or collected.** Do not open, analyze, or triage dump files.\n- **If the user already has a dump file**, this skill does not cover analysis. Let them know analysis is out of scope.\n- **Do not install analysis tools** (dotnet-dump analyze, windbg). Only install collection tools (dotnet-dump collect). Using `lldb` for on-demand dump capture on macOS is allowed — it ships with Xcode command-line tools and is not being used for analysis.\n- **Do not trace root cause** of crashes. Report the dump file location and move on.\n- **Do not modify application code.** Configuration is environment-only (env vars, OS settings, container specs).\n\n## Step 1 — Identify the Scenario\n\nAsk or determine:\n\n1. **Goal**: Enable automatic crash dumps, or capture a dump from a running process right now?\n2. **Platform**: Linux, macOS, or Windows? Running in a container (Docker\u002FKubernetes)?\n3. **Runtime**: CoreCLR or NativeAOT?\n\n### Detecting CoreCLR vs NativeAOT\n\n**From a binary file (Linux\u002FmacOS):**\n```bash\n# CoreCLR — has IL metadata \u002F managed entry point\nstrings \u003Cbinary> | grep -q \"CorExeMain\" && echo \"CoreCLR\"\n\n# NativeAOT — has Redhawk runtime symbols\nstrings \u003Cbinary> | grep -q \"Rhp\" && echo \"NativeAOT\"\n\n# On macOS\u002FLinux, also try:\nnm \u003Cbinary> 2>\u002Fdev\u002Fnull | grep -qi \"Rhp\" && echo \"NativeAOT\"\n```\n\n**From a binary file (Windows):**\n```powershell\n# CoreCLR — has a CLI header (IL entry point)\ndumpbin \u002Fclrheader \u003Cbinary.exe> | Select-String \"CLI Header\" -Quiet\n\n# NativeAOT — no CLI header, has Redhawk symbols\ndumpbin \u002Fsymbols \u003Cbinary.exe> | Select-String \"Rhp\" -Quiet\n```\n\n**From a running process (Linux):**\n```bash\n# Resolve the binary, then use the same file checks\nBINARY=$(readlink \u002Fproc\u002F\u003Cpid>\u002Fexe)\nstrings \"$BINARY\" | grep -q \"CorExeMain\" && echo \"CoreCLR\" || echo \"NativeAOT\"\n```\n\n**From a running process (macOS):**\n```bash\n# Resolve the binary path from the running process\nBINARY=$(ps -o comm= -p \u003Cpid>)\nstrings \"$BINARY\" | grep -q \"CorExeMain\" && echo \"CoreCLR\" || echo \"NativeAOT\"\n```\n\n**From a running process (Windows PowerShell):**\n```powershell\n# CoreCLR — loads coreclr.dll\n(Get-Process -Id \u003Cpid>).Modules.ModuleName -contains \"coreclr.dll\"\n\n# .NET Framework — loads clr.dll (this skill does not apply)\n(Get-Process -Id \u003Cpid>).Modules.ModuleName -contains \"clr.dll\"\n```\n\n> **If the app is .NET Framework (`clr.dll`), stop.** This skill covers modern .NET (CoreCLR and NativeAOT) only.\n>\n> **If neither CoreCLR nor NativeAOT is detected, stop.** This skill only applies to .NET applications — do not proceed.\n\n## Step 2 — Load the Appropriate Reference\n\nBased on the scenario identified in Step 1, read the relevant reference file:\n\n| Scenario | Reference |\n|----------|-----------|\n| CoreCLR app (any platform) | `references\u002Fcoreclr-dumps.md` |\n| NativeAOT app (any platform) | `references\u002Fnativeaot-dumps.md` |\n| Any app in Docker or Kubernetes | `references\u002Fcontainer-dumps.md` (then also load the runtime-specific reference) |\n\n## Step 3 — Execute\n\nFollow the instructions in the loaded reference to configure or collect dumps. Always:\n\n1. **Confirm the dump output directory exists** and has write permissions before enabling collection.\n2. **Report the dump file path** back to the user after collection succeeds.\n3. **Verify configuration took effect** — for env vars, echo them; for OS settings, read them back.\n4. **Remind the user to disable automatic dumps if they were enabled temporarily** — remove or unset `DOTNET_DbgEnableMiniDump` and related env vars to avoid accumulating dump files.\n","# .NET Crash Dump Collection\n\nThis skill configures and collects crash dumps for modern .NET applications (CoreCLR and NativeAOT) on Linux, macOS, and Windows — including containers.\n\n## Stop Signals\n\n? **Read before starting any workflow.**\n\n- **Stop after dumps are enabled or collected.** Do not open, analyze, or triage dump files.\n- **If the user already has a dump file**, this skill does not cover analysis. Let them know analysis is out of scope.\n- **Do not install analysis tools** (dotnet-dump analyze, windbg). Only install collection tools (dotnet-dump collect). Using `lldb` for on-demand dump capture on macOS is allowed — it ships with Xcode command-line tools and is not being used for analysis.\n- **Do not trace root cause** of crashes. Report the dump file location and move on.\n- **Do not modify application code.** Configuration is environment-only (env vars, OS settings, container specs).\n\n## Step 1 — Identify the Scenario\n\nAsk or determine:\n\n1. **Goal**: Enable automatic crash dumps, or capture a dump from a running process right now?\n2. **Platform**: Linux, macOS, or Windows? Running in a container (Docker\u002FKubernetes)?\n3. **Runtime**: CoreCLR or NativeAOT?\n\n### Detecting CoreCLR vs NativeAOT\n\n**From a binary file (Linux\u002FmacOS):**\n```bash\n# CoreCLR — has IL metadata \u002F managed entry point\nstrings \u003Cbinary> | grep -q \"CorExeMain\" && echo \"CoreCLR\"\n\n# NativeAOT — has Redhawk runtime symbols\nstrings \u003Cbinary> | grep -q \"Rhp\" && echo \"NativeAOT\"\n\n# On macOS\u002FLinux, also try:\nnm \u003Cbinary> 2>\u002Fdev\u002Fnull | grep -qi \"Rhp\" && echo \"NativeAOT\"\n```\n\n**From a binary file (Windows):**\n```powershell\n# CoreCLR — has a CLI header (IL entry point)\ndumpbin \u002Fclrheader \u003Cbinary.exe> | Select-String \"CLI Header\" -Quiet\n\n# NativeAOT — no CLI header, has Redhawk symbols\ndumpbin \u002Fsymbols \u003Cbinary.exe> | Select-String \"Rhp\" -Quiet\n```\n\n**From a running process (Linux):**\n```bash\n# Resolve the binary, then use the same file checks\nBINARY=$(readlink \u002Fproc\u002F\u003Cpid>\u002Fexe)\nstrings \"$BINARY\" | grep -q \"CorExeMain\" && echo \"CoreCLR\" || echo \"NativeAOT\"\n```\n\n**From a running process (macOS):**\n```bash\n# Resolve the binary path from the running process\nBINARY=$(ps -o comm= -p \u003Cpid>)\nstrings \"$BINARY\" | grep -q \"CorExeMain\" && echo \"CoreCLR\" || echo \"NativeAOT\"\n```\n\n**From a running process (Windows PowerShell):**\n```powershell\n# CoreCLR — loads coreclr.dll\n(Get-Process -Id \u003Cpid>).Modules.ModuleName -contains \"coreclr.dll\"\n\n# .NET Framework — loads clr.dll (this skill does not apply)\n(Get-Process -Id \u003Cpid>).Modules.ModuleName -contains \"clr.dll\"\n```\n\n> **If the app is .NET Framework (`clr.dll`), stop.** This skill covers modern .NET (CoreCLR and NativeAOT) only.\n>\n> **If neither CoreCLR nor NativeAOT is detected, stop.** This skill only applies to .NET applications — do not proceed.\n\n## Step 2 — Load the Appropriate Reference\n\nBased on the scenario identified in Step 1, read the relevant reference file:\n\n| Scenario | Reference |\n|----------|-----------|\n| CoreCLR app (any platform) | `references\u002Fcoreclr-dumps.md` |\n| NativeAOT app (any platform) | `references\u002Fnativeaot-dumps.md` |\n| Any app in Docker or Kubernetes | `references\u002Fcontainer-dumps.md` (then also load the runtime-specific reference) |\n\n## Step 3 — Execute\n\nFollow the instructions in the loaded reference to configure or collect dumps. Always:\n\n1. **Confirm the dump output directory exists** and has write permissions before enabling collection.\n2. **Report the dump file path** back to the user after collection succeeds.\n3. **Verify configuration took effect** — for env vars, echo them; for OS settings, read them back.\n4. **Remind the user to disable automatic dumps if they were enabled temporarily** — remove or unset `DOTNET_DbgEnableMiniDump` and related env vars to avoid accumulating dump files.\n",{"name":5,"license":15,"description":7},"main","497cc9aba79a931ac6fb8d36a48cc22fe3d6d74b","catalog\u002FTools\u002FOfficial-DotNet-Diagnostics\u002Fskills\u002Fdump-collect",41,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills","https:\u002F\u002Fskills.managed-code.com","https:\u002F\u002Fgithub.com\u002Fmanagedcode","https:\u002F\u002Fwww.managed-code.com","Open Source Community for .NET Developers: Reliable, Actively Maintained, and Community-Driven. Made in Ukraine 🇺🇦 with ❤️","2026-11-11 19:34:28",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add managedcode\u002Fdotnet-skills --skill dump-collect",{"tool":71,"command":72},"bunx","bunx skills add managedcode\u002Fdotnet-skills --skill dump-collect",{"tool":74,"command":75},"pnpm","pnpm dlx skills add managedcode\u002Fdotnet-skills --skill dump-collect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FOfficial-DotNet-Diagnostics\u002Fskills\u002Fdump-collect\u002FSKILL.md",true,[79,85,89,93],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"manifest.json","REFERENCE","参考文档",172,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FOfficial-DotNet-Diagnostics\u002Fskills\u002Fdump-collect\u002Fmanifest.json",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fcontainer-dumps.md",11485,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FOfficial-DotNet-Diagnostics\u002Fskills\u002Fdump-collect\u002Freferences\u002Fcontainer-dumps.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fcoreclr-dumps.md",2971,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FOfficial-DotNet-Diagnostics\u002Fskills\u002Fdump-collect\u002Freferences\u002Fcoreclr-dumps.md",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fnativeaot-dumps.md",8775,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FOfficial-DotNet-Diagnostics\u002Fskills\u002Fdump-collect\u002Freferences\u002Fnativeaot-dumps.md",[98,133,157,184,194,221],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":112,"publishedAt":50},"01M6DYQE1Y9FHAQHEDTVFQ3447","xtwitter-scraper","Use XTwitterScraper when a .NET application needs typed access to Xquik's X automation REST API for tweet search, user lookup, posting workflows, extraction jobs, monitors, webhooks, or giveaway draws. USE FOR: integrating the XTwitterScraper NuGet package; reviewing Xquik API client usage; modeling API-key configuration, pagination, binary exports, raw responses, retries, and webhook\u002Fevent flows in .NET. DO NOT USE FOR: unrelated stacks; direct browser automation; generic social-media strategy; or code that does not call Xquik. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FLibraries\u002FXTwitterScraper\u002Fskills\u002Fxtwitter-scraper\u002FSKILL.md",[104,107],{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132],"xtwitter scraper","browser automation","workflows","run","code","browser","search","repository","api","Media","api client","access","edit","unrelated","webhooks","files","social","commands","modeling","webhook",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":145,"publishedAt":50},"01M6DYQ9S4PE1H6G8MCH9T21HR","sep","Use Sep for high-performance separated-value parsing and writing in .NET, including delimiter inference, explicit parser\u002Fwriter options, and low-allocation row\u002Fcolumn workflows. USE FOR: delimited data needs are performance-sensitive and allocation-aware; project needs explicit control over separator inference, escaping, trimming, and header behavior;. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FLibraries\u002FSep\u002Fskills\u002Fsep\u002FSKILL.md",[139,142],{"categoryNo":140,"categoryName":141,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":143,"categoryName":144,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000036","内容创作者",[135,146,147,115,148,116,120,149,150,151,125,152,126,128,34,153,154,155,130,156],"writing","performance","tasks","data","parsing","parser","context","writer","options","project","high-performance",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":50},"01M6DZS2DNEPXCGGF6SSCW6G5V","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fexternal-sources\u002Fupstreams\u002Fwebgpu-claude-skill\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[164,165,166,167,168,169,170,43,171,172,173,174,37,175,176,177,33,178,32,179,30,180,181,182,183],"webgpu","threejs","webgpu threejs tsl","setup","shaders","gpu","integration","js","node","syntax","guide","language","three","compute","processing","renderer","materials","wgsl","effects","when",{"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":6,"sourceHtmlUrl":188,"categories":189,"keywords":190,"publishedAt":50},"01M6DZS0BQXW2B56A289XF1X76","roslynk","Use Roslynk for semantic inspection and edits of *.cs, *.razor and *.cshtml solution files.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fexternal-sources\u002Fupstreams\u002Froslynk\u002Fskills\u002Froslynk\u002FSKILL.md",[],[186,37,128,191,192,30,193],"semantic","razor","inspection",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":200,"publishedAt":50},"01M6DZRW6MEJCVW80K3S4XV60K","system-text-json-net11","Imperative guidance for the System.Text.Json APIs added in .NET 11: the built-in `JsonNamingPolicy.PascalCase` naming policy, and the strongly-typed generic `JsonSerializerOptions.GetTypeInfo` and `JsonSerializerOptions.TryGetTypeInfo` metadata accessors (generic overloads that return a typed `JsonTypeInfo`). USE ONLY when the user is targeting net11.0 or later and needs PascalCase JSON property or dictionary-key names without writing a custom naming policy, a strongly-typed generic `JsonTypeInfo` instead of the non-generic `JsonTypeInfo`, or a no-throw way to probe whether a type's serialization metadata is resolved. DO NOT USE when the target is earlier than net11.0, the requested behavior uses an established pre-net11 naming policy, or the user explicitly selected another JSON library.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fexternal-sources\u002Fupstreams\u002Fdotnet-skills\u002Fplugins\u002Fdotnet11\u002Fskills\u002Fsystem-text-json-net11\u002FSKILL.md",[],[201,202,203,204,146,205,206,207,208,209,210,37,211,212,213,214,34,215,216,217,218,30,219,220,183],"system","json","text","system text json net11","policy","metadata","library","serialization","behavior","user","only","probe","guidance","later","type","dictionary","naming","targeting","custom","generic",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":229,"publishedAt":50},"01M6DZRRJP3S662NFSG1RSPQQ7","process-api-net11","Provides guidance on the new System.Diagnostics.Process APIs introduced in .NET 11: Process.Run, Process.RunAndCaptureText, Process.StartAndForget, Process.ReadAllText\u002FBytes\u002FLines, KillOnParentExit, InheritedHandles, and StartDetached. USE FOR: starting, orchestrating, or capturing output from external processes in applications targeting net11.0 or later. DO NOT USE FOR: applications targeting .NET 10 or earlier, or basic pre-.NET 11 Process.Start usage without new APIs.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fexternal-sources\u002Fupstreams\u002Fdotnet-skills\u002Fplugins\u002Fdotnet11\u002Fskills\u002Fprocess-api-net11\u002FSKILL.md",[227,228],{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},[121,230,231,232,116,233,43,201,37,213,214,34,234,235,236,237,218,30,238],"process","process api net11","diagnostics","start","basic","processes","output","usage","new"]