[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DMQ9DWYZ2WSFNV3WEFWHJN":3,"skill-same:01M7DMQ9DWYZ2WSFNV3WEFWHJN":62},{"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},"01M7DMQ9DWYZ2WSFNV3WEFWHJN","domino-airflow-kubeflow",null,"Run Domino Jobs from an external orchestrator. Covers Apache Airflow (a PythonOperator task on the Public Jobs API, or python-domino's DominoOperator and DominoSparkOperator), Kubeflow Pipelines (a KFP component that starts a Job over REST and polls it), installing python-domino on workers, credentials outside Domino (Personal Access Token or service-account token, never an API key), network reachability, mapping DAG tasks to Jobs, polling status, fetching logs and results. Use when the user mentions Airflow, a DAG, DominoOperator, Kubeflow, KFP, an external scheduler or orchestrator, or wants a pipeline that lives outside Domino to trigger and wait for Domino Jobs. For pipelines inside Domino use domino-flows; for a recurring single Job use a scheduled Job (domino-jobs).","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-airflow-kubeflow\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: domino-airflow-kubeflow\ndescription: Run Domino Jobs from an external orchestrator. Covers Apache Airflow (a PythonOperator task on the Public Jobs API, or python-domino's DominoOperator and DominoSparkOperator), Kubeflow Pipelines (a KFP component that starts a Job over REST and polls it), installing python-domino on workers, credentials outside Domino (Personal Access Token or service-account token, never an API key), network reachability, mapping DAG tasks to Jobs, polling status, fetching logs and results. Use when the user mentions Airflow, a DAG, DominoOperator, Kubeflow, KFP, an external scheduler or orchestrator, or wants a pipeline that lives outside Domino to trigger and wait for Domino Jobs. For pipelines inside Domino use domino-flows; for a recurring single Job use a scheduled Job (domino-jobs).\ncompatibility: Domino 6.3 and Domino Cloud. The orchestrator runs outside Domino, so it needs the deployment URL and a Personal Access Token or service-account token; DOMINO_API_PROXY and the localhost:8899 access-token endpoint exist only inside Domino runs. python-domino 2.x (the Airflow operators ship with it).\n---\n\n# Airflow and Kubeflow integration\n\nApplies to Domino 6.3 and Domino Cloud.\n\nProduct page: https:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Fplatform-capabilities\u002Ffeatures\u002Fintegrations (6.3:\nsame path under `\u002F6.3\u002F`). The orchestrator is its own service outside Domino; each pipeline step\nstarts a Domino **Job** through the Domino API and waits for it; the code that does the work\nlives in the Domino project. Domino keeps reproducibility, the orchestrator keeps the schedule.\n\n## Pick the right tool first\n\n| Situation | Use |\n|---|---|\n| Multi-step DAG that should run **inside** Domino with lineage and typed artifacts | [domino-flows](..\u002Fdomino-flows\u002FSKILL.md) |\n| One Job on a cron | a scheduled Job, [domino-jobs](..\u002Fdomino-jobs\u002FSKILL.md) |\n| An existing Airflow or Kubeflow deployment already orchestrates the data estate | this skill |\n\n## What the orchestrator needs\n\n1. **Network path** from its workers to the Domino deployment URL (the one users open in a\n   browser), exported as `DOMINO_API_HOST` on the worker. Nothing from inside a run\n   (`DOMINO_API_PROXY`, `localhost:8899`) exists on an Airflow worker or a KFP pod.\n2. **A token**: a Personal Access Token for a pipeline that acts as you, or a service-account\n   token for unattended automation, created in Domino and held in the orchestrator's own secret\n   mechanism (Domino variables are not readable there). Legacy user API keys are deprecated; do\n   not copy the `DOMINO_USER_API_KEY` the product page and python-domino's example still\n   show.\n   https:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Freference\u002Fapi\u002Fdomino-api-authentication\n3. **Project id and command** per step, plus optional environment id and hardware tier id.\n\n## Airflow: recommended pattern (Public Jobs API, `requests` only)\n\nWorks on Airflow 2 and 3, installs under Airflow's constraints, and fails the task on every\nnon-success outcome:\n\n```python\nfrom datetime import datetime\nfrom airflow import DAG\nfrom airflow.decorators import task\n\n@task\ndef run_domino_job(run_command: str) -> str:\n    import os, time, requests\n    base = os.environ[\"DOMINO_API_HOST\"].rstrip(\"\u002F\")          # deployment URL, set on the worker\n    headers = {\"Authorization\": \"Bearer \" + open(os.environ[\"DOMINO_TOKEN_FILE\"]).readline().strip()}\n    job = requests.post(f\"{base}\u002Fapi\u002Fjobs\u002Fv1\u002Fjobs\", headers=headers, timeout=60,\n                        json={\"projectId\": os.environ[\"DOMINO_PROJECT_ID\"], \"runCommand\": run_command}).json()[\"job\"]\n    while not job[\"status\"][\"isCompleted\"]:\n        time.sleep(30)\n        job = requests.get(f\"{base}\u002Fapi\u002Fjobs\u002Fbeta\u002Fjobs\u002F{job['id']}\", headers=headers, timeout=60).json()[\"job\"]\n    if job[\"status\"][\"executionStatus\"] != \"Succeeded\":         # Stopped, Failed or Error\n        raise RuntimeError(f\"Domino job {job['id']} ended {job['status']['executionStatus']}\")\n    return job[\"commitDetails\"][\"outputCommitId\"]\n\nwith DAG(\"domino_pipeline\", start_date=datetime(2026, 1, 1), schedule=\"@daily\", catchup=False):\n    run_domino_job(\"python prepare.py\") >> run_domino_job(\"python train.py 20\")\n```\n\nThe output commit id becomes the task's XCom value; a downstream task reads result files from\nit. Request fields, logs, result hand-off and failure handling: [JOBS-API-PATTERN.md](.\u002FJOBS-API-PATTERN.md).\n\n## Airflow: python-domino operators\n\n`pip install dominodatalab` ships `domino.airflow.DominoOperator` and `DominoSparkOperator`.\nRead these before choosing them; details and a DAG in [AIRFLOW.md](.\u002FAIRFLOW.md):\n\n- `DominoOperator` starts Jobs with python-domino's `runs_start_blocking` on the **legacy v1\n  Runs API** (`\u002Fv1\u002Fprojects\u002F{owner}\u002F{project}\u002Fruns`; not in the Public API, may change in a future Domino version). python-domino's README: use `job_start` for all new development.\n- `DominoSparkOperator` uses `job_start_blocking` on the v4 Jobs API (**non-public route; may change in a future Domino version**) and takes `environment_id`, `hardware_tier_name` and a Spark, Ray,\n  Dask or MPI `compute_cluster_properties`. It raises only when the Job ends `Failed`; a Job that\n  ends `Error` or `Stopped` returns normally and the task goes green. AIRFLOW.md has a subclass\n  that checks `executionStatus == \"Succeeded\"`. `DominoOperator` fails on any non-success.\n- `dominodatalab` 2.2.0 pins `packaging` and `python-dateutil` below Airflow's constraints, so\n  a constraints-based install fails to resolve and a plain install downgrades Airflow's\n  dependencies; give the worker a dedicated virtual environment or use the pattern above\n  ([AIRFLOW.md](.\u002FAIRFLOW.md#install)). The `[airflow]` extra pins `apache-airflow==2.2.4`; do\n  not use it on an existing Airflow.\n- Both operators import `airflow.utils.decorators.apply_defaults`, removed in Airflow 3.0.\n- Neither accepts `auth_token`: pass a token file as `domino_token_file` or set `DOMINO_TOKEN_FILE`.\n\n## Kubeflow in one screen\n\nNo Domino-specific KFP component exists: install a client and call the API. The same\n`requests` function as the Airflow task above, wrapped in\n`@dsl.component(base_image=\"python:3.12\", packages_to_install=[\"requests\"])`, with the token\nmounted from a Kubernetes Secret by `kfp.kubernetes.use_secret_as_env(task, secret_name=...,\nsecret_key_to_env={\"token\": \"DOMINO_TOKEN\"})` (`pip install kfp[kubernetes]`). The component\nreturns the output commit id so the next component can read a result file from it. Full\ncomponents, pipeline, secret creation and logs on failure: [KUBEFLOW.md](.\u002FKUBEFLOW.md).\n\n## Pitfalls\n\n- `DominoOperator.command` is a **list**; with `isDirect=True` pass the whole shell command as\n  its single element (`command=[\"python -V\"]`).\n- `tier` on `DominoOperator` is validated against hardware tier **names** visible to the project.\n- `Domino(...)` calls `\u002Fversion` on construction, so a worker with no network path to Domino\n  fails at client creation, not at Job start.\n- Default `max_poll_time` is 6000 s (100 min); longer Jobs need a larger value or the task fails\n  while the Job keeps running.\n- python-domino reads `DOMINO_API_HOST`, `DOMINO_TOKEN_FILE` and the deprecated\n  `DOMINO_USER_API_KEY` from the environment; pass `auth_token` instead of setting the key.\n- Each step is a separate Job with its own input commit; hand data between steps through\n  Datasets, Data Sources or the output commit, not the local filesystem.\n\n## Related skills\n\n- [domino-jobs](..\u002Fdomino-jobs\u002FSKILL.md): Job bodies, hardware tiers, logs, scheduled Jobs\n- [domino-flows](..\u002Fdomino-flows\u002FSKILL.md): orchestration inside Domino\n- [domino-python-sdk](..\u002Fdomino-python-sdk\u002FSKILL.md): python-domino client and auth order\n- [domino-api-intro](..\u002Fdomino-api-intro\u002FSKILL.md): hosts, pagination, errors\n","# Airflow and Kubeflow integration\n\nApplies to Domino 6.3 and Domino Cloud.\n\nProduct page: https:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Fplatform-capabilities\u002Ffeatures\u002Fintegrations (6.3:\nsame path under `\u002F6.3\u002F`). The orchestrator is its own service outside Domino; each pipeline step\nstarts a Domino **Job** through the Domino API and waits for it; the code that does the work\nlives in the Domino project. Domino keeps reproducibility, the orchestrator keeps the schedule.\n\n## Pick the right tool first\n\n| Situation | Use |\n|---|---|\n| Multi-step DAG that should run **inside** Domino with lineage and typed artifacts | [domino-flows](..\u002Fdomino-flows\u002FSKILL.md) |\n| One Job on a cron | a scheduled Job, [domino-jobs](..\u002Fdomino-jobs\u002FSKILL.md) |\n| An existing Airflow or Kubeflow deployment already orchestrates the data estate | this skill |\n\n## What the orchestrator needs\n\n1. **Network path** from its workers to the Domino deployment URL (the one users open in a\n   browser), exported as `DOMINO_API_HOST` on the worker. Nothing from inside a run\n   (`DOMINO_API_PROXY`, `localhost:8899`) exists on an Airflow worker or a KFP pod.\n2. **A token**: a Personal Access Token for a pipeline that acts as you, or a service-account\n   token for unattended automation, created in Domino and held in the orchestrator's own secret\n   mechanism (Domino variables are not readable there). Legacy user API keys are deprecated; do\n   not copy the `DOMINO_USER_API_KEY` the product page and python-domino's example still\n   show.\n   https:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Freference\u002Fapi\u002Fdomino-api-authentication\n3. **Project id and command** per step, plus optional environment id and hardware tier id.\n\n## Airflow: recommended pattern (Public Jobs API, `requests` only)\n\nWorks on Airflow 2 and 3, installs under Airflow's constraints, and fails the task on every\nnon-success outcome:\n\n```python\nfrom datetime import datetime\nfrom airflow import DAG\nfrom airflow.decorators import task\n\n@task\ndef run_domino_job(run_command: str) -> str:\n    import os, time, requests\n    base = os.environ[\"DOMINO_API_HOST\"].rstrip(\"\u002F\")          # deployment URL, set on the worker\n    headers = {\"Authorization\": \"Bearer \" + open(os.environ[\"DOMINO_TOKEN_FILE\"]).readline().strip()}\n    job = requests.post(f\"{base}\u002Fapi\u002Fjobs\u002Fv1\u002Fjobs\", headers=headers, timeout=60,\n                        json={\"projectId\": os.environ[\"DOMINO_PROJECT_ID\"], \"runCommand\": run_command}).json()[\"job\"]\n    while not job[\"status\"][\"isCompleted\"]:\n        time.sleep(30)\n        job = requests.get(f\"{base}\u002Fapi\u002Fjobs\u002Fbeta\u002Fjobs\u002F{job['id']}\", headers=headers, timeout=60).json()[\"job\"]\n    if job[\"status\"][\"executionStatus\"] != \"Succeeded\":         # Stopped, Failed or Error\n        raise RuntimeError(f\"Domino job {job['id']} ended {job['status']['executionStatus']}\")\n    return job[\"commitDetails\"][\"outputCommitId\"]\n\nwith DAG(\"domino_pipeline\", start_date=datetime(2026, 1, 1), schedule=\"@daily\", catchup=False):\n    run_domino_job(\"python prepare.py\") >> run_domino_job(\"python train.py 20\")\n```\n\nThe output commit id becomes the task's XCom value; a downstream task reads result files from\nit. Request fields, logs, result hand-off and failure handling: [JOBS-API-PATTERN.md](.\u002FJOBS-API-PATTERN.md).\n\n## Airflow: python-domino operators\n\n`pip install dominodatalab` ships `domino.airflow.DominoOperator` and `DominoSparkOperator`.\nRead these before choosing them; details and a DAG in [AIRFLOW.md](.\u002FAIRFLOW.md):\n\n- `DominoOperator` starts Jobs with python-domino's `runs_start_blocking` on the **legacy v1\n  Runs API** (`\u002Fv1\u002Fprojects\u002F{owner}\u002F{project}\u002Fruns`; not in the Public API, may change in a future Domino version). python-domino's README: use `job_start` for all new development.\n- `DominoSparkOperator` uses `job_start_blocking` on the v4 Jobs API (**non-public route; may change in a future Domino version**) and takes `environment_id`, `hardware_tier_name` and a Spark, Ray,\n  Dask or MPI `compute_cluster_properties`. It raises only when the Job ends `Failed`; a Job that\n  ends `Error` or `Stopped` returns normally and the task goes green. AIRFLOW.md has a subclass\n  that checks `executionStatus == \"Succeeded\"`. `DominoOperator` fails on any non-success.\n- `dominodatalab` 2.2.0 pins `packaging` and `python-dateutil` below Airflow's constraints, so\n  a constraints-based install fails to resolve and a plain install downgrades Airflow's\n  dependencies; give the worker a dedicated virtual environment or use the pattern above\n  ([AIRFLOW.md](.\u002FAIRFLOW.md#install)). The `[airflow]` extra pins `apache-airflow==2.2.4`; do\n  not use it on an existing Airflow.\n- Both operators import `airflow.utils.decorators.apply_defaults`, removed in Airflow 3.0.\n- Neither accepts `auth_token`: pass a token file as `domino_token_file` or set `DOMINO_TOKEN_FILE`.\n\n## Kubeflow in one screen\n\nNo Domino-specific KFP component exists: install a client and call the API. The same\n`requests` function as the Airflow task above, wrapped in\n`@dsl.component(base_image=\"python:3.12\", packages_to_install=[\"requests\"])`, with the token\nmounted from a Kubernetes Secret by `kfp.kubernetes.use_secret_as_env(task, secret_name=...,\nsecret_key_to_env={\"token\": \"DOMINO_TOKEN\"})` (`pip install kfp[kubernetes]`). The component\nreturns the output commit id so the next component can read a result file from it. Full\ncomponents, pipeline, secret creation and logs on failure: [KUBEFLOW.md](.\u002FKUBEFLOW.md).\n\n## Pitfalls\n\n- `DominoOperator.command` is a **list**; with `isDirect=True` pass the whole shell command as\n  its single element (`command=[\"python -V\"]`).\n- `tier` on `DominoOperator` is validated against hardware tier **names** visible to the project.\n- `Domino(...)` calls `\u002Fversion` on construction, so a worker with no network path to Domino\n  fails at client creation, not at Job start.\n- Default `max_poll_time` is 6000 s (100 min); longer Jobs need a larger value or the task fails\n  while the Job keeps running.\n- python-domino reads `DOMINO_API_HOST`, `DOMINO_TOKEN_FILE` and the deprecated\n  `DOMINO_USER_API_KEY` from the environment; pass `auth_token` instead of setting the key.\n- Each step is a separate Job with its own input commit; hand data between steps through\n  Datasets, Data Sources or the output commit, not the local filesystem.\n\n## Related skills\n\n- [domino-jobs](..\u002Fdomino-jobs\u002FSKILL.md): Job bodies, hardware tiers, logs, scheduled Jobs\n- [domino-flows](..\u002Fdomino-flows\u002FSKILL.md): orchestration inside Domino\n- [domino-python-sdk](..\u002Fdomino-python-sdk\u002FSKILL.md): python-domino client and auth order\n- [domino-api-intro](..\u002Fdomino-api-intro\u002FSKILL.md): hosts, pagination, errors\n",{"name":5,"description":7,"compatibility":24},"Domino 6.3 and Domino Cloud. The orchestrator runs outside Domino, so it needs the deployment URL and a Personal Access Token or service-account token; DOMINO_API_PROXY and the localhost:8899 access-token endpoint exist only inside Domino runs. python-domino 2.x (the Airflow operators ship with it).","main","2c4dda96cbb98db0575b22d089730f3748afb604","skills\u002Fdomino-airflow-kubeflow",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-airflow-kubeflow",{"tool":40,"command":41},"bunx","bunx skills add dominodatalab\u002Fdomino-ai-plugin --skill domino-airflow-kubeflow",{"tool":43,"command":44},"pnpm","pnpm dlx skills add dominodatalab\u002Fdomino-ai-plugin --skill domino-airflow-kubeflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-airflow-kubeflow\u002FSKILL.md",true,[48,54,58],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"AIRFLOW.md","REFERENCE","参考文档",11931,"https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-airflow-kubeflow\u002FAIRFLOW.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"JOBS-API-PATTERN.md",5054,"https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-airflow-kubeflow\u002FJOBS-API-PATTERN.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"KUBEFLOW.md",6444,"https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-airflow-kubeflow\u002FKUBEFLOW.md",[63,70,77,84,91,98],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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",[],[]]