[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7976JG9QZSVCVMWGCKCBWKQ":3,"skill-same:01M7976JG9QZSVCVMWGCKCBWKQ":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":46},"01M7976JG9QZSVCVMWGCKCBWKQ","core-dashboard-build",null,"Build, validate, run, and troubleshoot Vizro dashboards in Python or YAML using vizro-core models and the Vizro app wrapper.","VectorSpaceLab\u002FAREX-Skill","VectorSpaceLab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F180637102?v=4","01M7538C5WPSJGWF7KHR4EFZ9F","01M7538C6R2GFP53NPXTCZNBRT",351,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fvizro\u002Fsub-skills\u002Fcore-dashboard-build\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: core-dashboard-build\ndescription: \"Build, validate, run, and troubleshoot Vizro dashboards in Python\n  or YAML using vizro-core models and the Vizro app wrapper.\"\ndisable-model-invocation: true\nmetadata:\n  disco-role: operating\nlicense: Apache 2.0\n---\n\n# Core Dashboard Build\n\nUse this sub-skill when the task is to create, validate, run, deploy, or troubleshoot a Vizro dashboard at the dashboard\u002Fpage\u002Flayout level.\n\nRoute elsewhere when the task is mainly about:\n- Data, controls, actions, or component wiring: `..\u002Fcore-components-data-actions\u002FSKILL.md`.\n- Chart selection or Plotly figure code: `..\u002Fcharts-and-figures\u002FSKILL.md`.\n- Agent\u002FMCP dashboard generation: `..\u002Fmcp-agent-workflows\u002FSKILL.md`.\n- Repository tests\u002Fbuild tooling: `..\u002Frepo-development-testing\u002FSKILL.md`.\n\n## Fast Path: Python dashboard\n\n```python\nfrom vizro import Vizro\nimport vizro.models as vm\n\npage = vm.Page(\n    title=\"Overview\",\n    components=[\n        vm.Card(text=\"Hello Vizro\"),\n    ],\n)\n\ndashboard = vm.Dashboard(pages=[page], title=\"My dashboard\")\napp = Vizro().build(dashboard)  # returns the Vizro wrapper\napp.run(debug=True)\n```\n\nImportant: `Vizro().build()` returns the `Vizro` wrapper. Use `app.dash` for raw Dash APIs, callback maps, `index_string`, server integration, or app title checks.\n\n## Fast Path: YAML dashboard\n\nYAML examples load into the same Pydantic models:\n\n```python\nfrom pathlib import Path\nimport yaml\nfrom vizro import Vizro\nfrom vizro.models import Dashboard\n\nconfig = yaml.safe_load(Path(\"dashboard.yaml\").read_text(encoding=\"utf-8\"))\ndashboard = Dashboard(**config)\nVizro().build(dashboard).run()\n```\n\nUse `scripts\u002Fvalidate_vizro_dashboard.py dashboard.yaml` to parse and build without starting a server.\n\n## Dashboard\u002Fpage rules of thumb\n\n- Build from `vm.Dashboard(pages=[...])` and `vm.Page(title=..., components=[...])` first; add data, filters, actions, and charts after the skeleton validates.\n- Keep each page title unique and human-readable. The navigation layer derives behavior from pages and routes.\n- Prefer documented Vizro models over raw Dash components for normal authoring; raw Dash components are useful for custom components only after model options are exhausted.\n- Use Pydantic validation errors as a guide: they usually point to a wrong model field, wrong component type, or missing required nested object.\n- If a page uses external assets, pass `assets_folder` into `Vizro(...)` rather than relying on the current working directory.\n\n## Layout guidance\n\n- Use Vizro containers\u002Flayout models for dashboard layout rather than manual Dash CSS when possible.\n- Start with simple vertical page structure and introduce grids\u002Ftabs\u002Fcontainers only when the user asks for specific layout behavior.\n- Existing e2e-flow layout knowledge in the repository favors task-driven layouts: prioritize dashboard purpose, page hierarchy, and scan order before styling details.\n\n## Validation and smoke checks\n\n```bash\n# Installed package smoke\npython scripts\u002Fprobe_vizro_environment.py\n\n# Validate a YAML or Python dashboard without running a server\npython scripts\u002Fvalidate_vizro_dashboard.py path\u002Fto\u002Fdashboard.yaml\npython scripts\u002Fvalidate_vizro_dashboard.py path\u002Fto\u002Fapp.py\n```\n\nFor repository edits, use package-local tests from `..\u002Frepo-development-testing\u002FSKILL.md`; do not start with full browser e2e unless the task actually touches browser behavior and Chrome\u002FChromium is available.\n\n## Evidence anchors\n\n- `vizro-core\u002Fsrc\u002Fvizro\u002F_vizro.py`: `Vizro`, `build`, `run`, Dash app handling.\n- `vizro-core\u002Fsrc\u002Fvizro\u002Fmodels\u002F_dashboard.py`, `_page.py`: core model validation\u002Fbuild behavior.\n- `vizro-core\u002Fexamples\u002Ftutorial\u002Fapp.py`: Python dashboard example.\n- `vizro-core\u002Fexamples\u002Fdev\u002Fyaml_version\u002F{app.py,dashboard.yaml}`: YAML loading pattern.\n- `vizro-core\u002Fdocs\u002Fpages\u002Fuser-guides\u002F{layouts,run-deploy}.md` and existing `vizro-e2e-flow` dashboard\u002FYAML\u002Flayout skills.\n","# Core Dashboard Build\n\nUse this sub-skill when the task is to create, validate, run, deploy, or troubleshoot a Vizro dashboard at the dashboard\u002Fpage\u002Flayout level.\n\nRoute elsewhere when the task is mainly about:\n- Data, controls, actions, or component wiring: `..\u002Fcore-components-data-actions\u002FSKILL.md`.\n- Chart selection or Plotly figure code: `..\u002Fcharts-and-figures\u002FSKILL.md`.\n- Agent\u002FMCP dashboard generation: `..\u002Fmcp-agent-workflows\u002FSKILL.md`.\n- Repository tests\u002Fbuild tooling: `..\u002Frepo-development-testing\u002FSKILL.md`.\n\n## Fast Path: Python dashboard\n\n```python\nfrom vizro import Vizro\nimport vizro.models as vm\n\npage = vm.Page(\n    title=\"Overview\",\n    components=[\n        vm.Card(text=\"Hello Vizro\"),\n    ],\n)\n\ndashboard = vm.Dashboard(pages=[page], title=\"My dashboard\")\napp = Vizro().build(dashboard)  # returns the Vizro wrapper\napp.run(debug=True)\n```\n\nImportant: `Vizro().build()` returns the `Vizro` wrapper. Use `app.dash` for raw Dash APIs, callback maps, `index_string`, server integration, or app title checks.\n\n## Fast Path: YAML dashboard\n\nYAML examples load into the same Pydantic models:\n\n```python\nfrom pathlib import Path\nimport yaml\nfrom vizro import Vizro\nfrom vizro.models import Dashboard\n\nconfig = yaml.safe_load(Path(\"dashboard.yaml\").read_text(encoding=\"utf-8\"))\ndashboard = Dashboard(**config)\nVizro().build(dashboard).run()\n```\n\nUse `scripts\u002Fvalidate_vizro_dashboard.py dashboard.yaml` to parse and build without starting a server.\n\n## Dashboard\u002Fpage rules of thumb\n\n- Build from `vm.Dashboard(pages=[...])` and `vm.Page(title=..., components=[...])` first; add data, filters, actions, and charts after the skeleton validates.\n- Keep each page title unique and human-readable. The navigation layer derives behavior from pages and routes.\n- Prefer documented Vizro models over raw Dash components for normal authoring; raw Dash components are useful for custom components only after model options are exhausted.\n- Use Pydantic validation errors as a guide: they usually point to a wrong model field, wrong component type, or missing required nested object.\n- If a page uses external assets, pass `assets_folder` into `Vizro(...)` rather than relying on the current working directory.\n\n## Layout guidance\n\n- Use Vizro containers\u002Flayout models for dashboard layout rather than manual Dash CSS when possible.\n- Start with simple vertical page structure and introduce grids\u002Ftabs\u002Fcontainers only when the user asks for specific layout behavior.\n- Existing e2e-flow layout knowledge in the repository favors task-driven layouts: prioritize dashboard purpose, page hierarchy, and scan order before styling details.\n\n## Validation and smoke checks\n\n```bash\n# Installed package smoke\npython scripts\u002Fprobe_vizro_environment.py\n\n# Validate a YAML or Python dashboard without running a server\npython scripts\u002Fvalidate_vizro_dashboard.py path\u002Fto\u002Fdashboard.yaml\npython scripts\u002Fvalidate_vizro_dashboard.py path\u002Fto\u002Fapp.py\n```\n\nFor repository edits, use package-local tests from `..\u002Frepo-development-testing\u002FSKILL.md`; do not start with full browser e2e unless the task actually touches browser behavior and Chrome\u002FChromium is available.\n\n## Evidence anchors\n\n- `vizro-core\u002Fsrc\u002Fvizro\u002F_vizro.py`: `Vizro`, `build`, `run`, Dash app handling.\n- `vizro-core\u002Fsrc\u002Fvizro\u002Fmodels\u002F_dashboard.py`, `_page.py`: core model validation\u002Fbuild behavior.\n- `vizro-core\u002Fexamples\u002Ftutorial\u002Fapp.py`: Python dashboard example.\n- `vizro-core\u002Fexamples\u002Fdev\u002Fyaml_version\u002F{app.py,dashboard.yaml}`: YAML loading pattern.\n- `vizro-core\u002Fdocs\u002Fpages\u002Fuser-guides\u002F{layouts,run-deploy}.md` and existing `vizro-e2e-flow` dashboard\u002FYAML\u002Flayout skills.\n",{"name":5,"license":23,"metadata":24,"description":7,"disable-model-invocation":26},"Apache 2.0",{"disco-role":25},"operating",true,"main","ac3fe1afa80fb9a09775ecfb2b6cc3ba850a2db6","skills\u002Frepositories\u002Frepo-skills\u002Fvizro\u002Fsub-skills\u002Fcore-dashboard-build",27,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab","2026-09-03 10:25:21",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":26},[36,39,42],{"tool":37,"command":38},"npx","npx skills add VectorSpaceLab\u002FAREX-Skill --skill core-dashboard-build",{"tool":40,"command":41},"bunx","bunx skills add VectorSpaceLab\u002FAREX-Skill --skill core-dashboard-build",{"tool":43,"command":44},"pnpm","pnpm dlx skills add VectorSpaceLab\u002FAREX-Skill --skill core-dashboard-build","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fvizro\u002Fsub-skills\u002Fcore-dashboard-build\u002FSKILL.md",[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":18},"01M799NYSH1R3RVAHSM2D88Y84","passnet-triton-opt","Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block\u002Fgrid\u002Fwarp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-triton-opt\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M799NS5APEC0N1FZ7XZVW6BN","passnet-solve","END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-solve\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M799NNY9BKSM21V5R7QVTBJX","passnet-skill","PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under .\u002Fpass_dir\u002F, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-skill\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M799NHH6NP7Z1RK77KGXAN6S","passnet-pattern-fusion","Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()\u002Freplacement_args()\u002Freplacement_func() files, when a pass \"failed to match\", or when deciding how to fuse multiple kernels\u002Fops.","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-pattern-fusion\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M799ND2J4WNC2PGAZ0A06NDF","passnet-orchestrate","Round\u002Fbatch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep\u002Frevert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-orchestrate\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M799N8SBTMY02ZDG2AZF5ZWE","passnet-feedback","Fast, deterministic feedback for PassNet work: pre-flight pattern\u002Fmatch verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-feedback\u002FSKILL.md",[],[]]