[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FD8B181CSBDX6RSXDTFYVA":3,"skill-same:01M7FD8B181CSBDX6RSXDTFYVA":73},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":50},"01M7FD8B181CSBDX6RSXDTFYVA","vizro",null,"Use Vizro to build, validate, debug, extend, and maintain dashboards across vizro-core, Vizro-MCP, deprecated Vizro-AI, experimental chat, and Vizro Dash Components.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fvizro\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: vizro\ndescription: \"Use Vizro to build, validate, debug, extend, and maintain\n  dashboards across vizro-core, Vizro-MCP, deprecated Vizro-AI, experimental\n  chat, and Vizro Dash Components.\"\ndisable-model-invocation: true\nmetadata:\n  disco-role: operating\n  source-repo: mckinsey\u002Fvizro\n  source-commit: 99634b8e837d371f0d25c53692278b39236594e6\nlicense: Apache 2.0\n---\n\n# Vizro\n\nUse this skill when a task involves the Vizro monorepo or the installed Vizro packages: dashboard authoring, model\u002FYAML validation, charts\u002Ftables\u002Flayouts\u002Factions, MCP-assisted dashboard generation, the deprecated `vizro-ai` chart agent, experimental chat\u002Fpopup components, or `vizro-dash-components` custom Dash components.\n\n## Start Here\n\n1. Read `references\u002Frepo-provenance.md` to confirm the source snapshot, evidence scope, and freshness limits.\n2. Read `references\u002Fpackage-map.md` to identify the relevant package, public API surface, and known version-specific facts.\n3. Read `references\u002Fenvironment.md` before installing packages, building `vizro-dash-components`, running tests, using browser-backed examples, or touching provider-backed LLM features.\n4. Run `python scripts\u002Fprobe_vizro_environment.py` in the target environment for a quick installed-package smoke check.\n5. Use the route map below. Each sub-skill owns task-specific workflows and near references.\n6. When modifying this repository, also route to `sub-skills\u002Frepo-development-testing\u002FSKILL.md` for package-specific commands, backend-classified tests, and AGENTS constraints.\n\n## Route Map\n\n| User task | Use sub-skill | Why |\n| --- | --- | --- |\n| Build\u002Frun a Vizro dashboard in Python or YAML; validate `Dashboard`\u002F`Page`\u002Flayout basics | `sub-skills\u002Fcore-dashboard-build\u002FSKILL.md` | Owns `Vizro().build()`, `Vizro().run()`, dashboard\u002Fpage models, Python\u002FYAML authoring, layout-first debug patterns. |\n| Add or debug cards, graphs, tables, filters, selectors, data sources, custom components, or actions | `sub-skills\u002Fcore-components-data-actions\u002FSKILL.md` | Owns Vizro model composition, `data_manager`, action wiring, controls, table\u002Fgrid behavior, and validation failures. |\n| Choose or author charts\u002Ffigures\u002Ftables with Plotly\u002FVizro conventions | `sub-skills\u002Fcharts-and-figures\u002FSKILL.md` | Owns `vizro.plotly.express`, custom chart callables, visual-vocabulary guidance, and figure model pitfalls. |\n| Use or change Vizro-MCP agent\u002Fserver workflows | `sub-skills\u002Fmcp-agent-workflows\u002FSKILL.md` | Owns FastMCP server tools\u002Fresources, dashboard creation\u002Fvalidation helpers, schema extraction, and PyCafe workflows. |\n| Inspect or maintain the deprecated `vizro-ai` chart agent | `sub-skills\u002Flegacy-ai-chart-agent\u002FSKILL.md` | Owns `chart_agent`, response models, safeguard behavior, and deprecation-safe routing. |\n| Use or modify `vizro-experimental` chat component or floating popup | `sub-skills\u002Fexperimental-chat-popup\u002FSKILL.md` | Owns `Chat`, `add_chat_popup`, lazy agent helpers, BYO callback mode, and security constraints. |\n| Use\u002Fmaintain `vizro-dash-components` Cascader\u002FMarkdown components or generated wrappers | `sub-skills\u002Fdash-components-build\u002FSKILL.md` | Owns TypeScript source-of-truth, npm\u002Fwebpack\u002Fdash-generate-components pipeline, props, and browser-test constraints. |\n| Change repository code, docs, tests, build config, or package metadata | `sub-skills\u002Frepo-development-testing\u002FSKILL.md` | Owns monorepo layout, Hatch commands, package-local test commands, changelog, and backend-classified verification. |\n\n## Public Package Facts\n\n- `vizro-core` installs the public distribution `vizro`. Public Python examples typically use:\n\n  ```python\n  import vizro.models as vm\n  from vizro import Vizro\n\n  dashboard = vm.Dashboard(pages=[vm.Page(title=\"Home\", components=[vm.Card(text=\"Hello\")])])\n  app = Vizro().build(dashboard)   # returns the Vizro wrapper, not the raw Dash app\n  app.run()\n  ```\n\n  The underlying Dash app is `app.dash` after build.\n- `vizro.plotly.express` provides Vizro-oriented wrappers around Plotly Express; use it when authoring standard Vizro charts unless the task requires custom Plotly code.\n- `vizro-mcp` is the preferred maintained agent-assistance path for new AI\u002Fdashboard workflows.\n- `vizro-ai` is deprecated in this checkout. Maintain existing chart-agent behavior when requested, but do not recommend it for greenfield workflows when Vizro-MCP\u002Fe2e-flow is a better fit.\n- `vizro-experimental` APIs may change or graduate into `vizro-core`; state that caveat in user-facing solutions.\n- `vizro-dash-components` source of truth is TypeScript\u002FReact under `src\u002Fts`. Python files and JS bundles under `vizro_dash_components\u002F` are generated; do not hand-edit them.\n\n## Safety Defaults\n\n- Do not run live LLM provider calls unless the user explicitly supplies\u002Fauthorizes credentials and network use. Prefer import, schema, or BYO callback checks.\n- Do not require browser-backed `dash_duo`\u002FSelenium\u002Fe2e tests on hosts without Chrome\u002FChromium. Treat them as optional backend-specific gates and document the missing backend.\n- Do not run full monorepo test suites first. Start with package-local focused tests for the touched behavior; then broaden if needed.\n- Do not edit generated `vizro_dash_components\u002F*.py` or JS bundles directly. Edit TypeScript in `vizro-dash-components\u002Fsrc\u002Fts` and regenerate.\n- For repo edits, obey package-local `AGENTS.md`\u002F`CLAUDE.md`: Hatch commands run from the specific package directory; `vizro-e2e-flow` is a Claude plugin and its guide says no Hatch commands.\n\n## Bundled Helpers\n\n- `scripts\u002Fprobe_vizro_environment.py` checks imports and small CPU-only smoke behavior across Vizro packages.\n- `scripts\u002Finspect_vizro_schema.py` summarizes public Vizro model fields\u002Fschemas for dashboard-writing tasks.\n- `scripts\u002Fvalidate_vizro_dashboard.py` validates a small Python or YAML dashboard path when the installed package and PyYAML are available.\n\n## Common First Moves\n\n- User wants a dashboard: route to `core-dashboard-build`, then to `charts-and-figures` and `core-components-data-actions` as components\u002Fcharts\u002Factions\u002Fdata appear.\n- User wants AI-generated or agent-validated dashboards: route to `mcp-agent-workflows`; only use `legacy-ai-chart-agent` if the task explicitly mentions `vizro-ai` or existing chart-agent code.\n- User wants chat in a dashboard: route to `experimental-chat-popup`; prefer BYO `generate_response` for credential-free examples.\n- User touches custom Dash components: route to `dash-components-build` and `repo-development-testing`.\n- User touches repository code: load the relevant feature subskill plus `repo-development-testing`, then run focused tests with the package-local working directory.\n","# Vizro\n\nUse this skill when a task involves the Vizro monorepo or the installed Vizro packages: dashboard authoring, model\u002FYAML validation, charts\u002Ftables\u002Flayouts\u002Factions, MCP-assisted dashboard generation, the deprecated `vizro-ai` chart agent, experimental chat\u002Fpopup components, or `vizro-dash-components` custom Dash components.\n\n## Start Here\n\n1. Read `references\u002Frepo-provenance.md` to confirm the source snapshot, evidence scope, and freshness limits.\n2. Read `references\u002Fpackage-map.md` to identify the relevant package, public API surface, and known version-specific facts.\n3. Read `references\u002Fenvironment.md` before installing packages, building `vizro-dash-components`, running tests, using browser-backed examples, or touching provider-backed LLM features.\n4. Run `python scripts\u002Fprobe_vizro_environment.py` in the target environment for a quick installed-package smoke check.\n5. Use the route map below. Each sub-skill owns task-specific workflows and near references.\n6. When modifying this repository, also route to `sub-skills\u002Frepo-development-testing\u002FSKILL.md` for package-specific commands, backend-classified tests, and AGENTS constraints.\n\n## Route Map\n\n| User task | Use sub-skill | Why |\n| --- | --- | --- |\n| Build\u002Frun a Vizro dashboard in Python or YAML; validate `Dashboard`\u002F`Page`\u002Flayout basics | `sub-skills\u002Fcore-dashboard-build\u002FSKILL.md` | Owns `Vizro().build()`, `Vizro().run()`, dashboard\u002Fpage models, Python\u002FYAML authoring, layout-first debug patterns. |\n| Add or debug cards, graphs, tables, filters, selectors, data sources, custom components, or actions | `sub-skills\u002Fcore-components-data-actions\u002FSKILL.md` | Owns Vizro model composition, `data_manager`, action wiring, controls, table\u002Fgrid behavior, and validation failures. |\n| Choose or author charts\u002Ffigures\u002Ftables with Plotly\u002FVizro conventions | `sub-skills\u002Fcharts-and-figures\u002FSKILL.md` | Owns `vizro.plotly.express`, custom chart callables, visual-vocabulary guidance, and figure model pitfalls. |\n| Use or change Vizro-MCP agent\u002Fserver workflows | `sub-skills\u002Fmcp-agent-workflows\u002FSKILL.md` | Owns FastMCP server tools\u002Fresources, dashboard creation\u002Fvalidation helpers, schema extraction, and PyCafe workflows. |\n| Inspect or maintain the deprecated `vizro-ai` chart agent | `sub-skills\u002Flegacy-ai-chart-agent\u002FSKILL.md` | Owns `chart_agent`, response models, safeguard behavior, and deprecation-safe routing. |\n| Use or modify `vizro-experimental` chat component or floating popup | `sub-skills\u002Fexperimental-chat-popup\u002FSKILL.md` | Owns `Chat`, `add_chat_popup`, lazy agent helpers, BYO callback mode, and security constraints. |\n| Use\u002Fmaintain `vizro-dash-components` Cascader\u002FMarkdown components or generated wrappers | `sub-skills\u002Fdash-components-build\u002FSKILL.md` | Owns TypeScript source-of-truth, npm\u002Fwebpack\u002Fdash-generate-components pipeline, props, and browser-test constraints. |\n| Change repository code, docs, tests, build config, or package metadata | `sub-skills\u002Frepo-development-testing\u002FSKILL.md` | Owns monorepo layout, Hatch commands, package-local test commands, changelog, and backend-classified verification. |\n\n## Public Package Facts\n\n- `vizro-core` installs the public distribution `vizro`. Public Python examples typically use:\n\n  ```python\n  import vizro.models as vm\n  from vizro import Vizro\n\n  dashboard = vm.Dashboard(pages=[vm.Page(title=\"Home\", components=[vm.Card(text=\"Hello\")])])\n  app = Vizro().build(dashboard)   # returns the Vizro wrapper, not the raw Dash app\n  app.run()\n  ```\n\n  The underlying Dash app is `app.dash` after build.\n- `vizro.plotly.express` provides Vizro-oriented wrappers around Plotly Express; use it when authoring standard Vizro charts unless the task requires custom Plotly code.\n- `vizro-mcp` is the preferred maintained agent-assistance path for new AI\u002Fdashboard workflows.\n- `vizro-ai` is deprecated in this checkout. Maintain existing chart-agent behavior when requested, but do not recommend it for greenfield workflows when Vizro-MCP\u002Fe2e-flow is a better fit.\n- `vizro-experimental` APIs may change or graduate into `vizro-core`; state that caveat in user-facing solutions.\n- `vizro-dash-components` source of truth is TypeScript\u002FReact under `src\u002Fts`. Python files and JS bundles under `vizro_dash_components\u002F` are generated; do not hand-edit them.\n\n## Safety Defaults\n\n- Do not run live LLM provider calls unless the user explicitly supplies\u002Fauthorizes credentials and network use. Prefer import, schema, or BYO callback checks.\n- Do not require browser-backed `dash_duo`\u002FSelenium\u002Fe2e tests on hosts without Chrome\u002FChromium. Treat them as optional backend-specific gates and document the missing backend.\n- Do not run full monorepo test suites first. Start with package-local focused tests for the touched behavior; then broaden if needed.\n- Do not edit generated `vizro_dash_components\u002F*.py` or JS bundles directly. Edit TypeScript in `vizro-dash-components\u002Fsrc\u002Fts` and regenerate.\n- For repo edits, obey package-local `AGENTS.md`\u002F`CLAUDE.md`: Hatch commands run from the specific package directory; `vizro-e2e-flow` is a Claude plugin and its guide says no Hatch commands.\n\n## Bundled Helpers\n\n- `scripts\u002Fprobe_vizro_environment.py` checks imports and small CPU-only smoke behavior across Vizro packages.\n- `scripts\u002Finspect_vizro_schema.py` summarizes public Vizro model fields\u002Fschemas for dashboard-writing tasks.\n- `scripts\u002Fvalidate_vizro_dashboard.py` validates a small Python or YAML dashboard path when the installed package and PyYAML are available.\n\n## Common First Moves\n\n- User wants a dashboard: route to `core-dashboard-build`, then to `charts-and-figures` and `core-components-data-actions` as components\u002Fcharts\u002Factions\u002Fdata appear.\n- User wants AI-generated or agent-validated dashboards: route to `mcp-agent-workflows`; only use `legacy-ai-chart-agent` if the task explicitly mentions `vizro-ai` or existing chart-agent code.\n- User wants chat in a dashboard: route to `experimental-chat-popup`; prefer BYO `generate_response` for credential-free examples.\n- User touches custom Dash components: route to `dash-components-build` and `repo-development-testing`.\n- User touches repository code: load the relevant feature subskill plus `repo-development-testing`, then run focused tests with the package-local working directory.\n",{"name":5,"license":24,"metadata":25,"description":7,"disable-model-invocation":29},"Apache 2.0",{"disco-role":26,"source-repo":27,"source-commit":28},"operating","mckinsey\u002Fvizro","99634b8e837d371f0d25c53692278b39236594e6",true,"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","06-前端与设计\u002Fvizro",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":29},[40,43,46],{"tool":41,"command":42},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill vizro",{"tool":44,"command":45},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill vizro",{"tool":47,"command":48},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill vizro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fvizro\u002FSKILL.md",[51,57,61,65,69],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fenvironment.md","REFERENCE","参考文档",4638,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fvizro\u002Freferences\u002Fenvironment.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fpackage-map.md",5007,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fvizro\u002Freferences\u002Fpackage-map.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Frepo-provenance.md",2827,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fvizro\u002Freferences\u002Frepo-provenance.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Frepo-routing-metadata.json",398,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fvizro\u002Freferences\u002Frepo-routing-metadata.json",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fverification.md",4292,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fvizro\u002Freferences\u002Fverification.md",[74,82,87,94,101,108],{"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":78,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":83,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\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":78,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\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":78,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\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":78,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]