[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76YDEX8QJAYVKTMDGPYFQYF":3,"skill-same:01M76YDEX8QJAYVKTMDGPYFQYF":46},{"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":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M76YDEX8QJAYVKTMDGPYFQYF","target-authoring",null,"Canonical patterns for writing custom MSBuild targets. USE FOR: diagnosing and fixing custom target authoring anti-patterns; broken SDK target chains across files (e.g., Directory.Build.targets silently redefining SDK targets); targets that replace CompileDependsOn instead of extending it with $(CompileDependsOn); query targets returning stale results from Outputs vs Returns misuse; missing Inputs\u002FOutputs causing unnecessary rebuilds; missing FileWrites registration. Covers DependsOnTargets vs BeforeTargets vs AfterTargets, the Build→CoreBuild three-level pattern, and the $(XxxDependsOn) chain-extension pattern. DO NOT USE FOR: incremental build tuning (use incremental-build), parallelization (use build-parallelism), general anti-patterns (use msbuild-antipatterns), non-MSBuild build systems.","stanfish06\u002Fskillquarium","stanfish06","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F93099613?v=4","01M75F1CK4ZW109ZK3T26VN52F","Zhiyuan","01M75F1CM53VH6F79DZ8GXKKES",12,"MIT","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Ftarget-authoring\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: target-authoring\ndescription: \"Canonical patterns for writing custom MSBuild targets. USE FOR: diagnosing and fixing custom target authoring anti-patterns; broken SDK target chains across files (e.g., Directory.Build.targets silently redefining SDK targets); targets that replace CompileDependsOn instead of extending it with $(CompileDependsOn); query targets returning stale results from Outputs vs Returns misuse; missing Inputs\u002FOutputs causing unnecessary rebuilds; missing FileWrites registration. Covers DependsOnTargets vs BeforeTargets vs AfterTargets, the Build→CoreBuild three-level pattern, and the $(XxxDependsOn) chain-extension pattern. DO NOT USE FOR: incremental build tuning (use incremental-build), parallelization (use build-parallelism), general anti-patterns (use msbuild-antipatterns), non-MSBuild build systems.\"\nlicense: MIT\n---\n\n# Custom Target Authoring Patterns\n\nCanonical patterns from `Microsoft.Common.CurrentVersion.targets` in the MSBuild repository.\n\n## The Three-Level Target Chain\n\nEvery major entry point (Build, Rebuild, Clean) delegates to a **property** listing its dependencies, which chains through Before → Core → After:\n\n```xml\n\u003CPropertyGroup>\n  \u003CBuildDependsOn>\n    BeforeBuild;\n    CoreBuild;\n    AfterBuild\n  \u003C\u002FBuildDependsOn>\n\u003C\u002FPropertyGroup>\n\n\u003CTarget Name=\"Build\"\n    Condition=\" '$(_InvalidConfigurationWarning)' != 'true' \"\n    DependsOnTargets=\"$(BuildDependsOn)\"\n    Returns=\"@(TargetPathWithTargetPlatformMoniker)\" \u002F>\n\n\u003C!-- Empty extensibility targets — users override these -->\n\u003CTarget Name=\"BeforeBuild\" \u002F>\n\u003CTarget Name=\"AfterBuild\" \u002F>\n```\n\n`CoreBuild` delegates to `$(CoreBuildDependsOn)` and includes error handlers:\n\n```xml\n\u003CTarget Name=\"CoreBuild\" DependsOnTargets=\"$(CoreBuildDependsOn)\">\n  \u003COnError ExecuteTargets=\"_TimeStampAfterCompile;PostBuildEvent\"\n      Condition=\"'$(RunPostBuildEvent)' == 'Always'\" \u002F>\n  \u003COnError ExecuteTargets=\"_CleanRecordFileWrites\" \u002F>\n\u003C\u002FTarget>\n```\n\n### Rules\n\n- Delegate to a property (`DependsOnTargets=\"$(MyTargetDependsOn)\"`), not hardcoded targets.\n- `OnError` goes inside the orchestrating target to ensure cleanup runs even on failure.\n- Empty Before\u002FAfter targets are extensibility points. Users override them; SDKs never put logic in them.\n\n## Chain Extension — Append, Never Overwrite\n\nWhen adding a custom target to an existing chain, **append** to the `DependsOn` property:\n\n```xml\n\u003C!-- GOOD: Append to existing chain -->\n\u003CPropertyGroup>\n  \u003CCompileDependsOn>$(CompileDependsOn);MyCodeGenTarget\u003C\u002FCompileDependsOn>\n\u003C\u002FPropertyGroup>\n\n\u003C!-- BAD: Overwrites the entire chain, dropping SDK targets -->\n\u003CPropertyGroup>\n  \u003CCompileDependsOn>MyCodeGenTarget\u003C\u002FCompileDependsOn>\n\u003C\u002FPropertyGroup>\n```\n\n## DependsOnTargets vs BeforeTargets vs AfterTargets\n\n| Mechanism | Defined in | Best for |\n|---|---|---|\n| `DependsOnTargets` | The target that needs deps | Target explicitly requires others |\n| `BeforeTargets` | The injecting target | Insert before a target you don't own |\n| `AfterTargets` | The injecting target | Insert after a target you don't own |\n\nValidation targets use `BeforeTargets` to intercept all entry points:\n\n```xml\n\u003CTarget Name=\"_CheckForInvalidConfigurationAndPlatform\"\n    BeforeTargets=\"$(BuildDependsOn);Build;$(RebuildDependsOn);Rebuild;$(CleanDependsOn);Clean\">\n\u003C\u002FTarget>\n```\n\n**Rules:**\n\n- Use `DependsOnTargets` when your target needs specific prerequisites.\n- Use `BeforeTargets`\u002F`AfterTargets` when injecting into a pipeline you don't own.\n- Prefer `BeforeTargets=\"CoreCompile\"` over modifying `$(CompileDependsOn)` when you don't control the targets file.\n\n## Returns vs Outputs\n\n```xml\n\u003C!-- Build returns items for consumption by referencing projects -->\n\u003CTarget Name=\"Build\"\n    DependsOnTargets=\"$(BuildDependsOn)\"\n    Returns=\"@(TargetPathWithTargetPlatformMoniker)\" \u002F>\n\n\u003C!-- GetTargetPath is a lightweight query target -->\n\u003CTarget Name=\"GetTargetPath\" Returns=\"@(TargetPathWithTargetPlatformMoniker)\" \u002F>\n```\n\n- **`Returns`** specifies what the MSBuild task receives when calling this project. Use for inter-project communication.\n- **`Outputs`** on inner targets is for incrementality (timestamp checks). Use for up-to-date detection.\n- Never mix the two purposes. Query targets (`GetTargetPath`, `GetTargetFrameworks`) should use `Returns`, not `Outputs`.\n\n## Target Naming Conventions\n\n| Pattern | Meaning | Example |\n|---|---|---|\n| `_PrefixedName` | Internal\u002Fprivate target | `_TimeStampBeforeCompile` |\n| `CoreXxx` | The actual implementation | `CoreBuild`, `CoreCompile` |\n| `BeforeXxx` \u002F `AfterXxx` | Empty extensibility hooks | `BeforeBuild`, `AfterCompile` |\n| `PrepareXxx` | Setup\u002Fvalidation phase | `PrepareForBuild` |\n| `ResolveXxx` | Discovery\u002Fresolution phase | `ResolveReferences` |\n| `GetXxx` | Lightweight query (no side effects) | `GetTargetPath` |\n\n## Complete Custom Target Template\n\n```xml\n\u003C!-- 1. Define the DependsOn chain for extensibility -->\n\u003CPropertyGroup>\n  \u003CMyFeatureDependsOn>\n    _ValidateMyFeatureInputs;\n    BeforeMyFeature;\n    CoreMyFeature;\n    AfterMyFeature\n  \u003C\u002FMyFeatureDependsOn>\n\u003C\u002FPropertyGroup>\n\n\u003C!-- 2. Outer target with Returns for inter-project communication -->\n\u003CTarget Name=\"MyFeature\"\n    DependsOnTargets=\"$(MyFeatureDependsOn)\"\n    Returns=\"@(MyFeatureOutput)\" \u002F>\n\n\u003C!-- 3. Empty extensibility points -->\n\u003CTarget Name=\"BeforeMyFeature\" \u002F>\n\u003CTarget Name=\"AfterMyFeature\" \u002F>\n\n\u003C!-- 4. Core implementation with Inputs\u002FOutputs for incrementality -->\n\u003CTarget Name=\"CoreMyFeature\"\n    Inputs=\"$(MSBuildAllProjects);@(MyFeatureInput)\"\n    Outputs=\"$(IntermediateOutputPath)myfeature.generated.cs\">\n  \u003CExec Command=\"my-tool.exe -o $(IntermediateOutputPath)myfeature.generated.cs\" \u002F>\n  \u003C!-- 5. Register outputs for clean tracking -->\n  \u003CItemGroup>\n    \u003CCompile Include=\"$(IntermediateOutputPath)myfeature.generated.cs\" \u002F>\n    \u003CFileWrites Include=\"$(IntermediateOutputPath)myfeature.generated.cs\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FTarget>\n\n\u003C!-- 6. Validation target runs first in the dependency chain -->\n\u003CTarget Name=\"_ValidateMyFeatureInputs\">\n  \u003CError Text=\"MyFeatureInput items are required.\"\n         Condition=\"'@(MyFeatureInput)' == ''\" \u002F>\n\u003C\u002FTarget>\n```\n\n## Common Pitfalls\n\n- **Overwriting `DependsOn` properties** drops SDK targets silently. Always include `$(ExistingProperty)` when appending.\n- **Using `Outputs` on query targets** causes MSBuild to skip them when \"up to date,\" returning stale data. Use `Returns`.\n- **Defining targets in `.props`** means `BeforeTargets` on SDK targets have nothing to hook into yet. Move targets to `.targets`.\n- **Forgetting `OnError`** in orchestrating targets means file tracking fails on build errors, breaking subsequent incremental builds.\n","# Custom Target Authoring Patterns\n\nCanonical patterns from `Microsoft.Common.CurrentVersion.targets` in the MSBuild repository.\n\n## The Three-Level Target Chain\n\nEvery major entry point (Build, Rebuild, Clean) delegates to a **property** listing its dependencies, which chains through Before → Core → After:\n\n```xml\n\u003CPropertyGroup>\n  \u003CBuildDependsOn>\n    BeforeBuild;\n    CoreBuild;\n    AfterBuild\n  \u003C\u002FBuildDependsOn>\n\u003C\u002FPropertyGroup>\n\n\u003CTarget Name=\"Build\"\n    Condition=\" '$(_InvalidConfigurationWarning)' != 'true' \"\n    DependsOnTargets=\"$(BuildDependsOn)\"\n    Returns=\"@(TargetPathWithTargetPlatformMoniker)\" \u002F>\n\n\u003C!-- Empty extensibility targets — users override these -->\n\u003CTarget Name=\"BeforeBuild\" \u002F>\n\u003CTarget Name=\"AfterBuild\" \u002F>\n```\n\n`CoreBuild` delegates to `$(CoreBuildDependsOn)` and includes error handlers:\n\n```xml\n\u003CTarget Name=\"CoreBuild\" DependsOnTargets=\"$(CoreBuildDependsOn)\">\n  \u003COnError ExecuteTargets=\"_TimeStampAfterCompile;PostBuildEvent\"\n      Condition=\"'$(RunPostBuildEvent)' == 'Always'\" \u002F>\n  \u003COnError ExecuteTargets=\"_CleanRecordFileWrites\" \u002F>\n\u003C\u002FTarget>\n```\n\n### Rules\n\n- Delegate to a property (`DependsOnTargets=\"$(MyTargetDependsOn)\"`), not hardcoded targets.\n- `OnError` goes inside the orchestrating target to ensure cleanup runs even on failure.\n- Empty Before\u002FAfter targets are extensibility points. Users override them; SDKs never put logic in them.\n\n## Chain Extension — Append, Never Overwrite\n\nWhen adding a custom target to an existing chain, **append** to the `DependsOn` property:\n\n```xml\n\u003C!-- GOOD: Append to existing chain -->\n\u003CPropertyGroup>\n  \u003CCompileDependsOn>$(CompileDependsOn);MyCodeGenTarget\u003C\u002FCompileDependsOn>\n\u003C\u002FPropertyGroup>\n\n\u003C!-- BAD: Overwrites the entire chain, dropping SDK targets -->\n\u003CPropertyGroup>\n  \u003CCompileDependsOn>MyCodeGenTarget\u003C\u002FCompileDependsOn>\n\u003C\u002FPropertyGroup>\n```\n\n## DependsOnTargets vs BeforeTargets vs AfterTargets\n\n| Mechanism | Defined in | Best for |\n|---|---|---|\n| `DependsOnTargets` | The target that needs deps | Target explicitly requires others |\n| `BeforeTargets` | The injecting target | Insert before a target you don't own |\n| `AfterTargets` | The injecting target | Insert after a target you don't own |\n\nValidation targets use `BeforeTargets` to intercept all entry points:\n\n```xml\n\u003CTarget Name=\"_CheckForInvalidConfigurationAndPlatform\"\n    BeforeTargets=\"$(BuildDependsOn);Build;$(RebuildDependsOn);Rebuild;$(CleanDependsOn);Clean\">\n\u003C\u002FTarget>\n```\n\n**Rules:**\n\n- Use `DependsOnTargets` when your target needs specific prerequisites.\n- Use `BeforeTargets`\u002F`AfterTargets` when injecting into a pipeline you don't own.\n- Prefer `BeforeTargets=\"CoreCompile\"` over modifying `$(CompileDependsOn)` when you don't control the targets file.\n\n## Returns vs Outputs\n\n```xml\n\u003C!-- Build returns items for consumption by referencing projects -->\n\u003CTarget Name=\"Build\"\n    DependsOnTargets=\"$(BuildDependsOn)\"\n    Returns=\"@(TargetPathWithTargetPlatformMoniker)\" \u002F>\n\n\u003C!-- GetTargetPath is a lightweight query target -->\n\u003CTarget Name=\"GetTargetPath\" Returns=\"@(TargetPathWithTargetPlatformMoniker)\" \u002F>\n```\n\n- **`Returns`** specifies what the MSBuild task receives when calling this project. Use for inter-project communication.\n- **`Outputs`** on inner targets is for incrementality (timestamp checks). Use for up-to-date detection.\n- Never mix the two purposes. Query targets (`GetTargetPath`, `GetTargetFrameworks`) should use `Returns`, not `Outputs`.\n\n## Target Naming Conventions\n\n| Pattern | Meaning | Example |\n|---|---|---|\n| `_PrefixedName` | Internal\u002Fprivate target | `_TimeStampBeforeCompile` |\n| `CoreXxx` | The actual implementation | `CoreBuild`, `CoreCompile` |\n| `BeforeXxx` \u002F `AfterXxx` | Empty extensibility hooks | `BeforeBuild`, `AfterCompile` |\n| `PrepareXxx` | Setup\u002Fvalidation phase | `PrepareForBuild` |\n| `ResolveXxx` | Discovery\u002Fresolution phase | `ResolveReferences` |\n| `GetXxx` | Lightweight query (no side effects) | `GetTargetPath` |\n\n## Complete Custom Target Template\n\n```xml\n\u003C!-- 1. Define the DependsOn chain for extensibility -->\n\u003CPropertyGroup>\n  \u003CMyFeatureDependsOn>\n    _ValidateMyFeatureInputs;\n    BeforeMyFeature;\n    CoreMyFeature;\n    AfterMyFeature\n  \u003C\u002FMyFeatureDependsOn>\n\u003C\u002FPropertyGroup>\n\n\u003C!-- 2. Outer target with Returns for inter-project communication -->\n\u003CTarget Name=\"MyFeature\"\n    DependsOnTargets=\"$(MyFeatureDependsOn)\"\n    Returns=\"@(MyFeatureOutput)\" \u002F>\n\n\u003C!-- 3. Empty extensibility points -->\n\u003CTarget Name=\"BeforeMyFeature\" \u002F>\n\u003CTarget Name=\"AfterMyFeature\" \u002F>\n\n\u003C!-- 4. Core implementation with Inputs\u002FOutputs for incrementality -->\n\u003CTarget Name=\"CoreMyFeature\"\n    Inputs=\"$(MSBuildAllProjects);@(MyFeatureInput)\"\n    Outputs=\"$(IntermediateOutputPath)myfeature.generated.cs\">\n  \u003CExec Command=\"my-tool.exe -o $(IntermediateOutputPath)myfeature.generated.cs\" \u002F>\n  \u003C!-- 5. Register outputs for clean tracking -->\n  \u003CItemGroup>\n    \u003CCompile Include=\"$(IntermediateOutputPath)myfeature.generated.cs\" \u002F>\n    \u003CFileWrites Include=\"$(IntermediateOutputPath)myfeature.generated.cs\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FTarget>\n\n\u003C!-- 6. Validation target runs first in the dependency chain -->\n\u003CTarget Name=\"_ValidateMyFeatureInputs\">\n  \u003CError Text=\"MyFeatureInput items are required.\"\n         Condition=\"'@(MyFeatureInput)' == ''\" \u002F>\n\u003C\u002FTarget>\n```\n\n## Common Pitfalls\n\n- **Overwriting `DependsOn` properties** drops SDK targets silently. Always include `$(ExistingProperty)` when appending.\n- **Using `Outputs` on query targets** causes MSBuild to skip them when \"up to date,\" returning stale data. Use `Returns`.\n- **Defining targets in `.props`** means `BeforeTargets` on SDK targets have nothing to hook into yet. Move targets to `.targets`.\n- **Forgetting `OnError`** in orchestrating targets means file tracking fails on build errors, breaking subsequent incremental builds.\n",{"name":5,"license":15,"description":7},"master","49e49abf2f670d429e0b7e2c0349739c3fdd5cbe","skills\u002Ftarget-authoring",5,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium","https:\u002F\u002Fgithub.com\u002Fstanfish06","https:\u002F\u002Fwww.stanfish.dev\u002F","2026-11-14 21:31:37",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add stanfish06\u002Fskillquarium --skill target-authoring",{"tool":38,"command":39},"bunx","bunx skills add stanfish06\u002Fskillquarium --skill target-authoring",{"tool":41,"command":42},"pnpm","pnpm dlx skills add stanfish06\u002Fskillquarium --skill target-authoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Ftarget-authoring\u002FSKILL.md",true,[],[47,54,63,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M76ZJTRVA456GD7K8Y3EP82H","zarr-python","Stores and queries chunked N-D scientific arrays with Zarr-Python 3, including codecs, sharding, S3\u002FGCS storage, and NumPy\u002FDask\u002FXarray integration. Use for array layout, bounded I\u002FO, format migration, or scientific metadata preservation.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":58,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M76ZJQZ15Q1HKC5V85NHE325","yeet","Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":58,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M76ZJ8ASZ4QYQ70Y6SBA4Z4S","xarray","N-dimensional labeled arrays and datasets in Python. Built on top of NumPy and Dask. It introduces labels in the form of dimensions, coordinates, and attributes on top of raw NumPy-like arrays, making data analysis in physical sciences more intuitive and less error-prone. Use for working with multi-dimensional scientific data, NetCDF\u002FGRIB\u002FZarr files, climate\u002Fweather\u002Foceanographic datasets, remote sensing, geospatial imaging, large out-of-memory datasets with Dask, and labeled array operations.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fxarray\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M76ZHFBXD6VXPQ02VCEG202B","writing-mstest-tests","Use when asked to fix, rewrite, update, improve, modernize, show corrected code for, or explain existing MSTest tests or MSTest-specific configuration. Use for \"review\" when corrected code or edits are wanted, even for one pasted assertion or passing tests with bad failure output. Covers expected\u002Factual labels; generic Boolean, collection, string, numeric, null, identity, exception, hard-cast, and object[] checks; TestContext\u002Flifecycle; timeout\u002Fcancellation; OS\u002FCI conditions, retry, cleanup, parallelization, MSTest.Sdk project setup, and MSTESTxxxx. Honor the installed MSTest version. DO NOT USE to design new test cases (code-testing), perform report-only audits, create project files rather than explain MSTest setup, run tests, migrate frameworks, or handle non-MSTest\u002Fnon-.NET code.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwriting-mstest-tests\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M76ZDFDF4N88RH6HSYGS7GP2","wgs-prs","End-to-end WGS to polygenic risk score pipeline. Takes paired-end FASTQ files (or a pre-existing VCF) through nf-core\u002Fsarek for variant calling, applies VCF QC (normalisation, hard filtering, Ti\u002FTv and Het\u002FHom checks), then computes polygenic risk scores via the PGS Catalog. Fills the FASTQ to VCF gap upstream of the gwas-prs skill.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwgs-prs\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":58,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M76ZCC1SC68J42QK4MDC8RCG","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[]]