Update to Centralize

{
  "description": "Set up supported account maps, buyer personas, and account views in the connected Centralize workspace. Use for a requested prospect workspace setup after the intended workspace is established.",
  "included_files": [],
  "name": "centralize-prospect-workspace-setup",
  "skill_md_contents": "---\nname: centralize-prospect-workspace-setup\ndescription: 'Set up supported account maps, buyer personas, and account views in the connected Centralize workspace. Use for a requested prospect workspace setup after the intended workspace is established.'\n---\n\n# Set up the connected workspace\n\nRead [workspace and write boundaries](../../references/workspace-safety.md) first.\nThis workflow adapts Hunter's prospect setup to the operations available through this plugin.\nIt cannot administer another workspace or complete browser-only settings.\n\n## Establish the requested setup\n\nCall `whoami` and compare the returned workspace with the user's intended workspace.\nIf they differ, stop before writes. Ask the user to connect the intended workspace.\nDo not assume that the connector belongs to Centralize's internal sales workspace or to the prospect.\n\nAsk only for missing account names and domains, target buyers, and requested saved account views.\nRead existing accounts and account context before proposing additions.\nShow the setup plan and its effects before confirmation. Account creation can activate accounts, consume capacity, and start background work.\nKeep account activation, deep research, notifications, and workspace-wide defaults outside the plan unless specifically requested.\n\n## Apply supported steps\n\n1. For an approved new account, call `addAccounts` with the confirmed name and domain. Inspect results before dependent steps.\n2. For buyer definitions, use [the persona workflow](../centralize-persona-functions-creation/SKILL.md). Reuse definitions before creation.\n3. For each requested account map, use [the chart workflow](../centralize-org-chart/SKILL.md). Confirm proposed changes before writes.\n4. For a requested saved accounts list, use `createAccountView` with filters supported by its current schema.\n\nEach saved view must match the requested owner and sharing scope. Use a resolved owner rather than a viewer-relative filter for a named person's view.\nDo not guess user identifiers. If the available tools cannot resolve a required owner or sharing setting, report that limitation before creation.\nDo not activate an existing account merely because it is absent from a search result.\n\n## Report remaining setup\n\nThe plugin does not support workspace switching, edits to existing functions or personas, default stakeholder filters, or account starring.\nIt also cannot create saved views for Home, Contacts, Connections, Opportunities, or Job Changes through `createAccountView`.\nDo not replace these missing operations with browser automation or another connector.\nGive the user a concise list of remaining settings to complete in Centralize.\n\nRead back accounts and charts with the available read tools. Use a returned view link to report successful view creation.\nDo not claim an unverified default, sharing setting, or saved view is complete.\nReport completed steps, failed steps, user-approved inferences, and remaining setup separately.\n"
}