[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DMTH89WM3FW4Q2F4QJC3GG":3,"skill-same:01M7DMTH89WM3FW4Q2F4QJC3GG":58},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7DMTH89WM3FW4Q2F4QJC3GG","domino-extensions",null,"Build and operate Domino UI Extensions (mount a published Domino App at a Domino UI mount point with page context). Covers extension_manifest.json, the official installer versus the manual Extensions API, App publish and identity requirements, auth and host rules for Extension backends, and the \u002Fapi\u002Fextensions\u002Fbeta routes. Use when creating an Extension, wiring mount points, publishing an Extension App from a project, pointing an Extension at a new App version, or automating the Extension install lifecycle. Not for generic App deployment alone (see domino-apps) or SPA scaffolding (see domino-ui-bootstrap).","dominodatalab\u002Fdomino-ai-plugin","dominodatalab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F8785569?v=4","01M7DMQ6VQCJ3KNYCSH3RRTDZM","Domino Data Lab","01M7DMQ6W7BDGQZFS2FX8NM6XG",5,"MIT","https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-extensions\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: domino-extensions\ndescription: Build and operate Domino UI Extensions (mount a published Domino App at a Domino UI mount point with page context). Covers extension_manifest.json, the official installer versus the manual Extensions API, App publish and identity requirements, auth and host rules for Extension backends, and the \u002Fapi\u002Fextensions\u002Fbeta routes. Use when creating an Extension, wiring mount points, publishing an Extension App from a project, pointing an Extension at a new App version, or automating the Extension install lifecycle. Not for generic App deployment alone (see domino-apps) or SPA scaffolding (see domino-ui-bootstrap).\ncompatibility: Domino 6.3 and Domino Cloud. Requires DOMINO_API_HOST; in a run use DOMINO_API_PROXY, outside a run a Personal Access Token or service account token. Creating an Extension needs admin permissions; publishing its App with extended identity propagation needs a SysAdmin or CloudAdmin.\n---\n\n# Domino Extensions\n\nApplies to Domino 6.3 and Domino Cloud.\n\nAn **Extension** surfaces a published **App** at a Domino UI **mount point** (Project sidebar, Dataset details page, Dataset file three-dot menu, Model details page, Admin panel). Domino opens the App in a new tab and passes the originating page's context as query parameters. One App can back several Extensions; pointing an Extension at a newer App version is an admin configuration change, not a rebuild.\n\n## When to use other skills\n\n| Goal | Skill |\n|---|---|\n| Vite\u002FReact design system, `@dominodatalab\u002Fextensions-tools`, proxy-safe URLs | [domino-ui-bootstrap](..\u002Fdomino-ui-bootstrap\u002FSKILL.md) |\n| `app.sh`, ports, prefixes, App publish chain (`\u002Fapi\u002Fapps\u002Fv1`), CI | [domino-apps](..\u002Fdomino-apps\u002FSKILL.md), [domino-apps\u002FAPI-APPS.md](..\u002Fdomino-apps\u002FAPI-APPS.md) |\n| Authentication, hosts, pagination and errors for any Domino API call | [domino-api-intro](..\u002Fdomino-api-intro\u002FSKILL.md) |\n| Governance from an Extension backend | [domino-governance](..\u002Fdomino-governance\u002FSKILL.md) |\n\nDocs: https:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Fplatform-capabilities\u002Ffeatures\u002Fextensions (overview), https:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Fplatform-capabilities\u002Ffeatures\u002Fextensions\u002Fcreate-manage-extensions (build your own), https:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Fplatform-capabilities\u002Ffeatures\u002Fextensions\u002Finstall-domino-official-extensions (official catalog). The same pages exist under `\u002F6.3\u002F`.\n\n## Requirements on the App\n\n1. **Extended identity propagation enabled** (\"Allow App to act for viewers in Domino\" on the Access & sharing step; `content.extendedIdentityPropagationToAppsEnabled: true` on the App version over the API). Only a SysAdmin or CloudAdmin can publish an App with it on; without it the App cannot back an Extension (`POST \u002Fapi\u002Fextensions\u002Fbeta\u002Fextensions` returns 400). The deployment needs `SecureIdentityPropagationToAppsEnabled` and `com.cerebro.domino.apps.extendedIdentityPropagationToAppsEnabled`, both on by default on Cloud and 6.3. Once enabled on an App it cannot be disabled.\n2. **A framework that reads proxied HTTP headers**: Flask and Dash do by default; Shiny needs Shiny Server Pro. The per-request viewer token arrives in the `Authorization` header after the viewer consents.\n3. **Published and viewable**: an Extension inherits the App's access controls; users without view access see it listed and are prompted to request access.\n4. Domino's App guidelines: call Domino APIs from backend code only (never from frontend JavaScript), authenticate with the per-request bearer from `Authorization` (never an API key), keep the App stateless or protect cached data like its source, declare dependencies in the Compute Environment's Dockerfile.\n\n## Mount points and context\n\n| `uiMountPointTypeConfigs` key | Where | Query parameters passed to `\u002F` |\n|---|---|---|\n| `projectSidebar` | Project navigation sidebar | `projectId` |\n| `dataset` | Dataset details page | `datasetId` |\n| `datasetFileContext` | Three-dot menu of a file in a Dataset | `datasetId`, `datasetSnapshotId`, `filePath` |\n| `modelDetails` | Model details page | `modelId`, `modelVersionId` |\n| `adminPanel` | New page in the Admin panel | none |\n| `netAppVolume`, `netAppVolumeFileContext` | NetApp Volume pages (API only) | `netAppVolumeId`, `netAppVolumeSnapshotId`, `filePath` |\n\n`urlConfig.contextualQueryParams` accepts only the spec enum (the eight names above), and the App receives exactly what the config lists. The file parameter is `filePath`, not `datasetFilePath`. Read the parameters on the App's root route, validate the ones you need and return a clear 400 when they are missing, and call Domino with the forwarded `Authorization` header. A worked Flask example and the exact config shapes are in [API-EXTENSIONS.md](.\u002FAPI-EXTENSIONS.md).\n\n## Create an Extension (custom App)\n\n1. **Build and preview** the App in a workspace (App Preview), then **Publish App** as a SysAdmin or CloudAdmin with extended identity propagation on. Over the API: [domino-apps\u002FAPI-APPS.md](..\u002Fdomino-apps\u002FAPI-APPS.md).\n2. **Create the Extension** from the App's three-dot menu (**Create Extension**) or **Admin panel > Extensions > Create Extension**: pick the App version and add one or more mount points. Needs admin permissions (a 403 means they are missing; see API-EXTENSIONS.md). Over the API: `POST \u002Fapi\u002Fextensions\u002Fbeta\u002Fextensions` with `name`, `enabled`, `appId`, **`appVersionId`** (a version with extended identity propagation on) and `uiMountPointTypeConfigs`; all five are required, `description` is optional. Body and the other routes: [API-EXTENSIONS.md](.\u002FAPI-EXTENSIONS.md).\n3. **Manage** from Admin panel > Extensions: toggle enabled, **Manage Extension > Edit** to change mount points or the App version, **Delete** to soft-delete. Publishing a new App version does not move the Extension; edit it in the UI or `PATCH` `appVersionId` over the API.\n\n## Official Extensions (manifest-driven)\n\nDomino-built Extensions are installed, upgraded and uninstalled from **Admin panel > Extensions > Manage Domino-official Extensions**; the installer reads `extension_manifest.json` (`manifestSchemaVersion: 1`, sections `project`, `app`, `extension`) from a GitHub release and creates the Project, Compute Environment, App and Extension itself. Do not edit those managed entities by hand. Manifest fields, lifecycle rules and the install routes: [MANIFEST.md](.\u002FMANIFEST.md).\n\n## Auth and hosts in Extension backends\n\n| Call | Credential and base |\n|---|---|\n| Platform API as the **viewer** | Forward the request's `Authorization` header unchanged to `$DOMINO_API_HOST\u002Fapi\u002F...`; answer 401 when it is missing. Consent expires (8 hours by default, up to 30 days) |\n| Platform API as the **publisher** | `$DOMINO_API_PROXY\u002Fapi\u002F...` with no header, or a bearer from `$DOMINO_API_PROXY\u002Faccess-token` |\n| Governance `\u002Fapi\u002Fgovernance\u002Fv1\u002F*` | Base URL per the `domino-governance` skill; bearer PAT or service account, never an API key |\n| Model inference | The `url` from the endpoint record, not a hand-built host |\n| Automation outside any run | Public deployment URL plus PAT or service account token |\n\nUntil a viewer consents, Domino redirects every request, JSON included, to `\u002Fapp-consent`. The bearer is the viewer's own credential: take the viewer from its `preferred_username` claim, never `domino-username` (not sent here; clients can forge it); never log or store the token, never call without it (`$DOMINO_API_HOST` runs header-less calls as the publisher). No browser links from `DOMINO_API_HOST` or `DOMINO_USER_HOST`; put the public URL in a project environment variable. Slash, routes, scripts: [API-EXTENSIONS.md](.\u002FAPI-EXTENSIONS.md#identity-urls-and-scripts).\n\n## Reference files\n\n- [API-EXTENSIONS.md](.\u002FAPI-EXTENSIONS.md): `\u002Fapi\u002Fextensions\u002Fbeta` routes, create body, mount config shapes, Flask context example, patch and delete.\n- [MANIFEST.md](.\u002FMANIFEST.md): `extension_manifest.json` fields, official install lifecycle and routes.\n","# Domino Extensions\n\nApplies to Domino 6.3 and Domino Cloud.\n\nAn **Extension** surfaces a published **App** at a Domino UI **mount point** (Project sidebar, Dataset details page, Dataset file three-dot menu, Model details page, Admin panel). Domino opens the App in a new tab and passes the originating page's context as query parameters. One App can back several Extensions; pointing an Extension at a newer App version is an admin configuration change, not a rebuild.\n\n## When to use other skills\n\n| Goal | Skill |\n|---|---|\n| Vite\u002FReact design system, `@dominodatalab\u002Fextensions-tools`, proxy-safe URLs | [domino-ui-bootstrap](..\u002Fdomino-ui-bootstrap\u002FSKILL.md) |\n| `app.sh`, ports, prefixes, App publish chain (`\u002Fapi\u002Fapps\u002Fv1`), CI | [domino-apps](..\u002Fdomino-apps\u002FSKILL.md), [domino-apps\u002FAPI-APPS.md](..\u002Fdomino-apps\u002FAPI-APPS.md) |\n| Authentication, hosts, pagination and errors for any Domino API call | [domino-api-intro](..\u002Fdomino-api-intro\u002FSKILL.md) |\n| Governance from an Extension backend | [domino-governance](..\u002Fdomino-governance\u002FSKILL.md) |\n\nDocs: https:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Fplatform-capabilities\u002Ffeatures\u002Fextensions (overview), https:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Fplatform-capabilities\u002Ffeatures\u002Fextensions\u002Fcreate-manage-extensions (build your own), https:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Fplatform-capabilities\u002Ffeatures\u002Fextensions\u002Finstall-domino-official-extensions (official catalog). The same pages exist under `\u002F6.3\u002F`.\n\n## Requirements on the App\n\n1. **Extended identity propagation enabled** (\"Allow App to act for viewers in Domino\" on the Access & sharing step; `content.extendedIdentityPropagationToAppsEnabled: true` on the App version over the API). Only a SysAdmin or CloudAdmin can publish an App with it on; without it the App cannot back an Extension (`POST \u002Fapi\u002Fextensions\u002Fbeta\u002Fextensions` returns 400). The deployment needs `SecureIdentityPropagationToAppsEnabled` and `com.cerebro.domino.apps.extendedIdentityPropagationToAppsEnabled`, both on by default on Cloud and 6.3. Once enabled on an App it cannot be disabled.\n2. **A framework that reads proxied HTTP headers**: Flask and Dash do by default; Shiny needs Shiny Server Pro. The per-request viewer token arrives in the `Authorization` header after the viewer consents.\n3. **Published and viewable**: an Extension inherits the App's access controls; users without view access see it listed and are prompted to request access.\n4. Domino's App guidelines: call Domino APIs from backend code only (never from frontend JavaScript), authenticate with the per-request bearer from `Authorization` (never an API key), keep the App stateless or protect cached data like its source, declare dependencies in the Compute Environment's Dockerfile.\n\n## Mount points and context\n\n| `uiMountPointTypeConfigs` key | Where | Query parameters passed to `\u002F` |\n|---|---|---|\n| `projectSidebar` | Project navigation sidebar | `projectId` |\n| `dataset` | Dataset details page | `datasetId` |\n| `datasetFileContext` | Three-dot menu of a file in a Dataset | `datasetId`, `datasetSnapshotId`, `filePath` |\n| `modelDetails` | Model details page | `modelId`, `modelVersionId` |\n| `adminPanel` | New page in the Admin panel | none |\n| `netAppVolume`, `netAppVolumeFileContext` | NetApp Volume pages (API only) | `netAppVolumeId`, `netAppVolumeSnapshotId`, `filePath` |\n\n`urlConfig.contextualQueryParams` accepts only the spec enum (the eight names above), and the App receives exactly what the config lists. The file parameter is `filePath`, not `datasetFilePath`. Read the parameters on the App's root route, validate the ones you need and return a clear 400 when they are missing, and call Domino with the forwarded `Authorization` header. A worked Flask example and the exact config shapes are in [API-EXTENSIONS.md](.\u002FAPI-EXTENSIONS.md).\n\n## Create an Extension (custom App)\n\n1. **Build and preview** the App in a workspace (App Preview), then **Publish App** as a SysAdmin or CloudAdmin with extended identity propagation on. Over the API: [domino-apps\u002FAPI-APPS.md](..\u002Fdomino-apps\u002FAPI-APPS.md).\n2. **Create the Extension** from the App's three-dot menu (**Create Extension**) or **Admin panel > Extensions > Create Extension**: pick the App version and add one or more mount points. Needs admin permissions (a 403 means they are missing; see API-EXTENSIONS.md). Over the API: `POST \u002Fapi\u002Fextensions\u002Fbeta\u002Fextensions` with `name`, `enabled`, `appId`, **`appVersionId`** (a version with extended identity propagation on) and `uiMountPointTypeConfigs`; all five are required, `description` is optional. Body and the other routes: [API-EXTENSIONS.md](.\u002FAPI-EXTENSIONS.md).\n3. **Manage** from Admin panel > Extensions: toggle enabled, **Manage Extension > Edit** to change mount points or the App version, **Delete** to soft-delete. Publishing a new App version does not move the Extension; edit it in the UI or `PATCH` `appVersionId` over the API.\n\n## Official Extensions (manifest-driven)\n\nDomino-built Extensions are installed, upgraded and uninstalled from **Admin panel > Extensions > Manage Domino-official Extensions**; the installer reads `extension_manifest.json` (`manifestSchemaVersion: 1`, sections `project`, `app`, `extension`) from a GitHub release and creates the Project, Compute Environment, App and Extension itself. Do not edit those managed entities by hand. Manifest fields, lifecycle rules and the install routes: [MANIFEST.md](.\u002FMANIFEST.md).\n\n## Auth and hosts in Extension backends\n\n| Call | Credential and base |\n|---|---|\n| Platform API as the **viewer** | Forward the request's `Authorization` header unchanged to `$DOMINO_API_HOST\u002Fapi\u002F...`; answer 401 when it is missing. Consent expires (8 hours by default, up to 30 days) |\n| Platform API as the **publisher** | `$DOMINO_API_PROXY\u002Fapi\u002F...` with no header, or a bearer from `$DOMINO_API_PROXY\u002Faccess-token` |\n| Governance `\u002Fapi\u002Fgovernance\u002Fv1\u002F*` | Base URL per the `domino-governance` skill; bearer PAT or service account, never an API key |\n| Model inference | The `url` from the endpoint record, not a hand-built host |\n| Automation outside any run | Public deployment URL plus PAT or service account token |\n\nUntil a viewer consents, Domino redirects every request, JSON included, to `\u002Fapp-consent`. The bearer is the viewer's own credential: take the viewer from its `preferred_username` claim, never `domino-username` (not sent here; clients can forge it); never log or store the token, never call without it (`$DOMINO_API_HOST` runs header-less calls as the publisher). No browser links from `DOMINO_API_HOST` or `DOMINO_USER_HOST`; put the public URL in a project environment variable. Slash, routes, scripts: [API-EXTENSIONS.md](.\u002FAPI-EXTENSIONS.md#identity-urls-and-scripts).\n\n## Reference files\n\n- [API-EXTENSIONS.md](.\u002FAPI-EXTENSIONS.md): `\u002Fapi\u002Fextensions\u002Fbeta` routes, create body, mount config shapes, Flask context example, patch and delete.\n- [MANIFEST.md](.\u002FMANIFEST.md): `extension_manifest.json` fields, official install lifecycle and routes.\n",{"name":5,"description":7,"compatibility":24},"Domino 6.3 and Domino Cloud. Requires DOMINO_API_HOST; in a run use DOMINO_API_PROXY, outside a run a Personal Access Token or service account token. Creating an Extension needs admin permissions; publishing its App with extended identity propagation needs a SysAdmin or CloudAdmin.","main","2c4dda96cbb98db0575b22d089730f3748afb604","skills\u002Fdomino-extensions",4,"https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin","https:\u002F\u002Fdocs.domino.ai","https:\u002F\u002Fgithub.com\u002Fdominodatalab","https:\u002F\u002Fdomino.ai\u002F","2026-11-14 02:00:14",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add dominodatalab\u002Fdomino-ai-plugin --skill domino-extensions",{"tool":40,"command":41},"bunx","bunx skills add dominodatalab\u002Fdomino-ai-plugin --skill domino-extensions",{"tool":43,"command":44},"pnpm","pnpm dlx skills add dominodatalab\u002Fdomino-ai-plugin --skill domino-extensions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-extensions\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"API-EXTENSIONS.md","REFERENCE","参考文档",11146,"https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-extensions\u002FAPI-EXTENSIONS.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"MANIFEST.md",3137,"https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-extensions\u002FMANIFEST.md",[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7DMZZDEZQWKSRCZ8RGXK1PD","tags-and-properties","Manage Domino tags and properties via the Tags (Taxonomy) API at \u002Fapi\u002Ftaxonomy\u002Fv1. Covers namespaces and tags (create, list, update, deprecate, delete; tag entities such as projects, models, datasets, apps, project templates, NetApp volumes, environments; query by tag; autocomplete; merge; CSV import\u002Fexport) and properties (typed metadata fields - text, number, date, boolean, url, user, organization, select, multi_select - with per-entity values, groups and versioned entities like model_version\u002Fapp_version). Use when organizing entities with tags, building hierarchical namespaces, defining typed metadata fields, setting property values, finding entities by tag, bulk-tagging during onboarding, or migrating a taxonomy across environments.","https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Ftags-and-properties\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7DMZR1BD7XYN9JR3T7R0TA6","netapp-volumes","Work with Domino Volumes for NetApp ONTAP (NetApp Volumes) - shared, multi-terabyte storage with near-instant snapshots. Covers creating volumes, attaching them to projects, mount paths (\u002Fmnt\u002Fnetapp-volumes\u002F or \u002Fdomino\u002Fnetapp-volumes\u002F), snapshots and tags, roles, deletion, mounting volumes in jobs, and the NetApp Volumes REST API (\u002Fremotefs\u002Fv1). Use when managing large-scale shared data, taking fast no-copy snapshots, or integrating NetApp ONTAP storage with Domino.","https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fnetapp-volumes\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7DMZHZJFG57N4532E6CY3KJ","domino-workspaces","Work with Domino Workspaces - interactive sessions running Jupyter, JupyterLab, VS Code or RStudio on a hardware tier with a compute environment. Covers launching and configuring a Workspace, what persists across stop and resume, file paths and syncing for DFS and Git-based Projects, package and home-directory persistence, SSH access from a local IDE, the Workspace API routes, and troubleshooting. Use when setting up or debugging an interactive development session in Domino.","https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-workspaces\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7DMZ5NJRQG6GGVKND5BY6DX","domino-ui-bootstrap","Bootstrap or retrofit a Vite + React 18 + TypeScript project so it uses the Domino design system (`@dominodatalab\u002Fextensions-tools`). Scoped to a **fully standalone SPA frontend for a Domino application or extension**, not snippets, library additions, or work inside an existing Domino monorepo package. Use whenever the user wants to create, scaffold, refactor, retrofit, or set up such an SPA (a React app, web app, frontend, UI, or extension) that should \"look like Domino\", use Domino components, follow the Domino design system, or integrate with the Domino platform, including when they mention DominoThemeProviderDecorator, extensions-tools, or base-components without saying \"Domino\". Also use to make an existing standalone React\u002FVite project \"Domino-styled\" or add Domino theming. Handles React 18 \u002F react-router 5 pinning, Storybook MCP registration, theme provider wiring, and build verification.","https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-ui-bootstrap\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":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7DMZ0V0K73HEE8EAWEZEG60","domino-trace-setup","Set up GenAI tracing for an LLM or agent application in Domino by checking the Domino SDK and MLflow requirements (the DSE needs nothing installed), then adding a tracing_setup.py helper, span evaluators, a config.yaml, and @add_tracing \u002F DominoAgentContext wiring. Use when the user asks to add tracing, observability, or evaluation to an agent or LLM app running on Domino.","https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-trace-setup\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":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7DMYNVZZSB16J9N4S57X11D","domino-rust-apps","Build a Rust web app (axum) in Domino and ship it as a Domino App that starts from a prebuilt binary. Covers installing a pinned Rust toolchain into a Compute Environment with rustup, Cargo project defaults (edition 2024, rust-toolchain.toml, Cargo.lock, Clippy pedantic, rustfmt, cargo-nextest, cargo-deny), rust-analyzer for the IDE and coding agents, check hooks, calling Domino as the viewer with extended identity propagation, dev and release build profiles, keeping target\u002F out of Git and Domino storage, and an app.sh that runs the binary in App Preview and deployments without compiling. Use when the user wants a Rust app, API, dashboard or Proa site on Domino, a performance-sensitive or correctness-critical App, or asks to set up Rust, cargo, Clippy, nextest or rust-analyzer in a Domino Workspace or environment.","https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-rust-apps\u002FSKILL.md",[],[]]