setup-openseo

Original：🇺🇸 English

Translated

Set up OpenSEO in the current AI agent. Use when a user pastes the OpenSEO installation prompt or asks to connect its plugin, MCP, and skills.

2installs

Added on2026-10-11

NPX Install

npx skill4agent add every-app/open-seo setup-openseo

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

Identify this agent and its version. Ask only if you cannot tell.
Check for an existing OpenSEO connection. Preserve other integrations and avoid duplicates.

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

If the plugin is unsupported:

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

Prefer OAuth. Start login; let me approve it in my browser.
No OAuth? Send me to
```
https://app.openseo.so/settings
```
→ API keys. Have me enter the key in the client's secret settings or environment, never chat or a repository.
Manual setup needed? Use this agent’s current documentation and give only the steps I need to do myself.

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.

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

[Give the native reload command or UI action for this agent, only if needed.]

Then say “Check that OpenSEO is connected.” Approve sign-in if prompted.

Want to know what was set up? Just ask.

Adapt the template to the actual result:

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.