[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DZ9SPGGCS0T7CK2MA04F5Q":3,"skill-same:01M6DZ9SPGGCS0T7CK2MA04F5Q":117},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6DZ9SPGGCS0T7CK2MA04F5Q","stylecop-analyzers",null,"Use the open-source free `StyleCop.Analyzers` package for naming, layout, documentation, and style rules in .NET projects. Use when a repo wants stricter style conventions than the SDK analyzers alone provide. USE FOR: the repo wants StyleCop.Analyzers; naming, layout, or documentation style needs stronger enforcement; the team needs stylecop.json guidance. DO NOT USE FOR: repos that intentionally rely only on SDK analyzers; repos where StyleCop overlaps too heavily with an existing style package and no. 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",512,"MIT","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FStyleCop-Analyzers\u002Fskills\u002Fstylecop-analyzers\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"stylecop analyzers","only","when","source","inspect","relevant","free","layout","commands","do","files","enforcement","repos","context","edit","repo","projects","team","open","repository","package","documentation style","run","documentation","2026-11-10 10:12:30",false,"---\nname: stylecop-analyzers\ndescription: \"Use the open-source free `StyleCop.Analyzers` package for naming, layout, documentation, and style rules in .NET projects. Use when a repo wants stricter style conventions than the SDK analyzers alone provide. USE FOR: the repo wants StyleCop.Analyzers; naming, layout, or documentation style needs stronger enforcement; the team needs stylecop.json guidance. DO NOT USE FOR: repos that intentionally rely only on SDK analyzers; repos where StyleCop overlaps too heavily with an existing style package and no. 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 SDK-based repository; respects the repo's `AGENTS.md` commands first.\"\n---\n\n# StyleCop Analyzers\n\n## Trigger On\n\n- the repo wants `StyleCop.Analyzers`\n- naming, layout, or documentation style needs stronger enforcement\n- the team needs `stylecop.json` guidance\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- repos that intentionally rely only on SDK analyzers\n- repos where `StyleCop` overlaps too heavily with an existing style package and no consolidation is planned\n\n## Inputs\n\n- the nearest `AGENTS.md`\n- current `.editorconfig`\n- any existing `stylecop.json`\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. Add `StyleCop.Analyzers` only if the repo wants its opinionated style rules.\n2. Keep severity in the root `.editorconfig`.\n3. Use `stylecop.json` only for StyleCop-specific behavioral options.\n4. Prefer one checked-in `stylecop.json` per repo unless a project genuinely needs its own behavior.\n5. Avoid rule duplication with SDK analyzers or other analyzer packs when possible.\n\n## Bootstrap When Missing\n\nIf `StyleCop.Analyzers` is not configured yet:\n\n1. Detect current state:\n   - `rg -n \"StyleCop\\\\.Analyzers|stylecop\\\\.json\" -g '*.csproj' -g 'stylecop.json' .`\n2. Add package to the intended scope:\n   - `dotnet add PROJECT.csproj package StyleCop.Analyzers`\n3. Keep severity in root `.editorconfig` and use `stylecop.json` only for StyleCop-specific behavior.\n4. Prevent overlap with existing analyzer packs by defining ownership.\n5. Run `dotnet build SOLUTION_OR_PROJECT` and return `status: configured` or `status: improved`.\n6. If the repo intentionally uses SDK analyzers only, return `status: not_applicable`.\n\n\n## Deliver\n\n- explicit StyleCop package setup\n- repo-owned StyleCop rule configuration\n- clear split between root `.editorconfig` and `stylecop.json`\n\n## Validate\n\n- StyleCop severity is versioned in repo config\n- `stylecop.json` is used only where it adds value\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\u002Fstylecop-analyzers.md](references\u002Fstylecop-analyzers.md)\n- [references\u002Frules.md](references\u002Frules.md)\n- [references\u002Fconfig.md](references\u002Fconfig.md)\n\n## Example Requests\n\n- \"Add `StyleCop.Analyzers` to this solution.\"\n- \"Configure StyleCop without losing `.editorconfig` ownership.\"\n","# StyleCop Analyzers\n\n## Trigger On\n\n- the repo wants `StyleCop.Analyzers`\n- naming, layout, or documentation style needs stronger enforcement\n- the team needs `stylecop.json` guidance\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- repos that intentionally rely only on SDK analyzers\n- repos where `StyleCop` overlaps too heavily with an existing style package and no consolidation is planned\n\n## Inputs\n\n- the nearest `AGENTS.md`\n- current `.editorconfig`\n- any existing `stylecop.json`\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. Add `StyleCop.Analyzers` only if the repo wants its opinionated style rules.\n2. Keep severity in the root `.editorconfig`.\n3. Use `stylecop.json` only for StyleCop-specific behavioral options.\n4. Prefer one checked-in `stylecop.json` per repo unless a project genuinely needs its own behavior.\n5. Avoid rule duplication with SDK analyzers or other analyzer packs when possible.\n\n## Bootstrap When Missing\n\nIf `StyleCop.Analyzers` is not configured yet:\n\n1. Detect current state:\n   - `rg -n \"StyleCop\\\\.Analyzers|stylecop\\\\.json\" -g '*.csproj' -g 'stylecop.json' .`\n2. Add package to the intended scope:\n   - `dotnet add PROJECT.csproj package StyleCop.Analyzers`\n3. Keep severity in root `.editorconfig` and use `stylecop.json` only for StyleCop-specific behavior.\n4. Prevent overlap with existing analyzer packs by defining ownership.\n5. Run `dotnet build SOLUTION_OR_PROJECT` and return `status: configured` or `status: improved`.\n6. If the repo intentionally uses SDK analyzers only, return `status: not_applicable`.\n\n\n## Deliver\n\n- explicit StyleCop package setup\n- repo-owned StyleCop rule configuration\n- clear split between root `.editorconfig` and `stylecop.json`\n\n## Validate\n\n- StyleCop severity is versioned in repo config\n- `stylecop.json` is used only where it adds value\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\u002Fstylecop-analyzers.md](references\u002Fstylecop-analyzers.md)\n- [references\u002Frules.md](references\u002Frules.md)\n- [references\u002Fconfig.md](references\u002Fconfig.md)\n\n## Example Requests\n\n- \"Add `StyleCop.Analyzers` to this solution.\"\n- \"Configure StyleCop without losing `.editorconfig` ownership.\"\n",{"name":5,"description":7,"compatibility":48},"Requires a .NET SDK-based repository; respects the repo's `AGENTS.md` commands first.","main","497cc9aba79a931ac6fb8d36a48cc22fe3d6d74b","catalog\u002FTools\u002FStyleCop-Analyzers\u002Fskills\u002Fstylecop-analyzers",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":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add managedcode\u002Fdotnet-skills --skill stylecop-analyzers",{"tool":65,"command":66},"bunx","bunx skills add managedcode\u002Fdotnet-skills --skill stylecop-analyzers",{"tool":68,"command":69},"pnpm","pnpm dlx skills add managedcode\u002Fdotnet-skills --skill stylecop-analyzers","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FStyleCop-Analyzers\u002Fskills\u002Fstylecop-analyzers\u002FSKILL.md",true,[73,79,83,87,91,95,99,103,109,113],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"manifest.json","REFERENCE","参考文档",101,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FStyleCop-Analyzers\u002Fskills\u002Fstylecop-analyzers\u002Fmanifest.json",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fapi_reference.md",9012,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Flabarchive-integration\u002Freferences\u002Fapi_reference.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fauthentication_guide.md",10709,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Flabarchive-integration\u002Freferences\u002Fauthentication_guide.md",{"path":88,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fconfig.md",8918,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FStyleCop-Analyzers\u002Fskills\u002Fstylecop-analyzers\u002Freferences\u002Fconfig.md",{"path":92,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fintegrations.md",12645,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Flabarchive-integration\u002Freferences\u002Fintegrations.md",{"path":96,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Frules.md",8769,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FStyleCop-Analyzers\u002Fskills\u002Fstylecop-analyzers\u002Freferences\u002Frules.md",{"path":100,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fstylecop-analyzers.md",2565,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FStyleCop-Analyzers\u002Fskills\u002Fstylecop-analyzers\u002Freferences\u002Fstylecop-analyzers.md",{"path":104,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":107,"sourceHtmlUrl":108},"scripts\u002Fentry_operations.py","SCRIPT","脚本",10576,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Flabarchive-integration\u002Fscripts\u002Fentry_operations.py",{"path":110,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":111,"sourceHtmlUrl":112},"scripts\u002Fnotebook_operations.py",8677,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Flabarchive-integration\u002Fscripts\u002Fnotebook_operations.py",{"path":114,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":115,"sourceHtmlUrl":116},"scripts\u002Fsetup_config.py",6412,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Flabarchive-integration\u002Fscripts\u002Fsetup_config.py",[118,150,173,204,214,240],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":134,"publishedAt":43},"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",[124,129],{"categoryNo":125,"categoryName":126,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":130,"categoryName":131,"taxonomyType":132,"taxonomyTypeDesc":133},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[135,136,137,41,138,139,140,38,141,142,143,144,33,145,146,29,147,27,148,149],"xtwitter scraper","browser automation","workflows","code","browser","search","api","Media","api client","access","unrelated","webhooks","social","modeling","webhook",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":162,"publishedAt":43},"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",[156,159],{"categoryNo":157,"categoryName":158,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":160,"categoryName":161,"taxonomyType":132,"taxonomyTypeDesc":133},"01JBSEEDCAT000000000000036","内容创作者",[152,163,164,137,165,41,38,166,167,168,33,32,145,29,28,169,170,171,27,172],"writing","performance","tasks","data","parsing","parser","writer","options","project","high-performance",{"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":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":43},"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",[],[180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,21],"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":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":208,"categories":209,"keywords":210,"publishedAt":43},"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",[],[206,192,29,211,212,200,213],"semantic","razor","inspection",{"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":220,"publishedAt":43},"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",[],[221,222,223,224,163,225,226,227,228,229,230,192,20,231,232,233,28,234,235,236,237,200,238,239,21],"system","json","text","system text json net11","policy","metadata","library","serialization","behavior","user","probe","guidance","later","type","dictionary","naming","targeting","custom","generic",{"skillNo":241,"name":242,"nameZh":6,"description":243,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":244,"categories":245,"keywords":248,"publishedAt":43},"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",[246,247],{"categoryNo":125,"categoryName":126,"taxonomyType":127,"taxonomyTypeDesc":128},{"categoryNo":130,"categoryName":131,"taxonomyType":132,"taxonomyTypeDesc":133},[141,249,250,251,41,252,187,221,192,232,233,28,253,254,255,256,237,200,257],"process","process api net11","diagnostics","start","basic","processes","output","usage","new"]