[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DZ8HJCMQTP16WNJ2TXDXJW":3,"skill-same:01M6DZ8HJCMQTP16WNJ2TXDXJW":92},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6DZ8HJCMQTP16WNJ2TXDXJW","profiling",null,"Use the free official .NET diagnostics CLI tools for profiling and runtime investigation in .NET repositories. USE FOR: the repo needs performance or runtime profiling for a .NET application; the user asks about slow code, high CPU, GC pressure, allocation growth, exception storms, lock. DO NOT USE FOR: replacing realistic performance tests or load tests with ad-hoc tracing alone; production heap collection when the pause risk has not been. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.","managedcode\u002Fdotnet-skills","managedcode","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F78253589?v=4","01M6DYDJR3EG8KB5G4PC65XCTT","Managed Code","01M6DYDJX0ZT432N04NYJW89DN",514,"MIT","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FProfiling\u002Fskills\u002Fprofiling\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"context","when","lock","inspect","heap","relevant","CPU","free","app","commands","do","files","gc","cli","edit","collection","risk","Tools","repository","tracing","code","run","diagnostics","official","performance","2026-11-10 10:12:30",false,"---\nname: profiling\ndescription: \"Use the free official .NET diagnostics CLI tools for profiling and runtime investigation in .NET repositories. USE FOR: the repo needs performance or runtime profiling for a .NET application; the user asks about slow code, high CPU, GC pressure, allocation growth, exception storms, lock. DO NOT USE FOR: replacing realistic performance tests or load tests with ad-hoc tracing alone; production heap collection when the pause risk has not been. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.\"\ncompatibility: \"Requires a .NET app or process to inspect; respects the repo's `AGENTS.md` commands first.\"\n---\n\n# .NET Profiling\n\n## Trigger On\n\n- the repo needs performance or runtime profiling for a .NET application\n- the user asks about slow code, high CPU, GC pressure, allocation growth, exception storms, lock contention, or startup diagnostics\n- the team wants official CLI-based diagnostics without depending on `dnx`\n\n## Value\n\n- produce a concrete project delta: code, docs, config, tests, CI, or review artifact\n- reduce ambiguity through explicit planning, verification, and final validation skills\n- leave reusable project context so future tasks are faster and safer\n\n## Do Not Use For\n\n- replacing realistic performance tests or load tests with ad-hoc tracing alone\n- production heap collection when the pause risk has not been accepted\n- GUI-only workflows that the repo cannot automate or document\n\n## Inputs\n\n- the nearest `AGENTS.md`\n- target application, process, or startup path\n- the symptom being investigated: CPU, memory, GC, contention, exceptions, or startup\n\n## Quick Start\n\n1. Read the nearest `AGENTS.md` and confirm scope and constraints.\n2. Run this skill's `Workflow` through the `Ralph Loop` until outcomes are acceptable.\n3. Return the `Required Result Format` with concrete artifacts and verification evidence.\n\n## Workflow\n\n1. Build and run a realistic target first:\n   - prefer `Release`\n   - prefer realistic config, inputs, and data volume\n2. Start with the lightest useful tool:\n   - `dotnet-counters` for live health signals\n   - `dotnet-trace` for CPU, exception, contention, GC, and startup traces\n   - `dotnet-gcdump` for managed heap inspection when memory shape matters\n3. Prefer installed CLI tools over `dnx` one-shot execution so the repo commands stay stable and reproducible.\n4. Capture one focused profile at a time instead of mixing every signal into one run.\n5. For CPU and general runtime hotspots, start with `dotnet-trace collect`.\n6. For live triage, start with `dotnet-counters monitor` on `System.Runtime`.\n7. For heap analysis, use `dotnet-gcdump` carefully and document the pause risk.\n8. After each change, rerun the same measurement path and compare before versus after.\n\n## Bootstrap When Missing\n\nIf official .NET profiling tools are not available yet:\n\n1. Detect current state:\n   - `dotnet --info`\n   - `dotnet tool list --global`\n   - `command -v dotnet-counters`\n   - `command -v dotnet-trace`\n   - `command -v dotnet-gcdump`\n2. Choose the install path deliberately:\n   - preferred machine-level install:\n     - `dotnet tool install --global dotnet-counters`\n     - `dotnet tool install --global dotnet-trace`\n     - `dotnet tool install --global dotnet-gcdump`\n   - direct-download fallback when global tools are not suitable:\n     - use the official Microsoft Learn download links for `dotnet-counters`, `dotnet-trace`, and `dotnet-gcdump`\n3. Verify the installed tools resolve correctly:\n   - `dotnet-counters --version`\n   - `dotnet-trace --version`\n   - `dotnet-gcdump --version`\n4. Record exact profiling commands in `AGENTS.md`, for example:\n   - `dotnet-counters monitor --process-id PID --counters System.Runtime`\n   - `dotnet-trace collect --process-id PID --profile dotnet-common,dotnet-sampled-thread-time -o trace.nettrace`\n   - `dotnet-gcdump collect --process-id PID --output heap.gcdump`\n5. Run one bounded command and return `status: configured` or `status: improved`.\n6. If the repo intentionally standardizes on another profiling stack and does not want these tools, return `status: not_applicable`.\n\n## Deliver\n\n- explicit official .NET profiling commands\n- a clear profiling path for CPU, counters, and heap inspection\n- reproducible diagnostics commands that humans and agents can rerun\n\n## Validate\n\n- the chosen tool matches the actual symptom\n- commands target a realistic process and configuration\n- before\u002Fafter comparisons use the same scenario\n- heap collection warnings are explicit when `dotnet-gcdump` is used\n\n## Ralph Loop\n\nUse the Ralph Loop for every task, including docs, architecture, testing, and tooling work.\n\n1. Plan first (mandatory):\n   - analyze current state\n   - define target outcome, constraints, and risks\n   - write a detailed execution plan\n   - list final validation skills to run at the end, with order and reason\n2. Execute one planned step and produce a concrete delta.\n3. Review the result and capture findings with actionable next fixes.\n4. Apply fixes in small batches and rerun the relevant checks or review steps.\n5. Update the plan after each iteration.\n6. Repeat until outcomes are acceptable or only explicit exceptions remain.\n7. If a dependency is missing, bootstrap it or return `status: not_applicable` with explicit reason and fallback path.\n\n### Required Result Format\n\n- `status`: `complete` | `clean` | `improved` | `configured` | `not_applicable` | `blocked`\n- `plan`: concise plan and current iteration step\n- `actions_taken`: concrete changes made\n- `validation_skills`: final skills run, or skipped with reasons\n- `verification`: commands, checks, or review evidence summary\n- `remaining`: top unresolved items or `none`\n\nFor setup-only requests with no execution, return `status: configured` and exact next commands.\n\n## Load References\n\n- [references\u002Fcommands.md](references\u002Fcommands.md)\n- [references\u002Fpatterns.md](references\u002Fpatterns.md)\n- [references\u002Fprofiling.md](references\u002Fprofiling.md)\n\n## Example Requests\n\n- \"Profile this .NET app for CPU hotspots.\"\n- \"Investigate GC pressure in this service.\"\n- \"Capture counters and a trace from startup.\"\n- \"Set up official .NET profiling tools for local investigations.\"\n","# .NET Profiling\n\n## Trigger On\n\n- the repo needs performance or runtime profiling for a .NET application\n- the user asks about slow code, high CPU, GC pressure, allocation growth, exception storms, lock contention, or startup diagnostics\n- the team wants official CLI-based diagnostics without depending on `dnx`\n\n## Value\n\n- produce a concrete project delta: code, docs, config, tests, CI, or review artifact\n- reduce ambiguity through explicit planning, verification, and final validation skills\n- leave reusable project context so future tasks are faster and safer\n\n## Do Not Use For\n\n- replacing realistic performance tests or load tests with ad-hoc tracing alone\n- production heap collection when the pause risk has not been accepted\n- GUI-only workflows that the repo cannot automate or document\n\n## Inputs\n\n- the nearest `AGENTS.md`\n- target application, process, or startup path\n- the symptom being investigated: CPU, memory, GC, contention, exceptions, or startup\n\n## Quick Start\n\n1. Read the nearest `AGENTS.md` and confirm scope and constraints.\n2. Run this skill's `Workflow` through the `Ralph Loop` until outcomes are acceptable.\n3. Return the `Required Result Format` with concrete artifacts and verification evidence.\n\n## Workflow\n\n1. Build and run a realistic target first:\n   - prefer `Release`\n   - prefer realistic config, inputs, and data volume\n2. Start with the lightest useful tool:\n   - `dotnet-counters` for live health signals\n   - `dotnet-trace` for CPU, exception, contention, GC, and startup traces\n   - `dotnet-gcdump` for managed heap inspection when memory shape matters\n3. Prefer installed CLI tools over `dnx` one-shot execution so the repo commands stay stable and reproducible.\n4. Capture one focused profile at a time instead of mixing every signal into one run.\n5. For CPU and general runtime hotspots, start with `dotnet-trace collect`.\n6. For live triage, start with `dotnet-counters monitor` on `System.Runtime`.\n7. For heap analysis, use `dotnet-gcdump` carefully and document the pause risk.\n8. After each change, rerun the same measurement path and compare before versus after.\n\n## Bootstrap When Missing\n\nIf official .NET profiling tools are not available yet:\n\n1. Detect current state:\n   - `dotnet --info`\n   - `dotnet tool list --global`\n   - `command -v dotnet-counters`\n   - `command -v dotnet-trace`\n   - `command -v dotnet-gcdump`\n2. Choose the install path deliberately:\n   - preferred machine-level install:\n     - `dotnet tool install --global dotnet-counters`\n     - `dotnet tool install --global dotnet-trace`\n     - `dotnet tool install --global dotnet-gcdump`\n   - direct-download fallback when global tools are not suitable:\n     - use the official Microsoft Learn download links for `dotnet-counters`, `dotnet-trace`, and `dotnet-gcdump`\n3. Verify the installed tools resolve correctly:\n   - `dotnet-counters --version`\n   - `dotnet-trace --version`\n   - `dotnet-gcdump --version`\n4. Record exact profiling commands in `AGENTS.md`, for example:\n   - `dotnet-counters monitor --process-id PID --counters System.Runtime`\n   - `dotnet-trace collect --process-id PID --profile dotnet-common,dotnet-sampled-thread-time -o trace.nettrace`\n   - `dotnet-gcdump collect --process-id PID --output heap.gcdump`\n5. Run one bounded command and return `status: configured` or `status: improved`.\n6. If the repo intentionally standardizes on another profiling stack and does not want these tools, return `status: not_applicable`.\n\n## Deliver\n\n- explicit official .NET profiling commands\n- a clear profiling path for CPU, counters, and heap inspection\n- reproducible diagnostics commands that humans and agents can rerun\n\n## Validate\n\n- the chosen tool matches the actual symptom\n- commands target a realistic process and configuration\n- before\u002Fafter comparisons use the same scenario\n- heap collection warnings are explicit when `dotnet-gcdump` is used\n\n## Ralph Loop\n\nUse the Ralph Loop for every task, including docs, architecture, testing, and tooling work.\n\n1. Plan first (mandatory):\n   - analyze current state\n   - define target outcome, constraints, and risks\n   - write a detailed execution plan\n   - list final validation skills to run at the end, with order and reason\n2. Execute one planned step and produce a concrete delta.\n3. Review the result and capture findings with actionable next fixes.\n4. Apply fixes in small batches and rerun the relevant checks or review steps.\n5. Update the plan after each iteration.\n6. Repeat until outcomes are acceptable or only explicit exceptions remain.\n7. If a dependency is missing, bootstrap it or return `status: not_applicable` with explicit reason and fallback path.\n\n### Required Result Format\n\n- `status`: `complete` | `clean` | `improved` | `configured` | `not_applicable` | `blocked`\n- `plan`: concise plan and current iteration step\n- `actions_taken`: concrete changes made\n- `validation_skills`: final skills run, or skipped with reasons\n- `verification`: commands, checks, or review evidence summary\n- `remaining`: top unresolved items or `none`\n\nFor setup-only requests with no execution, return `status: configured` and exact next commands.\n\n## Load References\n\n- [references\u002Fcommands.md](references\u002Fcommands.md)\n- [references\u002Fpatterns.md](references\u002Fpatterns.md)\n- [references\u002Fprofiling.md](references\u002Fprofiling.md)\n\n## Example Requests\n\n- \"Profile this .NET app for CPU hotspots.\"\n- \"Investigate GC pressure in this service.\"\n- \"Capture counters and a trace from startup.\"\n- \"Set up official .NET profiling tools for local investigations.\"\n",{"name":5,"description":7,"compatibility":49},"Requires a .NET app or process to inspect; respects the repo's `AGENTS.md` commands first.","main","497cc9aba79a931ac6fb8d36a48cc22fe3d6d74b","catalog\u002FTools\u002FProfiling\u002Fskills\u002Fprofiling",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-12 19:59:36",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add managedcode\u002Fdotnet-skills --skill profiling",{"tool":66,"command":67},"bunx","bunx skills add managedcode\u002Fdotnet-skills --skill profiling",{"tool":69,"command":70},"pnpm","pnpm dlx skills add managedcode\u002Fdotnet-skills --skill profiling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FProfiling\u002Fskills\u002Fprofiling\u002FSKILL.md",true,[74,80,84,88],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"manifest.json","REFERENCE","参考文档",50,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FProfiling\u002Fskills\u002Fprofiling\u002Fmanifest.json",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fcommands.md",9459,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FProfiling\u002Fskills\u002Fprofiling\u002Freferences\u002Fcommands.md",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fpatterns.md",14201,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FProfiling\u002Fskills\u002Fprofiling\u002Freferences\u002Fpatterns.md",{"path":89,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fprofiling.md",4111,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FProfiling\u002Fskills\u002Fprofiling\u002Freferences\u002Fprofiling.md",[93,124,146,177,187,214],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":109,"publishedAt":44},"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",[99,104],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[110,111,112,40,39,113,114,37,115,116,117,118,33,119,120,30,121,28,122,123],"xtwitter scraper","browser automation","workflows","browser","search","api","Media","api client","access","unrelated","webhooks","social","modeling","webhook",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":136,"publishedAt":44},"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",[130,133],{"categoryNo":131,"categoryName":132,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":134,"categoryName":135,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000036","内容创作者",[126,137,43,112,138,40,37,139,140,141,33,19,119,30,29,142,143,144,28,145],"writing","tasks","data","parsing","parser","writer","options","project","high-performance",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":44},"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",[],[153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175,176,20],"webgpu","threejs","webgpu threejs tsl","setup","shaders","gpu","integration","applications","js","node","syntax","guide","use","language","three","compute","post","processing","with","renderer","for","materials","wgsl","effects",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":44},"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",[],[179,165,30,184,185,173,186],"semantic","razor","inspection",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":193,"publishedAt":44},"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",[],[194,195,196,197,137,198,199,200,201,202,203,165,204,205,206,207,29,208,209,210,211,173,212,213,20],"system","json","text","system text json net11","policy","metadata","library","serialization","behavior","user","only","probe","guidance","later","type","dictionary","naming","targeting","custom","generic",{"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":6,"sourceHtmlUrl":218,"categories":219,"keywords":222,"publishedAt":44},"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",[220,221],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},[115,223,224,41,40,225,160,194,165,206,207,29,226,227,228,229,211,173,230],"process","process api net11","start","basic","processes","output","usage","new"]