[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698Z47JBA4W1XC0A96WXB8K":3,"skill-same:01M698Z47JBA4W1XC0A96WXB8K":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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M698Z47JBA4W1XC0A96WXB8K","update-gvisor-maintainers",null,"Update the gVisor maintainer roster in governance\u002Fmaintainers.yaml or the specialization areas in governance\u002Fareas.yaml, and regenerate the files derived from them (MAINTAINERS.md and CODEOWNERS). Use when a maintainer goes on hiatus, returns from hiatus, is added, steps down to emeritus, changes employer or specialization, or when MAINTAINERS.md \u002F CODEOWNERS are out of sync.","google\u002Fgvisor","google","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1342004?v=4","01M698VYEFDM0VJBZDYYJ2T83S","Google","01M698YX0KM1V8AAGJQZXZD6T7",20002,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fgvisor\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fupdate-gvisor-maintainers\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"update gvisor maintainers","update","maintainers","gvisor","sync","governance","yaml","returns","use","files","codeowners","roster","goes","changes","down","when","2026-11-10 10:12:30",false,"---\nname: update-gvisor-maintainers\ndescription: >\n  Update the gVisor maintainer roster in governance\u002Fmaintainers.yaml or the\n  specialization areas in governance\u002Fareas.yaml, and regenerate the files derived\n  from them (MAINTAINERS.md and CODEOWNERS).\n  Use when a maintainer goes on hiatus, returns from hiatus, is added, steps down to\n  emeritus, changes employer or specialization, or when MAINTAINERS.md \u002F\n  CODEOWNERS are out of sync.\n---\n\n# Update the gVisor maintainer roster\n\n`governance\u002Fmaintainers.yaml` (the roster) and `governance\u002Fareas.yaml`\n(specialization areas) are the sources of truth. Reviewer assignment and the Go\ngenerator read the same area data. The generator produces `MAINTAINERS.md` and\n`CODEOWNERS`. Edit the source data, regenerate, and run the comparison tests. Do\nnot hand-edit generated files.\n\n## Schema\n\nEach entry under `maintainers:`:\n\n```yaml\n  - name: Gee Vaïzaur           # Full name or nickname.\n    github: gvaizaur            # GitHub username.\n    github_id: 123456789        # GitHub user ID.\n    affiliation: Independent    # Current employer, or \"Independent\".\n    past_affiliation:           # Optional.\n      - affiliation: Arasaka Corporation\n        until: 2025-03-01\n    started: 2018-05-08         # First contribution. The list is sorted by this.\n    status: HIATUS_SINCE:2026-07-17\n    areas: [gpu, networking]    # Optional. Sorted area names from areas.yaml;\n                                # grants CODEOWNERS ownership of the paths of\n                                # areas with enforced_review. Not for emeritus.\n```\n\nEach entry under `areas:` in `areas.yaml`:\n\n```yaml\n  - name: gpu                   # Sorted by name.\n    enforced_review: false      # Required. `true` generates a CODEOWNERS\n                                # section for the area, making\n                                # specialized-maintainer review mandatory.\n                                # Needs at least one non-emeritus maintainer\n                                # with the area.\n    paths:                      # Repo-root-relative dirs (\u002Flike\u002Fthis), no\n      - \u002Fimages\u002Fgpu             # trailing slash. Each path in one area only.\n```\n\n`status` is one of three, and it drives everything downstream:\n\nStatus                      | Reviews | Merge permissions | `MAINTAINERS.md`\n--------------------------- | ------- | ----------------- | ----------------\n`ACTIVE`                    | yes     | yes               | main table\n`HIATUS_SINCE:YYYY-MM-DD`   | no      | yes               | main table\n`EMERITUS_SINCE:YYYY-MM-DD` | no      | no                | emeritus table\n\nThe review-assignment workflow reads the roster directly and selects only active\nmaintainers. Hiatus affects review assignment, not merge permissions or\nmembership in the main maintainer table.\n\n## Common changes\n\nMost of these are a one-line `status:` edit on an existing entry:\n\n-   Goes on hiatus: `status: HIATUS_SINCE:\u003Ctoday>`.\n-   Comes back from hiatus: `status: ACTIVE`. Drop the date; `ACTIVE` never\n    carries one.\n-   Steps down, or hits 12 months of inactivity: `status:\n    EMERITUS_SINCE:\u003Cdate>`.\n-   Comes back from emeritus: `status: ACTIVE`, but only through the normal\n    nomination process. See \"Becoming a maintainer\" in `GOVERNANCE.md`.\n\nThe two that are not:\n\n-   New maintainer: insert the entry in `started` order, not at the end of the\n    file. Look up `github_id` rather than guessing it.\n-   Changed employer: update `affiliation`, and move the old one to\n    `past_affiliation` with the date it ended as `until`.\n\nDates are real calendar dates, so go look up today's date rather than guessing\nat one. If the user gave you a date, use theirs.\n\nAfter any change, regenerate.\n\n## Regenerate\n\n```bash\nmake governance-regen\n```\n\nThis regenerates both files in place.\n\nThen:\n\n```bash\nmake governance-check\n```\n\nThis fails if the source data changed and you forgot to regenerate, or if\nsomeone edited a generated file by hand.\n\n## Before handing back\n\nShow the user the diff across all changed files (`governance\u002Fmaintainers.yaml`,\n`governance\u002Fareas.yaml`, `MAINTAINERS.md`, `CODEOWNERS`) and let them confirm\nthe roster reads the way they meant it to.\n\nIf a generated file contains something the generator does not emit, that content\nis drift, and regenerating is what removes it. Do not teach the generator to\nreproduce it without asking first: the generator decides what those files\ncontain, not whatever happened to be committed.\n","# Update the gVisor maintainer roster\n\n`governance\u002Fmaintainers.yaml` (the roster) and `governance\u002Fareas.yaml`\n(specialization areas) are the sources of truth. Reviewer assignment and the Go\ngenerator read the same area data. The generator produces `MAINTAINERS.md` and\n`CODEOWNERS`. Edit the source data, regenerate, and run the comparison tests. Do\nnot hand-edit generated files.\n\n## Schema\n\nEach entry under `maintainers:`:\n\n```yaml\n  - name: Gee Vaïzaur           # Full name or nickname.\n    github: gvaizaur            # GitHub username.\n    github_id: 123456789        # GitHub user ID.\n    affiliation: Independent    # Current employer, or \"Independent\".\n    past_affiliation:           # Optional.\n      - affiliation: Arasaka Corporation\n        until: 2025-03-01\n    started: 2018-05-08         # First contribution. The list is sorted by this.\n    status: HIATUS_SINCE:2026-07-17\n    areas: [gpu, networking]    # Optional. Sorted area names from areas.yaml;\n                                # grants CODEOWNERS ownership of the paths of\n                                # areas with enforced_review. Not for emeritus.\n```\n\nEach entry under `areas:` in `areas.yaml`:\n\n```yaml\n  - name: gpu                   # Sorted by name.\n    enforced_review: false      # Required. `true` generates a CODEOWNERS\n                                # section for the area, making\n                                # specialized-maintainer review mandatory.\n                                # Needs at least one non-emeritus maintainer\n                                # with the area.\n    paths:                      # Repo-root-relative dirs (\u002Flike\u002Fthis), no\n      - \u002Fimages\u002Fgpu             # trailing slash. Each path in one area only.\n```\n\n`status` is one of three, and it drives everything downstream:\n\nStatus                      | Reviews | Merge permissions | `MAINTAINERS.md`\n--------------------------- | ------- | ----------------- | ----------------\n`ACTIVE`                    | yes     | yes               | main table\n`HIATUS_SINCE:YYYY-MM-DD`   | no      | yes               | main table\n`EMERITUS_SINCE:YYYY-MM-DD` | no      | no                | emeritus table\n\nThe review-assignment workflow reads the roster directly and selects only active\nmaintainers. Hiatus affects review assignment, not merge permissions or\nmembership in the main maintainer table.\n\n## Common changes\n\nMost of these are a one-line `status:` edit on an existing entry:\n\n-   Goes on hiatus: `status: HIATUS_SINCE:\u003Ctoday>`.\n-   Comes back from hiatus: `status: ACTIVE`. Drop the date; `ACTIVE` never\n    carries one.\n-   Steps down, or hits 12 months of inactivity: `status:\n    EMERITUS_SINCE:\u003Cdate>`.\n-   Comes back from emeritus: `status: ACTIVE`, but only through the normal\n    nomination process. See \"Becoming a maintainer\" in `GOVERNANCE.md`.\n\nThe two that are not:\n\n-   New maintainer: insert the entry in `started` order, not at the end of the\n    file. Look up `github_id` rather than guessing it.\n-   Changed employer: update `affiliation`, and move the old one to\n    `past_affiliation` with the date it ended as `until`.\n\nDates are real calendar dates, so go look up today's date rather than guessing\nat one. If the user gave you a date, use theirs.\n\nAfter any change, regenerate.\n\n## Regenerate\n\n```bash\nmake governance-regen\n```\n\nThis regenerates both files in place.\n\nThen:\n\n```bash\nmake governance-check\n```\n\nThis fails if the source data changed and you forgot to regenerate, or if\nsomeone edited a generated file by hand.\n\n## Before handing back\n\nShow the user the diff across all changed files (`governance\u002Fmaintainers.yaml`,\n`governance\u002Fareas.yaml`, `MAINTAINERS.md`, `CODEOWNERS`) and let them confirm\nthe roster reads the way they meant it to.\n\nIf a generated file contains something the generator does not emit, that content\nis drift, and regenerating is what removes it. Do not teach the generator to\nreproduce it without asking first: the generator decides what those files\ncontain, not whatever happened to be committed.\n",{"name":5,"description":7},"master","aa767e4c43d011121271551fe24da501a56f729d",".agents\u002Fskills\u002Fupdate-gvisor-maintainers",2078,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fgvisor","https:\u002F\u002Fgvisor.dev","https:\u002F\u002Fgithub.com\u002Fgoogle","https:\u002F\u002Fopensource.google\u002F","Google ❤️ Open Source","2026-11-15 02:45:30",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add google\u002Fgvisor --skill update-gvisor-maintainers",{"tool":56,"command":57},"bunx","bunx skills add google\u002Fgvisor --skill update-gvisor-maintainers",{"tool":59,"command":60},"pnpm","pnpm dlx skills add google\u002Fgvisor --skill update-gvisor-maintainers","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fgvisor\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fupdate-gvisor-maintainers\u002FSKILL.md",true,[],[65,93],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":35},"01M698Z2GWDYSWWESR8FYDTB1P","gvisor-performance","Use when modifying gVisor in ways with potential performance implications; as a kernel, gVisor's performance matters almost as much as its security. Load imperatively when editing this performance-sensitive code:\n\n  * Syscall hot path: `pkg\u002Fsentry\u002Fkernel` (`task_run.go`, `task_syscall.go`),\n    `pkg\u002Fsentry\u002Fsyscalls\u002Flinux`, and app-memory copy layers\n    (`pkg\u002Fusermem`, `pkg\u002Fsafemem`, `pkg\u002Fsafecopy`, `pkg\u002Fmarshal`).\n  * Platform: `pkg\u002Fsentry\u002Fplatform`, `pkg\u002Fring0`.\n  * Sandbox startup: `runsc\u002Fboot`, `runsc\u002Fcontainer`, `runsc\u002Fsandbox`.\n  * Serialization and checkpoint\u002Frestore: `pkg\u002Fstate`, `pkg\u002Fsentry\u002Fstate`.\n  * Netstack: `pkg\u002Ftcpip`.\n  * File I\u002FO: `pkg\u002Fsentry\u002Fvfs`, `pkg\u002Fsentry\u002Ffsimpl`.\n  * Memory management: `pkg\u002Fsentry\u002Fmm`, `pkg\u002Fsentry\u002Fpgalloc`.\n  * Gofer IPC: `pkg\u002Flisafs`, `runsc\u002Ffsgofer`.\n  * Go `init()` functions, which run on every binary startup.\n\nAlso load for any change with potential performance impact, even outside these paths.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fgvisor\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fgvisor-performance\u002FSKILL.md",[],[22,72,73,74,75,76,77,78,79,34,80,81,82,83,84,85,86,87,88,89,90,91,92],"performance","gvisor performance","code","sentry","which","memory","init","impact","change","run","paths","security","marshal","path","mm","as","app","linux","kernel","go","sandbox",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":35},"01M698Z06KDHZGY585SB25C56E","gvisor-kernel-development","Use when modifying gVisor application kernel behavior: adding a new system call, adding new flags to an existing system call, editing the syscall tests in `\u002F\u002Ftest\u002Fsyscalls`.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fgvisor\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fgvisor-kernel-development\u002FSKILL.md",[],[100,90,22,101,102,103,104,105,34,106,27,107,108,109,110],"development","gvisor kernel development","application","flags","behavior","test","Existing","call","tests","system","editing"]