[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE6GDDF75XW8GQNTA79XG2":3,"skill-same:01M6AE6GDDF75XW8GQNTA79XG2":79},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6AE6GDDF75XW8GQNTA79XG2","sandbox-npm-install",null,"Install npm packages in a Docker sandbox environment. Use this skill whenever you need to install, reinstall, or update node_modules inside a container where the workspace is mounted via virtiofs. Native binaries (esbuild, lightningcss, rollup) crash on virtiofs, so packages must be installed on the local ext4 filesystem and symlinked back.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41046,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsandbox-npm-install\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"sandbox","install","sandbox npm install","npm","update","packages","workspace","filesystem","node","environment","docker","use","container","modules","back","local","docker sandbox","via","native","you","2026-11-10 10:12:30",false,"---\nname: sandbox-npm-install\ndescription: 'Install npm packages in a Docker sandbox environment. Use this skill whenever you need to install, reinstall, or update node_modules inside a container where the workspace is mounted via virtiofs. Native binaries (esbuild, lightningcss, rollup) crash on virtiofs, so packages must be installed on the local ext4 filesystem and symlinked back.'\n---\n\n# Sandbox npm Install\n\n## When to Use This Skill\n\nUse this skill whenever:\n- You need to install npm packages for the first time in a new sandbox session\n- `package.json` or `package-lock.json` has changed and you need to reinstall\n- You encounter native binary crashes with errors like `SIGILL`, `SIGSEGV`, `mmap`, or `unaligned sysNoHugePageOS`\n- The `node_modules` directory is missing or corrupted\n\n## Prerequisites\n\n- A Docker sandbox environment with a virtiofs-mounted workspace\n- Node.js and npm available in the container\n- A `package.json` file in the target workspace\n\n## Background\n\nDocker sandbox workspaces are typically mounted via **virtiofs** (file sync between the host and Linux VM). Native Go and Rust binaries (esbuild, lightningcss, rollup, etc.) crash with mmap alignment failures when executed from virtiofs on aarch64. The fix is to install on the container's local ext4 filesystem and symlink back into the workspace.\n\n## Step-by-Step Installation\n\nRun the bundled install script from the workspace root:\n\n```bash\nbash scripts\u002Finstall.sh\n```\n\n### Common Options\n\n| Option | Description |\n|---|---|\n| `--workspace \u003Cpath>` | Path to directory containing `package.json` (auto-detected if omitted) |\n| `--playwright` | Also install Playwright Chromium browser for E2E testing |\n\n### What the Script Does\n\n1. Copies `package.json`, `package-lock.json`, and `.npmrc` (if present) to a local ext4 directory\n2. Runs `npm ci` (or `npm install` if no lockfile) on the local filesystem\n3. Symlinks `node_modules` back into the workspace\n4. Verifies known native binaries (esbuild, rollup, lightningcss, vite) if present\n5. Optionally installs Playwright browsers and system dependencies (uses `sudo` when available)\n\nIf verification fails, run the script again — crashes can be intermittent during initial setup.\n\n## Post-Install Verification\n\nAfter the script completes, verify your toolchain works. For example:\n\n```bash\nnpm test             # Run project tests\nnpm run build        # Build the project\nnpm run dev          # Start dev server\n```\n\n## Important Notes\n\n- The local install directory (e.g., `\u002Fhome\u002Fagent\u002Fproject-deps`) is **container-local** and is NOT synced back to the host\n- The `node_modules` symlink appears as a broken link on the host — this is harmless since `node_modules` is typically gitignored\n- Running `npm ci` or `npm install` on the host naturally replaces the symlink with a real directory\n- After any `package.json` or `package-lock.json` change, re-run the install script\n- Do NOT run `npm ci` or `npm install` directly in the mounted workspace — native binaries will crash\n\n## Troubleshooting\n\n| Problem | Solution |\n|---|---|\n| `SIGILL` or `SIGSEGV` when running dev server | Re-run the install script; ensure you're not running `npm install` directly in the workspace |\n| `node_modules` not found after install | Check that the symlink exists: `ls -la node_modules` |\n| Permission errors during install | Ensure the local deps directory is writable by the current user |\n| Verification fails intermittently | Run the script again — native binary crashes can be non-deterministic on first load |\n\n## Vite Compatibility\n\nIf your project uses Vite, you may need to allow the symlinked path in `server.fs.allow`. Add the symlink target's parent directory (e.g., `\u002Fhome\u002Fagent\u002Fproject-deps\u002F`) to your Vite config so that Vite can serve files through the symlink.\n","# Sandbox npm Install\n\n## When to Use This Skill\n\nUse this skill whenever:\n- You need to install npm packages for the first time in a new sandbox session\n- `package.json` or `package-lock.json` has changed and you need to reinstall\n- You encounter native binary crashes with errors like `SIGILL`, `SIGSEGV`, `mmap`, or `unaligned sysNoHugePageOS`\n- The `node_modules` directory is missing or corrupted\n\n## Prerequisites\n\n- A Docker sandbox environment with a virtiofs-mounted workspace\n- Node.js and npm available in the container\n- A `package.json` file in the target workspace\n\n## Background\n\nDocker sandbox workspaces are typically mounted via **virtiofs** (file sync between the host and Linux VM). Native Go and Rust binaries (esbuild, lightningcss, rollup, etc.) crash with mmap alignment failures when executed from virtiofs on aarch64. The fix is to install on the container's local ext4 filesystem and symlink back into the workspace.\n\n## Step-by-Step Installation\n\nRun the bundled install script from the workspace root:\n\n```bash\nbash scripts\u002Finstall.sh\n```\n\n### Common Options\n\n| Option | Description |\n|---|---|\n| `--workspace \u003Cpath>` | Path to directory containing `package.json` (auto-detected if omitted) |\n| `--playwright` | Also install Playwright Chromium browser for E2E testing |\n\n### What the Script Does\n\n1. Copies `package.json`, `package-lock.json`, and `.npmrc` (if present) to a local ext4 directory\n2. Runs `npm ci` (or `npm install` if no lockfile) on the local filesystem\n3. Symlinks `node_modules` back into the workspace\n4. Verifies known native binaries (esbuild, rollup, lightningcss, vite) if present\n5. Optionally installs Playwright browsers and system dependencies (uses `sudo` when available)\n\nIf verification fails, run the script again — crashes can be intermittent during initial setup.\n\n## Post-Install Verification\n\nAfter the script completes, verify your toolchain works. For example:\n\n```bash\nnpm test             # Run project tests\nnpm run build        # Build the project\nnpm run dev          # Start dev server\n```\n\n## Important Notes\n\n- The local install directory (e.g., `\u002Fhome\u002Fagent\u002Fproject-deps`) is **container-local** and is NOT synced back to the host\n- The `node_modules` symlink appears as a broken link on the host — this is harmless since `node_modules` is typically gitignored\n- Running `npm ci` or `npm install` on the host naturally replaces the symlink with a real directory\n- After any `package.json` or `package-lock.json` change, re-run the install script\n- Do NOT run `npm ci` or `npm install` directly in the mounted workspace — native binaries will crash\n\n## Troubleshooting\n\n| Problem | Solution |\n|---|---|\n| `SIGILL` or `SIGSEGV` when running dev server | Re-run the install script; ensure you're not running `npm install` directly in the workspace |\n| `node_modules` not found after install | Check that the symlink exists: `ls -la node_modules` |\n| Permission errors during install | Ensure the local deps directory is writable by the current user |\n| Verification fails intermittently | Run the script again — native binary crashes can be non-deterministic on first load |\n\n## Vite Compatibility\n\nIf your project uses Vite, you may need to allow the symlinked path in `server.fs.allow`. Add the symlink target's parent directory (e.g., `\u002Fhome\u002Fagent\u002Fproject-deps\u002F`) to your Vite config so that Vite can serve files through the symlink.\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fsandbox-npm-install",5340,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-11 13:41:32",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add github\u002Fawesome-copilot --skill sandbox-npm-install",{"tool":65,"command":66},"bunx","bunx skills add github\u002Fawesome-copilot --skill sandbox-npm-install",{"tool":68,"command":69},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill sandbox-npm-install","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsandbox-npm-install\u002FSKILL.md",true,[73],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Finstall.sh","SCRIPT","脚本",5593,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsandbox-npm-install\u002Fscripts\u002Finstall.sh",[80,110,138,167,201,218],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":90,"publishedAt":44},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[86,89],{"categoryNo":87,"categoryName":88,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,35,107,108,109],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","users","functions","with",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":117,"publishedAt":44},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[116],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":150,"publishedAt":44},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[145],{"categoryNo":146,"categoryName":147,"taxonomyType":148,"taxonomyTypeDesc":149},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[151,152,153,154,155,156,124,95,157,158,39,159,160,161,162,35,163,164,165,166],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":171,"sourceHtmlUrl":172,"categories":173,"keywords":178,"publishedAt":44},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[174,177],{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":146,"categoryName":147,"taxonomyType":148,"taxonomyTypeDesc":149},[179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,96,194,195,196,197,198,124,199,200],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":205,"licenseFileUrl":206,"sourceHtmlUrl":207,"categories":208,"keywords":214,"publishedAt":44},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[209,210,213],{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":211,"categoryName":212,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[215,121,188,216,217],"resemble detect","https","identity",{"skillNo":219,"name":220,"nameZh":6,"description":221,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":205,"licenseFileUrl":222,"sourceHtmlUrl":223,"categories":224,"keywords":229,"publishedAt":44},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[225,228],{"categoryNo":226,"categoryName":227,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[230,231,232,233,152,97,9,120,234,235,216,236,237,238,239,240,241,242,243,244,245,246,105,247,248,249,250],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]