From iris-dev
Diagnoses IRIS connection issues and generates the correct .iris-agentic-dev.toml config block based on the user's deployment scenario (Docker, host, HTTPS, or VS Code Server Manager).
How this skill is triggered — by the user, by Claude, or both
Slash command
/iris-dev:iad-config-setupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Always run `check_config` first.** Never guess — read what the tool reports.
Always run check_config first. Never guess — read what the tool reports.
check_config → look at: connected, connection_source, config_watch_path, server_manager
| What you see | What it means |
|---|---|
connected: true, connection_source: "env_var" | Already connected via env vars — config optional |
connected: true, connection_source: "docker" | Already connected via Docker — config optional |
connected: true, connection_source: "server_manager" | VS Code Server Manager is working — no config needed |
connected: false | No connection found — config required |
config_parse_error present | Existing config has a syntax error — fix it |
server_manager.available: true | VS Code Server Manager detected — use IRIS_SERVER_NAME instead of manual config |
Ask the user: How are you running IRIS?
| Scenario | Config pattern |
|---|---|
| Docker container (named) | container = "my-iris" |
| Direct host:port | host = "hostname" + web_port = 52773 |
| VS Code Server Manager | No config — set IRIS_SERVER_NAME=<name> env var |
| HTTPS enterprise gateway | scheme = "https" + web_prefix = "irisaicore" (if behind reverse proxy) |
| Community IRIS (no web server) | container = "my-iris" + docker_only = true |
Write to the path shown in config_watch_path from check_config. Hot-reload is automatic.
container = "my-iris"
namespace = "USER"
Hot-reload fires automatically when you save. No restart needed.
host = "iris.example.com"
web_port = 52773
namespace = "PROD"
username = "_SYSTEM"
password = "SYS"
host = "iris.corp.example.com"
web_port = 443
scheme = "https"
web_prefix = "irisaicore"
namespace = "APP"
username = "apiuser"
password = "secret"
The Atelier API must be reachable at https://host:443/irisaicore/api/atelier/.
container = "iris-community"
namespace = "USER"
docker_only = true
All tool calls use docker exec instead of HTTP. No web port needed.
mode = "operate"
[instance.prod]
host = "prod.example.com"
web_port = 52773
namespace = "PROD"
username = "svc"
password = "secret"
role = "subject"
[instance.dev]
container = "dev-iris"
namespace = "DEV"
role = "workspace"
Roles: workspace (write allowed), subject (read-only by default), control-plane.
[policy.prod]
allow = ["query", "search", "docs"]
Blocks compile, execute, source_control, debug, admin, skill, kb on the prod Server Manager server.
Omit allow entirely to permit everything (or omit the [policy.*] block).
Tool categories: compile, execute, query, search, docs, source_control, debug, admin, skill, kb
| Var | Default | Purpose |
|---|---|---|
IRIS_HOST | — | Host for direct connection |
IRIS_WEB_PORT | 52773 | Web port |
IRIS_NAMESPACE | USER | Default namespace |
IRIS_USERNAME | _SYSTEM | Username |
IRIS_PASSWORD | SYS | Password |
IRIS_CONTAINER | — | Docker container name |
IRIS_SERVER_NAME | — | Server Manager server to use when multiple are configured |
OBJECTSCRIPT_WORKSPACE | $PWD | Override workspace root (where to look for config file) |
Priority: config file > env vars > auto-discovery.
config_parse_error in check_config output
TOML syntax error. Common causes:
host = iris.com → host = "iris.com"[instance.prod.role] → role = "subject" inside [instance.prod]Connected via wrong source (e.g. picking up community IRIS instead of target)
Set IRIS_CONTAINER or write a config file with explicit host/container.
Server Manager credential_status: "not_configured"
Credential not in OS keychain. In VS Code → Server Manager → right-click server → Reconnect.
After reconnecting, call check_config again to verify credential_status: "resolved".
Multiple Server Manager servers, no IRIS_SERVER_NAME set
check_config will show server_manager.available: true with multiple servers.
Set IRIS_SERVER_NAME=<name> (the map key from intersystems.servers) to select one.
docker_only = true needed when
2plugins reuse this skill
First indexed Jun 30, 2026
npx claudepluginhub intersystems-community/iris-agentic-devProvides correct connection patterns for InterSystems IRIS from Python (DBAPI/Native API), Java (JDBC), and ODBC, including port numbers and package names.
Drives iris-cli to search, browse, ask AI questions, and export content from an Iris architecture-knowledge repository.
Configures Arness Infra for projects by selecting cloud providers, IaC tools like Terraform/Pulumi, environments, CI/CD platforms, scanning existing artifacts, and persisting to CLAUDE.md.