{"id":78752,"plugin_id":"plugin_asdk_app_6a1ea93307208191b5fe82494caf73a8","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T18:19:52.973Z","digest":"f0225c7723f80f431fdf8809b27f2a794d3f3dd37e29ae7c1be5e5a6c83b0cbd","against":null,"payload":{"description":"Identify the authenticated Simplified user and workspace, inspect workspace settings, and discover or resolve accessible teamspaces safely. Use when the user asks \"who am I,\" which Simplified workspace or teamspace is connected, what teamspaces they can access, which timezone or language applies, or asks to work in a named teamspace before using assets, brands, projects, social accounts, drafts, or other workspace-scoped resources.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":253},{"relative_path":"references/teamspace-context.md","size_in_bytes":2901}],"name":"simplified-workspace","skill_md_contents":"---\nname: simplified-workspace\ndescription: Identify the authenticated Simplified user and workspace, inspect workspace settings, and discover or resolve accessible teamspaces safely. Use when the user asks \"who am I,\" which Simplified workspace or teamspace is connected, what teamspaces they can access, which timezone or language applies, or asks to work in a named teamspace before using assets, brands, projects, social accounts, drafts, or other workspace-scoped resources.\n---\n\n# Simplified Workspace\n\nEstablish the correct Simplified identity and workspace context before operating on scoped resources. This operator resolves a teamspace once, then scopes every downstream MCP call explicitly.\n\n## Workflow\n\n1. Call `api_getWorkspaceInfo` for the authenticated user's identity, current workspace, workspace settings, and visible active teamspaces.\n   Its `teamspaces` field is context information, not membership authority.\n2. Call `api_listTeamspaces` to discover the current user's accessible memberships,\n   including all relevant pages. Use `search` for name matching and\n   `expand:\"settings\"` when settings are needed. Return available teamspaces\n   from this membership list, not from `api_getWorkspaceInfo.teamspaces`.\n3. If the user names a teamspace, search with `api_listTeamspaces`. Resolve to one exact numeric ID; do not guess when names or slugs are ambiguous.\n4. If deeper workspace metadata is material, call `api_getWorkspace` with the workspace integer ID returned by `api_getWorkspaceInfo`.\n5. When the user says “use,” “push this to,” “create in,” or “switch to” a teamspace, remember the resolved ID for the current task and pass `space_id: <numeric_id>` on every downstream Simplified tool call.\n6. State the applied context before the downstream workflow: user, workspace, teamspace name and ID, and settings that affect the work.\n7. Follow [references/teamspace-context.md](references/teamspace-context.md) before handing off to another Simplified skill.\n\n## Identity and memory model\n\n- Treat `api_getWorkspaceInfo` as Simplified's authoritative `whoami`; never infer identity from conversation memory.\n- A credential belongs to one workspace. Teamspaces are sub-spaces inside that workspace, not alternate workspaces.\n- Brand kits and their context documents are durable Simplified marketing memory. Workspace identity decides where that memory is read or written; this skill does not replace `manage-brand`.\n- Conversation memory is not proof that a remote workspace, teamspace, account, asset, brand kit, project, or draft still exists or remains accessible. Re-read context when the user changes client, workspace, or teamspace, or before a consequential write when context is uncertain.\n- Workspace timezone, language, and start of week guide planning. For social\n  scheduling, inspect workspace settings and account metadata; the create tool\n  accepts no timezone field. Canonical guidance identifies workspace timezone,\n  but resolve conflicting service/account interpretation before converting a\n  user-specified time. Disclose uncertainty rather than scheduling at an assumed time.\n\n## Teamspace safety\n\n- Teamspace IDs are integers. Never pass a name, slug, alias, or fabricated value where a numeric ID is required.\n- Hosted MCP scoping is stateless: `space_id` applies to one tool call. Carry the same resolved ID into every related read, write, poll, and follow-up call for the current task.\n- It is fine to tell the user “Using Acme East (42)” after resolution, but do not imply the server persisted a global `teamspace:use` session.\n- Do not reuse IDs for accounts, assets, brand kits, projects, items, drafts, or posts across teamspaces without re-listing them in the correctly scoped context.\n- Never omit `space_id` midway through a scoped workflow. An omitted value uses the configured inbound `Space` header or server fallback\n  scope when present, otherwise the credential's default workspace context.\n  It does not reliably preserve the task's explicitly selected teamspace.\n- On `403`, report the denied operation and inspect whether access or permission\n  is missing. On `400`, read the actual validation error: it may concern a\n  payload field rather than teamspace scope. Preserve the selected scope while\n  correcting invalid fields. Never retry against a different space without the\n  user's direction.\n\n## Handoff contract\n\nWhen another skill will continue the work, provide a compact context block:\n\n- authenticated user;\n- workspace name and integer ID;\n- requested teamspace name and integer ID, or `default workspace context`;\n- workspace timezone/language/start-of-week when relevant;\n- the `space_id` that every downstream Simplified call must carry.\n\nDo not treat context resolution as permission to generate credits, edit brand memory, mutate projects, schedule, queue, or publish.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}