Update to Lobu

{
  "name": "lobu",
  "description": "Use Lobu for durable, permission-aware workspace context, authorized connected data, governed actions, and human approvals. Trigger when the user asks what their workspace knows, wants to preserve a durable fact or decision, needs to query an authorized source, or asks Lobu to preview or perform an action.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 488
    }
  ],
  "skill_md_contents": "---\nname: lobu\ndescription: Use Lobu for durable, permission-aware workspace context, authorized connected data, governed actions, and human approvals. Trigger when the user asks what their workspace knows, wants to preserve a durable fact or decision, needs to query an authorized source, or asks Lobu to preview or perform an action.\n---\n\n# Lobu\n\nUse Lobu for shared context that must survive one conversation, agent, or local workspace. Treat memory as durable append-only system events; keep temporary reasoning and scratch work outside Lobu.\n\n## Choose the smallest safe tool path\n\n1. Use `search_memory` for existing workspace knowledge.\n2. Use `save_memory` only when the user wants a fact, decision, preference, note, or observation preserved. Search first; supersede stale facts instead of duplicating or overwriting history.\n3. Use `search_sdk` before choosing an SDK method or connector operation. Never guess method names, identifiers, arguments, readiness, or returned URLs.\n4. Use `query_sdk` or `query_sql` for read-only work.\n5. Use `run_sdk` only for requested mutations or connector actions. Prefer `dry_run=true` when it can prove the intended change without executing it.\n\nStay within the identity, workspace, permissions, and connection readiness Lobu returns. Never request or expose connector credentials, and never claim an action completed from a preview or pending run.\n\n## Approvals and rendered actions\n\nWhen Lobu returns a pending approval, use `get_approval` with that exact run ID to render the canonical review card. Do not bypass the card or infer approval. `resolve_approval` may authorize an external or irreversible action, so use it only for the user's explicit approve or reject choice on that exact review card.\n\nUse `invoke_event_action` only for an interaction declared by a rendered Lobu template and initiated by the user. It records the validated interaction as an append-only, idempotent workspace event; it is not a substitute for executing an external connector action.\n\nIf authorization, approval, or device readiness blocks the requested operation, report the exact waiting state and the safe next step.\n"
}