Relewise/relewise-agent-plugins / plugins/relewise/skills/relewise-setup
relewise-setup
VerifiedSet up, verify, or repair Relewise Agent Gateway authentication. Use when a user wants to connect Relewise, sign in or reconnect with OAuth, diagnose MCP connectivity, configure a Personal Access Token, resolve missing Dataset access or Agent Gateway configuration, or check whether Relewise is already connected.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.3 KB |
| references/authentication-setup.md | markdown | 3.3 KB |
| references/dataset-access.md | markdown | 4.6 KB |
| references/my-relewise-links.md | markdown | 981 B |
references/my-relewise-links.md
View on GitHub# My Relewise setup links
My Relewise is Relewise's web portal at `https://my.relewise.com`. It is separate from the AI client, plugin settings, or MCP connection UI. When setup requires the user to inspect or change portal state, identify My Relewise by name and provide a clickable absolute URL.
Use only these links:
- Personal Access Tokens: `https://my.relewise.com/user#personal-access-tokens`
- Connected Apps: `https://my.relewise.com/user#connected-apps`
- Dataset Agent Gateway settings: `https://my.relewise.com/{datasetId}/administration/agent-gateway`
Substitute `{datasetId}` only with a Dataset ID returned by `get_me` or another verified Agent Gateway response. Preserve it exactly and never invent it. If the Dataset ID is unavailable, use the applicable account-scoped link instead of constructing a Dataset link.
Do not infer or construct other My Relewise URLs from these examples. Never place a PAT value, OAuth access token, or OAuth client ID in a URL.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |