[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DMXP2927VC3V8GMGG14JWK":3,"skill-same:01M7DMXP2927VC3V8GMGG14JWK":54},{"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},"01M7DMXP2927VC3V8GMGG14JWK","domino-model-serving",null,"Automate Domino endpoints (Model APIs) and registered models over REST. Covers the \u002Fapi\u002FmodelServing\u002Fv1 lifecycle (create an endpoint from a file or a registered model, add versions, poll deployment status, list, update replicas or hardware tier, archive, build and instance logs), registered models v1 vs v2 routes, MLflow tracking vs the registry API, management URL vs prediction URL, and sync Basic vs async Bearer prediction auth. Use when scripting deployments from CI, a Job or a notebook, registering a model version by API, or debugging stop, archive and delete behaviour. For UI publishing, the predict function, scaling and health settings use domino-model-endpoints; for drift and quality monitoring use domino-model-monitoring; for exporting a model out of Domino (image to your registry, NVIDIA Fleet Command, Snowflake UDF, SageMaker) or batch scoring Jobs use domino-model-delivery.","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-model-serving\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: domino-model-serving\ndescription: Automate Domino endpoints (Model APIs) and registered models over REST. Covers the \u002Fapi\u002FmodelServing\u002Fv1 lifecycle (create an endpoint from a file or a registered model, add versions, poll deployment status, list, update replicas or hardware tier, archive, build and instance logs), registered models v1 vs v2 routes, MLflow tracking vs the registry API, management URL vs prediction URL, and sync Basic vs async Bearer prediction auth. Use when scripting deployments from CI, a Job or a notebook, registering a model version by API, or debugging stop, archive and delete behaviour. For UI publishing, the predict function, scaling and health settings use domino-model-endpoints; for drift and quality monitoring use domino-model-monitoring; for exporting a model out of Domino (image to your registry, NVIDIA Fleet Command, Snowflake UDF, SageMaker) or batch scoring Jobs use domino-model-delivery.\ncompatibility: Domino 6.3 and Domino Cloud. Requires DOMINO_API_HOST; in a run use DOMINO_API_PROXY or the localhost:8899 access-token endpoint, outside a run a Personal Access Token or service-account token. The modelServing beta visibility and collaborator routes exist only on Domino Cloud.\n---\n\n# Domino model serving (REST)\n\nApplies to Domino 6.3 and Domino Cloud.\n\nProgrammatic lifecycle for Domino endpoints (**Model APIs** in the API) and registered models. UI publishing, the prediction function, scaling and endpoint health are in `domino-model-endpoints`. Worked requests for every step: [LIFECYCLE.md](.\u002FLIFECYCLE.md); route catalog: [API-MODEL-SERVING.md](..\u002Fdomino-python-sdk\u002FAPI-MODEL-SERVING.md).\n\n## Authentication and base URL\n\n[domino-api-intro](..\u002Fdomino-api-intro\u002FSKILL.md#authentication). Legacy API keys are deprecated; do not use them.\n\nConnectivity check: `GET \u002Fapi\u002FmodelServing\u002Fv1\u002FmodelApis?limit=1` returns 200.\n\n## Three surfaces (do not mix them)\n\n| Surface | Base path | Purpose |\n|---------|-----------|---------|\n| Model Serving | `\u002Fapi\u002FmodelServing\u002Fv1\u002FmodelApis` | Endpoints: create, versions, list, update, archive, logs |\n| Registered models | `\u002Fapi\u002Fregisteredmodels\u002Fv2` (list, register); `\u002Fapi\u002Fregisteredmodels\u002Fv1\u002F{modelName}` (get, patch, versions) | Registry records; `modelName` is the name, not an id |\n| MLflow tracking | `MLFLOW_TRACKING_URI` in a run; `\u002Fapi\u002F2.0\u002Fmlflow\u002F...` on the deployment URL with a bearer token | Experiments, runs, artifacts, the MLflow registry client |\n\nMLflow logging or registration deploys nothing; deployment is a Model Serving call.\n\n## Management URL vs prediction URL\n\nManagement calls go to the base above under `\u002Fapi\u002F...`. Predictions go to the deployment URL: `\u002Fmodels\u002F{modelApiId}\u002Flatest\u002Fmodel` (sync, Basic auth) or `\u002Fapi\u002FmodelApis\u002Fasync\u002Fv1\u002F{modelApiId}` (async, Bearer). The `ModelApi` object has no `url` field; build the prediction URL from its `id` and the deployment URL shown on the endpoint's Overview tab.\n\n## Lifecycle\n\n1. Train and, optionally, register (`POST \u002Fapi\u002Fregisteredmodels\u002Fv2`, or the MLflow client).\n2. `POST \u002Fapi\u002FmodelServing\u002Fv1\u002FmodelApis` with `name`, `description`, `environmentId`, `isAsync`, `strictNodeAntiAffinity`, `environmentVariables`, `version{projectId, source, logHttpRequestResponse, monitoringEnabled}`; `source.type` is `File` (`file`, `function`) or `Registry` (`registeredModelName`, `registeredModelVersion`). Optional `hardwareTierId`, `replicas`.\n3. Poll the version: `GET ...\u002FmodelApis\u002F{modelApiId}\u002Fversions\u002F{modelApiVersionId}` until `deployment.status` is `Running` and `isPending` is false (absent `deployment` means pending), then confirm `activeVersion.id` on the Model API. `Running` is not health: fetch `...\u002FinstanceLogs?maxResults=3000` (no `tail`), keep `model-` container lines, expect `WSGI app 0 (mountpoint='') ready` (`no app loaded. GAME OVER` is a crash loop), then one test prediction. Sync or commit before step 2 and pin `version.commitId`; the head lags uploads by seconds.\n4. New code: `POST ...\u002FmodelApis\u002F{modelApiId}\u002Fversions` (same `version` fields plus `shouldDeploy: true`). Poll that version, not the Model API; the old one stays active until the new one runs.\n5. Change replicas, hardware tier, name or environment: `PUT ...\u002FmodelApis\u002F{modelApiId}` (`name`, `description`, `replicas`, `environmentId` required; send current values back, including `resourceQuotaId`). Scale changes need a restart: UI, or internal `stopModelDeployment` then `startModelDeployment` (LIFECYCLE.md).\n6. Retire: stop the running version first (UI **Versions** > **Actions**, or `POST \u002Fv4\u002Fmodels\u002F{modelApiId}\u002F{versionId}\u002FstopModelDeployment` with `{}`; non-public route; may change in a future Domino version), then `DELETE ...\u002FmodelApis\u002F{modelApiId}`: 500 while a version runs; after success `GET` is 404 and the endpoint leaves all lists.\n7. Verify each mutation with a `GET`; 2xx means accepted, not applied.\n\nLogs: `GET ...\u002Fversions\u002F{modelApiVersionId}\u002FbuildLogs`, `exportLogs`, `instanceLogs`.\n\n`\u002Fapi\u002FmodelServing\u002Fv1\u002FmodelDeployments` (with `start`, `stop`, `credentials`, `logs`, `versions`) is a separate entity: a registered model deployed onto an admin-defined external deployment target, SageMaker only. It is not a Model API; see [domino-model-delivery](..\u002Fdomino-model-delivery\u002FEXPORT-TARGETS.md#amazon-sagemaker).\n\n## Registered models\n\n- List: `GET \u002Fapi\u002Fregisteredmodels\u002Fv2?projectId=&searchPattern=&maxResults=` (token-paginated with `pageToken`). Register: `POST \u002Fapi\u002Fregisteredmodels\u002Fv2` (`modelName`, `modelSource{sourceType, mlflowSource|huggingFaceSource}`, `create`). `POST \u002Fapi\u002Fregisteredmodels\u002Fv1\u002F{modelName}\u002Fversions` is deprecated.\n- Get and patch: `GET|PATCH \u002Fapi\u002Fregisteredmodels\u002Fv1\u002F{modelName}` (`PATCH` takes `description` and `discoverable`; `GET` returns neither `discoverable` nor aliases); versions at `\u002Fapi\u002Fregisteredmodels\u002Fv1\u002F{modelName}\u002Fversions\u002F{version}`; endpoints serving a version at `...\u002Fversions\u002F{version}\u002Fmodelapis`.\n- Aliases and tags are MLflow features: the MLflow client on `MLFLOW_TRACKING_URI`, or `\u002Fapi\u002F2.0\u002Fmlflow\u002Fregistered-models\u002F...` on the deployment URL; see `domino-experiment-tracking`.\n\n## Prediction auth\n\nRestricted **sync** endpoints require HTTP Basic with the endpoint access token as username and password. **Async** endpoints require `Authorization: Bearer \u003Ctoken>`. Unrestricted endpoints need neither. Tokens: the user's, or create one (`domino-model-endpoints` DEPLOY-ENDPOINT.md); never print it. Source: https:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Fplatform-capabilities\u002Ffeatures\u002Fmodel-deployment\u002Fdomino-endpoint-authorization.\n\n## Which path applies\n\n```bash\ncurl -s \"$DOMINO_API_HOST\u002Fversion\"   # \"version\": \"6.3.x\" self-managed; \"6.4.x\" or later on Domino Cloud\n```\n\nDomino Cloud adds `\u002Fapi\u002FmodelServing\u002Fbeta\u002FmodelApis\u002F{modelApiId}\u002Fvisibility` (`Public`, `Discoverable`, `Private`), `...\u002Faccess` and `...\u002Fcollaborators` (roles `Owner`, `Editor`, `Operator`, `Viewer`); not on 6.3, where you set them in the UI (**Settings** > **Access and Sharing**).\n\n## Related\n\n- [LIFECYCLE.md](.\u002FLIFECYCLE.md): request and response examples for each step\n- [API-MODEL-SERVING.md](..\u002Fdomino-python-sdk\u002FAPI-MODEL-SERVING.md), [API-MODELS.md](..\u002Fdomino-python-sdk\u002FAPI-MODELS.md)\n- [domino-model-endpoints](..\u002Fdomino-model-endpoints\u002FSKILL.md): UI, predict code, scaling, health, logs\n- [domino-model-delivery](..\u002Fdomino-model-delivery\u002FSKILL.md): model export, SageMaker, batch scoring\n- Route discovery: [API-SPECS.md](..\u002Fdomino-api-intro\u002FAPI-SPECS.md)\n- Model registry: https:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Fplatform-capabilities\u002Ffeatures\u002Fmodels\u002Fregister-and-govern\u002Fmodel-registry\n","# Domino model serving (REST)\n\nApplies to Domino 6.3 and Domino Cloud.\n\nProgrammatic lifecycle for Domino endpoints (**Model APIs** in the API) and registered models. UI publishing, the prediction function, scaling and endpoint health are in `domino-model-endpoints`. Worked requests for every step: [LIFECYCLE.md](.\u002FLIFECYCLE.md); route catalog: [API-MODEL-SERVING.md](..\u002Fdomino-python-sdk\u002FAPI-MODEL-SERVING.md).\n\n## Authentication and base URL\n\n[domino-api-intro](..\u002Fdomino-api-intro\u002FSKILL.md#authentication). Legacy API keys are deprecated; do not use them.\n\nConnectivity check: `GET \u002Fapi\u002FmodelServing\u002Fv1\u002FmodelApis?limit=1` returns 200.\n\n## Three surfaces (do not mix them)\n\n| Surface | Base path | Purpose |\n|---------|-----------|---------|\n| Model Serving | `\u002Fapi\u002FmodelServing\u002Fv1\u002FmodelApis` | Endpoints: create, versions, list, update, archive, logs |\n| Registered models | `\u002Fapi\u002Fregisteredmodels\u002Fv2` (list, register); `\u002Fapi\u002Fregisteredmodels\u002Fv1\u002F{modelName}` (get, patch, versions) | Registry records; `modelName` is the name, not an id |\n| MLflow tracking | `MLFLOW_TRACKING_URI` in a run; `\u002Fapi\u002F2.0\u002Fmlflow\u002F...` on the deployment URL with a bearer token | Experiments, runs, artifacts, the MLflow registry client |\n\nMLflow logging or registration deploys nothing; deployment is a Model Serving call.\n\n## Management URL vs prediction URL\n\nManagement calls go to the base above under `\u002Fapi\u002F...`. Predictions go to the deployment URL: `\u002Fmodels\u002F{modelApiId}\u002Flatest\u002Fmodel` (sync, Basic auth) or `\u002Fapi\u002FmodelApis\u002Fasync\u002Fv1\u002F{modelApiId}` (async, Bearer). The `ModelApi` object has no `url` field; build the prediction URL from its `id` and the deployment URL shown on the endpoint's Overview tab.\n\n## Lifecycle\n\n1. Train and, optionally, register (`POST \u002Fapi\u002Fregisteredmodels\u002Fv2`, or the MLflow client).\n2. `POST \u002Fapi\u002FmodelServing\u002Fv1\u002FmodelApis` with `name`, `description`, `environmentId`, `isAsync`, `strictNodeAntiAffinity`, `environmentVariables`, `version{projectId, source, logHttpRequestResponse, monitoringEnabled}`; `source.type` is `File` (`file`, `function`) or `Registry` (`registeredModelName`, `registeredModelVersion`). Optional `hardwareTierId`, `replicas`.\n3. Poll the version: `GET ...\u002FmodelApis\u002F{modelApiId}\u002Fversions\u002F{modelApiVersionId}` until `deployment.status` is `Running` and `isPending` is false (absent `deployment` means pending), then confirm `activeVersion.id` on the Model API. `Running` is not health: fetch `...\u002FinstanceLogs?maxResults=3000` (no `tail`), keep `model-` container lines, expect `WSGI app 0 (mountpoint='') ready` (`no app loaded. GAME OVER` is a crash loop), then one test prediction. Sync or commit before step 2 and pin `version.commitId`; the head lags uploads by seconds.\n4. New code: `POST ...\u002FmodelApis\u002F{modelApiId}\u002Fversions` (same `version` fields plus `shouldDeploy: true`). Poll that version, not the Model API; the old one stays active until the new one runs.\n5. Change replicas, hardware tier, name or environment: `PUT ...\u002FmodelApis\u002F{modelApiId}` (`name`, `description`, `replicas`, `environmentId` required; send current values back, including `resourceQuotaId`). Scale changes need a restart: UI, or internal `stopModelDeployment` then `startModelDeployment` (LIFECYCLE.md).\n6. Retire: stop the running version first (UI **Versions** > **Actions**, or `POST \u002Fv4\u002Fmodels\u002F{modelApiId}\u002F{versionId}\u002FstopModelDeployment` with `{}`; non-public route; may change in a future Domino version), then `DELETE ...\u002FmodelApis\u002F{modelApiId}`: 500 while a version runs; after success `GET` is 404 and the endpoint leaves all lists.\n7. Verify each mutation with a `GET`; 2xx means accepted, not applied.\n\nLogs: `GET ...\u002Fversions\u002F{modelApiVersionId}\u002FbuildLogs`, `exportLogs`, `instanceLogs`.\n\n`\u002Fapi\u002FmodelServing\u002Fv1\u002FmodelDeployments` (with `start`, `stop`, `credentials`, `logs`, `versions`) is a separate entity: a registered model deployed onto an admin-defined external deployment target, SageMaker only. It is not a Model API; see [domino-model-delivery](..\u002Fdomino-model-delivery\u002FEXPORT-TARGETS.md#amazon-sagemaker).\n\n## Registered models\n\n- List: `GET \u002Fapi\u002Fregisteredmodels\u002Fv2?projectId=&searchPattern=&maxResults=` (token-paginated with `pageToken`). Register: `POST \u002Fapi\u002Fregisteredmodels\u002Fv2` (`modelName`, `modelSource{sourceType, mlflowSource|huggingFaceSource}`, `create`). `POST \u002Fapi\u002Fregisteredmodels\u002Fv1\u002F{modelName}\u002Fversions` is deprecated.\n- Get and patch: `GET|PATCH \u002Fapi\u002Fregisteredmodels\u002Fv1\u002F{modelName}` (`PATCH` takes `description` and `discoverable`; `GET` returns neither `discoverable` nor aliases); versions at `\u002Fapi\u002Fregisteredmodels\u002Fv1\u002F{modelName}\u002Fversions\u002F{version}`; endpoints serving a version at `...\u002Fversions\u002F{version}\u002Fmodelapis`.\n- Aliases and tags are MLflow features: the MLflow client on `MLFLOW_TRACKING_URI`, or `\u002Fapi\u002F2.0\u002Fmlflow\u002Fregistered-models\u002F...` on the deployment URL; see `domino-experiment-tracking`.\n\n## Prediction auth\n\nRestricted **sync** endpoints require HTTP Basic with the endpoint access token as username and password. **Async** endpoints require `Authorization: Bearer \u003Ctoken>`. Unrestricted endpoints need neither. Tokens: the user's, or create one (`domino-model-endpoints` DEPLOY-ENDPOINT.md); never print it. Source: https:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Fplatform-capabilities\u002Ffeatures\u002Fmodel-deployment\u002Fdomino-endpoint-authorization.\n\n## Which path applies\n\n```bash\ncurl -s \"$DOMINO_API_HOST\u002Fversion\"   # \"version\": \"6.3.x\" self-managed; \"6.4.x\" or later on Domino Cloud\n```\n\nDomino Cloud adds `\u002Fapi\u002FmodelServing\u002Fbeta\u002FmodelApis\u002F{modelApiId}\u002Fvisibility` (`Public`, `Discoverable`, `Private`), `...\u002Faccess` and `...\u002Fcollaborators` (roles `Owner`, `Editor`, `Operator`, `Viewer`); not on 6.3, where you set them in the UI (**Settings** > **Access and Sharing**).\n\n## Related\n\n- [LIFECYCLE.md](.\u002FLIFECYCLE.md): request and response examples for each step\n- [API-MODEL-SERVING.md](..\u002Fdomino-python-sdk\u002FAPI-MODEL-SERVING.md), [API-MODELS.md](..\u002Fdomino-python-sdk\u002FAPI-MODELS.md)\n- [domino-model-endpoints](..\u002Fdomino-model-endpoints\u002FSKILL.md): UI, predict code, scaling, health, logs\n- [domino-model-delivery](..\u002Fdomino-model-delivery\u002FSKILL.md): model export, SageMaker, batch scoring\n- Route discovery: [API-SPECS.md](..\u002Fdomino-api-intro\u002FAPI-SPECS.md)\n- Model registry: https:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Fplatform-capabilities\u002Ffeatures\u002Fmodels\u002Fregister-and-govern\u002Fmodel-registry\n",{"name":5,"description":7,"compatibility":24},"Domino 6.3 and Domino Cloud. Requires DOMINO_API_HOST; in a run use DOMINO_API_PROXY or the localhost:8899 access-token endpoint, outside a run a Personal Access Token or service-account token. The modelServing beta visibility and collaborator routes exist only on Domino Cloud.","main","2c4dda96cbb98db0575b22d089730f3748afb604","skills\u002Fdomino-model-serving",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-model-serving",{"tool":40,"command":41},"bunx","bunx skills add dominodatalab\u002Fdomino-ai-plugin --skill domino-model-serving",{"tool":43,"command":44},"pnpm","pnpm dlx skills add dominodatalab\u002Fdomino-ai-plugin --skill domino-model-serving","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-model-serving\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"LIFECYCLE.md","REFERENCE","参考文档",17511,"https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-model-serving\u002FLIFECYCLE.md",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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",[],[]]