Update to Geocode AI

{
  "description": "Work inside a Geocode AI organization - tell which organization a key or connection acts in and the caller's role (get_account, list_orgs), who is in it and which teams exist (list_members, list_teams), save a boundary export to the organization's shared file library (save_file), find files teammates saved (list_files, get_file) and share a file with a team or a person at read, write or admin access (share_file, unshare_file, update_file). Use for \"share this boundary with the GIS team\", \"what files has my team saved\", \"who is in our account\", \"which org am I in\", a 403 forbidden; do not use for looking boundaries up (geocode-boundaries), purchases, or inviting and removing people, which a human does on the dashboard.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 288
    }
  ],
  "name": "geocode-teams",
  "skill_md_contents": "---\nname: geocode-teams\ndescription: Work inside a Geocode AI organization - tell which organization a key or connection acts in and the caller's role (get_account, list_orgs), who is in it and which teams exist (list_members, list_teams), save a boundary export to the organization's shared file library (save_file), find files teammates saved (list_files, get_file) and share a file with a team or a person at read, write or admin access (share_file, unshare_file, update_file). Use for \"share this boundary with the GIS team\", \"what files has my team saved\", \"who is in our account\", \"which org am I in\", a 403 forbidden; do not use for looking boundaries up (geocode-boundaries), purchases, or inviting and removing people, which a human does on the dashboard.\n---\n\n# Organizations, teams and the file library\n\nEvery Geocode AI account is an organization. A key, the CLI or a connected\napp acts in one organization: its plan, monthly units, API keys and file\nlibrary are shared by everyone in it. Each person has a role:\n\n| role | can |\n| --- | --- |\n| viewer | read files shared with the whole organization; nothing that costs units |\n| member | use every API op, save files, create teams and their own API keys |\n| admin | also invite and remove people, manage every key and team, billing |\n| owner | also make admins and owners, transfer or delete the organization |\n\nAn API key acts with its creator's role (at most admin) and keeps working if\nthey leave. A solo account is a personal organization with one owner, so for\nmost people nothing changes.\n\n## Where am I\n\n- `get_account`: `org` (id, slug, name, personal), `role`, and the plan and\n  units of that organization.\n- `list_orgs`: every organization the person is in (with a key: just the key's).\n  To act in another, the human approves a new key there (`geocode login`\n  asks which organization) or connects the app again and picks it.\n\n## Handing a boundary to the team\n\n1. Find the boundary as usual (`search_boundaries`, then its id).\n2. `list_files` first: someone may have saved it already; reuse that entry.\n3. `save_file` with `{\"boundary_id\": \"r62422\", \"format\": \"geojson\",\n   \"detail\": \"medium\"}` (1 unit). `visibility: \"org\"` (default) lets every\n   member see it; `\"restricted\"` keeps it to the creator, admins and shares.\n4. `list_teams` for the team's slug, then `share_file` with `{\"id\": \"<file\n   id>\", \"team\": \"gis\", \"access\": \"read\"}` (or `\"user\": \"<email>\"` for one\n   member from `list_members`). Sharing again changes the access.\n5. Give the human the file's `url` (a permanent CDN link) and say who can see it.\n\n`get_file` shows a file's shares when you can manage it; `unshare_file` removes\none by its grant id; `update_file` renames it or changes its visibility.\n\n## When something is refused\n\n- `403 forbidden` carries `required_role` or `required_access`: tell the human\n  which role or share they need and that an admin changes it at\n  `/dashboard/org`. Do not retry with another key.\n- Inviting, removing members, changing roles, teams, transferring or deleting\n  the organization are done by a person on the dashboard (`/dashboard/org`).\n  No tool does them; never try to work around that.\n- `list_invites` and `list_audit_log` are for admins: who was invited, and who\n  changed what (members, roles, keys, billing, shares) and when.\n\nFrom a terminal: `geocode whoami` names the organization and role;\n`geocode orgs`, `geocode members`, `geocode teams`, `geocode files`,\n`geocode save <id>` and `geocode share <file id> --team <slug>`.\n"
}