configure

Files (2)

• SKILL.md
• configure.js

SKILL.md (first lines)

# Configure Credentials

This is an **Action** skill — a one-time setup step. It stores your Thought
Industries **instance URL** and **Incoming API key** in a user-scoped config
file so every other skill can authenticate automatically.

## When to use

- First-time setup of the plugin.
- Any skill fails with `Missing API key` or `Missing base URL`.
- Rotating to a new API key or pointing at a different instance.

## Security — read before running

- **The user runs this in their own terminal.** The API key is typed at a
  hidden prompt and read inside the Node process only. Do **not** ask the user
  to paste their key into the chat, and do **not** print or `cat` the config
  file — that would leak the key into the transcript.
- Credentials are written to `~/.ti-admin-v3/config.json` with owner-only
  permissions (`0600`). The file lives in the user's home directory, **not**
  inside the plugin folder, so it is never committed or shipped.

## Agent instructions

1. If a skill reported missing credentials, tell the user to run the command
   below **in their own terminal** and re-run the original skill afterward.
2. Never request the API key value in chat; the interactive prompt collects it.

## Run the script

```bash
# Interactive (recommended): prompts for URL, then hidden API key input
node "${CLAUDE_PLUGIN_ROOT:+$CLAUDE_PLUGIN_ROOT/skills/actions/configure/}configure.js"

# Non-interactive: URL as a flag, key from a file (avoids shell history)
node "${CLAUDE_PLUGIN_ROOT:+$CLAUDE_PLUGIN_ROOT/skills/actions/configure/}configure.js" \
  --base-url=https://your-instance.thoughtindustries.com \
  --api-key-file=/path/to/ti-api-key.txt
```

<HARD-GATE>
Never echo, print, log, or `cat` the API key or the config file contents.
Never ask the user to paste their API key into the chat.
</HARD-GATE>

From thoughtindustries/ti-admin-plugin, MIT.

More from thoughtindustries/ti-admin-plugin