nim-interactive-chat
v1.0.0Generate interactive chat scripts for NVIDIA NIM models, enabling one-click start, auto health check, OpenAI-compatible API, and seamless local conversation.
⭐ 0· 39·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (create interactive chat scripts for NIM models) matches the SKILL.md content. Required runtime tools (Docker, Python, openai package) are consistent with starting containers and providing an OpenAI-compatible client.
Instruction Scope
SKILL.md instructs creating scripts in the user's home directory, starting/stopping Docker containers, removing old containers, and waiting for health checks. Those actions are within scope for a start/stop/chat helper but are potentially disruptive (container removal, port exposure) so users should review generated scripts before running them.
Install Mechanism
Instruction-only skill with no install specification or downloaded artifacts — the lowest-risk form. Nothing will be written by the skill itself until the agent/user runs the generated scripts.
Credentials
The skill declares no required environment variables (none in metadata), which is consistent with the package being instruction-only. However, the generated Python client is 'OpenAI-compatible' and the SKILL.md lists the openai Python package as a requirement — a runtime API key (e.g., OPENAI_API_KEY or an equivalent) may be needed when using that client but is not declared here. This omission is plausible but worth awareness.
Persistence & Privilege
No always: true or other elevated privileges requested. The skill writes files under ~/ (start/stop scripts and a chat client) and controls Docker containers — expected for its purpose but users should confirm file locations and permissions before executing.
Assessment
This skill is coherent for creating local start/stop scripts and an interactive OpenAI-compatible client for NIM models, but review the generated files before running them. Points to consider: 1) The scripts will create/stop/remove Docker containers and write files to your home directory — ensure you don't overwrite important containers or files. 2) Verify the Docker image source (e.g., tgcr.turing-agi.com) is trusted before pulling. 3) The Python client requires the openai package and may need an API key at runtime even though no env vars are declared; be prepared to provide credentials when you run the client and avoid exposing them in plain script files. 4) Check port mappings and firewall rules to avoid unintended network exposure. If unsure, run the generated scripts in a controlled environment (VM or sandbox) and inspect the scripts line-by-line before execution.Like a lobster shell, security has layers — review code before you run it.
latestvk97dmm22vgyad0fhxnfmspdzwn84tdhd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.