Skip to content

Frequently Asked Questions (FAQ)

Find answers to common questions about using and building with Seer Agent Engine.

General

What is Seer Agent Engine?

Seer Agent Engine is an AI-powered infrastructure designed for SEO, Analytics, and Paid Media workflows. It provides a set of standardized "agents" that automate complex marketing tasks—like content audits and SERP analysis—while maintaining the high-quality standards of the Seer Interactive team.

Do I need paid AI subscriptions?

It depends on your platform:

  • Claude.ai: Requires a Claude subscription (Pro/Team/Enterprise) with Skills enabled via Customize → Skills.
  • Claude Code: Requires an Anthropic subscription that includes Claude Code access.
  • MCP Servers: Some data sources (like DataForSEO or BigQuery) have their own separate costs and subscription requirements.

Already using OpenCode? It uses your configured AI providers via OAuth or API keys.

How is my data handled?

Data privacy is a core principle of the system: * Local Processing: Most data processing happens in your local environment. * Direct Connections: MCP servers connect directly from your machine to your data sources (BigQuery, Wrike, etc.). * No Training: By default, data sent to your configured AI provider is not used to train external models. Always check your specific provider's terms to confirm.

Claude.ai & Cowork

Why can't I share a Cowork project with a teammate?

Cowork projects are tied to a local folder on your computer, so the project itself isn't shareable — only skills are shareable directly from Cowork. To collaborate:

  • Create the project in Claude.ai chat instead — Projects there are cloud-based and shareable, or
  • Point Cowork at a synced, shared Google Drive folder as the working folder so teammates use the same folder as their own Cowork project.
My Claude connectors (Google Drive, Gmail, Seer MCP) keep disconnecting — why?

The most common cause is a Google/Gmail password change. Seer requires periodic password rotation, and that silently disconnects every connector tied to Google single sign-on. Reconnect via Claude → Manage Connectors after any password update.

A teammate shared a Project with me and then left Seer — can I still access it?

Possibly, but you'll need help. Offboarding removes the owner's seat, which can lock the Project to view-only for everyone else. An admin can temporarily re-enable the departed account long enough to grant another teammate edit or ownership access, then remove it again. Ask in #help-tips-claude if this happens to you.

Using the System

What if an MCP server is unavailable?

The system is designed with graceful degradation. If a required MCP server (like BigQuery) is missing or disconnected, the command will not fail completely. Instead, it will: 1. Notify you that the server is unavailable. 2. Prompt you to provide the necessary data manually (e.g., by pasting CSV content or providing a URL). 3. Continue the workflow using the provided data.

What's the difference between commands and skills?
  • Commands: These are user-triggered workflows. You explicitly run them by typing / followed by the command name (e.g., /seo-content-audit).
  • Skills: These are auto-activated behaviors. They define how the agent thinks and writes (e.g., core-writing-standards). You don't trigger them manually; the system loads them automatically based on the context of your request.

Commands use skills automatically to ensure the output meets our quality standards.

How long do workflows take?

Workflows are designed to save you hours of manual work, though they do take some time to process: * Content Audit: 30-60 minutes (typically saves 3+ hours) * Search Landscape: 90-120 minutes (typically saves 2+ days) * Content Outline: 45-90 minutes

Technical

Can I use this without MCP servers?

Yes. While MCP servers provide the most seamless experience by automatically fetching data, all commands support manual input fallbacks. You can find more details on connecting data in the Plugin Authoring Guide.

How do I add new commands or skills?

The system uses a modular plugin architecture. New commands and skills are added by creating or modifying division plugins. * Commands live in plugins/divisions/{division}/commands/ * Skills live in plugins/divisions/{division}/skills/

For a step-by-step walkthrough, see the Plugin Authoring Guide.

What platforms are supported?
  • Claude.ai: Chat and Cowork interface. Skills are installed via Customize → Skills (Personal, Shared, or Organization Skills).
  • Claude Code: Plugin marketplace distribution with namespaced commands (e.g., /seo:content-audit).
  • Other platforms: Skills and commands use standard Markdown format and can be adapted for other AI coding assistants. Already using OpenCode? It reads Claude Code plugins natively.

Troubleshooting

Why isn't my command working?

If a command isn't responding as expected, check the following: 1. Directory: Ensure you are running the agent from the root of the agents-infra directory. 2. Plugin Loading: Run /utils:commands to see if your plugin is active. 3. Core Dependencies: Verify that the core-dependencies plugin is present and updated.

For more detailed solutions, visit the Troubleshooting Guide.

Last updated: 2026-01-26