[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSFDG1S4TY052PJ602979E":3,"skill-same:01M7CSFDG1S4TY052PJ602979E":85},{"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":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":37,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M7CSFDG1S4TY052PJ602979E","dynamo-interconnect-check",null,"Validate that a Dynamo deployment's NIXL\u002FUCX\u002FNCCL interconnect is ready for disaggregated serving over RDMA\u002FNVLink. Use after recipe-runner brings a deployment up (especially disagg\u002Fmulti-node) to confirm the KV transport is correct; use troubleshoot for diagnosing already-failed pods.","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\u002Fdynamo-interconnect-check\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dynamo-interconnect-check\ndescription: Validate that a Dynamo deployment's NIXL\u002FUCX\u002FNCCL interconnect is ready for disaggregated serving over RDMA\u002FNVLink. Use after recipe-runner brings a deployment up (especially disagg\u002Fmulti-node) to confirm the KV transport is correct; use troubleshoot for diagnosing already-failed pods.\nlicense: Apache-2.0\nmetadata:\n  author: Dan Gil \u003Cdagil@nvidia.com>\n  tags:\n    - dynamo\n    - nixl\n    - rdma\n    - disagg\n    - validation\n---\n\n# Dynamo Interconnect Check\n\n\u003C!--\nSPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.\nSPDX-License-Identifier: CC-BY-4.0\n-->\n\n## Purpose\n\nConfirm that the transport disaggregated serving depends on actually works. A\ndeployment can pass an endpoint smoke test while disagg is silently wrong: if\nNIXL\u002FUCX cannot reach the peer worker over RDMA or NVLink, KV transfer falls\nback to a slow or broken path. Catch that with read-only checks before trusting\na disagg deployment or its benchmark numbers.\n\nThis skill is read-only. It never mutates the cluster and never prints secrets.\n\n## Prerequisites\n\n- Python 3.10+ on the operator machine.\n- `kubectl exec` access to a worker pod in the target Dynamo deployment.\n- Read access to the recipe directory (`recipes\u002F\u003Cmodel>\u002F\u003Cframework>\u002F\u003Cmode>`).\n- For node-capability checks: tools like `ibstat`, `nvidia-smi`, `lsmod` available in the worker pod image (missing tools are reported as `skipped`, not failures).\n\n## When To Use\n\n- After `dynamo-recipe-runner` deploys a **disagg** or multi-node recipe.\n- Before reporting disagg throughput\u002Flatency, so numbers reflect the real\n  transport.\n- When agg works but disagg is slow, hangs, or returns wrong output and you\n  suspect the fabric rather than the model.\n\nFor diagnosing pods that are already crashing or unschedulable, use\n`dynamo-troubleshoot` first.\n\n## Instructions\n\n### 1. Check Transport Env Vars On The Recipe\n\n```bash\npython3 scripts\u002Fcheck_interconnect.py env recipes\u002F\u003Cmodel>\u002F\u003Cframework>\u002F\u003Cmode>\n```\n\nReports which NIXL\u002FUCX\u002FNCCL transport variables are set and flags\ndisagg-critical ones (e.g. `UCX_TLS`, `UCX_NET_DEVICES`, `NCCL_IB_HCA`) that are\nabsent. Missing here is only a warning — they may be baked into the image — so\nconfirm with the node and NIXL checks. See\n`references\u002Finterconnect-env-vars.md` for what each variable does.\n\n### 2. Check Node Capabilities\n\nLocally on a GPU node, or inside a running worker pod:\n\n```bash\npython3 scripts\u002Fcheck_interconnect.py node \\\n  --namespace \"${NAMESPACE}\" --pod \u003Cworker-pod>\n```\n\nProbes (read-only) for: InfiniBand devices and Active links, GPUDirect RDMA\n(`nvidia_peermem`), GDRCopy, and NVLink in the GPU topology. Missing tools are\nreported as `skipped`, not failures.\n\n### 3. Validate NIXL Reachability\n\n```bash\npython3 scripts\u002Fcheck_interconnect.py nixl \\\n  --namespace \"${NAMESPACE}\" --pod \u003Cworker-pod>\n```\n\nLooks for NIXL test tooling in the pod and surfaces the exact next step to run a\npairwise prefill↔decode transfer test. A full cross-pod transfer test requires\ntwo scheduled GPU pods on the fabric.\n\n## Available Scripts\n\n| Script | Purpose | Arguments |\n|---|---|---|\n| `scripts\u002Fcheck_interconnect.py env` | Inspect NIXL\u002FUCX\u002FNCCL env vars on a recipe | positional recipe path |\n| `scripts\u002Fcheck_interconnect.py node` | Probe InfiniBand, GPUDirect RDMA, GDRCopy, NVLink on a node or pod | `--namespace`, `--pod` |\n| `scripts\u002Fcheck_interconnect.py nixl` | Surface NIXL transfer-test readiness for a pod | `--namespace`, `--pod` |\n\nInvoke via the agentskills.io `run_script()` protocol:\n\n```python\nrun_script(\"scripts\u002Fcheck_interconnect.py\", args=[\"env\", \"recipes\u002Fqwen3-coder-480b\u002Fsglang\u002Fdisagg\"])\nrun_script(\"scripts\u002Fcheck_interconnect.py\", args=[\"node\", \"--namespace\", \"dynamo-demo\", \"--pod\", \"qwen-worker-0\"])\n```\n\n## Examples\n\nVerify a disagg recipe's transport env shape before deploy:\n\n```bash\npython3 scripts\u002Fcheck_interconnect.py env recipes\u002Fqwen3-coder-480b\u002Fsglang\u002Fdisagg\n```\n\nAfter deploy, validate a worker pod's fabric:\n\n```bash\npython3 scripts\u002Fcheck_interconnect.py node \\\n  --namespace dynamo-demo --pod qwen-worker-0\npython3 scripts\u002Fcheck_interconnect.py nixl \\\n  --namespace dynamo-demo --pod qwen-worker-0\n```\n\nEquivalent through the agent protocol:\n\n```python\nrun_script(\"scripts\u002Fcheck_interconnect.py\", args=[\"nixl\", \"--namespace\", \"dynamo-demo\", \"--pod\", \"qwen-worker-0\"])\n```\n\n## Output Contract\n\nEach check returns `ok` \u002F `warn` \u002F `fail` \u002F `skipped` with a one-line detail,\nplus a rolled-up verdict on disagg transport readiness. Report:\n\n- transport env vars present vs. disagg-critical ones missing\n- RDMA \u002F GPUDirect \u002F NVLink capability status\n- whether NIXL reachability was validated, and the next command if not\n- a clear statement of whether disagg can be trusted, or what to fix first\n\n## Limitations\n\n- Read-only fabric probe; does not run a full pairwise NIXL transfer (requires two scheduled GPU pods and the in-pod NIXL test tools).\n- `skipped` results for missing tools (`ibstat`, `nvidia-smi`, `lsmod`) are inconclusive, not a pass.\n- Env-var check inspects the recipe text; values injected at runtime via initContainers or operator-applied envs are not detected.\n- Single-node agg deployments do not exercise the transport — this skill is for disagg \u002F multi-node validation.\n\n## Troubleshooting\n\n| Symptom | Likely cause | Next step |\n|---|---|---|\n| `env` reports all critical vars missing | Vars baked into image or injected by operator | Run the `node` check inside the worker pod to verify actual env |\n| `node` reports no Active IB link | Fabric down or HCA not provisioned to the node | Contact cluster admin; verify `kubectl describe node` shows `nvidia.com\u002Fgpu` and IB labels |\n| `nvidia_peermem` missing | GPUDirect RDMA module not loaded | Ask cluster admin to load `nvidia-peermem`; without it, NIXL falls back to staged copies |\n| `nixl` finds no test tools | Worker image lacks NIXL test harness | Use a NIXL-enabled image or run the standalone transfer test from a debug pod |\n\n## Benchmark\n\nSee `BENCHMARK.md` for the NVCARPS-EVAL performance report (auto-generated by the NVSkills CI pipeline). To refresh, re-run `\u002Fnvskills-ci` on an upstream PR touching this skill.\n\n## References\n\n- `references\u002Finterconnect-env-vars.md` — NIXL\u002FUCX\u002FNCCL env var catalog and IB\n  capability checklist.\n- Use `scripts\u002Fcheck_interconnect.py` for all read-only checks.\n","# Dynamo Interconnect Check\n\n\u003C!--\nSPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.\nSPDX-License-Identifier: CC-BY-4.0\n-->\n\n## Purpose\n\nConfirm that the transport disaggregated serving depends on actually works. A\ndeployment can pass an endpoint smoke test while disagg is silently wrong: if\nNIXL\u002FUCX cannot reach the peer worker over RDMA or NVLink, KV transfer falls\nback to a slow or broken path. Catch that with read-only checks before trusting\na disagg deployment or its benchmark numbers.\n\nThis skill is read-only. It never mutates the cluster and never prints secrets.\n\n## Prerequisites\n\n- Python 3.10+ on the operator machine.\n- `kubectl exec` access to a worker pod in the target Dynamo deployment.\n- Read access to the recipe directory (`recipes\u002F\u003Cmodel>\u002F\u003Cframework>\u002F\u003Cmode>`).\n- For node-capability checks: tools like `ibstat`, `nvidia-smi`, `lsmod` available in the worker pod image (missing tools are reported as `skipped`, not failures).\n\n## When To Use\n\n- After `dynamo-recipe-runner` deploys a **disagg** or multi-node recipe.\n- Before reporting disagg throughput\u002Flatency, so numbers reflect the real\n  transport.\n- When agg works but disagg is slow, hangs, or returns wrong output and you\n  suspect the fabric rather than the model.\n\nFor diagnosing pods that are already crashing or unschedulable, use\n`dynamo-troubleshoot` first.\n\n## Instructions\n\n### 1. Check Transport Env Vars On The Recipe\n\n```bash\npython3 scripts\u002Fcheck_interconnect.py env recipes\u002F\u003Cmodel>\u002F\u003Cframework>\u002F\u003Cmode>\n```\n\nReports which NIXL\u002FUCX\u002FNCCL transport variables are set and flags\ndisagg-critical ones (e.g. `UCX_TLS`, `UCX_NET_DEVICES`, `NCCL_IB_HCA`) that are\nabsent. Missing here is only a warning — they may be baked into the image — so\nconfirm with the node and NIXL checks. See\n`references\u002Finterconnect-env-vars.md` for what each variable does.\n\n### 2. Check Node Capabilities\n\nLocally on a GPU node, or inside a running worker pod:\n\n```bash\npython3 scripts\u002Fcheck_interconnect.py node \\\n  --namespace \"${NAMESPACE}\" --pod \u003Cworker-pod>\n```\n\nProbes (read-only) for: InfiniBand devices and Active links, GPUDirect RDMA\n(`nvidia_peermem`), GDRCopy, and NVLink in the GPU topology. Missing tools are\nreported as `skipped`, not failures.\n\n### 3. Validate NIXL Reachability\n\n```bash\npython3 scripts\u002Fcheck_interconnect.py nixl \\\n  --namespace \"${NAMESPACE}\" --pod \u003Cworker-pod>\n```\n\nLooks for NIXL test tooling in the pod and surfaces the exact next step to run a\npairwise prefill↔decode transfer test. A full cross-pod transfer test requires\ntwo scheduled GPU pods on the fabric.\n\n## Available Scripts\n\n| Script | Purpose | Arguments |\n|---|---|---|\n| `scripts\u002Fcheck_interconnect.py env` | Inspect NIXL\u002FUCX\u002FNCCL env vars on a recipe | positional recipe path |\n| `scripts\u002Fcheck_interconnect.py node` | Probe InfiniBand, GPUDirect RDMA, GDRCopy, NVLink on a node or pod | `--namespace`, `--pod` |\n| `scripts\u002Fcheck_interconnect.py nixl` | Surface NIXL transfer-test readiness for a pod | `--namespace`, `--pod` |\n\nInvoke via the agentskills.io `run_script()` protocol:\n\n```python\nrun_script(\"scripts\u002Fcheck_interconnect.py\", args=[\"env\", \"recipes\u002Fqwen3-coder-480b\u002Fsglang\u002Fdisagg\"])\nrun_script(\"scripts\u002Fcheck_interconnect.py\", args=[\"node\", \"--namespace\", \"dynamo-demo\", \"--pod\", \"qwen-worker-0\"])\n```\n\n## Examples\n\nVerify a disagg recipe's transport env shape before deploy:\n\n```bash\npython3 scripts\u002Fcheck_interconnect.py env recipes\u002Fqwen3-coder-480b\u002Fsglang\u002Fdisagg\n```\n\nAfter deploy, validate a worker pod's fabric:\n\n```bash\npython3 scripts\u002Fcheck_interconnect.py node \\\n  --namespace dynamo-demo --pod qwen-worker-0\npython3 scripts\u002Fcheck_interconnect.py nixl \\\n  --namespace dynamo-demo --pod qwen-worker-0\n```\n\nEquivalent through the agent protocol:\n\n```python\nrun_script(\"scripts\u002Fcheck_interconnect.py\", args=[\"nixl\", \"--namespace\", \"dynamo-demo\", \"--pod\", \"qwen-worker-0\"])\n```\n\n## Output Contract\n\nEach check returns `ok` \u002F `warn` \u002F `fail` \u002F `skipped` with a one-line detail,\nplus a rolled-up verdict on disagg transport readiness. Report:\n\n- transport env vars present vs. disagg-critical ones missing\n- RDMA \u002F GPUDirect \u002F NVLink capability status\n- whether NIXL reachability was validated, and the next command if not\n- a clear statement of whether disagg can be trusted, or what to fix first\n\n## Limitations\n\n- Read-only fabric probe; does not run a full pairwise NIXL transfer (requires two scheduled GPU pods and the in-pod NIXL test tools).\n- `skipped` results for missing tools (`ibstat`, `nvidia-smi`, `lsmod`) are inconclusive, not a pass.\n- Env-var check inspects the recipe text; values injected at runtime via initContainers or operator-applied envs are not detected.\n- Single-node agg deployments do not exercise the transport — this skill is for disagg \u002F multi-node validation.\n\n## Troubleshooting\n\n| Symptom | Likely cause | Next step |\n|---|---|---|\n| `env` reports all critical vars missing | Vars baked into image or injected by operator | Run the `node` check inside the worker pod to verify actual env |\n| `node` reports no Active IB link | Fabric down or HCA not provisioned to the node | Contact cluster admin; verify `kubectl describe node` shows `nvidia.com\u002Fgpu` and IB labels |\n| `nvidia_peermem` missing | GPUDirect RDMA module not loaded | Ask cluster admin to load `nvidia-peermem`; without it, NIXL falls back to staged copies |\n| `nixl` finds no test tools | Worker image lacks NIXL test harness | Use a NIXL-enabled image or run the standalone transfer test from a debug pod |\n\n## Benchmark\n\nSee `BENCHMARK.md` for the NVCARPS-EVAL performance report (auto-generated by the NVSkills CI pipeline). To refresh, re-run `\u002Fnvskills-ci` on an upstream PR touching this skill.\n\n## References\n\n- `references\u002Finterconnect-env-vars.md` — NIXL\u002FUCX\u002FNCCL env var catalog and IB\n  capability checklist.\n- Use `scripts\u002Fcheck_interconnect.py` for all read-only checks.\n",{"name":5,"license":15,"metadata":24,"description":7},{"tags":25,"author":31},[26,27,28,29,30],"dynamo","nixl","rdma","disagg","validation","Dan Gil \u003Cdagil@nvidia.com>","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fdynamo-interconnect-check",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":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill dynamo-interconnect-check",{"tool":47,"command":48},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill dynamo-interconnect-check",{"tool":50,"command":51},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill dynamo-interconnect-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fdynamo-interconnect-check\u002FSKILL.md",true,[55,61,65,69,75,79],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"BENCHMARK.md","REFERENCE","参考文档",2924,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fdynamo-interconnect-check\u002FBENCHMARK.md",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"evals\u002Fevals.json",3203,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fdynamo-interconnect-check\u002Fevals\u002Fevals.json",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Finterconnect-env-vars.md",3580,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fdynamo-interconnect-check\u002Freferences\u002Finterconnect-env-vars.md",{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Fcheck_interconnect.py","SCRIPT","脚本",13099,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fdynamo-interconnect-check\u002Fscripts\u002Fcheck_interconnect.py",{"path":76,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":77,"sourceHtmlUrl":78},"skill-card.md",2512,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fdynamo-interconnect-check\u002Fskill-card.md",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"skill.oms.sig","OTHER","其他",5093,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fdynamo-interconnect-check\u002Fskill.oms.sig",[86,94,101,108,115,122],{"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":90,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"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",[],[]]