[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DZ9C95F1GWHXSMP0KFT119":3,"skill-same:01M6DZ9C95F1GWHXSMP0KFT119":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":18,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6DZ9C95F1GWHXSMP0KFT119","reportgenerator",null,"Use the open-source free `ReportGenerator` tool for turning .NET coverage outputs into HTML, Markdown, Cobertura, badges, and merged reports. USE FOR: the repo uses or wants ReportGenerator; CI needs human-readable coverage reports; multiple coverage files must be merged. DO NOT USE FOR: raw coverage collection with no reporting need. 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\u002FReportGenerator\u002Fskills\u002Freportgenerator\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,44,45,46,47,48],"use","when","source","inspect","relevant","open-source","free","as","commands","human","do","build","files","reports","html","test","coverage","edit","repo","tool","markdown","open","collection","first","reporting","ci","repository","artifacts","lint","run","2026-11-10 10:12:30",false,"---\nname: reportgenerator\ndescription: \"Use the open-source free `ReportGenerator` tool for turning .NET coverage outputs into HTML, Markdown, Cobertura, badges, and merged reports. USE FOR: the repo uses or wants ReportGenerator; CI needs human-readable coverage reports; multiple coverage files must be merged. DO NOT USE FOR: raw coverage collection with no reporting need. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.\"\ncompatibility: \"Requires coverage artifacts such as Cobertura, OpenCover, or lcov; respects the repo's `AGENTS.md` commands first.\"\n---\n\n# ReportGenerator for .NET\n\n## Trigger On\n\n- the repo uses or wants `ReportGenerator`\n- CI needs human-readable coverage reports\n- multiple coverage files must be merged\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- raw coverage collection with no reporting need\n\n## Inputs\n\n- the nearest `AGENTS.md`\n- existing coverage artifacts\n- desired output formats\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. Keep collection and rendering separate: Coverlet collects, ReportGenerator renders.\n2. Prefer the local or manifest-based .NET tool for reproducible CI runs.\n3. Choose output formats deliberately:\n   - `HtmlSummary`\n   - `Cobertura`\n   - `MarkdownSummaryGithub`\n   - badges\n4. Merge multiple reports only when the repo really needs a consolidated view.\n\n## Bootstrap When Missing\n\nIf `ReportGenerator` is not configured yet:\n\n1. Detect current state:\n   - `rg --files -g '.config\u002Fdotnet-tools.json'`\n   - `dotnet tool list --local`\n   - `dotnet tool list --global`\n   - `command -v reportgenerator`\n2. Prefer local tool installation for reproducible CI:\n   - `dotnet new tool-manifest` (if missing)\n   - `dotnet tool install dotnet-reportgenerator-globaltool`\n3. Add one explicit render command to `AGENTS.md` and CI, for example:\n   - `dotnet tool run reportgenerator -reports:\"**\u002Fcoverage.cobertura.xml\" -targetdir:\"artifacts\u002Fcoverage\" -reporttypes:\"HtmlSummary;Cobertura\"`\n4. Run the report command once and return `status: configured` or `status: improved`.\n5. If raw coverage outputs are already sufficient and no rendered artifacts are needed, return `status: not_applicable`.\n\n## Deliver\n\n- readable coverage artifacts for humans and CI systems\n- explicit report-generation commands\n\n## Validate\n\n- report inputs match the generated coverage format\n- generated reports land in a stable artifact path\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\u002Freportgenerator.md](references\u002Freportgenerator.md)\n- [references\u002Fcommands.md](references\u002Fcommands.md)\n- [references\u002Fformats.md](references\u002Fformats.md)\n\n## Example Requests\n\n- \"Render coverage as HTML in CI.\"\n- \"Merge multiple Coverlet reports.\"\n","# ReportGenerator for .NET\n\n## Trigger On\n\n- the repo uses or wants `ReportGenerator`\n- CI needs human-readable coverage reports\n- multiple coverage files must be merged\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- raw coverage collection with no reporting need\n\n## Inputs\n\n- the nearest `AGENTS.md`\n- existing coverage artifacts\n- desired output formats\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. Keep collection and rendering separate: Coverlet collects, ReportGenerator renders.\n2. Prefer the local or manifest-based .NET tool for reproducible CI runs.\n3. Choose output formats deliberately:\n   - `HtmlSummary`\n   - `Cobertura`\n   - `MarkdownSummaryGithub`\n   - badges\n4. Merge multiple reports only when the repo really needs a consolidated view.\n\n## Bootstrap When Missing\n\nIf `ReportGenerator` is not configured yet:\n\n1. Detect current state:\n   - `rg --files -g '.config\u002Fdotnet-tools.json'`\n   - `dotnet tool list --local`\n   - `dotnet tool list --global`\n   - `command -v reportgenerator`\n2. Prefer local tool installation for reproducible CI:\n   - `dotnet new tool-manifest` (if missing)\n   - `dotnet tool install dotnet-reportgenerator-globaltool`\n3. Add one explicit render command to `AGENTS.md` and CI, for example:\n   - `dotnet tool run reportgenerator -reports:\"**\u002Fcoverage.cobertura.xml\" -targetdir:\"artifacts\u002Fcoverage\" -reporttypes:\"HtmlSummary;Cobertura\"`\n4. Run the report command once and return `status: configured` or `status: improved`.\n5. If raw coverage outputs are already sufficient and no rendered artifacts are needed, return `status: not_applicable`.\n\n## Deliver\n\n- readable coverage artifacts for humans and CI systems\n- explicit report-generation commands\n\n## Validate\n\n- report inputs match the generated coverage format\n- generated reports land in a stable artifact path\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\u002Freportgenerator.md](references\u002Freportgenerator.md)\n- [references\u002Fcommands.md](references\u002Fcommands.md)\n- [references\u002Fformats.md](references\u002Fformats.md)\n\n## Example Requests\n\n- \"Render coverage as HTML in CI.\"\n- \"Merge multiple Coverlet reports.\"\n",{"name":5,"description":7,"compatibility":54},"Requires coverage artifacts such as Cobertura, OpenCover, or lcov; respects the repo's `AGENTS.md` commands first.","main","497cc9aba79a931ac6fb8d36a48cc22fe3d6d74b","catalog\u002FTools\u002FReportGenerator\u002Fskills\u002Freportgenerator",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":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add managedcode\u002Fdotnet-skills --skill reportgenerator",{"tool":71,"command":72},"bunx","bunx skills add managedcode\u002Fdotnet-skills --skill reportgenerator",{"tool":74,"command":75},"pnpm","pnpm dlx skills add managedcode\u002Fdotnet-skills --skill reportgenerator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FReportGenerator\u002Fskills\u002Freportgenerator\u002FSKILL.md",true,[79,85,89,93],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"manifest.json","REFERENCE","参考文档",93,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FReportGenerator\u002Fskills\u002Freportgenerator\u002Fmanifest.json",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fcommands.md",3351,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FReportGenerator\u002Fskills\u002Freportgenerator\u002Freferences\u002Fcommands.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fformats.md",4806,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FReportGenerator\u002Fskills\u002Freportgenerator\u002Freferences\u002Fformats.md",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Freportgenerator.md",1219,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FReportGenerator\u002Fskills\u002Freportgenerator\u002Freferences\u002Freportgenerator.md",[98,130,154,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":114,"publishedAt":49},"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,109],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[115,116,117,48,118,119,120,45,121,122,123,124,36,125,126,31,127,27,128,129],"xtwitter scraper","browser automation","workflows","code","browser","search","api","Media","api client","access","unrelated","webhooks","social","modeling","webhook",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":142,"publishedAt":49},"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",[136,139],{"categoryNo":137,"categoryName":138,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":140,"categoryName":141,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000036","内容创作者",[132,143,144,117,145,48,45,146,147,148,36,149,125,31,29,150,151,152,27,153],"writing","performance","tasks","data","parsing","parser","context","writer","options","project","high-performance",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":49},"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",[],[161,162,163,164,165,166,167,168,169,170,171,172,19,173,174,175,176,177,178,179,180,181,182,183,20],"webgpu","threejs","webgpu threejs tsl","setup","shaders","gpu","integration","applications","js","node","syntax","guide","language","three","compute","post","processing","with","renderer","for","materials","wgsl","effects",{"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":49},"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,19,31,191,192,180,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":49},"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,143,205,206,207,208,209,210,19,211,212,213,214,29,215,216,217,218,180,219,220,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":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":49},"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":107,"taxonomyTypeDesc":108},{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},[121,230,231,232,48,233,168,201,19,213,214,29,234,235,236,237,218,180,238],"process","process api net11","diagnostics","start","basic","processes","output","usage","new"]