Agent setup

Set up Relay in this agent. Do what you can; guide me through anything that needs my input.

## 1. Check this agent

- Identify this agent and its version. Ask only if you cannot tell.
- Check for an existing Relay connection. Preserve other integrations and avoid duplicates.
- Check for Relay skills separately. A connection without skills is incomplete.

## 2. If this is ChatGPT

If I pasted this into a regular ChatGPT conversation (web or desktop app, not Codex), you cannot install Relay from here. Don't run commands or edit files. Instead, give me these steps and stop:

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. This works on Free and paid plans; no upgrade is needed.
2. Open **Settings → Plugins → Developer mode** (or **Plugins → + → Create MCP App**). Name it Relay, enter the server URL `https://relay.playbookmedia.io/mcp` in full, including `https://` (otherwise ChatGPT reports "Unsafe URL"), and keep **OAuth** selected.
3. Create it, sign in to Relay, and approve the connection.
4. Start a new chat, select Relay from the **+** menu, and send: "Use Relay to check my connection and list my projects."

Link the [ChatGPT setup guide](https://relay.playbookmedia.io/docs/chatgpt) for screenshots and troubleshooting. If Relay is self-hosted, ChatGPT needs a publicly reachable HTTPS URL; point me to the [self-hosting guide](https://relay.playbookmedia.io/docs/self-hosting) instead. If I'm in Codex, continue below.

## 3. Install the plugin first

The official plugin bundles MCP + SEO skills, with Relay namespacing and shared updates.

- **Codex:** follow the [plugin guide](https://relay.playbookmedia.io/docs/codex-plugin).
- **Claude Code:** follow the [plugin guide](https://relay.playbookmedia.io/docs/claude-code-plugin).
- **Claude Cowork or the Claude desktop app:** you cannot install plugins from this chat, so don't run commands. Tell me to open **Customize** (in Cowork, the **Cowork** tab first) → **Plugins** → **+** or **Add** → **Add marketplace** → **Add from a repository**, enter `https://github.com/PlaybookMediaLLC/open-seo`, and install **Relay**. Then I start a new task and type `/` to check that Relay skills appear. If I already have a custom Relay connector, have me remove it once the plugin signs in. Plugins need a paid plan. The plugin connects only to hosted Relay, so skip it if `https://relay.playbookmedia.io/mcp` is not on openseo.so (self-hosted) or I'm on Free. Instead, have me add that endpoint under **Customize → Connectors** → **Add custom connector** and upload the [public skills](https://relay.playbookmedia.io/docs/skills/setup) in **Customize → Skills**. Then continue at step 5.
- **Other agents:** verify plugin compatibility in their current documentation.
- Check the installed client's help before running commands.

## 4. Fall back to MCP + skills

If the plugin is unsupported:

- Add `https://relay.playbookmedia.io/mcp` using the [MCP guide](https://relay.playbookmedia.io/docs/mcp).
- Install the [public SEO skills](https://relay.playbookmedia.io/docs/skills/setup) for this agent only.
- Do not copy internal repository skills or duplicate bundled skills.
- If skills are unsupported, use MCP alone and link to the workflow guides.

For self-hosted Relay, use its endpoint directly; the official plugin targets the hosted service.

## 5. Sign in

- **Hosted Relay:** Prefer OAuth and let me approve login in my browser. If this client cannot use OAuth, send me to `https://relay.playbookmedia.io/settings` → API keys. Have me enter the key in the client's secret settings or environment, never chat or a repository.
- **Self-hosted Relay:** Follow the deployment's authentication instructions. A local server configured without authentication needs no OAuth or Relay API key. For Cloudflare Access deployments, follow the self-hosting guide to configure Managed OAuth for the MCP client.
- **Manual setup needed?** Use this agent’s current documentation and give only the steps I need to do myself.

## 6. Reload and verify

- Use the current agent’s native reload flow, checking its installed version, help, or official documentation. Prefer automatic discovery or an in-place reload; restart only if required to load the new tools and skills.
- Once tools load in this session, run whoami and list_projects (free reads). Check skill discovery too. If a reload needs my action, give the instructions rather than repeatedly retrying unavailable tools.
- Track installation, sign-in, and verification separately. A connected server is not proof that this session can use its tools. Never claim verification before the free reads succeed.
- Do not create projects or run paid research during installation.

## 7. Finish with a short handoff

Keep progress updates brief. The final reply must be **140 words or fewer** and follow this template:

**Status**
[Briefly say what succeeded or what blocked setup.]

**Next**

1. `[Give the native reload command or UI action for this agent, only if needed.]` Then say “Check that Relay is connected.” Approve sign-in if prompted.
2. Try one of these:
   - `[SEO Audit invocation]` **(recommended)** — find your website's biggest SEO issues.
   - `[SEO Project Setup invocation]` — interview you about your website and set up its project context.
   - `[Keyword Research invocation]` — find keywords worth targeting.
   - `[Local SEO invocation]` — review your Google Business Profile and local competitors.

Want to know what was set up? Just ask.

Adapt the template to the actual result:

- If I must install the plugin by hand, as in Claude Cowork, replace step 1 with those clicks.
- If installation failed, name the blocker and replace reload with the fix. If fully verified, say it is ready and omit reload. Do not claim sign-in failed or is required merely because tools need reloading.
- Recommend this agent’s idiomatic way to invoke each installed skill: its native command, mention, picker, or natural-language request. Use the discovered skill name and plugin namespace; do not assume `/skill-name` works everywhere or create aliases to force it. Check the agent’s help or official documentation when unsure. If skills are unsupported, give equivalent plain-language requests using the connected tools. Recommend workflows; do not run them during installation.
- Keep tool names such as whoami and list_projects in your checks, not the final reply. Omit versions, paths, connection details, skill counts, other integrations, and cleanup commands unless they explain the blocker or I ask. Do not add more sections or a verification checklist.

Update my installed Relay skills using https://relay.playbookmedia.io/docs/agent-setup#update-your-skills.

If this is ChatGPT on the web or a regular desktop chat, use https://relay.playbookmedia.io/docs/chatgpt#update-openseo. For a public directory plugin, start a new chat to load the available tools and skills; reconnect only if sign-in needs attention. For a custom MCP connection, select Refresh in its details, then start a new chat. Refreshing a custom connection updates tools, not skill files. Do not run local Codex commands to update ChatGPT web.

Identify this agent and how Relay was installed. Use the matching plugin or skills installer, checking the installed client's help before running commands. Update only Relay in its existing scope. Preserve my MCP endpoint, sign-in, and personal skill edits; ask before replacing conflicting edits. Avoid duplicate skills and do not install internal repository skills.

If the skills were copied manually, compare them with https://github.com/PlaybookMediaLLC/open-seo/tree/main/plugins/openseo/skills and update the installed public skill folders, including their supporting files. For Grok Bot or another agent without a verified update command, use its supported skill management flow or give me the exact manual steps available in this version.

Reload skills if supported. If I need to reload or start a new session, tell me what to do. Verify the updated skill files and that this agent can discover them; an active MCP connection alone does not prove the skills updated. Briefly tell me what changed and anything left to do. Do not run SEO research during the update.