Relewise Setup
Never ask the user to paste a Personal Access Token into the conversation. Do not print, repeat, inspect, or place a token in command text, command arguments, output, logs, or repository files.
Before any Agent Gateway call, activate and follow the installed relewise-agent-gateway skill from this plugin. Pass it the identity operation or MCP tool; do not resolve the CLI, choose a transport, or handle transport mechanics in this setup skill. This setup is idempotent: verify existing authentication before changing anything, and stop as soon as a reusable route works.
Set up or repair authentication
- Verify identity without changing configuration using REST operation
IdentityGetCurrentUser or related MCP tool get_me through the Agent Gateway skill.
- If identity discovery succeeds, explain that Relewise is already connected and make no changes. Include accessible Dataset display names only when useful.
- If authentication fails, distinguish a missing token from a rejected, expired, revoked, or regenerated token using the returned error. Do not inspect or print the environment variable itself.
- Follow authentication setup. Prefer a reusable secure credential-provider route; otherwise guide the user to a persistent user or system environment variable named
RELEWISE_AGENT_GATEWAY_TOKEN.
- Let the user create, store, or replace the token outside the conversation and wait for confirmation when their action is required. If they ask for concrete configuration steps, use current official documentation for their environment rather than relying on fixed vendor UI navigation stored in this skill.
- Verify identity again through an available transport. For MCP, the AI client may need to restart after its environment changes before the registered server can authenticate. Confirm success without exposing token metadata that is not needed. If authentication still fails, explain the specific next corrective action; do not repeatedly ask the user to redo unchanged steps.
The workflow is idempotent: every invocation starts by verifying the current configuration, and a working setup is never replaced merely because the skill was invoked again. A setup is complete only when future Relewise commands can receive the PAT without the user re-entering or re-exporting it each time.
Do not create, regenerate, revoke, or change the scope of a Personal Access Token on the user's behalf. Explain those actions and their consequences, then let the user perform them in My Relewise.
1---2name: relewise-setup3description: Set up, verify, or repair Relewise Agent Gateway authentication. Use when a user wants to connect Relewise, configure a Personal Access Token, resolve a missing or rejected token, or check whether Relewise is already connected.4---56# Relewise Setup78Never ask the user to paste a Personal Access Token into the conversation. Do not print, repeat, inspect, or place a token in command text, command arguments, output, logs, or repository files.910Before any Agent Gateway call, activate and follow the installed `relewise-agent-gateway` skill from this plugin. Pass it the identity operation or MCP tool; do not resolve the CLI, choose a transport, or handle transport mechanics in this setup skill. This setup is idempotent: verify existing authentication before changing anything, and stop as soon as a reusable route works.1112## Set up or repair authentication13141. Verify identity without changing configuration using REST operation `IdentityGetCurrentUser` or related MCP tool `get_me` through the Agent Gateway skill.152. If identity discovery succeeds, explain that Relewise is already connected and make no changes. Include accessible Dataset display names only when useful.163. If authentication fails, distinguish a missing token from a rejected, expired, revoked, or regenerated token using the returned error. Do not inspect or print the environment variable itself.174. Follow [authentication setup](references/authentication-setup.md). Prefer a reusable secure credential-provider route; otherwise guide the user to a persistent user or system environment variable named `RELEWISE_AGENT_GATEWAY_TOKEN`.185. Let the user create, store, or replace the token outside the conversation and wait for confirmation when their action is required. If they ask for concrete configuration steps, use current official documentation for their environment rather than relying on fixed vendor UI navigation stored in this skill.196. Verify identity again through an available transport. For MCP, the AI client may need to restart after its environment changes before the registered server can authenticate. Confirm success without exposing token metadata that is not needed. If authentication still fails, explain the specific next corrective action; do not repeatedly ask the user to redo unchanged steps.2021The workflow is idempotent: every invocation starts by verifying the current configuration, and a working setup is never replaced merely because the skill was invoked again. A setup is complete only when future Relewise commands can receive the PAT without the user re-entering or re-exporting it each time.2223Do not create, regenerate, revoke, or change the scope of a Personal Access Token on the user's behalf. Explain those actions and their consequences, then let the user perform them in My Relewise.
Relewise