Update to Marketing Swarm

{
  "description": "Use when a Marketing Swarm workflow needs to inspect, search, modify, or verify files in the host workspace using the safest native tools available.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 285
    }
  ],
  "name": "host-workspace-operator",
  "skill_md_contents": "---\nname: host-workspace-operator\ndescription: Use when a Marketing Swarm workflow needs to inspect, search, modify, or verify files in the host workspace using the safest native tools available.\n---\n\n# Host Workspace Operator\n\nUse workspace tools supplied by the current ChatGPT/Codex host instead of pretending the Plugin owns a filesystem API.\n\nTool names differ by surface. Route by capability, not by a hard-coded tool name. Typical capabilities include read, list, search, grep, write, patch, shell, and python.\n\n## Capability order\n\nPrefer the narrowest operation that can answer the task:\n\n1. **read**: open a known file or exact range when the path is known.\n2. **list**: enumerate a directory or workspace scope when filenames are unknown.\n3. **search**: use semantic/content search when the user asks a broad question or exact wording is uncertain.\n4. **grep**: use exact text or regex search when the term, symbol, field, or pattern is known.\n5. **patch**: make a focused edit to an existing file when a patch-capable host tool exists.\n6. **write**: create or replace a file only when the requested workflow requires a mutation.\n7. **shell**: run repository commands when file tools are insufficient and command execution is appropriate.\n8. **python**: use host-native Python for deterministic parsing, transformations, hashing, package inspection, or verification.\n\nDo not use shell or Python just to imitate a safer read/search/file operation that the host already provides.\n\n## Read-only first\n\nTreat read, list, search, and grep as the default discovery phase. Inspect enough evidence to understand the current state before mutation.\n\nFor campaign-export or report work:\n\n- inspect the file shape before transforming it\n- preserve original files unless the user requested an edit\n- prefer exact reads after search locates the relevant material\n- distinguish raw source data from generated analysis artifacts\n\n## Mutation boundary\n\nWrite, patch, delete, move, rename, format, or command-based modification are mutation operations.\n\nBefore mutation:\n\n- confirm the user requested or clearly authorized the change\n- preserve unrelated work\n- prefer a focused patch over full-file replacement\n- never write secrets into reports, examples, manifests, or release artifacts\n\nAfter mutation, read the changed area back when practical, run the relevant verifier when available, and report the exact files changed.\n\n## If a tool is unavailable\n\nDo not invent a replacement tool name, claim an operation occurred, or imply the Plugin grants filesystem permissions. Use another available capability only when it preserves the task semantics; otherwise mark the dependent result unverified.\n"
}