[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSGVE2S0YESK3NXG57N5AE":3,"skill-same:01M7CSGVE2S0YESK3NXG57N5AE":77},{"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":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":39,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M7CSGVE2S0YESK3NXG57N5AE","holoscan-install-source",null,"Build Holoscan SDK from source via the in-tree .\u002Frun script. Use only when published packages don't meet the user's needs.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fholoscan-install-source\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: holoscan-install-source\nversion: \"1.0.0\"\ndescription: \"Build Holoscan SDK from source via the in-tree .\u002Frun script. Use only when published packages don't meet the user's needs.\"\nlicense: Apache-2.0\nmetadata:\n  author: \"Holoscan Team \u003Choloscan-team@nvidia.com>\"\n  github-url: \"https:\u002F\u002Fgithub.com\u002Fnvidia-holoscan\u002Fholoscan-sdk\"\n  tags:\n    - holoscan\n    - install\n    - source\n    - build\n    - cmake\n---\n\n# Holoscan SDK — Build from Source\n\n## Purpose\n\nBuild the Holoscan SDK from the `nvidia-holoscan\u002Fholoscan-sdk` source tree using its `.\u002Frun` script (which builds inside a Docker container), producing a local install tree consumable as a CMake dependency.\n\n## Prerequisites\n\n- Linux host with NVIDIA GPU + driver (`nvidia-smi`).\n- `git`, Docker with NVIDIA Container Toolkit (`docker run --gpus all` works), and `docker-buildx-plugin`.\n- ~20 GB free disk for the build container + build\u002Finstall trees.\n- 10–30 min for a clean first build.\n\n## Limitations\n\n- Only recommended when published packages (Conda \u002F container \u002F apt \u002F wheel) don't fit — debug symbols, custom CMake options, or unsupported configs.\n- Still requires Docker — the `.\u002Frun` script builds inside a container; this is not a true bare-metal build.\n- Cross-compiling to aarch64 needs `qemu-user-static` on the host.\n\n## Step 0: Consult the Official Install Instructions\n\nAlways fetch the \"Build from Source\" section of `https:\u002F\u002Fdocs.nvidia.com\u002Fholoscan\u002Fsdk-user-guide\u002Fsdk_installation.html` (and the linked GitHub `README.md` \u002F `DEVELOP.md` for the chosen tag) before building. Extract: required `.\u002Frun` flags for the target architecture and CUDA major, supported branches\u002Ftags, any Dockerfile patches called out for the release, and the test names recommended for verification. If the doc disagrees with anything below, the doc wins.\n\n## Step 1: Prerequisites\n\nCheck that git and Docker (with GPU passthrough) are available:\n\n```bash\ngit --version\ndocker --version\ndocker run --rm --gpus all ubuntu:22.04 nvidia-smi\n```\n\n- If Docker is missing → help install from https:\u002F\u002Fdocs.docker.com\u002Fengine\u002Finstall\u002F\n- If GPU passthrough fails → install NVIDIA Container Toolkit:\n  ```bash\n  curl -fsSL https:\u002F\u002Fnvidia.github.io\u002Flibnvidia-container\u002Fgpgkey | sudo gpg --dearmor -o \u002Fusr\u002Fshare\u002Fkeyrings\u002Fnvidia-container-toolkit-keyring.gpg\n  curl -s -L https:\u002F\u002Fnvidia.github.io\u002Flibnvidia-container\u002Fstable\u002Fdeb\u002Fnvidia-container-toolkit.list \\\n    | sed 's#deb https:\u002F\u002F#deb [signed-by=\u002Fusr\u002Fshare\u002Fkeyrings\u002Fnvidia-container-toolkit-keyring.gpg] https:\u002F\u002F#g' \\\n    | sudo tee \u002Fetc\u002Fapt\u002Fsources.list.d\u002Fnvidia-container-toolkit.list\n  sudo apt-get update && sudo apt-get install -y nvidia-container-toolkit\n  sudo nvidia-ctk runtime configure --runtime=docker && sudo systemctl restart docker\n  ```\n- If Docker buildx is missing: `sudo apt-get install docker-buildx-plugin`\n\n## Step 2: Clone the Repository\n\nClone repo to ~\u002Fholoscan\u002Fholoscan-sdk if needed\n\n```bash\nmkdir -p ~\u002Fholoscan\u002F\ngit clone https:\u002F\u002Fgithub.com\u002Fnvidia-holoscan\u002Fholoscan-sdk.git\ncd ~\u002Fholoscan\u002Fholoscan-sdk\n```\n\nTo build a specific release tag (recommended for stability):\n\n```bash\ngit tag | grep -E '^v[0-9]' | sort -V | tail -5   # list recent tags\ngit checkout v\u003CVERSION>                             # e.g. v4.1.0\n```\n\n## Step 3: Build\n\nThe `.\u002Frun build` script handles container creation, CMake configuration, compilation, and install in one step. Warn the user this takes **10–30 minutes** on first run (downloads base image + compiles).\n\n```bash\n.\u002Frun build\n```\n\nCommon options:\n\n| Flag | Purpose |\n|------|---------|\n| `--type debug` | Debug build (symbols, no optimization) |\n| `--type RelWithDebInfo` | Release + debug symbols |\n| `--arch aarch64` | Cross-compile for ARM64 (needs `sudo apt install qemu-user-static`) |\n| `--gpu igpu` | iGPU build for Jetson\u002FIGX |\n| `--dryrun` | Preview commands without executing |\n\nIf CMake cache errors occur after changing options:\n\n```bash\n.\u002Frun clear_cache && .\u002Frun build\n```\n\nOutput lands in these folders, and can be retrieved with `.\u002Frun get_build_dir` and `.\u002Frun get_install_dir`\n* Build dir: `build-cu\u003CN>-\u003Carch>\u002F`\n* Install dir: `install-cu\u003CN>-\u003Carch>\u002F`.\n\n## Step 4: Run Tests\n\nRun the following tests\n* EXAMPLE_CPP_HELLO_WORLD_TEST\n* EXAMPLE_PYTHON_HELLO_WORLD_TEST\n* EXAMPLE_CPP_TENSOR_INTEROP_TEST\n* EXAMPLE_PYTHON_TENSOR_INTEROP_TEST\n* EXAMPLE_CPP_VIDEO_REPLAYER_TEST\n* EXAMPLE_PYTHON_VIDEO_REPLAYER_TEST\n\n```bash\n.\u002Frun test\n```\n\nTo run all six required tests at once, use a single-quoted regex (the `|` must be quoted to prevent bash from treating it as a pipe):\n\n```bash\n.\u002Frun test --options \"-R 'EXAMPLE_CPP_HELLO_WORLD_TEST|EXAMPLE_PYTHON_HELLO_WORLD_TEST|EXAMPLE_CPP_TENSOR_INTEROP_TEST|EXAMPLE_PYTHON_TENSOR_INTEROP_TEST|EXAMPLE_CPP_VIDEO_REPLAYER_TEST|EXAMPLE_PYTHON_VIDEO_REPLAYER_TEST' --output-on-failure\"\n```\n\nRun a specific test by name or regex:\n\n```bash\n.\u002Frun test --name \u003Ctest_name>\n.\u002Frun test --options \"-R '\u003Cregex>' --output-on-failure\"\n.\u002Frun test --verbose\n```\n\n**Important:** Always single-quote the regex string when it contains `|` — without quotes, bash interprets `|` as a pipe and the command fails with `command not found`.\n\nExpected: all tests pass. Note any failures and report them to the user before continuing.\n\n## Step 5: Point Applications at the Install Tree\n\nOnce built, applications can use the install tree as a CMake dependency. Give the user this path:\n\n```\n\u002Fpath\u002Fto\u002Fholoscan-sdk\u002Finstall-cu\u003CN>-\u003Carch>\u002F\n```\n\nThey can set `Holoscan_ROOT` or `CMAKE_PREFIX_PATH` to this directory when building their own applications.\n\n## Troubleshooting\n\n| Symptom | Fix |\n|---------|-----|\n| `bash: \u003CTEST_NAME>: command not found` when running tests | The regex contains `\\|` — wrap it in single quotes: `--options \"-R '\u003Cregex>'\"` |\n| CMake cache errors after option change | `.\u002Frun clear_cache && .\u002Frun build` |\n| Docker buildx not found | `sudo apt-get install docker-buildx-plugin` |\n| GPU not visible inside build container | Verify NVIDIA Container Toolkit and re-run `sudo nvidia-ctk runtime configure --runtime=docker` |\n| Cross-compile fails (aarch64) | Install qemu: `sudo apt-get install qemu-user-static` |\n","# Holoscan SDK — Build from Source\n\n## Purpose\n\nBuild the Holoscan SDK from the `nvidia-holoscan\u002Fholoscan-sdk` source tree using its `.\u002Frun` script (which builds inside a Docker container), producing a local install tree consumable as a CMake dependency.\n\n## Prerequisites\n\n- Linux host with NVIDIA GPU + driver (`nvidia-smi`).\n- `git`, Docker with NVIDIA Container Toolkit (`docker run --gpus all` works), and `docker-buildx-plugin`.\n- ~20 GB free disk for the build container + build\u002Finstall trees.\n- 10–30 min for a clean first build.\n\n## Limitations\n\n- Only recommended when published packages (Conda \u002F container \u002F apt \u002F wheel) don't fit — debug symbols, custom CMake options, or unsupported configs.\n- Still requires Docker — the `.\u002Frun` script builds inside a container; this is not a true bare-metal build.\n- Cross-compiling to aarch64 needs `qemu-user-static` on the host.\n\n## Step 0: Consult the Official Install Instructions\n\nAlways fetch the \"Build from Source\" section of `https:\u002F\u002Fdocs.nvidia.com\u002Fholoscan\u002Fsdk-user-guide\u002Fsdk_installation.html` (and the linked GitHub `README.md` \u002F `DEVELOP.md` for the chosen tag) before building. Extract: required `.\u002Frun` flags for the target architecture and CUDA major, supported branches\u002Ftags, any Dockerfile patches called out for the release, and the test names recommended for verification. If the doc disagrees with anything below, the doc wins.\n\n## Step 1: Prerequisites\n\nCheck that git and Docker (with GPU passthrough) are available:\n\n```bash\ngit --version\ndocker --version\ndocker run --rm --gpus all ubuntu:22.04 nvidia-smi\n```\n\n- If Docker is missing → help install from https:\u002F\u002Fdocs.docker.com\u002Fengine\u002Finstall\u002F\n- If GPU passthrough fails → install NVIDIA Container Toolkit:\n  ```bash\n  curl -fsSL https:\u002F\u002Fnvidia.github.io\u002Flibnvidia-container\u002Fgpgkey | sudo gpg --dearmor -o \u002Fusr\u002Fshare\u002Fkeyrings\u002Fnvidia-container-toolkit-keyring.gpg\n  curl -s -L https:\u002F\u002Fnvidia.github.io\u002Flibnvidia-container\u002Fstable\u002Fdeb\u002Fnvidia-container-toolkit.list \\\n    | sed 's#deb https:\u002F\u002F#deb [signed-by=\u002Fusr\u002Fshare\u002Fkeyrings\u002Fnvidia-container-toolkit-keyring.gpg] https:\u002F\u002F#g' \\\n    | sudo tee \u002Fetc\u002Fapt\u002Fsources.list.d\u002Fnvidia-container-toolkit.list\n  sudo apt-get update && sudo apt-get install -y nvidia-container-toolkit\n  sudo nvidia-ctk runtime configure --runtime=docker && sudo systemctl restart docker\n  ```\n- If Docker buildx is missing: `sudo apt-get install docker-buildx-plugin`\n\n## Step 2: Clone the Repository\n\nClone repo to ~\u002Fholoscan\u002Fholoscan-sdk if needed\n\n```bash\nmkdir -p ~\u002Fholoscan\u002F\ngit clone https:\u002F\u002Fgithub.com\u002Fnvidia-holoscan\u002Fholoscan-sdk.git\ncd ~\u002Fholoscan\u002Fholoscan-sdk\n```\n\nTo build a specific release tag (recommended for stability):\n\n```bash\ngit tag | grep -E '^v[0-9]' | sort -V | tail -5   # list recent tags\ngit checkout v\u003CVERSION>                             # e.g. v4.1.0\n```\n\n## Step 3: Build\n\nThe `.\u002Frun build` script handles container creation, CMake configuration, compilation, and install in one step. Warn the user this takes **10–30 minutes** on first run (downloads base image + compiles).\n\n```bash\n.\u002Frun build\n```\n\nCommon options:\n\n| Flag | Purpose |\n|------|---------|\n| `--type debug` | Debug build (symbols, no optimization) |\n| `--type RelWithDebInfo` | Release + debug symbols |\n| `--arch aarch64` | Cross-compile for ARM64 (needs `sudo apt install qemu-user-static`) |\n| `--gpu igpu` | iGPU build for Jetson\u002FIGX |\n| `--dryrun` | Preview commands without executing |\n\nIf CMake cache errors occur after changing options:\n\n```bash\n.\u002Frun clear_cache && .\u002Frun build\n```\n\nOutput lands in these folders, and can be retrieved with `.\u002Frun get_build_dir` and `.\u002Frun get_install_dir`\n* Build dir: `build-cu\u003CN>-\u003Carch>\u002F`\n* Install dir: `install-cu\u003CN>-\u003Carch>\u002F`.\n\n## Step 4: Run Tests\n\nRun the following tests\n* EXAMPLE_CPP_HELLO_WORLD_TEST\n* EXAMPLE_PYTHON_HELLO_WORLD_TEST\n* EXAMPLE_CPP_TENSOR_INTEROP_TEST\n* EXAMPLE_PYTHON_TENSOR_INTEROP_TEST\n* EXAMPLE_CPP_VIDEO_REPLAYER_TEST\n* EXAMPLE_PYTHON_VIDEO_REPLAYER_TEST\n\n```bash\n.\u002Frun test\n```\n\nTo run all six required tests at once, use a single-quoted regex (the `|` must be quoted to prevent bash from treating it as a pipe):\n\n```bash\n.\u002Frun test --options \"-R 'EXAMPLE_CPP_HELLO_WORLD_TEST|EXAMPLE_PYTHON_HELLO_WORLD_TEST|EXAMPLE_CPP_TENSOR_INTEROP_TEST|EXAMPLE_PYTHON_TENSOR_INTEROP_TEST|EXAMPLE_CPP_VIDEO_REPLAYER_TEST|EXAMPLE_PYTHON_VIDEO_REPLAYER_TEST' --output-on-failure\"\n```\n\nRun a specific test by name or regex:\n\n```bash\n.\u002Frun test --name \u003Ctest_name>\n.\u002Frun test --options \"-R '\u003Cregex>' --output-on-failure\"\n.\u002Frun test --verbose\n```\n\n**Important:** Always single-quote the regex string when it contains `|` — without quotes, bash interprets `|` as a pipe and the command fails with `command not found`.\n\nExpected: all tests pass. Note any failures and report them to the user before continuing.\n\n## Step 5: Point Applications at the Install Tree\n\nOnce built, applications can use the install tree as a CMake dependency. Give the user this path:\n\n```\n\u002Fpath\u002Fto\u002Fholoscan-sdk\u002Finstall-cu\u003CN>-\u003Carch>\u002F\n```\n\nThey can set `Holoscan_ROOT` or `CMAKE_PREFIX_PATH` to this directory when building their own applications.\n\n## Troubleshooting\n\n| Symptom | Fix |\n|---------|-----|\n| `bash: \u003CTEST_NAME>: command not found` when running tests | The regex contains `\\|` — wrap it in single quotes: `--options \"-R '\u003Cregex>'\"` |\n| CMake cache errors after option change | `.\u002Frun clear_cache && .\u002Frun build` |\n| Docker buildx not found | `sudo apt-get install docker-buildx-plugin` |\n| GPU not visible inside build container | Verify NVIDIA Container Toolkit and re-run `sudo nvidia-ctk runtime configure --runtime=docker` |\n| Cross-compile fails (aarch64) | Install qemu: `sudo apt-get install qemu-user-static` |\n",{"name":5,"license":15,"version":24,"metadata":25,"description":7},"1.0.0",{"tags":26,"author":32,"github-url":33},[27,28,29,30,31],"holoscan","install","source","build","cmake","Holoscan Team \u003Choloscan-team@nvidia.com>","https:\u002F\u002Fgithub.com\u002Fnvidia-holoscan\u002Fholoscan-sdk","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fholoscan-install-source",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill holoscan-install-source",{"tool":49,"command":50},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill holoscan-install-source",{"tool":52,"command":53},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill holoscan-install-source","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fholoscan-install-source\u002FSKILL.md",true,[57,63,67,71],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"BENCHMARK.md","REFERENCE","参考文档",3943,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fholoscan-install-source\u002FBENCHMARK.md",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"evals\u002Fevals.json",4624,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fholoscan-install-source\u002Fevals\u002Fevals.json",{"path":68,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":69,"sourceHtmlUrl":70},"skill-card.md",3798,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fholoscan-install-source\u002Fskill-card.md",{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"skill.oms.sig","OTHER","其他",4593,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fholoscan-install-source\u002Fskill.oms.sig",[78,86,93,100,107,114],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"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":82,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]