[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75KWQBC9AG1M35D87FQWXAB":3,"skill-same:01M75KWQBC9AG1M35D87FQWXAB":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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M75KWQBC9AG1M35D87FQWXAB","kermt-setup",null,"Bootstrap the KERMT agent environment — verify host docker + nvidia-container-toolkit, build the kermt:latest image from the repo's Dockerfile if it doesn't yet exist, and run a GPU smoke test inside the container. Every other kermt-* skill depends on this; invoke it first.","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\u002Fkermt-setup\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: kermt-setup\ndescription: Bootstrap the KERMT agent environment — verify host docker + nvidia-container-toolkit, build the kermt:latest image from the repo's Dockerfile if it doesn't yet exist, and run a GPU smoke test inside the container. Every other kermt-* skill depends on this; invoke it first.\nlicense: Apache-2.0\ncompatibility: Requires docker, nvidia-container-toolkit, and a CUDA-capable NVIDIA GPU. Designed for Claude Code, Codex, and Nemotron.\nmetadata:\n  owner: evax@nvidia.com\n  classification: atomic-skill\n  risk_tier: skill\n# This file is intentionally short (~110 lines, ~1200 tokens) — well within the\n# 500-line \u002F 5000-token budget for skill files. Longer reference material lives\n# alongside agent\u002Fscripts\u002Fkermt_container.sh.\n---\n\n# kermt-setup\n\nBootstrap the KERMT agent environment. Run this once on a fresh machine (or\nafter the Dockerfile or `environment.yml` changes) before invoking any other\n`kermt-*` skill.\n\n## Hardware requirements\n\n- **GPU**: at least one CUDA-capable NVIDIA GPU visible to the host. The image\n  is based on `nvidia\u002Fcuda:12.6.3-cudnn-devel-ubuntu22.04`, so the host driver\n  must support CUDA 12.6. Verify with host `nvidia-smi` before invoking.\n- **Host docker**: docker engine + nvidia-container-toolkit. Without the\n  toolkit, `docker run --gpus all` will fail at step 2 of the workflow below.\n- **Disk**: ≈ 50 GB free for the built kermt image (`docker image inspect\n  --format '{{.Size}}'` reports ≈ 44 GB; the `docker images` Size column\n  can show ~100 GB because it counts shareable buildx attestation layers\n  that are deduplicated across images). Plan for ~50 GB of unique on-disk\n  storage; add a comfortable buffer if you're also keeping build cache.\n- **Memory**: the build itself peaks at ~4 GB RAM during conda env solve.\n- This skill does not run training\u002Finference workloads itself; per-workflow\n  hardware requirements (VRAM, GPU count) are declared in the respective\n  `kermt-\u003Cworkflow>` skills.\n\n## When to invoke\n\n- User explicitly asks (`\u002Fkermt-setup`, \"set up kermt\", \"build the kermt image\",\n  etc.).\n- Or another `kermt-*` skill detected that the image does not exist and routed\n  here. (Most other skills call `kermt_ensure_image` themselves, so this is\n  usually only needed for the first-time setup, debugging, or a forced rebuild.)\n\n## Inputs\n\nThe skill takes no required arguments. Optional overrides (via env vars before\ninvoking, or by setting them in the user's shell):\n\n- `KERMT_IMAGE` — image tag to build\u002Fverify (default: `kermt:latest`).\n- `KERMT_REPO` — host path of the kermt repo checkout (default: auto-derived\n  from the script's location).\n\nIf the user has not specified a repo path and the current working directory is\nnot inside a kermt repo clone, ask for the repo path before proceeding.\n\n## Workflow\n\nAll work goes through `agent\u002Fscripts\u002Fkermt_container.sh`. The script's\nsubcommand dispatch can be invoked directly without sourcing — that is the\npreferred form for skill use.\n\nLet `HELPER=$KERMT_REPO\u002Fagent\u002Fscripts\u002Fkermt_container.sh`.\n\n1. **Verify docker is installed and the daemon is reachable.**\n   ```\n   $HELPER check_docker\n   ```\n   Exit 0 → continue. Non-zero → surface the error to the user (typically\n   \"docker not on PATH\" or \"daemon not reachable\"); do not attempt step 2.\n\n2. **Verify GPU passthrough works.**\n   ```\n   $HELPER check_gpu\n   ```\n   This runs `docker run --rm --gpus all nvidia\u002Fcuda:12.6.3-base-ubuntu22.04\n   nvidia-smi` and checks the exit status. Non-zero → tell the user to install\n   `nvidia-container-toolkit` on the host and confirm a CUDA-capable NVIDIA GPU\n   is visible to the host (`nvidia-smi` on the host should also work). Stop\n   here; without GPU passthrough the kermt image will build but no workflow\n   will run.\n\n3. **Build or verify the kermt image.**\n   ```\n   $HELPER ensure_image\n   ```\n   If the image already exists, this returns immediately. Otherwise it builds\n   from `$KERMT_REPO\u002FDockerfile`. **Warn the user before invoking** that the\n   first build takes ~10–20 minutes on a typical workstation and streams build\n   logs to the console. Do not run this in the background — the user wants to\n   see progress and any build failures must surface immediately.\n\n4. **GPU smoke test inside the container.** Quote the whole `python` command\n   as a single string — the helper passes args through `bash -c \"$*\"`, so\n   unquoted multi-word commands get re-parsed and any embedded quotes are\n   collapsed.\n   ```\n   $HELPER run -- 'python -c \"import torch; print(\\\"cuda_available:\\\", torch.cuda.is_available()); print(\\\"device_count:\\\", torch.cuda.device_count())\"'\n   ```\n   Expected output: `cuda_available: True` and a positive `device_count`. If\n   `cuda_available` is `False` despite step 2 passing, something is wrong with\n   the container's CUDA wiring — report the full output to the user and stop;\n   do not declare the environment ready.\n\n5. **Summary to user.** Report:\n   - Image tag and ID (`docker image inspect $KERMT_IMAGE --format '{{.Id}}'`).\n   - Image size (`docker image inspect $KERMT_IMAGE --format '{{.Size}}'`).\n   - GPU count detected inside the container.\n   - \"Ready\" — the user can now invoke other `kermt-*` skills.\n\n## Hard rules\n\n- Do **not** pull or push docker images. The kermt image is built locally only.\n- Do **not** auto-delete or prune older `kermt:*` tags without the user's\n  explicit confirmation — the user may be running a finetune or pretrain in\n  another container that depends on a specific tag.\n- Do **not** modify the host's docker daemon configuration, daemon.json, or\n  user-group membership.\n- Do **not** modify the `Dockerfile` or `environment.yml` as part of this\n  skill. If the build fails because of a Dockerfile issue, surface the error\n  and stop; let the user decide whether to edit.\n- Do **not** rebuild the image when it already exists (i.e. do not pass a\n  `--no-cache` or `--pull` flag to ensure_image) unless the user explicitly\n  asks for a forced rebuild.\n\n## Forced rebuild\n\nIf the user explicitly asks to rebuild (e.g. after changing the Dockerfile or\n`environment.yml`), the cleanest path is to remove the old image first, then\nrerun `ensure_image`:\n\n```\ndocker image rm $KERMT_IMAGE\n$HELPER ensure_image\n```\n\nConfirm with the user before running `docker image rm`.\n","# kermt-setup\n\nBootstrap the KERMT agent environment. Run this once on a fresh machine (or\nafter the Dockerfile or `environment.yml` changes) before invoking any other\n`kermt-*` skill.\n\n## Hardware requirements\n\n- **GPU**: at least one CUDA-capable NVIDIA GPU visible to the host. The image\n  is based on `nvidia\u002Fcuda:12.6.3-cudnn-devel-ubuntu22.04`, so the host driver\n  must support CUDA 12.6. Verify with host `nvidia-smi` before invoking.\n- **Host docker**: docker engine + nvidia-container-toolkit. Without the\n  toolkit, `docker run --gpus all` will fail at step 2 of the workflow below.\n- **Disk**: ≈ 50 GB free for the built kermt image (`docker image inspect\n  --format '{{.Size}}'` reports ≈ 44 GB; the `docker images` Size column\n  can show ~100 GB because it counts shareable buildx attestation layers\n  that are deduplicated across images). Plan for ~50 GB of unique on-disk\n  storage; add a comfortable buffer if you're also keeping build cache.\n- **Memory**: the build itself peaks at ~4 GB RAM during conda env solve.\n- This skill does not run training\u002Finference workloads itself; per-workflow\n  hardware requirements (VRAM, GPU count) are declared in the respective\n  `kermt-\u003Cworkflow>` skills.\n\n## When to invoke\n\n- User explicitly asks (`\u002Fkermt-setup`, \"set up kermt\", \"build the kermt image\",\n  etc.).\n- Or another `kermt-*` skill detected that the image does not exist and routed\n  here. (Most other skills call `kermt_ensure_image` themselves, so this is\n  usually only needed for the first-time setup, debugging, or a forced rebuild.)\n\n## Inputs\n\nThe skill takes no required arguments. Optional overrides (via env vars before\ninvoking, or by setting them in the user's shell):\n\n- `KERMT_IMAGE` — image tag to build\u002Fverify (default: `kermt:latest`).\n- `KERMT_REPO` — host path of the kermt repo checkout (default: auto-derived\n  from the script's location).\n\nIf the user has not specified a repo path and the current working directory is\nnot inside a kermt repo clone, ask for the repo path before proceeding.\n\n## Workflow\n\nAll work goes through `agent\u002Fscripts\u002Fkermt_container.sh`. The script's\nsubcommand dispatch can be invoked directly without sourcing — that is the\npreferred form for skill use.\n\nLet `HELPER=$KERMT_REPO\u002Fagent\u002Fscripts\u002Fkermt_container.sh`.\n\n1. **Verify docker is installed and the daemon is reachable.**\n   ```\n   $HELPER check_docker\n   ```\n   Exit 0 → continue. Non-zero → surface the error to the user (typically\n   \"docker not on PATH\" or \"daemon not reachable\"); do not attempt step 2.\n\n2. **Verify GPU passthrough works.**\n   ```\n   $HELPER check_gpu\n   ```\n   This runs `docker run --rm --gpus all nvidia\u002Fcuda:12.6.3-base-ubuntu22.04\n   nvidia-smi` and checks the exit status. Non-zero → tell the user to install\n   `nvidia-container-toolkit` on the host and confirm a CUDA-capable NVIDIA GPU\n   is visible to the host (`nvidia-smi` on the host should also work). Stop\n   here; without GPU passthrough the kermt image will build but no workflow\n   will run.\n\n3. **Build or verify the kermt image.**\n   ```\n   $HELPER ensure_image\n   ```\n   If the image already exists, this returns immediately. Otherwise it builds\n   from `$KERMT_REPO\u002FDockerfile`. **Warn the user before invoking** that the\n   first build takes ~10–20 minutes on a typical workstation and streams build\n   logs to the console. Do not run this in the background — the user wants to\n   see progress and any build failures must surface immediately.\n\n4. **GPU smoke test inside the container.** Quote the whole `python` command\n   as a single string — the helper passes args through `bash -c \"$*\"`, so\n   unquoted multi-word commands get re-parsed and any embedded quotes are\n   collapsed.\n   ```\n   $HELPER run -- 'python -c \"import torch; print(\\\"cuda_available:\\\", torch.cuda.is_available()); print(\\\"device_count:\\\", torch.cuda.device_count())\"'\n   ```\n   Expected output: `cuda_available: True` and a positive `device_count`. If\n   `cuda_available` is `False` despite step 2 passing, something is wrong with\n   the container's CUDA wiring — report the full output to the user and stop;\n   do not declare the environment ready.\n\n5. **Summary to user.** Report:\n   - Image tag and ID (`docker image inspect $KERMT_IMAGE --format '{{.Id}}'`).\n   - Image size (`docker image inspect $KERMT_IMAGE --format '{{.Size}}'`).\n   - GPU count detected inside the container.\n   - \"Ready\" — the user can now invoke other `kermt-*` skills.\n\n## Hard rules\n\n- Do **not** pull or push docker images. The kermt image is built locally only.\n- Do **not** auto-delete or prune older `kermt:*` tags without the user's\n  explicit confirmation — the user may be running a finetune or pretrain in\n  another container that depends on a specific tag.\n- Do **not** modify the host's docker daemon configuration, daemon.json, or\n  user-group membership.\n- Do **not** modify the `Dockerfile` or `environment.yml` as part of this\n  skill. If the build fails because of a Dockerfile issue, surface the error\n  and stop; let the user decide whether to edit.\n- Do **not** rebuild the image when it already exists (i.e. do not pass a\n  `--no-cache` or `--pull` flag to ensure_image) unless the user explicitly\n  asks for a forced rebuild.\n\n## Forced rebuild\n\nIf the user explicitly asks to rebuild (e.g. after changing the Dockerfile or\n`environment.yml`), the cleanest path is to remove the old image first, then\nrerun `ensure_image`:\n\n```\ndocker image rm $KERMT_IMAGE\n$HELPER ensure_image\n```\n\nConfirm with the user before running `docker image rm`.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":28},{"owner":25,"risk_tier":26,"classification":27},"evax@nvidia.com","skill","atomic-skill","Requires docker, nvidia-container-toolkit, and a CUDA-capable NVIDIA GPU. Designed for Claude Code, Codex, and Nemotron.","master","49e49abf2f670d429e0b7e2c0349739c3fdd5cbe","skills\u002Fkermt-setup",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":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add stanfish06\u002Fskillquarium --skill kermt-setup",{"tool":43,"command":44},"bunx","bunx skills add stanfish06\u002Fskillquarium --skill kermt-setup",{"tool":46,"command":47},"pnpm","pnpm dlx skills add stanfish06\u002Fskillquarium --skill kermt-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fkermt-setup\u002FSKILL.md",true,[51],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"evals\u002Fevals.json","REFERENCE","参考文档",4554,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fkermt-setup\u002Fevals\u002Fevals.json",[58,66,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":62,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"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.","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":15,"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":62,"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":62,"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":15,"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",[],[]]