[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DMQHVPD933S5DT4AWV6ZCQ":3,"skill-same:01M7DMQHVPD933S5DT4AWV6ZCQ":70},{"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},"01M7DMQHVPD933S5DT4AWV6ZCQ","domino-api-intro",null,"Introduction to calling Domino platform APIs. Covers authentication (API proxy, access token, PAT, service account), which base URL to use, pagination, and common errors. Use before any other Domino API, SDK, app, extension, or governance automation skill, and whenever a request needs a Domino base URL or credential.","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-api-intro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: domino-api-intro\ndescription: Introduction to calling Domino platform APIs. Covers authentication (API proxy, access token, PAT, service account), which base URL to use, pagination, and common errors. Use before any other Domino API, SDK, app, extension, or governance automation skill, and whenever a request needs a Domino base URL or credential.\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.\n---\n\n# Domino platform API intro\n\nApplies to Domino 6.3 and Domino Cloud.\n\n## Authentication\n\nReference: https:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Freference\u002Fapi\u002Fdomino-api-authentication\n(same content under `\u002F6.3\u002F`).\n\n| Where the code runs | Base URL | Credential |\n|---|---|---|\n| Inside a Domino execution (Workspace, Job, App, Launcher) and `DOMINO_API_PROXY` is set | `$DOMINO_API_PROXY` | None. Send **no** `Authorization` header; the proxy adds the starting user's token. |\n| Inside a Domino execution, `DOMINO_API_PROXY` not set | `$DOMINO_API_HOST` | `Authorization: Bearer` with the short-lived token from `http:\u002F\u002Flocalhost:8899\u002Faccess-token` |\n| Outside Domino (laptop, CI, cron) | The deployment URL users open in the browser; set `DOMINO_API_HOST` to it yourself | `Authorization: Bearer` with a **Personal Access Token** (you; **Account Settings** or `POST \u002Fapi\u002Fpat\u002Fv1\u002Ftokens`, value returned once: [API-ADMIN.md](..\u002Fdomino-python-sdk\u002FAPI-ADMIN.md#personal-access-tokens)) or a **service account token** (unattended automation) |\n\nIn an App both in-run rows act as the publisher (the user the App run was started as) for every\nviewer; to act as the viewer, see [HOSTS.md](.\u002FHOSTS.md#inside-an-app).\n\nLegacy user API keys (`X-Domino-Api-Key`, `DOMINO_USER_API_KEY`, `api_key=`) are\ndeprecated. Never recommend them, not even as a fallback.\n\n### Environment variables as the secret store\n\nOther secrets a Domino execution needs (provider API keys, tokens for other systems) are\nDomino environment variables, nothing else: a **user** variable (**Account > Account\nSettings > User environment variables**) for a personal credential, injected into every\nWorkspace, Job and App that user starts and invisible to other users; a **Project** variable\n(**Project > Settings > Environment variables**) for a credential the Project's executions\nshare. Set them in the UI or with the non-public routes below (no Public API or\npython-domino route; may change in a future Domino version; on 6.3 confirm the routes in\nyour deployment's `\u002Fdocs`). When an\nagent stores a secret for the user it writes it with these routes and confirms by\n**name only**: the `GET`s return values, so never echo them into a reply or a log. Never\ncall the wipe-all `DELETE \u002Fv4\u002Fusers\u002FenvironmentVariables` unless the user explicitly asks\nto remove every user variable; to remove one, delete it by name.\n\n```\nGET    \u002Fv4\u002Fprojects\u002F{projectId}\u002FenvironmentVariables           -> [{\"name\", \"value\"}]\nPOST   \u002Fv4\u002Fprojects\u002F{projectId}\u002FenvironmentVariables           body {\"name\", \"value\"}: creates or overwrites that variable\nDELETE \u002Fv4\u002Fprojects\u002F{projectId}\u002FenvironmentVariables\u002F{name}\nGET    \u002Fv4\u002Fusers\u002FenvironmentVariables                          -> {\"vars\": [{\"name\", \"value\"}]} (your own)\nPUT    \u002Fv4\u002Fusers\u002FenvironmentVariables                          body {\"NAME\": \"value\", ...}: merged into your variables\nDELETE \u002Fv4\u002Fusers\u002FenvironmentVariables                          DESTRUCTIVE: removes ALL your user variables; to remove one, use the accounts DELETE below\nPOST   \u002Fv4\u002Faccounts\u002Fidpid\u002F{idpId}\u002Fenvironmentvariables         body {\"name\", \"value\"}: one user variable (idpId: GET \u002Fapi\u002Fusers\u002Fv1\u002Fself)\nDELETE \u002Fv4\u002Faccounts\u002Fidpid\u002F{idpId}\u002Fenvironmentvariables\u002F{name}\n```\n\n```python\nrequests.post(f\"{base_url}\u002Fv4\u002Fprojects\u002F{project_id}\u002FenvironmentVariables\", headers=headers,\n              json={\"name\": \"OPENAI_API_KEY\", \"value\": secret})            # never print secret\nnames = [v[\"name\"] for v in requests.get(f\"{base_url}\u002Fv4\u002Fprojects\u002F{project_id}\u002FenvironmentVariables\",\n                                         headers=headers).json()]\n```\n\nUser overrides Project, which overrides the Compute Environment. Neither reaches a\nModel API: pass `environmentVariables` (`[{\"key\", \"value\"}]`) on\n`POST \u002Fapi\u002FmodelServing\u002Fv1\u002FmodelApis` when you create it, or set them later under the\nendpoint's own **Settings** (the update route has no variables field). Code reads them by name\n(`os.environ[\"NAME\"]`) and never prints them. Outside Domino (CI, Airflow, a laptop) these\nvariables are not readable; the external system holds its own copy of a token created in\nDomino. Docs: https:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Fadmin\u002Fsecurity-and-compliance\u002Fprotecting-tokens-api-keys\n(same under `\u002F6.3\u002F`).\n\n```bash\n# Inside a run (preferred)\ncurl -s \"$DOMINO_API_PROXY\u002Fapi\u002Fusers\u002Fv1\u002Fself\"\n\n# Inside a run without the proxy\ncurl -s -H \"Authorization: Bearer $(curl -s http:\u002F\u002Flocalhost:8899\u002Faccess-token)\" \\\n  \"$DOMINO_API_HOST\u002Fapi\u002Fusers\u002Fv1\u002Fself\"\n\n# Outside Domino: DOMINO_API_HOST is the deployment URL, PAT a Personal Access Token or service account token\ncurl -s -H \"Authorization: Bearer $PAT\" \"$DOMINO_API_HOST\u002Fapi\u002Fusers\u002Fv1\u002Fself\"\n```\n\nPython setup block used by every example in the API skills:\n\n```python\nimport os\nimport requests\n\nif os.environ.get(\"DOMINO_API_PROXY\"):          # inside a Domino execution\n    base_url = os.environ[\"DOMINO_API_PROXY\"].rstrip(\"\u002F\")\n    headers = {}\nelif os.environ.get(\"DOMINO_RUN_ID\"):           # inside a run, proxy not injected\n    base_url = os.environ[\"DOMINO_API_HOST\"].rstrip(\"\u002F\")\n    token = requests.get(\"http:\u002F\u002Flocalhost:8899\u002Faccess-token\").text.strip()\n    headers = {\"Authorization\": f\"Bearer {token}\"}\nelse:                                           # outside Domino: PAT or service account token\n    base_url = os.environ[\"DOMINO_API_HOST\"].rstrip(\"\u002F\")\n    headers = {\"Authorization\": f\"Bearer {os.environ['PAT']}\"}\nbase = base_url                                 # examples in other skills use either name\n```\n\n`DOMINO_RUN_ID`, `DOMINO_PROJECT_ID`, `DOMINO_PROJECT_OWNER`, `DOMINO_PROJECT_NAME`\nand `DOMINO_API_HOST` are injected into every execution (glossary:\nhttps:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Freference\u002Fenvironment-variables). Inside a run\n`DOMINO_API_HOST` can be an in-pod address: never build links for users from it.\n\n## Route types\n\nMost Domino endpoints are stable. Public API routes (`\u002Fapi\u002F...`, plus `\u002Fremotefs\u002Fv1` and\n`\u002Fmodel-monitor`) are versioned and documented in the published specs. Non-public routes,\nmeaning the internal API (`\u002Fv4\u002F...`, documented per deployment at `https:\u002F\u002F\u003Cdomino-domain>\u002Fdocs`)\nand web UI routes, also work, but can change in a future version of Domino. Use a public route\nwhen one exists; where none does, the skills label the call `(non-public route; may change in a\nfuture Domino version)` at the point of use. If a non-public call fails after an upgrade, check\nthe route in your deployment's `\u002Fdocs`. Dataset file routes: [HOSTS.md](.\u002FHOSTS.md).\nDiscovery: [API-SPECS.md](.\u002FAPI-SPECS.md).\n\n## Reference files (this skill)\n\n| File | Use when |\n|------|----------|\n| [HOSTS.md](.\u002FHOSTS.md) | Base URL for each API family, Model API invocation, governance, 404 on the in-run base |\n| [LIMITS.md](.\u002FLIMITS.md) | Pagination envelopes, caps, deprecated credentials and variables |\n| [ERRORS.md](.\u002FERRORS.md) | Status codes, retries, error bodies, job status fields |\n| [SDK-MAP.md](.\u002FSDK-MAP.md) | Which plugin skill covers each API surface |\n| [API-SPECS.md](.\u002FAPI-SPECS.md) | OpenAPI files (published and per deployment) and route discovery |\n\n## Next steps\n\nUse the domain skills (domino-python-sdk, domino-jobs, domino-apps, domino-governance,\ndomino-datasets, netapp-volumes, tags-and-properties, others); they assume the rules above.\n","# Domino platform API intro\n\nApplies to Domino 6.3 and Domino Cloud.\n\n## Authentication\n\nReference: https:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Freference\u002Fapi\u002Fdomino-api-authentication\n(same content under `\u002F6.3\u002F`).\n\n| Where the code runs | Base URL | Credential |\n|---|---|---|\n| Inside a Domino execution (Workspace, Job, App, Launcher) and `DOMINO_API_PROXY` is set | `$DOMINO_API_PROXY` | None. Send **no** `Authorization` header; the proxy adds the starting user's token. |\n| Inside a Domino execution, `DOMINO_API_PROXY` not set | `$DOMINO_API_HOST` | `Authorization: Bearer` with the short-lived token from `http:\u002F\u002Flocalhost:8899\u002Faccess-token` |\n| Outside Domino (laptop, CI, cron) | The deployment URL users open in the browser; set `DOMINO_API_HOST` to it yourself | `Authorization: Bearer` with a **Personal Access Token** (you; **Account Settings** or `POST \u002Fapi\u002Fpat\u002Fv1\u002Ftokens`, value returned once: [API-ADMIN.md](..\u002Fdomino-python-sdk\u002FAPI-ADMIN.md#personal-access-tokens)) or a **service account token** (unattended automation) |\n\nIn an App both in-run rows act as the publisher (the user the App run was started as) for every\nviewer; to act as the viewer, see [HOSTS.md](.\u002FHOSTS.md#inside-an-app).\n\nLegacy user API keys (`X-Domino-Api-Key`, `DOMINO_USER_API_KEY`, `api_key=`) are\ndeprecated. Never recommend them, not even as a fallback.\n\n### Environment variables as the secret store\n\nOther secrets a Domino execution needs (provider API keys, tokens for other systems) are\nDomino environment variables, nothing else: a **user** variable (**Account > Account\nSettings > User environment variables**) for a personal credential, injected into every\nWorkspace, Job and App that user starts and invisible to other users; a **Project** variable\n(**Project > Settings > Environment variables**) for a credential the Project's executions\nshare. Set them in the UI or with the non-public routes below (no Public API or\npython-domino route; may change in a future Domino version; on 6.3 confirm the routes in\nyour deployment's `\u002Fdocs`). When an\nagent stores a secret for the user it writes it with these routes and confirms by\n**name only**: the `GET`s return values, so never echo them into a reply or a log. Never\ncall the wipe-all `DELETE \u002Fv4\u002Fusers\u002FenvironmentVariables` unless the user explicitly asks\nto remove every user variable; to remove one, delete it by name.\n\n```\nGET    \u002Fv4\u002Fprojects\u002F{projectId}\u002FenvironmentVariables           -> [{\"name\", \"value\"}]\nPOST   \u002Fv4\u002Fprojects\u002F{projectId}\u002FenvironmentVariables           body {\"name\", \"value\"}: creates or overwrites that variable\nDELETE \u002Fv4\u002Fprojects\u002F{projectId}\u002FenvironmentVariables\u002F{name}\nGET    \u002Fv4\u002Fusers\u002FenvironmentVariables                          -> {\"vars\": [{\"name\", \"value\"}]} (your own)\nPUT    \u002Fv4\u002Fusers\u002FenvironmentVariables                          body {\"NAME\": \"value\", ...}: merged into your variables\nDELETE \u002Fv4\u002Fusers\u002FenvironmentVariables                          DESTRUCTIVE: removes ALL your user variables; to remove one, use the accounts DELETE below\nPOST   \u002Fv4\u002Faccounts\u002Fidpid\u002F{idpId}\u002Fenvironmentvariables         body {\"name\", \"value\"}: one user variable (idpId: GET \u002Fapi\u002Fusers\u002Fv1\u002Fself)\nDELETE \u002Fv4\u002Faccounts\u002Fidpid\u002F{idpId}\u002Fenvironmentvariables\u002F{name}\n```\n\n```python\nrequests.post(f\"{base_url}\u002Fv4\u002Fprojects\u002F{project_id}\u002FenvironmentVariables\", headers=headers,\n              json={\"name\": \"OPENAI_API_KEY\", \"value\": secret})            # never print secret\nnames = [v[\"name\"] for v in requests.get(f\"{base_url}\u002Fv4\u002Fprojects\u002F{project_id}\u002FenvironmentVariables\",\n                                         headers=headers).json()]\n```\n\nUser overrides Project, which overrides the Compute Environment. Neither reaches a\nModel API: pass `environmentVariables` (`[{\"key\", \"value\"}]`) on\n`POST \u002Fapi\u002FmodelServing\u002Fv1\u002FmodelApis` when you create it, or set them later under the\nendpoint's own **Settings** (the update route has no variables field). Code reads them by name\n(`os.environ[\"NAME\"]`) and never prints them. Outside Domino (CI, Airflow, a laptop) these\nvariables are not readable; the external system holds its own copy of a token created in\nDomino. Docs: https:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Fadmin\u002Fsecurity-and-compliance\u002Fprotecting-tokens-api-keys\n(same under `\u002F6.3\u002F`).\n\n```bash\n# Inside a run (preferred)\ncurl -s \"$DOMINO_API_PROXY\u002Fapi\u002Fusers\u002Fv1\u002Fself\"\n\n# Inside a run without the proxy\ncurl -s -H \"Authorization: Bearer $(curl -s http:\u002F\u002Flocalhost:8899\u002Faccess-token)\" \\\n  \"$DOMINO_API_HOST\u002Fapi\u002Fusers\u002Fv1\u002Fself\"\n\n# Outside Domino: DOMINO_API_HOST is the deployment URL, PAT a Personal Access Token or service account token\ncurl -s -H \"Authorization: Bearer $PAT\" \"$DOMINO_API_HOST\u002Fapi\u002Fusers\u002Fv1\u002Fself\"\n```\n\nPython setup block used by every example in the API skills:\n\n```python\nimport os\nimport requests\n\nif os.environ.get(\"DOMINO_API_PROXY\"):          # inside a Domino execution\n    base_url = os.environ[\"DOMINO_API_PROXY\"].rstrip(\"\u002F\")\n    headers = {}\nelif os.environ.get(\"DOMINO_RUN_ID\"):           # inside a run, proxy not injected\n    base_url = os.environ[\"DOMINO_API_HOST\"].rstrip(\"\u002F\")\n    token = requests.get(\"http:\u002F\u002Flocalhost:8899\u002Faccess-token\").text.strip()\n    headers = {\"Authorization\": f\"Bearer {token}\"}\nelse:                                           # outside Domino: PAT or service account token\n    base_url = os.environ[\"DOMINO_API_HOST\"].rstrip(\"\u002F\")\n    headers = {\"Authorization\": f\"Bearer {os.environ['PAT']}\"}\nbase = base_url                                 # examples in other skills use either name\n```\n\n`DOMINO_RUN_ID`, `DOMINO_PROJECT_ID`, `DOMINO_PROJECT_OWNER`, `DOMINO_PROJECT_NAME`\nand `DOMINO_API_HOST` are injected into every execution (glossary:\nhttps:\u002F\u002Fdocs.domino.ai\u002Fcloud\u002Freference\u002Fenvironment-variables). Inside a run\n`DOMINO_API_HOST` can be an in-pod address: never build links for users from it.\n\n## Route types\n\nMost Domino endpoints are stable. Public API routes (`\u002Fapi\u002F...`, plus `\u002Fremotefs\u002Fv1` and\n`\u002Fmodel-monitor`) are versioned and documented in the published specs. Non-public routes,\nmeaning the internal API (`\u002Fv4\u002F...`, documented per deployment at `https:\u002F\u002F\u003Cdomino-domain>\u002Fdocs`)\nand web UI routes, also work, but can change in a future version of Domino. Use a public route\nwhen one exists; where none does, the skills label the call `(non-public route; may change in a\nfuture Domino version)` at the point of use. If a non-public call fails after an upgrade, check\nthe route in your deployment's `\u002Fdocs`. Dataset file routes: [HOSTS.md](.\u002FHOSTS.md).\nDiscovery: [API-SPECS.md](.\u002FAPI-SPECS.md).\n\n## Reference files (this skill)\n\n| File | Use when |\n|------|----------|\n| [HOSTS.md](.\u002FHOSTS.md) | Base URL for each API family, Model API invocation, governance, 404 on the in-run base |\n| [LIMITS.md](.\u002FLIMITS.md) | Pagination envelopes, caps, deprecated credentials and variables |\n| [ERRORS.md](.\u002FERRORS.md) | Status codes, retries, error bodies, job status fields |\n| [SDK-MAP.md](.\u002FSDK-MAP.md) | Which plugin skill covers each API surface |\n| [API-SPECS.md](.\u002FAPI-SPECS.md) | OpenAPI files (published and per deployment) and route discovery |\n\n## Next steps\n\nUse the domain skills (domino-python-sdk, domino-jobs, domino-apps, domino-governance,\ndomino-datasets, netapp-volumes, tags-and-properties, others); they assume the rules above.\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.","main","2c4dda96cbb98db0575b22d089730f3748afb604","skills\u002Fdomino-api-intro",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-api-intro",{"tool":40,"command":41},"bunx","bunx skills add dominodatalab\u002Fdomino-ai-plugin --skill domino-api-intro",{"tool":43,"command":44},"pnpm","pnpm dlx skills add dominodatalab\u002Fdomino-ai-plugin --skill domino-api-intro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-api-intro\u002FSKILL.md",true,[48,54,58,62,66],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"API-SPECS.md","REFERENCE","参考文档",3054,"https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-api-intro\u002FAPI-SPECS.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"ERRORS.md",5865,"https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-api-intro\u002FERRORS.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"HOSTS.md",5914,"https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-api-intro\u002FHOSTS.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"LIMITS.md",2959,"https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-api-intro\u002FLIMITS.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"SDK-MAP.md",4904,"https:\u002F\u002Fgithub.com\u002Fdominodatalab\u002Fdomino-ai-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fdomino-api-intro\u002FSDK-MAP.md",[71,78,85,92,99,106],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"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",[],[]]