[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698Z06KDHZGY585SB25C56E":3,"skill-same:01M698Z06KDHZGY585SB25C56E":63},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M698Z06KDHZGY585SB25C56E","gvisor-kernel-development",null,"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`.","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\u002Fgvisor-kernel-development\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"gvisor kernel development","development","kernel","gvisor","editing","system","tests","call","use","Existing","when","test","behavior","flags","application","2026-11-10 10:12:30",false,"---\nname: gvisor-kernel-development\ndescription: >\n  Use when modifying gVisor application kernel behavior:\n  adding a new system call, adding new flags to an existing\n  system call, editing the syscall tests in `\u002F\u002Ftest\u002Fsyscalls`.\n---\n\nWhen modifying or expanding the way the gVisor kernel works, such as when\nimplementing a new system call, adding a new flag to an existing system call, or\nmodifying the way an existing system call works, you should generally follow\nthis approach:\n\n1.  Repeat your understanding of this aspect of the Linux kernel functionality.\n2.  If applicable, come up with a way to quickly test and exercise the relevant\n    kernel functionality by using a shell command or a short Python script. For\n    example, if asked to change the way the `stat(2)` system call works on a\n    specific device file like `\u002Fdev\u002Fzero`, you can use `stat \u002Fdev\u002Fzero` as a\n    representative command for which the output can guide your understanding of\n    the way the kernel works. See the \"Running a C program in gVisor\" section\n    below for how to run it. Syscall tests are also appropriate and excellent at\n    establishing coverage of all the edge cases a syscall may have; during\n    development, both are useful.\n3.  Before you look at any gVisor code, start by establishing a black-box\n    understanding of the current behavior of both Linux and gVisor for the\n    representative command or script you have come up with. Use the tools\n    available at your disposal to verify this.\n4.  If asked to modify the behavior of a specific system call, look for existing\n    syscall tests that cover this syscall. Read the syscall test file, and run\n    it under both Linux and gVisor at least once to make sure it is starting\n    from a good state to begin with.\n5.  Only after you have done the above, start reading gVisor kernel source code.\n    Do not stop at the first file you think is most likely to implement the\n    functionality you want to implement; look for multiple such files and only\n    settle on a decision once you are confident about your decision.\n6.  Make code changes, running your representative command or script or syscall\n    tests as often as necessary.\n\nNOTE: None of the above involves reading Linux source code. You **must not**\nread nor refer to Linux source code or Linux `man` pages, as they are often\nwrong or out-of-date. Therefore, gVisor exclusively uses black-box C++ syscall\ntests to assert Linux behavior, and you should use this approach exclusively in\norder to build up your understanding of the behavior of the syscall. When\nreviewing compatibility code, you should also follow this approach.\n\n### Running gVisor development workflows\n\n#### Running a C program in gVisor\n\nDuring development, to verify more complex syscall behavior in gVisor, it may be\nuseful to write a custom program in C that calls system calls directly, then to\ncompile it, and to run it in Linux and in gVisor.\n\nTo do so, generate a dependency-free C program, compile it with `gcc`, move it\nto a temporary directory such as `\u002Ftmp` (important: gVisor cannot directly run\nfrom special directories such as `bazel-bin` due to uninteresting permission\nissues), then use `runsc`'s `do` helper as follows:\n\n```\n# Recompile and extract to a world-accessible directory:\n$ make release-tarball DESTINATION=out\u002F && mkdir -p \u002Ftmp\u002Fgvisor && tar -C \u002Ftmp\u002Fgvisor -xf out\u002Fgvisor.tar.bz2\n\n# Run:\n$ \u002Ftmp\u002Fgvisor\u002Frunsc --rootless=true --network=none --debug-log=\u002Fdev\u002Fstderr --strace=true do \u002Fabsolute\u002Fpath\u002Fto\u002Fthe\u002Fbinary\n```\n\nThis will run `\u002Fabsolute\u002Fpath\u002Fto\u002Fthe\u002Fbinary` inside gVisor, with debug logs and\nthe syscall trace (strace) output included. Don't forget to also run it under\nLinux so that you can compare its behavior.\n\n#### Running syscall tests\n\nAs gVisor is a kernel meant to replicate Linux-like behavior,\n**application-observable kernel behavior is not tested with Go unit tests**, and\nyou should not add such tests for it. Go unit tests are only appropriate for\nself-contained internals with no Linux behavior to compare against. Instead, the\ngVisor kernel behavior is tested by \"syscall tests\", which are C++ test binaries\nwhich can be run either in Linux and in gVisor. These syscall test binaries call\nsome system calls in the kernel they are run in (either Linux or gVisor), and\nverify that the system call behaves in the same expected way.\n\nThese tests are defined in `\u002F\u002Ftest\u002Fsyscalls\u002Flinux` as `.cc`.\n\nIf you change or add a syscall test, you should first run it under Linux to make\nsure that the syscall test works properly under Linux. A syscall test that fails\nunder Linux reflects a problem with the test itself, not a problem in gVisor. If\nthis happens, fix the syscall test C++ program itself. Example:\n\n```\nmake syscall-tests TARGETS=\"\u002F\u002Ftest\u002Fsyscalls:signalfd_test_native\"\n```\n\nOnly **after** a syscall test works under Linux does it make sense to ever run\nit under gVisor. A syscall test that succeeds under Linux but fails under gVisor\nreflects a problem in gVisor itself. In this case, iterate on the gVisor kernel\ncode, and keep running the syscall test under gVisor until the syscall test\npasses. Example to run `signalfd.cc` in both Linux and gVisor in one shot:\n\n```\nmake syscall-tests TARGETS=\"\u002F\u002Ftest\u002Fsyscalls:signalfd_test_native \u002F\u002Ftest\u002Fsyscalls:signalfd_test_runsc_systrap_shared\"\n```\n","When modifying or expanding the way the gVisor kernel works, such as when\nimplementing a new system call, adding a new flag to an existing system call, or\nmodifying the way an existing system call works, you should generally follow\nthis approach:\n\n1.  Repeat your understanding of this aspect of the Linux kernel functionality.\n2.  If applicable, come up with a way to quickly test and exercise the relevant\n    kernel functionality by using a shell command or a short Python script. For\n    example, if asked to change the way the `stat(2)` system call works on a\n    specific device file like `\u002Fdev\u002Fzero`, you can use `stat \u002Fdev\u002Fzero` as a\n    representative command for which the output can guide your understanding of\n    the way the kernel works. See the \"Running a C program in gVisor\" section\n    below for how to run it. Syscall tests are also appropriate and excellent at\n    establishing coverage of all the edge cases a syscall may have; during\n    development, both are useful.\n3.  Before you look at any gVisor code, start by establishing a black-box\n    understanding of the current behavior of both Linux and gVisor for the\n    representative command or script you have come up with. Use the tools\n    available at your disposal to verify this.\n4.  If asked to modify the behavior of a specific system call, look for existing\n    syscall tests that cover this syscall. Read the syscall test file, and run\n    it under both Linux and gVisor at least once to make sure it is starting\n    from a good state to begin with.\n5.  Only after you have done the above, start reading gVisor kernel source code.\n    Do not stop at the first file you think is most likely to implement the\n    functionality you want to implement; look for multiple such files and only\n    settle on a decision once you are confident about your decision.\n6.  Make code changes, running your representative command or script or syscall\n    tests as often as necessary.\n\nNOTE: None of the above involves reading Linux source code. You **must not**\nread nor refer to Linux source code or Linux `man` pages, as they are often\nwrong or out-of-date. Therefore, gVisor exclusively uses black-box C++ syscall\ntests to assert Linux behavior, and you should use this approach exclusively in\norder to build up your understanding of the behavior of the syscall. When\nreviewing compatibility code, you should also follow this approach.\n\n### Running gVisor development workflows\n\n#### Running a C program in gVisor\n\nDuring development, to verify more complex syscall behavior in gVisor, it may be\nuseful to write a custom program in C that calls system calls directly, then to\ncompile it, and to run it in Linux and in gVisor.\n\nTo do so, generate a dependency-free C program, compile it with `gcc`, move it\nto a temporary directory such as `\u002Ftmp` (important: gVisor cannot directly run\nfrom special directories such as `bazel-bin` due to uninteresting permission\nissues), then use `runsc`'s `do` helper as follows:\n\n```\n# Recompile and extract to a world-accessible directory:\n$ make release-tarball DESTINATION=out\u002F && mkdir -p \u002Ftmp\u002Fgvisor && tar -C \u002Ftmp\u002Fgvisor -xf out\u002Fgvisor.tar.bz2\n\n# Run:\n$ \u002Ftmp\u002Fgvisor\u002Frunsc --rootless=true --network=none --debug-log=\u002Fdev\u002Fstderr --strace=true do \u002Fabsolute\u002Fpath\u002Fto\u002Fthe\u002Fbinary\n```\n\nThis will run `\u002Fabsolute\u002Fpath\u002Fto\u002Fthe\u002Fbinary` inside gVisor, with debug logs and\nthe syscall trace (strace) output included. Don't forget to also run it under\nLinux so that you can compare its behavior.\n\n#### Running syscall tests\n\nAs gVisor is a kernel meant to replicate Linux-like behavior,\n**application-observable kernel behavior is not tested with Go unit tests**, and\nyou should not add such tests for it. Go unit tests are only appropriate for\nself-contained internals with no Linux behavior to compare against. Instead, the\ngVisor kernel behavior is tested by \"syscall tests\", which are C++ test binaries\nwhich can be run either in Linux and in gVisor. These syscall test binaries call\nsome system calls in the kernel they are run in (either Linux or gVisor), and\nverify that the system call behaves in the same expected way.\n\nThese tests are defined in `\u002F\u002Ftest\u002Fsyscalls\u002Flinux` as `.cc`.\n\nIf you change or add a syscall test, you should first run it under Linux to make\nsure that the syscall test works properly under Linux. A syscall test that fails\nunder Linux reflects a problem with the test itself, not a problem in gVisor. If\nthis happens, fix the syscall test C++ program itself. Example:\n\n```\nmake syscall-tests TARGETS=\"\u002F\u002Ftest\u002Fsyscalls:signalfd_test_native\"\n```\n\nOnly **after** a syscall test works under Linux does it make sense to ever run\nit under gVisor. A syscall test that succeeds under Linux but fails under gVisor\nreflects a problem in gVisor itself. In this case, iterate on the gVisor kernel\ncode, and keep running the syscall test under gVisor until the syscall test\npasses. Example to run `signalfd.cc` in both Linux and gVisor in one shot:\n\n```\nmake syscall-tests TARGETS=\"\u002F\u002Ftest\u002Fsyscalls:signalfd_test_native \u002F\u002Ftest\u002Fsyscalls:signalfd_test_runsc_systrap_shared\"\n```\n",{"name":5,"description":7},"master","dbcce494395f0f40564701651b76de5a96d70c8f",".agents\u002Fskills\u002Fgvisor-kernel-development",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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add google\u002Fgvisor --skill gvisor-kernel-development",{"tool":55,"command":56},"bunx","bunx skills add google\u002Fgvisor --skill gvisor-kernel-development",{"tool":58,"command":59},"pnpm","pnpm dlx skills add google\u002Fgvisor --skill gvisor-kernel-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fgvisor\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fgvisor-kernel-development\u002FSKILL.md",true,[],[64,84],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":34},"01M698Z47JBA4W1XC0A96WXB8K","update-gvisor-maintainers","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.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fgvisor\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fupdate-gvisor-maintainers\u002FSKILL.md",[],[71,22,72,73,27,74,75,76,77,29,78,79,80,81,82,83],"update gvisor maintainers","maintainers","update","down","roster","codeowners","files","changes","governance","yaml","sync","goes","returns",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":34},"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",[],[91,92,22,93,94,95,96,97,21,98,99,100,101,102,103,29,104,105,106,107,108,109,110],"gvisor performance","performance","sentry","path","impact","sandbox","go","linux","app","which","memory","init","as","code","change","run","paths","security","marshal","mm"]