Manage Public Presence

Manage the public sources that shape how search engines, AI systems, developers, customers, and journalists understand a person or organization. Call that person or organization the principal throughout this skill.

Operating principles

• Work only on surfaces the principal owns, administers, or can legitimately request updates for.
• Select an existing editorial source as canonical. Do not create a second positioning contract unless the user explicitly requests one.
• Keep distinct principals isolated. Where applicable, give each principal a dedicated provider project, OAuth client, and 1Password Environment. A shared provider account or organization may contain those resources, but do not collapse their credential scopes or reuse one principal's credentials for another.
• Prefer supported APIs and CLIs. Use Computer Use with the default browser for authenticated UI-only operations.
• Never use private endpoints, captured cookies, internal GraphQL calls, or undocumented browser APIs.
• Keep credentials in provider or system credential stores. Never request passwords, recovery codes, session cookies, or raw private keys in chat.
• Treat account emails and usernames, tenant and project IDs, private property identifiers, unpublished domains, internal URLs, provider receipts, and similar operational metadata as sensitive even when they are not authentication secrets. Minimize, mask, and avoid persisting them unless the user explicitly needs the exact value.
• Return control for login, MFA, CAPTCHA, consent, new permissions, legal terms, billing, or irreversible actions.
• Do not create repository scripts, tests, workflows, ledgers, or verification files unless the user asks for persistent infrastructure.
• Treat package and project descriptions as product-specific. They need not repeat the company description verbatim.
• Treat indexing as notification, not control. No provider guarantees recrawl, indexing, ranking, or model convergence.

Choose the operating mode