superrelay
/superrelay
Obsługuje zgłoszenia klientów w Superrelay z terminala lub przez agenta: odpowiada, ustawia status, priorytet i przypisanie oraz szuka kontaktów.
- Autor
- superrelayhq ↗
- Repozytorium
- skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 08.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 3
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 5
Brak sygnałów. Repozytorium zmienione 08.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Obsługuje zgłoszenia klientów w Superrelay z terminala lub przez agenta: odpowiada, ustawia status, priorytet i przypisanie oraz szuka kontaktów.
Oryginalny opis (EN)
Work in a Superrelay customer support workspace from the terminal or an agent. Read and answer conversations, triage them (status, priority, labels, assignee), look up contacts and companies, manage feature requests, changelog entries and help center articles through the `relay` CLI, the MCP server or the REST API. Use when the user mentions Superrelay or Relay support, asks to check or reply to support conversations, triage the inbox, find a customer, update a feature request, or edit help center articles.
Jak działa
- Setup
- Concepts
- Common tasks
- Output and errors
- Guardrails
Podgląd SKILL.md
---
name: superrelay
description: Work in a Superrelay customer support workspace from the terminal or an agent. Read and answer conversations, triage them (status, priority, labels, assignee), look up contacts and companies, manage feature requests, changelog entries and help center articles through the `relay` CLI, the MCP server or the REST API. Use when the user mentions Superrelay or Relay support, asks to check or reply to support conversations, triage the inbox, find a customer, update a feature request, or edit help center articles.
---
# Superrelay
[Superrelay](https://superrelay.com) is a support platform: live chat widget, email and WhatsApp inbox, AI agents, help center, feature request board and changelog. Everything in a workspace is reachable three ways, all backed by the same public API and the same API key scopes:
| Way | Best for | Setup |
| --- | --- | --- |
| `relay` CLI (`@superrelay/cli`) | Shell access, scripts, CI, bulk work | `npm i -g @superrelay/cli` or `npx @superrelay/cli <command>` |
| MCP server `https://api.superrelay.com/v1/mcp` | Agents with MCP tools and no shell | OAuth sign-in, or `Authorization: Bearer rl_live_…` |
| REST API `https://api.superrelay.com/v1/public` | Code that integrates Superrelay | `Authorization: Bearer rl_live_…` |
Prefer the CLI when you can run commands: every command takes `--json`, IDs accept short prefixes, and lists take `--all`. If Superrelay MCP tools (`list_conversations`, `reply_to_conversation`, …) are already connected, use them instead of installing anything.
## Setup
1. Check for credentials: `relay doctor` (or `relay config --show`). `RELAY_API_KEY` and `RELAY_API_URL` in the environment override stored config.
2. If there is no key, ask the user to create one in the Superrelay dashboard under **Settings → API Keys** (it starts with `rl_live_`). Never invent one and never print it back.
3. Store it with `relay config --api-key <key>`, or export `RELAY_API_KEY` for one session or CI.
To connect the MCP server in Claude Code instead:
```bash
claude mcp add --transport http superrelay https://api.superrelay.com/v1/mcp
```
then `/mcp` to sign in. Owners and admins get every tool; members connect read-only.
### Scopes
A key only does what its scopes allow; a missing scope fails with an error naming it. Write scopes do not imply read.
| Scope | Allows |
| --- | --- |
| `conversations:read` / `conversations:write` | Read conversations and messages / reply, create, change status, priority, labels, assignee |
| `contacts:read` / `contacts:write` | Read / create and update contacts |
| `companies:read` / `companies:write` | Read / create and update companies |
| `products:read` | List products |
| `knowledge_bases:read` / `knowledge_bases:write` | Read / write help center articles and categories |
| `feature_requests:read` / `feature_requests:write` | Read / create, edit, move and link feature requests |
| `changelog:read` / `changelog:write` | Read / draft, edit and publish changelog entries |
## Concepts
- **Workspace**: one company's Superrelay account. A key belongs to one workspace.
- **Product**: what the workspace supports (an app, a site). Conversations, requests, changelog entries and knowledge bases belong to a product. `relay products --json` lists them. When a workspace has several, ask which one before writing anything.
- **Conversation**: one thread with a customer over chat, email or WhatsApp. Status `open`, `pending` or `resolved`; priority `low`, `medium`, `high`, `urgent` or none.
- **Contact** and **company**: the customer and the organization they belong to.
- **Knowledge base**: the articles behind a help center. Articles are `draft` or `published`.
- **Feature request** and **changelog entry**: the public roadmap board and release notes. Publishing an entry completes its linked requests and tells their voters.
## Common tasks
### Read the inbox
```bash
relay list --status open --json # open conversations
relay list --status open --priority urgent --all --json
relay list --product none --json # not yet routed to a product
relay list --search "refund" --json
relay show <id> --json # details
relay chat <id> --limit 50 --json # message history
```
IDs accept a prefix of at least four characters; the CLI refuses an ambiguous prefix.
### Triage
```bash
relay priority <id> high
relay label <id> billing vip # replaces all labels; no args clears
relay assign <id> <userId> # --unassign to clear
relay pending <id>
relay resolve <id>
relay reopen <id>
```
### Reply to a customer
```bash
relay reply <id> "Thanks, I've refunded the order. It shows up in 3-5 days."
relay reply <id> --file reply.md # or --file - for stdin
```
A reply reaches the customer right away, in their chat or by email if they are offline. Read the conversation first, draft the reply, and show it to the user before sending unless they told you to send it.
### Customers
```bash
relay people --email jane@example.com --json
relay people --search "Acme" --json
relay person <id> --json
relay companies --search "Acme" --json
relay company:contacts <companyId> --json
relay contact:update <id> --company <companyId>
```
### Feature requests and changelog
```bash
relay requests list --product <productId> --status planned --json
relay requests create --title "Dark mode" --description "…" --product <productId>
relay requests move <id> --status in_progress
relay requests link <id> https://github.com/org/repo/pull/123 --title "Add dark mode"
relay changelog draft --file release.md --product <productId>
relay changelog publish <entryId> # customer-facing, see guardrails
```
New requests are private by default. For a full release flow (commits since the last tag → linked requests → draft → publish), use the `superrelay-release` skill.
### Help center articles
```bash
relay kb list --json
relay kb articles <kb> --status published --json
relay kb article <articleId> # markdown
relay kb publish <articleId>
relay kb suggestions list <kb> --json # topics customers ask that no article answers
```
To keep a help center in a folder of Markdown files with pull, diff and push, use the `superrelay-docs` skill.
## Output and errors
- `--json` prints results to stdout and structured errors to stderr; a nonzero exit means failure.
- Lists return `{ data, has_more, next_cursor }`. Pass `--cursor <next_cursor>` or use `--all`.
- Reads retry on 429/502/503/504 (`--retries`, default 2). Writes are never retried automatically; `requests create`, `changelog draft` and `changelog publish` take an idempotency key, so rerunning the same input resumes instead of duplicating.
- `relay <command> --help` lists every flag. The full command list is in [references/cli.md](references/cli.md); REST and MCP details are in [references/api.md](references/api.md).
## Guardrails
- **Ask before anything a customer sees**: `relay reply`, `relay changelog publish` (completes requests, emails voters, replies to and closes their tickets), `relay kb publish` and pushing published articles. Show what will go out and wait for a yes.
- Never paste conversation content, customer emails or phone numbers into places outside the workspace (issues, commits, public docs) without the user's say-so.
- Never link a feature request from another product, and never guess a request match; a wrong link emails the wrong voters.
- Keep the API key out of files you commit, logs and replies.
Pliki w paczce (3)
- SKILL.md 7 KB
- references/api.md 5 KB
- references/cli.md 5 KB
Wersje
W bazie nie ma innych skilli o nazwie superrelay.
Migawka bazy z 13.11.2026 · wersja paczki 02cb4dd1e31e (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100superrelay-docs
Prowadzi centrum pomocy Superrelay jako pliki Markdown w repozytorium: pisze artykuły, sprawdza je i synchronizuje z platformą. - 100superrelay-widget
Dodaje widżet czatu Superrelay do strony, przekazuje tożsamość zalogowanych użytkowników i podpisuje ją po stronie serwera. - 90gleap
Obsługuje przestrzeń roboczą Gleap przez MCP: zgłoszenia wsparcia, rozmowy z klientami, prośby o funkcje, CRM i bazę wiedzy. - 90customer-support-knowledge-base
Pisze dokładne artykuły pomocy, runbooki i procedury obsługi dla systemów używanych przez użytkowników, z triażem zgłoszeń. - 90intercom-analysis
Analizuje rozmowy w Intercom, szuka wzorców zgłoszeń wsparcia i wyszukuje kontakty oraz firmy. - 100mb-support
Prowadzi obsługę klienta, która dotrzymuje obietnic: zapisuje sprawy i zobowiązania, przegląda je tygodniowo i trzyma zasady w repozytorium.