[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75F9Q2PC34HBX25E6R2CPCM":3,"skill-same:01M75F9Q2PC34HBX25E6R2CPCM":64},{"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},"01M75F9Q2PC34HBX25E6R2CPCM","alerting-irm",null,"Configure Grafana Alerting, Incident Response Management (IRM), and SLOs end-to-end — provisions Grafana-managed and data-source-managed alert rules, contact points (Slack\u002FPagerDuty\u002Femail\u002Fwebhook), notification policies with hierarchical matchers, silences, mute timings, on-call schedules and escalation chains, incident-management integrations, and SLOs with multi-window burn-rate alerts. Use when configuring alerts, debugging notification routing, setting up on-call rotations, declaring or managing incidents, defining SLOs, provisioning alerting via YAML or API, picking matchers for a notification policy, building a PagerDuty\u002FSlack webhook receiver, or troubleshooting why an alert isn't firing — even when the user says \"page me on errors\", \"alert me when X happens\", \"route this to the platform team\", or \"set up an SLO\" without naming Alerting or IRM.","stanfish06\u002Fskillquarium","stanfish06","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F93099613?v=4","01M75F1CK4ZW109ZK3T26VN52F","Zhiyuan","01M75F1CM53VH6F79DZ8GXKKES",12,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Falerting-irm\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: alerting-irm\nlicense: Apache-2.0\ndescription: Configure Grafana Alerting, Incident Response Management (IRM), and SLOs end-to-end — provisions Grafana-managed and data-source-managed alert rules, contact points (Slack\u002FPagerDuty\u002Femail\u002Fwebhook), notification policies with hierarchical matchers, silences, mute timings, on-call schedules and escalation chains, incident-management integrations, and SLOs with multi-window burn-rate alerts. Use when configuring alerts, debugging notification routing, setting up on-call rotations, declaring or managing incidents, defining SLOs, provisioning alerting via YAML or API, picking matchers for a notification policy, building a PagerDuty\u002FSlack webhook receiver, or troubleshooting why an alert isn't firing — even when the user says \"page me on errors\", \"alert me when X happens\", \"route this to the platform team\", or \"set up an SLO\" without naming Alerting or IRM.\n---\n\n# Grafana Alerting & IRM\n\n> **Docs**: https:\u002F\u002Fgrafana.com\u002Fdocs\u002Fgrafana\u002Flatest\u002Falerting.md\n\n## Common Workflows\n\n### Provisioning a new alert end-to-end\n\n1. **Create contact points** (where notifications go):\n   ```bash\n   curl -X POST https:\u002F\u002Fgrafana.example.com\u002Fapi\u002Fv1\u002Fprovisioning\u002Fcontact-points \\\n     -H 'Authorization: Bearer \u003Ctoken>' -H 'Content-Type: application\u002Fjson' \\\n     -d @contact-points.json\n   ```\n   Verify:\n   ```bash\n   curl https:\u002F\u002Fgrafana.example.com\u002Fapi\u002Fv1\u002Fprovisioning\u002Fcontact-points \\\n     -H 'Authorization: Bearer \u003Ctoken>' | jq '.[].name'\n   ```\n\n2. **Add notification policies** (which alerts go where) — see [§ Notification policies](#notification-policies) below for the matchers pattern.\n\n3. **Write the alert rule** — pick the type:\n   - Grafana-managed → see [references\u002Falerting.md § Grafana-managed alert rule](references\u002Falerting.md#grafana-managed-alert-rule-yaml-provisioning)\n   - Prometheus\u002FMimir ruler → see [references\u002Falerting.md § Prometheus \u002F Mimir alert rule](references\u002Falerting.md#prometheus--mimir-alert-rule-ruler)\n   - Loki LogQL → see [references\u002Falerting.md § Loki alert rule](references\u002Falerting.md#loki-alert-rule-logql)\n\n4. **Verify routing** before going live:\n   ```bash\n   # Force-fire a test alert from the rule's UI, then check Alertmanager's view\n   curl https:\u002F\u002Fgrafana.example.com\u002Fapi\u002Falertmanager\u002Fgrafana\u002Fapi\u002Fv2\u002Falerts \\\n     -H 'Authorization: Bearer \u003Ctoken>' | jq '.[] | {alertname: .labels.alertname, receiver: .receivers}'\n   ```\n   The expected receiver should appear. If the wrong receiver appears, re-check the policy's matchers.\n\n### Routing alerts to IRM \u002F on-call\n\n1. In IRM, create an Integration of type \"Grafana Alerting webhook\" → copy the integration URL\n2. Add a webhook contact point in Grafana Alerting pointing at that URL (full YAML in [references\u002Firm.md § Routing](references\u002Firm.md#routing-from-grafana-alerting-to-irm))\n3. Add a notification policy matcher routing the right severity to the new contact point\n4. Verify: trigger a test alert; it should appear in IRM within ~30s. Full debug procedure in [references\u002Firm.md § Verifying the IRM integration](references\u002Firm.md#verifying-the-irm-integration).\n\n### Defining an SLO\n\n1. Create the SLO via UI or API → Grafana auto-generates recording rules, dashboards, and burn-rate alerts (the generated YAML is in [references\u002Fslo.md](references\u002Fslo.md))\n2. **Use multi-window burn-rate alerts**, not single-window — see [references\u002Fslo.md § Multi-window burn-rate alerts](references\u002Fslo.md#multi-window-burn-rate-alerts-recommended) for why single-window fires on noise\n3. Verify with the 4-step pattern in [references\u002Fslo.md § Validating SLO config](references\u002Fslo.md#validating-slo-config)\n\n## Contact Points (YAML provisioning)\n\n```yaml\n# provisioning\u002Falerting\u002Fcontact_points.yaml\napiVersion: 1\ncontactPoints:\n  - orgId: 1\n    name: pagerduty-critical\n    receivers:\n      - uid: pd-receiver\n        type: pagerduty\n        settings:\n          integrationKey: YOUR_PAGERDUTY_KEY\n          severity: critical\n\n  - orgId: 1\n    name: slack-alerts\n    receivers:\n      - uid: slack-receiver\n        type: slack\n        settings:\n          url: https:\u002F\u002Fhooks.slack.com\u002Fservices\u002FYOUR\u002FWEBHOOK\u002FURL\n          channel: '#alerts'\n```\n\nFor email, webhook, Teams, Telegram, OnCall, and other receiver types, see [references\u002Falerting.md § Contact point receiver types](references\u002Falerting.md#contact-point-receiver-types).\n\n## Notification policies\n\nHierarchical routing tree with label matchers:\n\n```yaml\n# provisioning\u002Falerting\u002Fnotification_policies.yaml\napiVersion: 1\npolicies:\n  - orgId: 1\n    receiver: default-receiver\n    group_by: ['alertname', 'cluster', 'service']\n    group_wait: 30s\n    group_interval: 5m\n    repeat_interval: 12h\n    routes:\n      # Critical alerts → PagerDuty\n      - receiver: pagerduty-critical\n        matchers:\n          - severity = critical\n        group_wait: 10s\n        repeat_interval: 4h\n\n      # Platform team → Slack, but page on critical\n      - receiver: slack-alerts\n        matchers:\n          - team = platform\n        routes:\n          - receiver: pagerduty-critical\n            matchers:\n              - severity = critical\n\n      # Everything else → email\n      - receiver: email-alerts\n        matchers:\n          - severity =~ \"warning|info\"\n```\n\n## Silences\n\nSuppress notifications for matching alerts without stopping evaluation:\n\n```bash\ncurl -X POST https:\u002F\u002Fgrafana.example.com\u002Fapi\u002Falertmanager\u002Fgrafana\u002Fapi\u002Fv2\u002Fsilences \\\n  -H 'Authorization: Bearer \u003Ctoken>' \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d '{\n    \"matchers\": [\n      {\"name\": \"alertname\", \"value\": \"HighErrorRate\", \"isRegex\": false},\n      {\"name\": \"env\", \"value\": \"staging\", \"isRegex\": false}\n    ],\n    \"startsAt\": \"2024-01-01T00:00:00Z\",\n    \"endsAt\": \"2024-01-01T02:00:00Z\",\n    \"comment\": \"Maintenance window\",\n    \"createdBy\": \"admin\"\n  }'\n\n# Verify it was created\ncurl https:\u002F\u002Fgrafana.example.com\u002Fapi\u002Falertmanager\u002Fgrafana\u002Fapi\u002Fv2\u002Fsilences \\\n  -H 'Authorization: Bearer \u003Ctoken>' | jq '.[] | select(.status.state == \"active\")'\n```\n\n## Alert rule states\n\n| State | Description |\n|-------|-------------|\n| **Normal** | Condition not met |\n| **Pending** | Condition met, waiting for `for` duration |\n| **Firing** | Condition met for full `for` duration |\n| **NoData** | Query returned no data |\n| **Error** | Query\u002Fevaluation error |\n| **Recovering** | Was firing, condition no longer met |\n\n## Provisioning directory layout\n\n```\nprovisioning\u002Falerting\u002F\n├── alert_rules.yaml          # Alert and recording rules\n├── contact_points.yaml       # Notification destinations\n├── notification_policies.yaml  # Routing tree\n├── templates.yaml            # Message templates\n└── mute_timings.yaml         # Recurring mute windows\n```\n\n## API provisioning (keeps UI editable)\n\nAdd `X-Disable-Provenance: true` to keep resources editable in the UI after API provisioning:\n\n```bash\ncurl -X PUT https:\u002F\u002Fgrafana.example.com\u002Fapi\u002Fv1\u002Fprovisioning\u002Fpolicies \\\n  -H 'Authorization: Bearer \u003Ctoken>' \\\n  -H 'X-Disable-Provenance: true' \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d @policy.json\n\ncurl -X POST https:\u002F\u002Fgrafana.example.com\u002Fapi\u002Fv1\u002Fprovisioning\u002Falert-rules \\\n  -H 'Authorization: Bearer \u003Ctoken>' \\\n  -H 'X-Disable-Provenance: true' \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d @rule.json\n```\n\n## References\n\n- [`references\u002Falerting.md`](references\u002Falerting.md) — full alert rule YAML (Grafana-managed \u002F Prometheus \u002F Loki) + notification templates\n- [`references\u002Fslo.md`](references\u002Fslo.md) — generated SLO recording rules + multi-window burn-rate alert pattern + validation steps\n- [`references\u002Firm.md`](references\u002Firm.md) — IRM capabilities, integration sources, Alerting → IRM routing + verification + common failure modes\n","# Grafana Alerting & IRM\n\n> **Docs**: https:\u002F\u002Fgrafana.com\u002Fdocs\u002Fgrafana\u002Flatest\u002Falerting.md\n\n## Common Workflows\n\n### Provisioning a new alert end-to-end\n\n1. **Create contact points** (where notifications go):\n   ```bash\n   curl -X POST https:\u002F\u002Fgrafana.example.com\u002Fapi\u002Fv1\u002Fprovisioning\u002Fcontact-points \\\n     -H 'Authorization: Bearer \u003Ctoken>' -H 'Content-Type: application\u002Fjson' \\\n     -d @contact-points.json\n   ```\n   Verify:\n   ```bash\n   curl https:\u002F\u002Fgrafana.example.com\u002Fapi\u002Fv1\u002Fprovisioning\u002Fcontact-points \\\n     -H 'Authorization: Bearer \u003Ctoken>' | jq '.[].name'\n   ```\n\n2. **Add notification policies** (which alerts go where) — see [§ Notification policies](#notification-policies) below for the matchers pattern.\n\n3. **Write the alert rule** — pick the type:\n   - Grafana-managed → see [references\u002Falerting.md § Grafana-managed alert rule](references\u002Falerting.md#grafana-managed-alert-rule-yaml-provisioning)\n   - Prometheus\u002FMimir ruler → see [references\u002Falerting.md § Prometheus \u002F Mimir alert rule](references\u002Falerting.md#prometheus--mimir-alert-rule-ruler)\n   - Loki LogQL → see [references\u002Falerting.md § Loki alert rule](references\u002Falerting.md#loki-alert-rule-logql)\n\n4. **Verify routing** before going live:\n   ```bash\n   # Force-fire a test alert from the rule's UI, then check Alertmanager's view\n   curl https:\u002F\u002Fgrafana.example.com\u002Fapi\u002Falertmanager\u002Fgrafana\u002Fapi\u002Fv2\u002Falerts \\\n     -H 'Authorization: Bearer \u003Ctoken>' | jq '.[] | {alertname: .labels.alertname, receiver: .receivers}'\n   ```\n   The expected receiver should appear. If the wrong receiver appears, re-check the policy's matchers.\n\n### Routing alerts to IRM \u002F on-call\n\n1. In IRM, create an Integration of type \"Grafana Alerting webhook\" → copy the integration URL\n2. Add a webhook contact point in Grafana Alerting pointing at that URL (full YAML in [references\u002Firm.md § Routing](references\u002Firm.md#routing-from-grafana-alerting-to-irm))\n3. Add a notification policy matcher routing the right severity to the new contact point\n4. Verify: trigger a test alert; it should appear in IRM within ~30s. Full debug procedure in [references\u002Firm.md § Verifying the IRM integration](references\u002Firm.md#verifying-the-irm-integration).\n\n### Defining an SLO\n\n1. Create the SLO via UI or API → Grafana auto-generates recording rules, dashboards, and burn-rate alerts (the generated YAML is in [references\u002Fslo.md](references\u002Fslo.md))\n2. **Use multi-window burn-rate alerts**, not single-window — see [references\u002Fslo.md § Multi-window burn-rate alerts](references\u002Fslo.md#multi-window-burn-rate-alerts-recommended) for why single-window fires on noise\n3. Verify with the 4-step pattern in [references\u002Fslo.md § Validating SLO config](references\u002Fslo.md#validating-slo-config)\n\n## Contact Points (YAML provisioning)\n\n```yaml\n# provisioning\u002Falerting\u002Fcontact_points.yaml\napiVersion: 1\ncontactPoints:\n  - orgId: 1\n    name: pagerduty-critical\n    receivers:\n      - uid: pd-receiver\n        type: pagerduty\n        settings:\n          integrationKey: YOUR_PAGERDUTY_KEY\n          severity: critical\n\n  - orgId: 1\n    name: slack-alerts\n    receivers:\n      - uid: slack-receiver\n        type: slack\n        settings:\n          url: https:\u002F\u002Fhooks.slack.com\u002Fservices\u002FYOUR\u002FWEBHOOK\u002FURL\n          channel: '#alerts'\n```\n\nFor email, webhook, Teams, Telegram, OnCall, and other receiver types, see [references\u002Falerting.md § Contact point receiver types](references\u002Falerting.md#contact-point-receiver-types).\n\n## Notification policies\n\nHierarchical routing tree with label matchers:\n\n```yaml\n# provisioning\u002Falerting\u002Fnotification_policies.yaml\napiVersion: 1\npolicies:\n  - orgId: 1\n    receiver: default-receiver\n    group_by: ['alertname', 'cluster', 'service']\n    group_wait: 30s\n    group_interval: 5m\n    repeat_interval: 12h\n    routes:\n      # Critical alerts → PagerDuty\n      - receiver: pagerduty-critical\n        matchers:\n          - severity = critical\n        group_wait: 10s\n        repeat_interval: 4h\n\n      # Platform team → Slack, but page on critical\n      - receiver: slack-alerts\n        matchers:\n          - team = platform\n        routes:\n          - receiver: pagerduty-critical\n            matchers:\n              - severity = critical\n\n      # Everything else → email\n      - receiver: email-alerts\n        matchers:\n          - severity =~ \"warning|info\"\n```\n\n## Silences\n\nSuppress notifications for matching alerts without stopping evaluation:\n\n```bash\ncurl -X POST https:\u002F\u002Fgrafana.example.com\u002Fapi\u002Falertmanager\u002Fgrafana\u002Fapi\u002Fv2\u002Fsilences \\\n  -H 'Authorization: Bearer \u003Ctoken>' \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d '{\n    \"matchers\": [\n      {\"name\": \"alertname\", \"value\": \"HighErrorRate\", \"isRegex\": false},\n      {\"name\": \"env\", \"value\": \"staging\", \"isRegex\": false}\n    ],\n    \"startsAt\": \"2024-01-01T00:00:00Z\",\n    \"endsAt\": \"2024-01-01T02:00:00Z\",\n    \"comment\": \"Maintenance window\",\n    \"createdBy\": \"admin\"\n  }'\n\n# Verify it was created\ncurl https:\u002F\u002Fgrafana.example.com\u002Fapi\u002Falertmanager\u002Fgrafana\u002Fapi\u002Fv2\u002Fsilences \\\n  -H 'Authorization: Bearer \u003Ctoken>' | jq '.[] | select(.status.state == \"active\")'\n```\n\n## Alert rule states\n\n| State | Description |\n|-------|-------------|\n| **Normal** | Condition not met |\n| **Pending** | Condition met, waiting for `for` duration |\n| **Firing** | Condition met for full `for` duration |\n| **NoData** | Query returned no data |\n| **Error** | Query\u002Fevaluation error |\n| **Recovering** | Was firing, condition no longer met |\n\n## Provisioning directory layout\n\n```\nprovisioning\u002Falerting\u002F\n├── alert_rules.yaml          # Alert and recording rules\n├── contact_points.yaml       # Notification destinations\n├── notification_policies.yaml  # Routing tree\n├── templates.yaml            # Message templates\n└── mute_timings.yaml         # Recurring mute windows\n```\n\n## API provisioning (keeps UI editable)\n\nAdd `X-Disable-Provenance: true` to keep resources editable in the UI after API provisioning:\n\n```bash\ncurl -X PUT https:\u002F\u002Fgrafana.example.com\u002Fapi\u002Fv1\u002Fprovisioning\u002Fpolicies \\\n  -H 'Authorization: Bearer \u003Ctoken>' \\\n  -H 'X-Disable-Provenance: true' \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d @policy.json\n\ncurl -X POST https:\u002F\u002Fgrafana.example.com\u002Fapi\u002Fv1\u002Fprovisioning\u002Falert-rules \\\n  -H 'Authorization: Bearer \u003Ctoken>' \\\n  -H 'X-Disable-Provenance: true' \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d @rule.json\n```\n\n## References\n\n- [`references\u002Falerting.md`](references\u002Falerting.md) — full alert rule YAML (Grafana-managed \u002F Prometheus \u002F Loki) + notification templates\n- [`references\u002Fslo.md`](references\u002Fslo.md) — generated SLO recording rules + multi-window burn-rate alert pattern + validation steps\n- [`references\u002Firm.md`](references\u002Firm.md) — IRM capabilities, integration sources, Alerting → IRM routing + verification + common failure modes\n",{"name":5,"license":15,"description":7},"master","49e49abf2f670d429e0b7e2c0349739c3fdd5cbe","skills\u002Falerting-irm",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 alerting-irm",{"tool":38,"command":39},"bunx","bunx skills add stanfish06\u002Fskillquarium --skill alerting-irm",{"tool":41,"command":42},"pnpm","pnpm dlx skills add stanfish06\u002Fskillquarium --skill alerting-irm","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Falerting-irm\u002FSKILL.md",true,[46,52,56,60],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",160,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Falerting-irm\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Falerting.md",4705,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Falerting-irm\u002Freferences\u002Falerting.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Firm.md",2234,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Falerting-irm\u002Freferences\u002Firm.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fslo.md",2110,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Falerting-irm\u002Freferences\u002Fslo.md",[65,73,81,88,95,102],{"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":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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.","MIT","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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.","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":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},"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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":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":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"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",[],[]]