[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CQ7RYVR68W9PX6YRKBV921":3,"skill-same:01M7CQ7RYVR68W9PX6YRKBV921":60},{"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":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M7CQ7RYVR68W9PX6YRKBV921","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.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fnvidia-skills\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","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fnvidia-skills\u002Fphysicsnemo-discover",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill physicsnemo-discover",{"tool":46,"command":47},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill physicsnemo-discover",{"tool":49,"command":50},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill physicsnemo-discover","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fnvidia-skills\u002Fphysicsnemo-discover\u002FSkill.md",true,[54],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"metadata.json","REFERENCE","参考文档",430,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fnvidia-skills\u002Fphysicsnemo-discover\u002Fmetadata.json",[61,69,74,81,86,93],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":70,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":82,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\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":65,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":94,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]