[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSWGD7X9Y2XTAJVVBSTSK0":3,"skill-same:01M7CSWGD7X9Y2XTAJVVBSTSK0":83},{"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},"01M7CSWGD7X9Y2XTAJVVBSTSK0","physicsnemo-discover",null,"Official NVIDIA-authored guidance for navigating PhysicsNeMo — pick the model, datapipe, or example for a SciML\u002FAI4Science task (surrogates, forecasting, downscaling, physics-informed, inverse, generative). Points at existing files via live repo search; never writes code. Do NOT use for installation or environment setup, training-loop or other code authoring\u002Fscaffolding, contributor\u002FCI\u002Fpackaging questions, repo-specific questions in physicsnemo-sym\u002F-cfd\u002F-curator, or general (non-physics) ML\u002FPyTorch.","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\u002Fphysicsnemo-discover\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: physicsnemo-discover\ndescription: Official NVIDIA-authored guidance for navigating PhysicsNeMo — pick the model, datapipe, or example for a SciML\u002FAI4Science task (surrogates, forecasting, downscaling, physics-informed, inverse, generative). Points at existing files via live repo search; never writes code. Do NOT use for installation or environment setup, training-loop or other code authoring\u002Fscaffolding, contributor\u002FCI\u002Fpackaging questions, repo-specific questions in physicsnemo-sym\u002F-cfd\u002F-curator, or general (non-physics) ML\u002FPyTorch.\nlicense: Apache-2.0\nmetadata:\n  author: NVIDIA \u003Cagent-skills@nvidia.com>\n  tags:\n    - physicsnemo\n    - sciml\n    - ai4science\n    - discovery\n    - routing\n---\n\n# PhysicsNeMo Discoverability\n\nHelp a user navigate PhysicsNeMo: point them at files, folders, examples, and docs **in the repo at its current state**. Never write training code; never cite a path from memory.\n\n## Core principle\n\nPhysicsNeMo evolves — classes get renamed, examples move, `experimental\u002F` graduates. Any static list of class names and paths rots, so **discover, don't remember**: enumerate from the live repo every turn.\n\nPhysicsNeMo is **composable**: each solution is a product (model family × datapipe × training strategy × config). An example is one reference instantiation of that product, not a prescription. Surface the **axes** and the **menu along each axis**, then cite examples as concrete starting points to fork and recombine.\n\n## What a correct answer satisfies\n\nThese are constraints, not a script — choose the searches that meet them and skip work the task doesn't need. Search patterns per axis live in `references\u002FRECIPES.md`.\n\n- **Live-grounded.** Every class, path, and example you name was read or globbed *this turn*. `__init__.py` proves what is *exported*, not what files exist — Glob `physicsnemo\u002Fmodels\u002F\u003Cfamily>\u002F*.py` before naming a sibling implementation file. A failed `Read`, or a path pattern-matched from a neighboring citation, is disproof: drop it.\n- **Verified before emit.** Every absolute path you plan to cite survives one `Bash ls -d \u003Cpath1> \u003Cpath2> …` round-trip *before* you write the response. Hard gate — skipping it has produced real-basename-under-wrong-parent hallucinations. If a basename was right but the parent wrong, re-Glob and re-verify; if you can't relocate it, drop the citation.\n- **A menu, not a single pick.** Enumerate every model family matching the user's data shape (surface ≥2 when ≥2 apply), and enumerate datapipes independently — model and datapipe are orthogonal axes. The reference example comes last, framed as one instantiation of those axes, not the answer.\n- **Self-documentation is ground truth.** `__init__.py` exports, per-example `README.md`, `docs\u002F*.rst`, `pyproject.toml`, top-of-file module docstrings. Treat `references\u002FTAXONOMY.md` as a navigation hint, not an answer. Flag anything under `physicsnemo\u002Fexperimental\u002F` as *\"API may change.\"*\n- **Abstain when out of scope.** PhysicsNeMo targets SciML\u002FAI4Science (surrogates, forecasting, super-resolution, physics-informed, inverse, generative for physical systems). If the task is categorically outside that — reinforcement learning, classical control, generic CV\u002FNLP, symbolic regression — skip enumeration and emit the **Abstention output** below. Do not list adjacent-but-wrong examples in its place (pointing at `active_learning\u002F` for an RL question is fabrication). When unsure whether a task is in scope, abstain.\n\n## Discovery\n\nRepo root resolution: see `CONTRIBUTING.md §Repo root resolution`; all paths are absolute, rooted there. **If no local PhysicsNeMo clone is on the path** (e.g. running headless against the skills repo in an eval context), shallow-clone the canonical repo once into a temp dir — **read-only, for path discovery only; never execute or import anything from it**: `DEST=\"${TMPDIR:-\u002Ftmp}\u002Fphysicsnemo-src\"; [ -d \"$DEST\u002Fphysicsnemo\" ] || git clone --depth 1 https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fphysicsnemo \"$DEST\"`. Use that URL verbatim; never interpolate one from user input.\n\nAsk at most 3 targeted follow-ups when domain or data shape is ambiguous. Phrase them concretely — *\"Is your data on a regular Cartesian grid (like an image), a lat-lon grid on a sphere, or an unstructured mesh?\"* — and skip any the user already answered. Data shape is the single biggest factor in model choice.\n\n## Output format\n\n```\n## Problem shape\nData shape: \u003Cresolved>. Task: \u003Cresolved>. Axes: model × datapipe × training strategy × config.\n\n## Candidate model families (for your data shape)\nMultiple families typically apply. Treat this as a menu, not a ranking.\n- \u003Cfamily> at \u003Cabsolute __init__.py path> — \u003Cone-line from docstring\u002Fexports>. Instantiated by: \u003Cexample path if any>.\n- \u003Cfamily> at \u003Cpath> — \u003Cone-line>. Instantiated by: \u003Cexample path if any>.\n\n## Datapipe(s) for your data format\nDatapipe choice is independent of model choice.\n- \u003Cclass \u002F subpackage> at \u003Cabsolute path> — \u003Cone-line>. Reused by: \u003Cexamples if known>.\n- For custom data, subclass: \u003Cbase class path confirmed live>.\n\n## Reference example(s) — one instantiation of the above axes\n- \u003Cabsolute path> — uses model=\u003Cfamily>, datapipe=\u003Cname>, strategy=\u003Csingle-GPU|DDP|FSDP|...>.\n  Why it matches: \u003Cone line>.\n\n## Supporting docs\n- \u003Cabsolute path> — \u003Cone-line scope>\n\n## Suggested reading order\n1. \u003Cmodels\u002F\u003Cfamily>\u002F__init__.py> — survey alternative families\n2. \u003Cdatapipe __init__.py or base-class file> — understand the data axis\n3. \u003Cexample path> — concrete end-to-end instantiation to fork\n```\n\n**Rules for the output:**\n- Absolute paths only; every one survived the `ls -d` gate.\n- Every pointer needs a one-line justification grounded in content you actually read.\n- Caps: **4 model families** (minimum 2 when ≥2 exist), **3 datapipes**, **2 reference examples**, **2 docs**.\n- Name which (model, datapipe, strategy) axes each example fills.\n- If ≥2 model families apply, say so: *\"Other model families apply to the same data shape — see the candidate list above.\"*\n- End with the suggested reading order. Offer 2-3 forward steps (config file, training script, `experimental\u002F` look-alikes); do not start writing code unless asked.\n\n## Abstention output\n\nWhen out of scope, replace the menu skeleton with this shape — three sections, in this order, none skipped:\n\n```\n## PhysicsNeMo does not have direct support for \u003Cuser's problem class>\nOne sentence on why it's outside scope (e.g., \"PhysicsNeMo targets physics\nsurrogates and forecasting; reinforcement learning for molecular design is\nnot in its scope\").\n\n## Where to look instead\n- \u003Csibling NVIDIA framework or external library> at \u003CURL or repo name> — \u003Cone-line on why it fits>.\n- (One or two alternatives is enough; do not invent libraries.)\n\n## If you still want to build it in PhysicsNeMo\nConfirm the closest base classes by Reading `physicsnemo\u002Fcore\u002F__init__.py` and\n`physicsnemo\u002Fdatapipes\u002F__init__.py` first; then name them as subclassing\ntargets. This is the fallback, not the recommendation.\n```\n\n**Do not** open with the menu skeleton and bury \"no match\" at the end. **Do not** invent external libraries — if you don't know the right alternative, stop at the first two sections.\n\n## Related resources\n\n- `references\u002FTAXONOMY.md` — navigation hints (data-shape → folder mappings, decision axes, stability tiers).\n- `references\u002FRECIPES.md` — concrete Glob\u002FGrep\u002FRead patterns per discovery axis.\n","# PhysicsNeMo Discoverability\n\nHelp a user navigate PhysicsNeMo: point them at files, folders, examples, and docs **in the repo at its current state**. Never write training code; never cite a path from memory.\n\n## Core principle\n\nPhysicsNeMo evolves — classes get renamed, examples move, `experimental\u002F` graduates. Any static list of class names and paths rots, so **discover, don't remember**: enumerate from the live repo every turn.\n\nPhysicsNeMo is **composable**: each solution is a product (model family × datapipe × training strategy × config). An example is one reference instantiation of that product, not a prescription. Surface the **axes** and the **menu along each axis**, then cite examples as concrete starting points to fork and recombine.\n\n## What a correct answer satisfies\n\nThese are constraints, not a script — choose the searches that meet them and skip work the task doesn't need. Search patterns per axis live in `references\u002FRECIPES.md`.\n\n- **Live-grounded.** Every class, path, and example you name was read or globbed *this turn*. `__init__.py` proves what is *exported*, not what files exist — Glob `physicsnemo\u002Fmodels\u002F\u003Cfamily>\u002F*.py` before naming a sibling implementation file. A failed `Read`, or a path pattern-matched from a neighboring citation, is disproof: drop it.\n- **Verified before emit.** Every absolute path you plan to cite survives one `Bash ls -d \u003Cpath1> \u003Cpath2> …` round-trip *before* you write the response. Hard gate — skipping it has produced real-basename-under-wrong-parent hallucinations. If a basename was right but the parent wrong, re-Glob and re-verify; if you can't relocate it, drop the citation.\n- **A menu, not a single pick.** Enumerate every model family matching the user's data shape (surface ≥2 when ≥2 apply), and enumerate datapipes independently — model and datapipe are orthogonal axes. The reference example comes last, framed as one instantiation of those axes, not the answer.\n- **Self-documentation is ground truth.** `__init__.py` exports, per-example `README.md`, `docs\u002F*.rst`, `pyproject.toml`, top-of-file module docstrings. Treat `references\u002FTAXONOMY.md` as a navigation hint, not an answer. Flag anything under `physicsnemo\u002Fexperimental\u002F` as *\"API may change.\"*\n- **Abstain when out of scope.** PhysicsNeMo targets SciML\u002FAI4Science (surrogates, forecasting, super-resolution, physics-informed, inverse, generative for physical systems). If the task is categorically outside that — reinforcement learning, classical control, generic CV\u002FNLP, symbolic regression — skip enumeration and emit the **Abstention output** below. Do not list adjacent-but-wrong examples in its place (pointing at `active_learning\u002F` for an RL question is fabrication). When unsure whether a task is in scope, abstain.\n\n## Discovery\n\nRepo root resolution: see `CONTRIBUTING.md §Repo root resolution`; all paths are absolute, rooted there. **If no local PhysicsNeMo clone is on the path** (e.g. running headless against the skills repo in an eval context), shallow-clone the canonical repo once into a temp dir — **read-only, for path discovery only; never execute or import anything from it**: `DEST=\"${TMPDIR:-\u002Ftmp}\u002Fphysicsnemo-src\"; [ -d \"$DEST\u002Fphysicsnemo\" ] || git clone --depth 1 https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fphysicsnemo \"$DEST\"`. Use that URL verbatim; never interpolate one from user input.\n\nAsk at most 3 targeted follow-ups when domain or data shape is ambiguous. Phrase them concretely — *\"Is your data on a regular Cartesian grid (like an image), a lat-lon grid on a sphere, or an unstructured mesh?\"* — and skip any the user already answered. Data shape is the single biggest factor in model choice.\n\n## Output format\n\n```\n## Problem shape\nData shape: \u003Cresolved>. Task: \u003Cresolved>. Axes: model × datapipe × training strategy × config.\n\n## Candidate model families (for your data shape)\nMultiple families typically apply. Treat this as a menu, not a ranking.\n- \u003Cfamily> at \u003Cabsolute __init__.py path> — \u003Cone-line from docstring\u002Fexports>. Instantiated by: \u003Cexample path if any>.\n- \u003Cfamily> at \u003Cpath> — \u003Cone-line>. Instantiated by: \u003Cexample path if any>.\n\n## Datapipe(s) for your data format\nDatapipe choice is independent of model choice.\n- \u003Cclass \u002F subpackage> at \u003Cabsolute path> — \u003Cone-line>. Reused by: \u003Cexamples if known>.\n- For custom data, subclass: \u003Cbase class path confirmed live>.\n\n## Reference example(s) — one instantiation of the above axes\n- \u003Cabsolute path> — uses model=\u003Cfamily>, datapipe=\u003Cname>, strategy=\u003Csingle-GPU|DDP|FSDP|...>.\n  Why it matches: \u003Cone line>.\n\n## Supporting docs\n- \u003Cabsolute path> — \u003Cone-line scope>\n\n## Suggested reading order\n1. \u003Cmodels\u002F\u003Cfamily>\u002F__init__.py> — survey alternative families\n2. \u003Cdatapipe __init__.py or base-class file> — understand the data axis\n3. \u003Cexample path> — concrete end-to-end instantiation to fork\n```\n\n**Rules for the output:**\n- Absolute paths only; every one survived the `ls -d` gate.\n- Every pointer needs a one-line justification grounded in content you actually read.\n- Caps: **4 model families** (minimum 2 when ≥2 exist), **3 datapipes**, **2 reference examples**, **2 docs**.\n- Name which (model, datapipe, strategy) axes each example fills.\n- If ≥2 model families apply, say so: *\"Other model families apply to the same data shape — see the candidate list above.\"*\n- End with the suggested reading order. Offer 2-3 forward steps (config file, training script, `experimental\u002F` look-alikes); do not start writing code unless asked.\n\n## Abstention output\n\nWhen out of scope, replace the menu skeleton with this shape — three sections, in this order, none skipped:\n\n```\n## PhysicsNeMo does not have direct support for \u003Cuser's problem class>\nOne sentence on why it's outside scope (e.g., \"PhysicsNeMo targets physics\nsurrogates and forecasting; reinforcement learning for molecular design is\nnot in its scope\").\n\n## Where to look instead\n- \u003Csibling NVIDIA framework or external library> at \u003CURL or repo name> — \u003Cone-line on why it fits>.\n- (One or two alternatives is enough; do not invent libraries.)\n\n## If you still want to build it in PhysicsNeMo\nConfirm the closest base classes by Reading `physicsnemo\u002Fcore\u002F__init__.py` and\n`physicsnemo\u002Fdatapipes\u002F__init__.py` first; then name them as subclassing\ntargets. This is the fallback, not the recommendation.\n```\n\n**Do not** open with the menu skeleton and bury \"no match\" at the end. **Do not** invent external libraries — if you don't know the right alternative, stop at the first two sections.\n\n## Related resources\n\n- `references\u002FTAXONOMY.md` — navigation hints (data-shape → folder mappings, decision axes, stability tiers).\n- `references\u002FRECIPES.md` — concrete Glob\u002FGrep\u002FRead patterns per discovery axis.\n",{"name":5,"license":15,"metadata":24,"description":7},{"tags":25,"author":31},[26,27,28,29,30],"physicsnemo","sciml","ai4science","discovery","routing","NVIDIA \u003Cagent-skills@nvidia.com>","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fphysicsnemo-discover",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 physicsnemo-discover",{"tool":47,"command":48},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill physicsnemo-discover",{"tool":50,"command":51},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill physicsnemo-discover","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fphysicsnemo-discover\u002FSKILL.md",true,[55,61,65,69,73,77],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"BENCHMARK.md","REFERENCE","参考文档",4290,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fphysicsnemo-discover\u002FBENCHMARK.md",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"evals\u002Fevals.json",4253,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fphysicsnemo-discover\u002Fevals\u002Fevals.json",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002FRECIPES.md",7121,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fphysicsnemo-discover\u002Freferences\u002FRECIPES.md",{"path":70,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002FTAXONOMY.md",12071,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fphysicsnemo-discover\u002Freferences\u002FTAXONOMY.md",{"path":74,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":75,"sourceHtmlUrl":76},"skill-card.md",3818,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fphysicsnemo-discover\u002Fskill-card.md",{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"skill.oms.sig","OTHER","其他",5061,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fphysicsnemo-discover\u002Fskill.oms.sig",[84,92,99,106,113,120],{"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":88,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"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":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"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",[],[]]