[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75NWQW9R74Q1M024PEM3PVC":3,"skill-same:01M75NWQW9R74Q1M024PEM3PVC":57},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75NWQW9R74Q1M024PEM3PVC","nuget-trusted-publishing",null,"Set up NuGet trusted publishing (OIDC) on a GitHub Actions repo — replaces long-lived API keys with short-lived tokens. USE FOR: trusted publishing, NuGet OIDC, keyless NuGet publish, migrate from NuGet API key, NuGet\u002Flogin, secure NuGet publishing. DO NOT USE FOR: publishing to private feeds or Azure Artifacts (OIDC is nuget.org only). INVOKES: shell (powershell or bash), edit, create, ask_user for guided repo setup.","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\u002Fnuget-trusted-publishing\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: nuget-trusted-publishing\ndescription: >\n  Set up NuGet trusted publishing (OIDC) on a GitHub Actions repo — replaces long-lived API keys\n  with short-lived tokens. USE FOR: trusted publishing, NuGet OIDC, keyless NuGet publish,\n  migrate from NuGet API key, NuGet\u002Flogin, secure NuGet publishing.\n  DO NOT USE FOR: publishing to private feeds or Azure Artifacts (OIDC is nuget.org only).\n  INVOKES: shell (powershell or bash), edit, create, ask_user for guided repo setup.\nlicense: MIT\n---\n\n# NuGet Trusted Publishing Setup\n\nSet up [NuGet trusted publishing](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fnuget\u002Fnuget-org\u002Ftrusted-publishing) on a GitHub Actions repo. Replaces long-lived API keys with OIDC-based short-lived tokens — no secrets to rotate or leak.\n\n## Prerequisites\n\n- **GitHub Actions** — this skill covers GitHub Actions setup only\n- **nuget.org account** — the user needs access to create trusted publishing policies\n\n## When to Use This Skill\n\nUse this skill when:\n- Setting up trusted publishing for a NuGet package\n- Migrating from `secrets.NUGET_API_KEY` to OIDC-based publishing\n- Asked about keyless or secure NuGet publishing\n- Creating a new NuGet publish workflow from scratch\n- Asked to \"remove NuGet API key\" or \"use NuGet\u002Flogin\"\n- Setting up publishing for a dotnet tool, MCP server, or template package\n- Asked about `NuGet\u002Flogin@v1` or `id-token: write`\n\n## Safety Rules\n\n> ⚠️ **Bail-out rule**: If any phase fails after one fix attempt on an infrastructure\u002Fauth issue, stop and ask the user. Don't loop on environment problems.\n\n> ⚠️ **Never delete or overwrite without confirmation**: Removing API key secrets, deleting tags\u002Freleases, removing workflow steps, or changing package IDs. NuGet package IDs are permanent — mistakes can't be undone.\n\n## Process\n\n> **Fast-path for greenfield repos**: When the user has a simple setup (one packable project, no existing publish workflow), don't gate on multi-turn assessment. Combine phases: create the workflow immediately, include nuget.org policy guidance, local pack recommendation, and filename-matching warning all in one response. The full phased process below is for complex or migration scenarios.\n\n### Phase 1: Assess\n\nInspect the repo and report findings before making any changes.\n\n1. **Find and classify packable projects** — check `.csproj` files **and `Directory.Build.props`** (package metadata is often set repo-wide). Classify in this order (earlier matches win):\n   - `\u003CPackageType>Template\u003C\u002FPackageType>` → **Template**\n   - `\u003CPackageType>McpServer\u003C\u002FPackageType>` → **MCP server** (also a dotnet tool)\n   - `\u003CPackAsTool>true\u003C\u002FPackAsTool>` → **Dotnet tool**\n   - Class library (`IsPackable=true` or no `OutputType`) → **Library**\n   - `\u003COutputType>Exe\u003C\u002FOutputType>` with `\u003CIsPackable>true\u003C\u002FIsPackable>` → **Application package** (not a tool, but still publishable)\n   - `\u003COutputType>Exe\u003C\u002FOutputType>` without `PackAsTool` or `IsPackable` → Not packable by default (ask user if they intend to publish it)\n\n2. **Validate structure** for each project's type:\n\n   | Type | Required |\n   |------|----------|\n   | All | `PackageId`, `Version` (in .csproj or Directory.Build.props) |\n   | Dotnet tool | `PackAsTool` (required); `ToolCommandName` (optional but recommended — defaults to assembly name) |\n   | MCP server | `PackageType=McpServer`, `.mcp\u002Fserver.json` included in package |\n   | Template | `PackageType=Template`, `.template.config\u002Ftemplate.json` under content dir |\n\n3. **Find existing publish workflows** in `.github\u002Fworkflows\u002F` — look for `dotnet nuget push`, `nuget push`, or `dotnet pack`.\n\n4. **Check version consistency** — for MCP servers, verify `.csproj` `\u003CVersion>` matches both `server.json` version fields (root `version` and `packages[].version`). Flag any mismatch.\n\n5. **Report findings** to the user: classification, missing properties, version mismatches, existing workflows. For multi-project repos, note whether one workflow or separate workflows per package are needed. Offer to fix gaps — use `ask_user` before modifying project files.\n\n> ❌ See [references\u002Fpackage-types.md](references\u002Fpackage-types.md) for per-type details and required properties.\n\n### Phase 2: Local Verification\n\nPack and verify locally before touching nuget.org — publishing errors waste a permanent version number.\n\n> ⚠️ **Always mention this step**, even if you defer running it. Tell the user: \"Before your first publish, run `dotnet pack -c Release -o .\u002Fartifacts` to verify the .nupkg is created correctly.\"\n\n1. `dotnet pack -c Release -o .\u002Fartifacts` — verify `.nupkg` is created\n2. For tools\u002FMCP servers: install from `.\u002Fartifacts`, run `--help`, uninstall\n3. For libraries: inspect the `.nupkg` contents (it's a zip)\n\n### Phase 3: nuget.org Policy\n\nThis phase requires the user to act on nuget.org — guide them with exact values.\n\n1. Determine the **repo owner**, **repo name**, and the **workflow filename** that will publish.\n\n   > ❌ The policy requires the **exact workflow filename** (e.g., `publish.yml` or `publish.yaml`) — just the filename, no path prefix. Matching is case-insensitive. Don't use the workflow `name:` field.\n\n2. Guide the user to create the trusted publishing policy:\n   > Go to [**nuget.org\u002Faccount\u002Ftrustedpublishing**](https:\u002F\u002Fwww.nuget.org\u002Faccount\u002Ftrustedpublishing) → **Add policy**\n   >\n   > - **Repository Owner**: `{owner}`\n   > - **Repository**: `{repo}`\n   > - **Workflow File**: `{filename}.yml`\n   > - **Environment**: `release` *(only if the workflow uses `environment:`; leave blank otherwise)*\n\n   Policy ownership: the user chooses individual account or organization. Org-owned policies apply to all packages owned by that org.\n\n   For **private repos**: policy is \"temporarily active\" for 7 days — becomes permanent after the first successful publish.\n\n3. Guide the user to create a **GitHub Environment** (recommended but optional — provides secret scoping + approval gates):\n   > Repo **Settings** → **Environments** → **New environment** → `release`\n   >\n   > Add environment secret: **Name** = `NUGET_USER`, **Value** = nuget.org username (NOT email)\n\n   Optional: add **Required reviewers** for an approval gate.\n\n> ⚠️ Wait for the user to confirm they've created the policy **before asking them to remove old API keys\u002Fsecrets or before attempting to run\u002Fpublish with the workflow**. Drafting or showing the workflow file itself is OK before confirmation.\n\n### Phase 4: Workflow Setup\n\nCreate or modify the publish workflow. **The workflow must always be created or shown in your response** — you may draft\u002Fshow it even if the nuget.org policy is not yet confirmed, but do not guide the user to actually run\u002Fpublish or remove old secrets until after confirmation.\n\n**Greenfield**: Create `publish.yml` from the template in [references\u002Fpublish-workflow.md](references\u002Fpublish-workflow.md). Adapt .NET version, project path, and environment name. Ensure your output explicitly mentions `id-token: write` and `NuGet\u002Flogin@v1`.\n\n**Migration** (existing workflow with API key): Modify in place —\n\n1. **Add OIDC permission and environment** to the publishing job:\n   ```yaml\n   jobs:\n     publish:\n       environment: release\n       permissions:\n         id-token: write     # Required — without this, NuGet\u002Flogin fails with 403\n         contents: read      # Explicit — setting permissions overrides defaults\n   ```\n\n2. **Add the NuGet login step** before push:\n   ```yaml\n   - name: NuGet login (OIDC)\n     id: login\n     uses: NuGet\u002Flogin@v1\n     with:\n       user: ${{ secrets.NUGET_USER }}  # nuget.org profile name, NOT email\n   ```\n\n3. **Replace the API key** in the push step:\n   ```yaml\n   --api-key ${{ steps.login.outputs.NUGET_API_KEY }} --skip-duplicate\n   ```\n\n4. **Verify**: Ask the user to trigger a publish and confirm the package appears on nuget.org.\n\n> ❌ **Don't delete the old API key secret** until trusted publishing is verified. Removing it is a one-way door — wait for confirmation.\n\n## Troubleshooting\n\n| Problem | Cause | Fix |\n|---------|-------|-----|\n| `NuGet\u002Flogin` 403 | Missing `id-token: write` | Add to job permissions |\n| \"no matching policy\" | Workflow filename mismatch | Verify exact filename on nuget.org |\n| Push unauthorized | Package not owned by policy account | Check policy owner on nuget.org |\n| Token expired | Login step >1hr before push | Move `NuGet\u002Flogin` closer to push |\n| \"temporarily active\" policy | Private repo, first publish pending | Publish within 7 days |\n| `already_exists` on push | Re-running same version | Add `--skip-duplicate` |\n| GitHub Release 422 | Duplicate release for tag | Delete conflicting release (confirm first) |\n| Re-run uses wrong YAML | `gh run rerun` replays original commit's YAML | Delete obstacle, re-run — never re-tag |\n\n> ⚠️ If any blocker persists after one fix attempt, **stop and ask the user**.\n\n## References\n\n- **Package type details**: [references\u002Fpackage-types.md](references\u002Fpackage-types.md) — detection logic, required properties, minimal .csproj examples\n- **Publish workflow template**: [references\u002Fpublish-workflow.md](references\u002Fpublish-workflow.md) — complete tag-triggered workflow ready to adapt\n- **Microsoft docs**: [NuGet Trusted Publishing](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fnuget\u002Fnuget-org\u002Ftrusted-publishing)\n","# NuGet Trusted Publishing Setup\n\nSet up [NuGet trusted publishing](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fnuget\u002Fnuget-org\u002Ftrusted-publishing) on a GitHub Actions repo. Replaces long-lived API keys with OIDC-based short-lived tokens — no secrets to rotate or leak.\n\n## Prerequisites\n\n- **GitHub Actions** — this skill covers GitHub Actions setup only\n- **nuget.org account** — the user needs access to create trusted publishing policies\n\n## When to Use This Skill\n\nUse this skill when:\n- Setting up trusted publishing for a NuGet package\n- Migrating from `secrets.NUGET_API_KEY` to OIDC-based publishing\n- Asked about keyless or secure NuGet publishing\n- Creating a new NuGet publish workflow from scratch\n- Asked to \"remove NuGet API key\" or \"use NuGet\u002Flogin\"\n- Setting up publishing for a dotnet tool, MCP server, or template package\n- Asked about `NuGet\u002Flogin@v1` or `id-token: write`\n\n## Safety Rules\n\n> ⚠️ **Bail-out rule**: If any phase fails after one fix attempt on an infrastructure\u002Fauth issue, stop and ask the user. Don't loop on environment problems.\n\n> ⚠️ **Never delete or overwrite without confirmation**: Removing API key secrets, deleting tags\u002Freleases, removing workflow steps, or changing package IDs. NuGet package IDs are permanent — mistakes can't be undone.\n\n## Process\n\n> **Fast-path for greenfield repos**: When the user has a simple setup (one packable project, no existing publish workflow), don't gate on multi-turn assessment. Combine phases: create the workflow immediately, include nuget.org policy guidance, local pack recommendation, and filename-matching warning all in one response. The full phased process below is for complex or migration scenarios.\n\n### Phase 1: Assess\n\nInspect the repo and report findings before making any changes.\n\n1. **Find and classify packable projects** — check `.csproj` files **and `Directory.Build.props`** (package metadata is often set repo-wide). Classify in this order (earlier matches win):\n   - `\u003CPackageType>Template\u003C\u002FPackageType>` → **Template**\n   - `\u003CPackageType>McpServer\u003C\u002FPackageType>` → **MCP server** (also a dotnet tool)\n   - `\u003CPackAsTool>true\u003C\u002FPackAsTool>` → **Dotnet tool**\n   - Class library (`IsPackable=true` or no `OutputType`) → **Library**\n   - `\u003COutputType>Exe\u003C\u002FOutputType>` with `\u003CIsPackable>true\u003C\u002FIsPackable>` → **Application package** (not a tool, but still publishable)\n   - `\u003COutputType>Exe\u003C\u002FOutputType>` without `PackAsTool` or `IsPackable` → Not packable by default (ask user if they intend to publish it)\n\n2. **Validate structure** for each project's type:\n\n   | Type | Required |\n   |------|----------|\n   | All | `PackageId`, `Version` (in .csproj or Directory.Build.props) |\n   | Dotnet tool | `PackAsTool` (required); `ToolCommandName` (optional but recommended — defaults to assembly name) |\n   | MCP server | `PackageType=McpServer`, `.mcp\u002Fserver.json` included in package |\n   | Template | `PackageType=Template`, `.template.config\u002Ftemplate.json` under content dir |\n\n3. **Find existing publish workflows** in `.github\u002Fworkflows\u002F` — look for `dotnet nuget push`, `nuget push`, or `dotnet pack`.\n\n4. **Check version consistency** — for MCP servers, verify `.csproj` `\u003CVersion>` matches both `server.json` version fields (root `version` and `packages[].version`). Flag any mismatch.\n\n5. **Report findings** to the user: classification, missing properties, version mismatches, existing workflows. For multi-project repos, note whether one workflow or separate workflows per package are needed. Offer to fix gaps — use `ask_user` before modifying project files.\n\n> ❌ See [references\u002Fpackage-types.md](references\u002Fpackage-types.md) for per-type details and required properties.\n\n### Phase 2: Local Verification\n\nPack and verify locally before touching nuget.org — publishing errors waste a permanent version number.\n\n> ⚠️ **Always mention this step**, even if you defer running it. Tell the user: \"Before your first publish, run `dotnet pack -c Release -o .\u002Fartifacts` to verify the .nupkg is created correctly.\"\n\n1. `dotnet pack -c Release -o .\u002Fartifacts` — verify `.nupkg` is created\n2. For tools\u002FMCP servers: install from `.\u002Fartifacts`, run `--help`, uninstall\n3. For libraries: inspect the `.nupkg` contents (it's a zip)\n\n### Phase 3: nuget.org Policy\n\nThis phase requires the user to act on nuget.org — guide them with exact values.\n\n1. Determine the **repo owner**, **repo name**, and the **workflow filename** that will publish.\n\n   > ❌ The policy requires the **exact workflow filename** (e.g., `publish.yml` or `publish.yaml`) — just the filename, no path prefix. Matching is case-insensitive. Don't use the workflow `name:` field.\n\n2. Guide the user to create the trusted publishing policy:\n   > Go to [**nuget.org\u002Faccount\u002Ftrustedpublishing**](https:\u002F\u002Fwww.nuget.org\u002Faccount\u002Ftrustedpublishing) → **Add policy**\n   >\n   > - **Repository Owner**: `{owner}`\n   > - **Repository**: `{repo}`\n   > - **Workflow File**: `{filename}.yml`\n   > - **Environment**: `release` *(only if the workflow uses `environment:`; leave blank otherwise)*\n\n   Policy ownership: the user chooses individual account or organization. Org-owned policies apply to all packages owned by that org.\n\n   For **private repos**: policy is \"temporarily active\" for 7 days — becomes permanent after the first successful publish.\n\n3. Guide the user to create a **GitHub Environment** (recommended but optional — provides secret scoping + approval gates):\n   > Repo **Settings** → **Environments** → **New environment** → `release`\n   >\n   > Add environment secret: **Name** = `NUGET_USER`, **Value** = nuget.org username (NOT email)\n\n   Optional: add **Required reviewers** for an approval gate.\n\n> ⚠️ Wait for the user to confirm they've created the policy **before asking them to remove old API keys\u002Fsecrets or before attempting to run\u002Fpublish with the workflow**. Drafting or showing the workflow file itself is OK before confirmation.\n\n### Phase 4: Workflow Setup\n\nCreate or modify the publish workflow. **The workflow must always be created or shown in your response** — you may draft\u002Fshow it even if the nuget.org policy is not yet confirmed, but do not guide the user to actually run\u002Fpublish or remove old secrets until after confirmation.\n\n**Greenfield**: Create `publish.yml` from the template in [references\u002Fpublish-workflow.md](references\u002Fpublish-workflow.md). Adapt .NET version, project path, and environment name. Ensure your output explicitly mentions `id-token: write` and `NuGet\u002Flogin@v1`.\n\n**Migration** (existing workflow with API key): Modify in place —\n\n1. **Add OIDC permission and environment** to the publishing job:\n   ```yaml\n   jobs:\n     publish:\n       environment: release\n       permissions:\n         id-token: write     # Required — without this, NuGet\u002Flogin fails with 403\n         contents: read      # Explicit — setting permissions overrides defaults\n   ```\n\n2. **Add the NuGet login step** before push:\n   ```yaml\n   - name: NuGet login (OIDC)\n     id: login\n     uses: NuGet\u002Flogin@v1\n     with:\n       user: ${{ secrets.NUGET_USER }}  # nuget.org profile name, NOT email\n   ```\n\n3. **Replace the API key** in the push step:\n   ```yaml\n   --api-key ${{ steps.login.outputs.NUGET_API_KEY }} --skip-duplicate\n   ```\n\n4. **Verify**: Ask the user to trigger a publish and confirm the package appears on nuget.org.\n\n> ❌ **Don't delete the old API key secret** until trusted publishing is verified. Removing it is a one-way door — wait for confirmation.\n\n## Troubleshooting\n\n| Problem | Cause | Fix |\n|---------|-------|-----|\n| `NuGet\u002Flogin` 403 | Missing `id-token: write` | Add to job permissions |\n| \"no matching policy\" | Workflow filename mismatch | Verify exact filename on nuget.org |\n| Push unauthorized | Package not owned by policy account | Check policy owner on nuget.org |\n| Token expired | Login step >1hr before push | Move `NuGet\u002Flogin` closer to push |\n| \"temporarily active\" policy | Private repo, first publish pending | Publish within 7 days |\n| `already_exists` on push | Re-running same version | Add `--skip-duplicate` |\n| GitHub Release 422 | Duplicate release for tag | Delete conflicting release (confirm first) |\n| Re-run uses wrong YAML | `gh run rerun` replays original commit's YAML | Delete obstacle, re-run — never re-tag |\n\n> ⚠️ If any blocker persists after one fix attempt, **stop and ask the user**.\n\n## References\n\n- **Package type details**: [references\u002Fpackage-types.md](references\u002Fpackage-types.md) — detection logic, required properties, minimal .csproj examples\n- **Publish workflow template**: [references\u002Fpublish-workflow.md](references\u002Fpublish-workflow.md) — complete tag-triggered workflow ready to adapt\n- **Microsoft docs**: [NuGet Trusted Publishing](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fnuget\u002Fnuget-org\u002Ftrusted-publishing)\n",{"name":5,"license":15,"description":24},"Set up NuGet trusted publishing (OIDC) on a GitHub Actions repo — replaces long-lived API keys with short-lived tokens. USE FOR: trusted publishing, NuGet OIDC, keyless NuGet publish, migrate from NuGet API key, NuGet\u002Flogin, secure NuGet publishing. DO NOT USE FOR: publishing to private feeds or Azure Artifacts (OIDC is nuget.org only). INVOKES: shell (powershell or bash), edit, create, ask_user for guided repo setup.\n","master","49e49abf2f670d429e0b7e2c0349739c3fdd5cbe","skills\u002Fnuget-trusted-publishing",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":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add stanfish06\u002Fskillquarium --skill nuget-trusted-publishing",{"tool":39,"command":40},"bunx","bunx skills add stanfish06\u002Fskillquarium --skill nuget-trusted-publishing",{"tool":42,"command":43},"pnpm","pnpm dlx skills add stanfish06\u002Fskillquarium --skill nuget-trusted-publishing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fnuget-trusted-publishing\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fpackage-types.md","REFERENCE","参考文档",8446,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fnuget-trusted-publishing\u002Freferences\u002Fpackage-types.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fpublish-workflow.md",3910,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fnuget-trusted-publishing\u002Freferences\u002Fpublish-workflow.md",[58,65,74,81,88,95],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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",[],[]]