setup-openseo

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Set up OpenSEO in this agent. Do what you can; guide me through anything that needs my input.
在此 Agent 中设置 OpenSEO。尽可能自行完成;对于任何需要我输入的环节,请指导我完成。

1. Check this agent

1. 检查当前 Agent

  • Identify this agent and its version. Ask only if you cannot tell.
  • Check for an existing OpenSEO connection. Preserve other integrations and avoid duplicates.
  • 识别此 Agent 及其版本。仅在无法确定时询问。
  • 检查是否已存在 OpenSEO 连接。保留其他集成,避免重复配置。

2. Install the plugin first

2. 首先安装 plugin

The official plugin bundles MCP + SEO skills, with OpenSEO namespacing and shared updates.
  • Codex: follow the plugin guide.
  • Claude Code: follow the plugin guide.
  • Other agents: verify plugin compatibility in their current documentation.
  • Check the installed client's help before running commands.
官方 plugin 将 MCP + SEO skills 打包在一起,并采用 OpenSEO 命名空间和共享更新机制。
  • **Codex:**按照 plugin 指南。
  • **Claude Code:**按照 plugin 指南。
  • **其他 Agent:**根据其当前文档验证 plugin 兼容性。
  • 运行命令前,先查看已安装客户端的帮助信息。

3. Fall back to MCP + skills

3. 回退到 MCP + skills

If the plugin is unsupported:
  • Add
    https://app.openseo.so/mcp
    using the MCP guide.
  • Install the public SEO skills 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 OpenSEO, use its endpoint directly; the official plugin targets the hosted service.
如果不支持 plugin:
  • 按照 MCP 指南 添加
    https://app.openseo.so/mcp
    。
  • 仅为当前 Agent 安装 公开 SEO skills。
  • 不要复制内部 repository skills,也不要重复安装 bundled skills。
  • 如果不支持 skills,则仅使用 MCP,并提供 workflow 指南链接。
对于 self-hosted OpenSEO,直接使用其 endpoint;官方 plugin 面向 hosted service。

4. Sign in

4. 登录

  • 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.
  • 优先使用 OAuth。 启动登录流程,让我在浏览器中批准授权。
  • 没有 OAuth? 引导我前往
    https://app.openseo.so/settings
    → API keys。让我将 key 输入客户端的 secret 设置或 environment 中,切勿在聊天或 repository 中输入。
  • 需要手动设置? 使用当前 Agent 的文档,只提供需要我亲自完成的步骤。

5. Reload and verify

5. 重新加载并验证

  • 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.
  • 使用当前 Agent 原生的 reload 流程,并查看其已安装版本、帮助信息或官方文档。优先使用自动发现或原地 reload;仅在必须重启才能加载新 tools 和 skills 时才重启。
  • tools 在当前会话中加载后,运行 whoami 和 list_projects(免费读取操作)。同时检查 skills discovery。如果 reload 需要我采取行动,请给出操作说明,不要反复重试尚不可用的 tools。
  • 分别跟踪 installation、sign-in 和 verification。服务器已连接并不能证明当前会话可以使用其 tools。在免费读取操作成功之前,绝不能声称已验证。
  • installation 期间不要创建 projects 或运行付费 research。

6. Finish with a short handoff

6. 最后给出简短交接说明

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 OpenSEO 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 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.
进度更新应保持简短。最终回复必须控制在 140 个单词以内,并遵循以下模板:
状态 [简要说明设置成功的部分或设置受阻的原因。]
下一步
  1. [仅在需要时,给出当前 Agent 原生的 reload 命令或 UI 操作。]
    然后说:“确认 OpenSEO 已连接。”如果出现登录提示,请批准登录。
  2. 尝试以下任一操作:
    • [SEO Audit 调用]
      (推荐)——找出你网站中最严重的 SEO 问题。
    • [SEO Project Setup 调用]
      ——通过访谈了解你的网站,并设置其项目上下文。
    • [Keyword Research 调用]
      ——找出值得布局的 keywords。
    • [Local SEO 调用]
      ——审查你的 Google Business Profile 和本地竞争对手。
想了解具体设置了哪些内容?直接问即可。
根据实际结果调整模板:
  • 如果安装失败,指出阻碍因素,并用相应的修复方法替代 reload。
  • 如果已完全验证,说明已就绪并省略 reload。
  • 不要仅因为 tools 需要 reload,就声称 sign-in 失败或必须进行 sign-in。
  • 以当前 Agent 惯用的方式调用每个已安装 skill:native command、mention、picker 或 natural-language request。使用发现的 skill name 和 plugin namespace;不要假设
    /skill-name
    在所有环境中都有效,也不要创建 aliases 来强制调用。不确定时,查看 Agent 的帮助信息或官方文档。
  • 如果不支持 skills,请使用已连接的 tools 给出等效的 natural-language requests。推荐这些 workflows,但不要在 installation 期间运行。
  • 在 checks 中保留 whoami 和 list_projects 等 tool names,但不要在最终回复中提及。除非这些信息能够解释 blocker 或我提出要求,否则省略 versions、paths、connection details、skill counts、other integrations 和 cleanup commands。不要添加更多 sections 或 verification checklist。