datarobot-agent-llm-selectionlisted

Use when the user wants to configure LLM integration for a DataRobot agent application. This skill helps to change LLM model, switch between the LLM integrations the project supports (LLM Gateway, a DataRobot-deployed LLM, an external provider, an LLM Blueprint, and any others its config declares), or set up provider credentials. The skill reads the project's .datarobot/cli/llm.yml for the real options, interviews the user, then runs sync_llm_env.py with the chosen values as CLI args to merge into .env.
datarobot-oss/datarobot-agent-skills · ★ 25 · AI & Automation · score 78

Install: claude install-skill datarobot-oss/datarobot-agent-skills

# DataRobot LLM gateway configuration Configure LLM integration **without hand-editing `.env`**. The skill drives `sync_llm_env.py` with the user's answers as CLI arguments. ## Resolve script path once per session `<skill_scripts_dir>` = the `scripts/` subdirectory of the directory containing this `SKILL.md`. ```shell ls <skill_scripts_dir>/sync_llm_env.py ``` ## Hard rules 1. **Never** ask the user to paste API keys or `DATAROBOT_API_TOKEN` in chat 2. **Never** read, copy, echo, or pass `DATAROBOT_API_TOKEN` yourself. The token lives in `$XDG_CONFIG_HOME/datarobot/drconfig.yaml` (default `~/.config/datarobot/drconfig.yaml`), populated by `dr auth login`, and the `dr` CLI reads it internally. Do not run `cat drconfig.yaml`, `cat .env`, `env | grep TOKEN`, `echo $DATAROBOT_API_TOKEN`, `curl -H "Authorization: Bearer $..."`, or any equivalent one-liner 3. **Never** pass secrets as CLI args to `sync_llm_env.py` or write them to tracked files 4. **Never** set provider credentials for an integration whose config section doesn't declare them. Let `sync_llm_env.py` decide — it reads the section from the project's config 5. Only `sync_llm_env.py` merges LLM keys into `.env` — do not edit `.env` manually 6. Run all commands from **project root** 7. Pressing enter in chat does nothing. Don't tell the user to "press enter to accept the default" or "hit return". If a field has a sensible default, apply it silently and mention it in the confirmation, or