{"id":"f02dd826-146d-4c44-a09f-0f1db51054ec","entityType":"agent","slug":"clawhub-oomol-oo-supabase","name":"Supabase","canonicalUrl":"https://www.xpersona.co/agent/clawhub-oomol-oo-supabase","canonicalPath":"/agent/clawhub-oomol-oo-supabase","generatedAt":"2026-10-11T20:56:57.769Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T17:29:04.525Z","emptyReason":null},"description":"Supabase (supabase.com). Use this skill for ANY Supabase request — reading, creating, updating, and deleting data. Whenever a task involves Supabase, use this skill instead of calling the API directly.","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-supabase","sourceUrl":"https://clawhub.ai/oomol/oo-supabase","homepage":"https://clawhub.ai/oomol/skills/oo-supabase","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/oomol/oo-supabase","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/oomol/skills/oo-supabase","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":60,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Supabase technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T17:29:04.525Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T17:29:04.525Z","emptyReason":null},"stars":null,"forks":null,"downloads":1018,"packageName":null,"latestVersion":"1.0.6","tractionLabel":"1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T17:29:04.511Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T17:29:04.525Z","lastCrawledAt":"2026-10-11T17:29:04.511Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T17:29:04.511Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.6","createdAt":"2026-09-15T05:48:46.458Z","changelog":"- Operate Supabase through an OOMOL-connected account using the `oo` CLI. - Inspect live action schemas before constructing requests. - Manage projects, organizations, API keys, secrets, Edge Functions, regions, and health checks. - Query databases and generate TypeScript database types. - List, upload, and download Supabase Storage resources. - Apply confirmation safeguards for write and destructive operations. Source: `oomol-lab/skills@75bac03`","fileCount":3,"zipByteSize":3629},{"version":"1.0.4","createdAt":"2026-09-03T08:22:03.892Z","changelog":"- Adds `oo-supabase` as a Supabase skill for working through an OOMOL-connected account. - Uses the `oo` CLI connector to run Supabase actions without handling raw credentials. - Covers core project and organization workflows, including listing, fetching, and health checks. - Supports database access for read-only SQL queries and TypeScript type generation. - Includes storage and edge function operations for inspecting and moving app assets and serverless logic. - Adds key management and secret management actions, with clear read/write/destructive safety tagging. Source: `oomol-lab/skills@d46aad3`","fileCount":3,"zipByteSize":3708},{"version":"1.0.3","createdAt":"2026-08-25T04:48:34.434Z","changelog":"- Added the `oo-supabase` skill for operating Supabase through an OOMOL-connected account. - Uses the `oo` CLI to inspect each action’s live schema before sending a payload, keeping requests aligned with the connector contract. - Supports core Supabase read workflows: listing and fetching organizations, projects, Edge Functions, storage buckets, API keys, secrets, and project health. - Includes read-only SQL execution and TypeScript database type generation for inspection and integration work. - Covers controlled write paths for API keys and secrets, with destructive actions clearly separated and gated by confirmation. - Provides first-time setup guidance for CLI, auth, connection, and billing issues when the connector is not ready. Source: `oomol-lab/skills@3e4b3ff`","fileCount":3,"zipByteSize":3729},{"version":"1.0.2","createdAt":"2026-06-16T09:57:24.026Z","changelog":"- Operates Supabase through the OOMOL `oo` CLI connector with server-side credential injection. - Supports project, organization, member, region, Storage bucket, Edge Function, and health inspection workflows. - Runs read-only SQL queries and generates TypeScript database types. - Manages project API keys, including create, update, list, get, and delete actions. - Manages project secrets with bulk upsert and delete actions, with explicit safety guidance for write and destructive operations. Source: `oomol-lab/skills@4597539`","fileCount":3,"zipByteSize":3565},{"version":"1.0.1","createdAt":"2026-06-09T10:22:13.867Z","changelog":"- Operates Supabase through the OOMOL `supabase` connector using the `oo` CLI, with credentials handled server-side. - Documents the schema-first workflow: inspect each action contract before sending JSON payloads. - Supports project and organization discovery with `list_projects`, `get_project`, and `list_organizations`. - Adds API key management actions for listing, retrieving, and creating Supabase project API keys. - Clarifies safety rules for read, write, and destructive actions, including user confirmation before state changes. Source: `oomol-lab/skills@146ef20`","fileCount":3,"zipByteSize":3208},{"version":"1.0.0","createdAt":"2026-06-03T14:31:56.123Z","changelog":"- Initial 1.0.0 release of the `oo-supabase` skill for operating Supabase through an OOMOL-connected account. - Provides safe project discovery with actions to list organizations, list visible projects, and fetch detailed project metadata. - Adds API key management support for listing project API keys, fetching a single API key record, and creating publishable or secret project keys. - Uses the `oo` CLI Supabase connector with server-side credential injection, so raw Supabase tokens are not handled directly. - Documents action-level schema inspection, JSON execution patterns, required scopes, and safety rules for read, write, and destructive operations.","fileCount":9,"zipByteSize":6620}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-supabase","setupComplexity":"low","setupSteps":["Install using `clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-supabase` in an isolated environment before connecting it to live workloads.","No published capability contract is available yet, so validate auth and request/response behavior manually.","Review the upstream CLAWHUB listing at https://clawhub.ai/oomol/oo-supabase before using production credentials."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-supabase/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-supabase/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-supabase/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-supabase/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-supabase/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-supabase/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T20:56:57.768Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-supabase/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-supabase/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-supabase/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-supabase/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T17:29:04.525Z","emptyReason":null},"readme":"Skill: Supabase\n\nOwner: oomol\n\nSummary: Supabase (supabase.com). Use this skill for ANY Supabase request — reading, creating, updating, and deleting data. Whenever a task involves Supabase, use this skill instead of calling the API directly.\n\nTags: latest:1.0.6\n\nVersion history:\n\nv1.0.6 | 2026-09-15T05:48:46.458Z | user\n\n- Operate Supabase through an OOMOL-connected account using the `oo` CLI.\n- Inspect live action schemas before constructing requests.\n- Manage projects, organizations, API keys, secrets, Edge Functions, regions, and health checks.\n- Query databases and generate TypeScript database types.\n- List, upload, and download Supabase Storage resources.\n- Apply confirmation safeguards for write and destructive operations.\n\nSource: `oomol-lab/skills@75bac03`\n\nv1.0.4 | 2026-09-03T08:22:03.892Z | user\n\n- Adds `oo-supabase` as a Supabase skill for working through an OOMOL-connected account.\n- Uses the `oo` CLI connector to run Supabase actions without handling raw credentials.\n- Covers core project and organization workflows, including listing, fetching, and health checks.\n- Supports database access for read-only SQL queries and TypeScript type generation.\n- Includes storage and edge function operations for inspecting and moving app assets and serverless logic.\n- Adds key management and secret management actions, with clear read/write/destructive safety tagging.\n\nSource: `oomol-lab/skills@d46aad3`\n\nv1.0.3 | 2026-08-25T04:48:34.434Z | user\n\n- Added the `oo-supabase` skill for operating Supabase through an OOMOL-connected account.\n- Uses the `oo` CLI to inspect each action’s live schema before sending a payload, keeping requests aligned with the connector contract.\n- Supports core Supabase read workflows: listing and fetching organizations, projects, Edge Functions, storage buckets, API keys, secrets, and project health.\n- Includes read-only SQL execution and TypeScript database type generation for inspection and integration work.\n- Covers controlled write paths for API keys and secrets, with destructive actions clearly separated and gated by confirmation.\n- Provides first-time setup guidance for CLI, auth, connection, and billing issues when the connector is not ready.\n\nSource: `oomol-lab/skills@3e4b3ff`\n\nv1.0.2 | 2026-06-16T09:57:24.026Z | user\n\n- Operates Supabase through the OOMOL `oo` CLI connector with server-side credential injection.\n- Supports project, organization, member, region, Storage bucket, Edge Function, and health inspection workflows.\n- Runs read-only SQL queries and generates TypeScript database types.\n- Manages project API keys, including create, update, list, get, and delete actions.\n- Manages project secrets with bulk upsert and delete actions, with explicit safety guidance for write and destructive operations.\n\nSource: `oomol-lab/skills@4597539`\n\nv1.0.1 | 2026-06-09T10:22:13.867Z | user\n\n- Operates Supabase through the OOMOL `supabase` connector using the `oo` CLI, with credentials handled server-side.\n- Documents the schema-first workflow: inspect each action contract before sending JSON payloads.\n- Supports project and organization discovery with `list_projects`, `get_project`, and `list_organizations`.\n- Adds API key management actions for listing, retrieving, and creating Supabase project API keys.\n- Clarifies safety rules for read, write, and destructive actions, including user confirmation before state changes.\n\nSource: `oomol-lab/skills@146ef20`\n\nv1.0.0 | 2026-06-03T14:31:56.123Z | user\n\n- Initial 1.0.0 release of the `oo-supabase` skill for operating Supabase through an OOMOL-connected account.\n- Provides safe project discovery with actions to list organizations, list visible projects, and fetch detailed project metadata.\n- Adds API key management support for listing project API keys, fetching a single API key record, and creating publishable or secret project keys.\n- Uses the `oo` CLI Supabase connector with server-side credential injection, so raw Supabase tokens are not handled directly.\n- Documents action-level schema inspection, JSON execution patterns, required scopes, and safety rules for read, write, and destructive operations.\n\nArchive index:\n\nArchive v1.0.6: 3 files, 3629 bytes\n\nFiles: skill-card.md (2003b), SKILL.md (5229b), _meta.json (130b)\n\nFile v1.0.6:SKILL.md\n\n---\nname: oo-supabase\ndescription: \"Supabase (supabase.com). Use this skill for ANY Supabase request — reading, creating, updating, and deleting data. Whenever a task involves Supabase, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Supabase\"\n  author: \"OOMOL\"\n  version: \"1.0.6\"\n  services: [\"supabase\"]\n  icon: \"https://static.oomol.com/logo/third-party/Supabase.svg\"\n---\n\n# Supabase\n\nOperate **Supabase** through your OOMOL-connected account. This skill calls the `supabase` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Supabase. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"supabase\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"supabase\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `create_project_api_key` — Create a publishable or secret API key for a Supabase project. [write]\n- `delete_project_api_key` — Delete a Supabase project API key. [destructive]\n- `delete_project_secrets` — Bulk delete secrets from a Supabase project. [destructive]\n- `download_storage_object` — Download a private Supabase Storage object to connector transit storage.\n- `generate_typescript_types` — Generate TypeScript database types for a Supabase project.\n- `get_edge_function` — Get metadata for one Supabase Edge Function by slug.\n- `get_organization` — Get details for a Supabase organization by slug.\n- `get_project` — Get detailed metadata for a Supabase project by project ref.\n- `get_project_api_key` — Get one API key record from a Supabase project.\n- `get_project_health` — Check health for selected services in a Supabase project.\n- `list_available_regions` — List Supabase regions available for creating projects in an organization.\n- `list_edge_functions` — List Edge Functions in a Supabase project.\n- `list_organization_members` — List members of a Supabase organization.\n- `list_organization_projects` — List projects in a Supabase organization with optional search and pagination.\n- `list_organizations` — List the organizations available to the authenticated Supabase account.\n- `list_project_api_keys` — List API keys for a Supabase project.\n- `list_project_secrets` — List secrets configured for a Supabase project.\n- `list_projects` — List Supabase projects visible to the authenticated account.\n- `list_storage_buckets` — List Storage buckets for a Supabase project.\n- `run_read_only_query` — Run a SQL query through Supabase as the read-only database user.\n- `update_project_api_key` — Update the name, description, or JWT template for a Supabase project API key. [write]\n- `upload_storage_object` — Upload an object from a public URL to Supabase Storage. [write]\n- `upsert_project_secrets` — Bulk create or update secrets for a Supabase project. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Supabase state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):\n\n  ```bash\n  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux\n  ```\n\n  ```powershell\n  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell\n  ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n  ```bash\n  oo auth login\n  ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Supabase is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2, API key) at:\n\n  ```text\n  https://console.oomol.com/app-connections?provider=supabase\n  ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Supabase homepage: https://supabase.com\n\nFile v1.0.6:_meta.json\n\n{\n  \"ownerId\": \"kn750e6wt5q1rjhbw2ej5vsmyd87z8vj\",\n  \"slug\": \"oo-supabase\",\n  \"version\": \"1.0.6\",\n  \"publishedAt\": 1789451326458\n}\n\nFile v1.0.6:skill-card.md\n\n## Description:\n\nSupabase (supabase.com). Use this skill for ANY Supabase request - reading, creating, updating, and deleting data.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and operators use this skill to manage Supabase projects through an OOMOL-connected account, including projects, organizations, API keys, secrets, Edge Functions, regions, health checks, database queries, generated TypeScript types, and storage resources.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Setup instructions include pipe-to-shell installer commands.\n\nMitigation: Review the installer before use or prefer a verified package-managed oo CLI installation.\n\nRisk: The skill can perform sensitive Supabase administration actions, including API key, secret, storage, and project changes.\n\nMitigation: Confirm the exact project, key, secret, storage object, payload, and expected effect before approving write or destructive actions.\n\n## Reference(s):\n\n- [ClawHub Supabase Skill](https://clawhub.ai/oomol/skills/oo-supabase)\n- [OOMOL oo CLI](https://github.com/oomol-lab/oo-cli)\n- [Supabase](https://supabase.com)\n\n## Skill Output:\n\n**Output Type(s):** [Shell commands, Configuration, Code, Guidance]\n\n**Output Format:** [Markdown with inline shell commands and JSON payloads]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Produces oo CLI commands that inspect live action schemas and run Supabase connector actions; write and destructive actions require explicit user confirmation.]\n\n## Skill Version(s):\n\n1.0.6 (source: artifact frontmatter and release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.4: 3 files, 3708 bytes\n\nFiles: skill-card.md (2194b), SKILL.md (5229b), _meta.json (130b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: oo-supabase\ndescription: \"Supabase (supabase.com). Use this skill for ANY Supabase request — reading, creating, updating, and deleting data. Whenever a task involves Supabase, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Supabase\"\n  author: \"OOMOL\"\n  version: \"1.0.4\"\n  services: [\"supabase\"]\n  icon: \"https://static.oomol.com/logo/third-party/Supabase.svg\"\n---\n\n# Supabase\n\nOperate **Supabase** through your OOMOL-connected account. This skill calls the `supabase` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Supabase. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"supabase\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"supabase\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `create_project_api_key` — Create a publishable or secret API key for a Supabase project. [write]\n- `delete_project_api_key` — Delete a Supabase project API key. [destructive]\n- `delete_project_secrets` — Bulk delete secrets from a Supabase project. [destructive]\n- `download_storage_object` — Download a private Supabase Storage object to connector transit storage.\n- `generate_typescript_types` — Generate TypeScript database types for a Supabase project.\n- `get_edge_function` — Get metadata for one Supabase Edge Function by slug.\n- `get_organization` — Get details for a Supabase organization by slug.\n- `get_project` — Get detailed metadata for a Supabase project by project ref.\n- `get_project_api_key` — Get one API key record from a Supabase project.\n- `get_project_health` — Check health for selected services in a Supabase project.\n- `list_available_regions` — List Supabase regions available for creating projects in an organization.\n- `list_edge_functions` — List Edge Functions in a Supabase project.\n- `list_organization_members` — List members of a Supabase organization.\n- `list_organization_projects` — List projects in a Supabase organization with optional search and pagination.\n- `list_organizations` — List the organizations available to the authenticated Supabase account.\n- `list_project_api_keys` — List API keys for a Supabase project.\n- `list_project_secrets` — List secrets configured for a Supabase project.\n- `list_projects` — List Supabase projects visible to the authenticated account.\n- `list_storage_buckets` — List Storage buckets for a Supabase project.\n- `run_read_only_query` — Run a SQL query through Supabase as the read-only database user.\n- `update_project_api_key` — Update the name, description, or JWT template for a Supabase project API key. [write]\n- `upload_storage_object` — Upload an object from a public URL to Supabase Storage. [write]\n- `upsert_project_secrets` — Bulk create or update secrets for a Supabase project. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Supabase state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):\n\n  ```bash\n  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux\n  ```\n\n  ```powershell\n  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell\n  ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n  ```bash\n  oo auth login\n  ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Supabase is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2, API key) at:\n\n  ```text\n  https://console.oomol.com/app-connections?provider=supabase\n  ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Supabase homepage: https://supabase.com\n\nFile v1.0.4:_meta.json\n\n{\n  \"ownerId\": \"kn750e6wt5q1rjhbw2ej5vsmyd87z8vj\",\n  \"slug\": \"oo-supabase\",\n  \"version\": \"1.0.4\",\n  \"publishedAt\": 1788423723892\n}\n\nFile v1.0.4:skill-card.md\n\n## Description:\n\nEnables agents to operate Supabase projects through OOMOL's oo CLI connector for account, project, database, storage, Edge Function, API key, and secret workflows.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and operators use this skill to inspect and manage Supabase organizations, projects, database access, storage objects, Edge Functions, API keys, and secrets through an OOMOL-connected account.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The first-time setup includes installer pipe commands for the oo CLI.\n\nMitigation: Install the oo CLI manually from a trusted source and verify it before allowing an agent to use the connector.\n\nRisk: The skill can operate on sensitive Supabase resources, including API keys, secrets, storage objects, and project data.\n\nMitigation: Grant connector access only for trusted OOMOL accounts and review requested scopes and targets before use.\n\nRisk: Write and destructive actions can modify or remove Supabase state.\n\nMitigation: Require explicit user confirmation for each write or destructive action, including the exact payload and expected effect.\n\n## Reference(s):\n\n- [ClawHub Skill Page](https://clawhub.ai/oomol/skills/oo-supabase)\n- [Supabase Homepage](https://supabase.com)\n- [oo CLI](https://github.com/oomol-lab/oo-cli)\n- [oo CLI Install Guide](https://cli.oomol.com/install-guide.md)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Code, Shell commands, Configuration, Guidance]\n\n**Output Format:** [Markdown with inline shell commands and JSON payload examples]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Uses live connector schemas before constructing action payloads.]\n\n## Skill Version(s):\n\n1.0.4 (source: server release evidence and skill metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.3: 3 files, 3729 bytes\n\nFiles: skill-card.md (2350b), SKILL.md (5135b), _meta.json (130b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: oo-supabase\ndescription: \"Supabase (supabase.com). Use this skill for ANY Supabase request — reading, creating, updating, and deleting data. Whenever a task involves Supabase, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Supabase\"\n  author: \"OOMOL\"\n  version: \"1.0.3\"\n  services: [\"supabase\"]\n  icon: \"https://static.oomol.com/logo/third-party/Supabase.svg\"\n---\n\n# Supabase\n\nOperate **Supabase** through your OOMOL-connected account. This skill calls the `supabase` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Supabase. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"supabase\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"supabase\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `create_project_api_key` — Create a publishable or secret API key for a Supabase project. [write]\n- `delete_project_api_key` — Delete a Supabase project API key. [destructive]\n- `delete_project_secrets` — Bulk delete secrets from a Supabase project. [destructive]\n- `download_storage_object` — Download a private Supabase Storage object to connector transit storage.\n- `generate_typescript_types` — Generate TypeScript database types for a Supabase project.\n- `get_edge_function` — Get metadata for one Supabase Edge Function by slug.\n- `get_organization` — Get details for a Supabase organization by slug.\n- `get_project` — Get detailed metadata for a Supabase project by project ref.\n- `get_project_api_key` — Get one API key record from a Supabase project.\n- `get_project_health` — Check health for selected services in a Supabase project.\n- `list_available_regions` — List Supabase regions available for creating projects in an organization.\n- `list_edge_functions` — List Edge Functions in a Supabase project.\n- `list_organization_members` — List members of a Supabase organization.\n- `list_organization_projects` — List projects in a Supabase organization with optional search and pagination.\n- `list_organizations` — List the organizations available to the authenticated Supabase account.\n- `list_project_api_keys` — List API keys for a Supabase project.\n- `list_project_secrets` — List secrets configured for a Supabase project.\n- `list_projects` — List Supabase projects visible to the authenticated account.\n- `list_storage_buckets` — List Storage buckets for a Supabase project.\n- `run_read_only_query` — Run a SQL query through Supabase as the read-only database user.\n- `update_project_api_key` — Update the name, description, or JWT template for a Supabase project API key. [write]\n- `upsert_project_secrets` — Bulk create or update secrets for a Supabase project. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Supabase state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):\n\n  ```bash\n  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux\n  ```\n\n  ```powershell\n  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell\n  ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n  ```bash\n  oo auth login\n  ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Supabase is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2, API key) at:\n\n  ```text\n  https://console.oomol.com/app-connections?provider=supabase\n  ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Supabase homepage: https://supabase.com\n\nFile v1.0.3:_meta.json\n\n{\n  \"ownerId\": \"kn750e6wt5q1rjhbw2ej5vsmyd87z8vj\",\n  \"slug\": \"oo-supabase\",\n  \"version\": \"1.0.3\",\n  \"publishedAt\": 1787633314434\n}\n\nFile v1.0.3:skill-card.md\n\n## Description:\n\nOperate Supabase through an OOMOL-connected account for reading, creating, updating, and deleting Supabase resources by using the oo CLI connector.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and operators use this skill to inspect and administer Supabase organizations, projects, Edge Functions, storage buckets, API keys, secrets, health checks, read-only SQL queries, and generated TypeScript database types through an OOMOL-connected account.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill can operate with administrative visibility into connected Supabase projects through OOMOL.\n\nMitigation: Install it only for accounts and projects where OOMOL-mediated access is acceptable, and avoid connecting projects that the agent should not administer.\n\nRisk: API key, secret, and deletion actions can change or remove Supabase resources.\n\nMitigation: Review the exact payload and effect before approving write actions, and require explicit approval before destructive actions.\n\nRisk: Connector action schemas may change over time.\n\nMitigation: Inspect the live connector schema before constructing each payload so requests match the current connector contract.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/oomol/skills/oo-supabase)\n- [Supabase homepage](https://supabase.com)\n- [oo CLI](https://github.com/oomol-lab/oo-cli)\n- [oo CLI install guide](https://cli.oomol.com/install-guide.md)\n\n## Skill Output:\n\n**Output Type(s):** [text, code, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown with inline shell commands, JSON payloads, connector responses, and generated TypeScript types when requested]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Uses live connector schemas before sending action payloads; responses may include connector execution metadata.]\n\n## Skill Version(s):\n\n1.0.3 (source: server evidence and frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.2: 3 files, 3565 bytes\n\nFiles: skill-card.md (2077b), SKILL.md (5030b), _meta.json (130b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: oo-supabase\ndescription: \"Supabase (supabase.com). Use this skill for ANY Supabase request — reading, creating, updating, and deleting data. Whenever a task involves Supabase, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Supabase\"\n  author: \"OOMOL\"\n  version: \"1.0.2\"\n  services: [\"supabase\"]\n  icon: \"https://static.oomol.com/logo/third-party/Supabase.svg\"\n---\n\n# Supabase\n\nOperate **Supabase** through your OOMOL-connected account. This skill calls the `supabase` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Supabase. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"supabase\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"supabase\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `create_project_api_key` — Create a publishable or secret API key for a Supabase project. [write]\n- `delete_project_api_key` — Delete a Supabase project API key. [destructive]\n- `delete_project_secrets` — Bulk delete secrets from a Supabase project. [destructive]\n- `generate_typescript_types` — Generate TypeScript database types for a Supabase project.\n- `get_edge_function` — Get metadata for one Supabase Edge Function by slug.\n- `get_organization` — Get details for a Supabase organization by slug.\n- `get_project` — Get detailed metadata for a Supabase project by project ref.\n- `get_project_api_key` — Get one API key record from a Supabase project.\n- `get_project_health` — Check health for selected services in a Supabase project.\n- `list_available_regions` — List Supabase regions available for creating projects in an organization.\n- `list_edge_functions` — List Edge Functions in a Supabase project.\n- `list_organization_members` — List members of a Supabase organization.\n- `list_organization_projects` — List projects in a Supabase organization with optional search and pagination.\n- `list_organizations` — List the organizations available to the authenticated Supabase account.\n- `list_project_api_keys` — List API keys for a Supabase project.\n- `list_project_secrets` — List secrets configured for a Supabase project.\n- `list_projects` — List Supabase projects visible to the authenticated account.\n- `list_storage_buckets` — List Storage buckets for a Supabase project.\n- `run_read_only_query` — Run a SQL query through Supabase as the read-only database user.\n- `update_project_api_key` — Update the name, description, or JWT template for a Supabase project API key. [write]\n- `upsert_project_secrets` — Bulk create or update secrets for a Supabase project. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Supabase state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):\n\n  ```bash\n  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux\n  ```\n\n  ```powershell\n  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell\n  ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n  ```bash\n  oo auth login\n  ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Supabase is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2, API key) at:\n\n  ```text\n  https://console.oomol.com/app-connections?provider=supabase\n  ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Supabase homepage: https://supabase.com\n\nFile v1.0.2:_meta.json\n\n{\n  \"ownerId\": \"kn750e6wt5q1rjhbw2ej5vsmyd87z8vj\",\n  \"slug\": \"oo-supabase\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1781603844026\n}\n\nFile v1.0.2:skill-card.md\n\n## Description: <br>\nOperate Supabase through the OOMOL oo CLI connector for reading, creating, updating, and deleting Supabase resources. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[oomol](https://clawhub.ai/user/oomol) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and operators use this skill to inspect and manage Supabase projects, organizations, storage buckets, Edge Functions, API keys, secrets, health, SQL queries, and TypeScript database types through a connected OOMOL account. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill requires connecting a Supabase account to OOMOL and allowing an agent to operate that account through the oo CLI. <br>\nMitigation: Install only when that account connection and delegated operation model are acceptable for the workspace. <br>\nRisk: Write and destructive actions can change Supabase resources, API keys, or secrets. <br>\nMitigation: Review the exact payload and intended effect, and require explicit approval before API key, secret, project, delete, or update actions. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/oomol/oo-supabase) <br>\n- [oo CLI](https://github.com/oomol-lab/oo-cli) <br>\n- [Supabase homepage](https://supabase.com) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance] <br>\n**Output Format:** [Markdown with inline shell commands and JSON payload guidance] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Connector command responses may include JSON data and execution metadata.] <br>\n\n## Skill Version(s): <br>\n1.0.2 (source: server release evidence and skill frontmatter) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.1: 3 files, 3208 bytes\n\nFiles: skill-card.md (2134b), SKILL.md (3701b), _meta.json (130b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: oo-supabase\ndescription: \"Supabase (supabase.com). Use this skill for ANY Supabase request — reading, creating, and updating data. Whenever a task involves Supabase, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Supabase\"\n  author: \"OOMOL\"\n  version: \"1.0.1\"\n  services: [\"supabase\"]\n  icon: \"https://static.oomol.com/logo/third-party/Supabase.svg\"\n---\n\n# Supabase\n\nOperate **Supabase** through your OOMOL-connected account. This skill calls the `supabase` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Supabase. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"supabase\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"supabase\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `create_project_api_key` — Create a publishable or secret API key for a Supabase project. [write]\n- `get_project` — Get detailed metadata for a Supabase project by project ref.\n- `get_project_api_key` — Get one API key record from a Supabase project.\n- `list_organizations` — List the organizations available to the authenticated Supabase account.\n- `list_project_api_keys` — List API keys for a Supabase project.\n- `list_projects` — List Supabase projects visible to the authenticated account.\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Supabase state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):\n\n  ```bash\n  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux\n  ```\n\n  ```powershell\n  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell\n  ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n  ```bash\n  oo auth login\n  ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Supabase is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2, API key) at:\n\n  ```text\n  https://console.oomol.com/app-connections?provider=supabase\n  ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Supabase homepage: https://supabase.com\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn750e6wt5q1rjhbw2ej5vsmyd87z8vj\",\n  \"slug\": \"oo-supabase\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1781000533867\n}\n\nFile v1.0.1:skill-card.md\n\n## Description: <br>\nSupabase (supabase.com). Use this skill for ANY Supabase request - reading, creating, and updating data. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[oomol](https://clawhub.ai/user/oomol) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and agents use this skill to operate Supabase through an OOMOL-connected account, including project and organization discovery and API key management. It guides the agent to inspect live action schemas before running connector actions. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill can use connected Supabase credentials and create project API keys. <br>\nMitigation: Install only for trusted workflows, use least-privilege Supabase access, and confirm write payloads and effects before running API key creation. <br>\nRisk: Connector action inputs may change because the skill relies on live Supabase connector schemas. <br>\nMitigation: Inspect the current action schema before constructing each JSON payload and retry setup only after an authentication or connection error. <br>\n\n\n## Reference(s): <br>\n- [Supabase homepage](https://supabase.com) <br>\n- [oo CLI](https://github.com/oomol-lab/oo-cli) <br>\n- [ClawHub skill page](https://clawhub.ai/oomol/oo-supabase) <br>\n- [OOMOL publisher profile](https://clawhub.ai/user/oomol) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance] <br>\n**Output Format:** [Markdown with inline shell commands and JSON payload guidance] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Uses live connector schemas before constructing action payloads.] <br>\n\n## Skill Version(s): <br>\n1.0.1 (source: frontmatter and server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.0: 9 files, 6620 bytes\n\nFiles: actions/create_project_api_key.md (851b), actions/get_project_api_key.md (694b), actions/get_project.md (668b), actions/list_organizations.md (719b), actions/list_project_api_keys.md (694b), actions/list_projects.md (678b), skill-card.md (2357b), SKILL.md (3973b), _meta.json (130b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: oo-supabase\ndescription: \"Supabase (supabase.com). Use this skill for ANY Supabase request — reading, creating, and updating data. Whenever a task involves Supabase, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Supabase\"\n  author: \"OOMOL\"\n  version: \"1.0.0\"\n  service: \"supabase\"\n  categories: \"Developer Tools, Data & Analytics, Storage\"\n  homepage: \"https://supabase.com\"\n  icon: \"https://static.oomol.com/logo/third-party/Supabase.svg\"\n---\n\n# Supabase\n\nOperate **Supabase** through your OOMOL-connected account. This skill calls the `supabase` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\nCategory: Developer Tools, Data & Analytics, Storage. Exposes 6 action(s).\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Supabase. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"supabase\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"supabase\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with `oo connector schema` before constructing `--data`.\n\n## Available actions\n\n- [`create_project_api_key`](actions/create_project_api_key.md) — Create a publishable or secret API key for a Supabase project.\n- [`get_project`](actions/get_project.md) — Get detailed metadata for a Supabase project by project ref.\n- [`get_project_api_key`](actions/get_project_api_key.md) — Get one API key record from a Supabase project.\n- [`list_organizations`](actions/list_organizations.md) — List the organizations available to the authenticated Supabase account.\n- [`list_project_api_keys`](actions/list_project_api_keys.md) — List API keys for a Supabase project.\n- [`list_projects`](actions/list_projects.md) — List Supabase projects visible to the authenticated account.\n\n## Safety\n\n- Read actions (get / list / search) are safe to run directly.\n- **Create, update, send, or post actions change Supabase state — confirm the exact payload and effect with the user before running.**\n- **Delete or remove actions are destructive — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):\n\n  ```bash\n  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux\n  ```\n\n  ```powershell\n  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell\n  ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n  ```bash\n  oo auth login\n  ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Supabase is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2, API key) at:\n\n  ```text\n  https://console.oomol.com/app-connections?provider=supabase\n  ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Supabase homepage: https://supabase.com\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn750e6wt5q1rjhbw2ej5vsmyd87z8vj\",\n  \"slug\": \"oo-supabase\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1780497116123\n}\n\nFile v1.0.0:actions/create_project_api_key.md\n\n# Supabase · `create_project_api_key`\n\nCreate a publishable or secret API key for a Supabase project.\n\n- **Service**: `supabase`\n- **Action**: `create_project_api_key`\n- **Action id**: `supabase.create_project_api_key`\n- **Required scopes**: supabase.secrets.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"supabase\" --action \"create_project_api_key\"\n```\n\n## Run\n\n```bash\noo connector run \"supabase\" --action \"create_project_api_key\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Supabase state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.0:actions/get_project_api_key.md\n\n# Supabase · `get_project_api_key`\n\nGet one API key record from a Supabase project.\n\n- **Service**: `supabase`\n- **Action**: `get_project_api_key`\n- **Action id**: `supabase.get_project_api_key`\n- **Required scopes**: supabase.secrets.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"supabase\" --action \"get_project_api_key\"\n```\n\n## Run\n\n```bash\noo connector run \"supabase\" --action \"get_project_api_key\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/get_project.md\n\n# Supabase · `get_project`\n\nGet detailed metadata for a Supabase project by project ref.\n\n- **Service**: `supabase`\n- **Action**: `get_project`\n- **Action id**: `supabase.get_project`\n- **Required scopes**: supabase.projects.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"supabase\" --action \"get_project\"\n```\n\n## Run\n\n```bash\noo connector run \"supabase\" --action \"get_project\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/list_organizations.md\n\n# Supabase · `list_organizations`\n\nList the organizations available to the authenticated Supabase account.\n\n- **Service**: `supabase`\n- **Action**: `list_organizations`\n- **Action id**: `supabase.list_organizations`\n- **Required scopes**: supabase.organizations.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"supabase\" --action \"list_organizations\"\n```\n\n## Run\n\n```bash\noo connector run \"supabase\" --action \"list_organizations\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/list_project_api_keys.md\n\n# Supabase · `list_project_api_keys`\n\nList API keys for a Supabase project.\n\n- **Service**: `supabase`\n- **Action**: `list_project_api_keys`\n- **Action id**: `supabase.list_project_api_keys`\n- **Required scopes**: supabase.secrets.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"supabase\" --action \"list_project_api_keys\"\n```\n\n## Run\n\n```bash\noo connector run \"supabase\" --action \"list_project_api_keys\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/list_projects.md\n\n# Supabase · `list_projects`\n\nList Supabase projects visible to the authenticated account.\n\n- **Service**: `supabase`\n- **Action**: `list_projects`\n- **Action id**: `supabase.list_projects`\n- **Required scopes**: supabase.projects.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"supabase\" --action \"list_projects\"\n```\n\n## Run\n\n```bash\noo connector run \"supabase\" --action \"list_projects\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:skill-card.md\n\n## Description: <br>\nOperate Supabase through an OOMOL-connected account for project discovery, project metadata lookup, and project API key management. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[oomol](https://clawhub.ai/user/oomol) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and operators use this skill to inspect Supabase organizations and projects, fetch project metadata, and list, retrieve, or create project API keys through the oo CLI connector. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill can retrieve and create Supabase project API keys. <br>\nMitigation: Confirm the exact project, key type, and need before API-key actions, and avoid printing or storing returned keys in transcripts or logs. <br>\nRisk: The oo CLI installer is presented as a pipe-to-shell command for first-time setup. <br>\nMitigation: Inspect or verify the installer before running it, and only install the CLI when the command actually fails because oo is unavailable. <br>\nRisk: Write actions can change Supabase state. <br>\nMitigation: Confirm the exact payload and intended effect with the user before running create, update, send, or post actions. <br>\n\n\n## Reference(s): <br>\n- [ClawHub Skill Page](https://clawhub.ai/oomol/oo-supabase) <br>\n- [Publisher Profile](https://clawhub.ai/user/oomol) <br>\n- [Supabase Homepage](https://supabase.com) <br>\n- [oo CLI](https://github.com/oomol-lab/oo-cli) <br>\n- [oo CLI Install Guide](https://cli.oomol.com/install-guide.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance] <br>\n**Output Format:** [Markdown guidance with oo CLI shell commands and JSON connector responses] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Connector responses include a data payload and meta.executionId when actions run with --json.] <br>\n\n## Skill Version(s): <br>\n1.0.0 (source: server release metadata and skill frontmatter) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>","readmeExcerpt":"Skill: Supabase Owner: oomol Summary: Supabase (supabase.com). Use this skill for ANY Supabase request — reading, creating, updating, and deleting data. Whenever a task involves Supabase, use this skill instead of calling the API directly. Tags: latest:1.0.6 Version history: v1.0.6 | 2026-09-15T05:48:46.458Z | user - Operate Supabase through an OOMOL-connected account using the oo CLI. - Inspect live action schemas b","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"oo connector schema \"supabase\" --action \"<action_name>\""},{"language":"bash","snippet":"oo connector run \"supabase\" --action \"<action_name>\" --data '<json>' --json"},{"language":"bash","snippet":"curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux"},{"language":"bash","snippet":"curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux"},{"language":"powershell","snippet":"irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell"},{"language":"bash","snippet":"oo auth login"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: oo-supabase\ndescription: \"Supabase (supabase.com). Use this skill for ANY Supabase request — reading, creating, updating, and deleting data. Whenever a task involves Supabase, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Supabase\"\n  author: \"OOMOL\"\n  version: \"1.0.6\"\n  services: [\"supabase\"]\n  icon: \"https://static.oomol.com/logo/third-party/Supabase.svg\"\n---\n\n# Supabase\n\nOperate **Supabase** through your OOMOL-connected account. This skill calls the `supabase` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Supabase. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"supabase\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"supabase\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `create_project_api_key` — Create a publishable or secret API key for a Supabase project. [write]\n- `delete_project_api_key` — Delete a Supabase project API key. [destructive]\n- `delete_project_secrets` — Bulk delete secrets from a Supabase project. [destructive]\n- `download_storage_object` — Download a private Supabase Storage object to connector transit storage.\n- `generate_typescript_types` — Generate TypeScript database types for a Supabase project.\n- `get_edge_function` — Get metadata for one Supabase Edge Function by slug.\n- `get_organization` — Get details for a Supabase organization by slug.\n- `get_project` — Get detailed metadata for a Supabase project by project ref.\n- `get_project_api_key` — Get one API key record from a Supabase project.\n- `get_project_health` — Check health for selected services in a Supabase project.\n- `list_available_regions` — List Supabase regions available for creating projects in an organization.\n- `list_edge_functions` — List Edge Functions in a Supabase project.\n- `list_organization_members` — List members of a Supabase organization.\n- `list_organization_projects` — List projects in a Supabase organization with optional search and pagina"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn750e6wt5q1rjhbw2ej5vsmyd87z8vj\",\n  \"slug\": \"oo-supabase\",\n  \"version\": \"1.0.6\",\n  \"publishedAt\": 1789451326458\n}"},{"path":"skill-card.md","content":"## Description:\n\nSupabase (supabase.com). Use this skill for ANY Supabase request - reading, creating, updating, and deleting data.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and operators use this skill to manage Supabase projects through an OOMOL-connected account, including projects, organizations, API keys, secrets, Edge Functions, regions, health checks, database queries, generated TypeScript types, and storage resources.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Setup instructions include pipe-to-shell installer commands.\n\nMitigation: Review the installer before use or prefer a verified package-managed oo CLI installation.\n\nRisk: The skill can perform sensitive Supabase administration actions, including API key, secret, storage, and project changes.\n\nMitigation: Confirm the exact project, key, secret, storage object, payload, and expected effect before approving write or destructive actions.\n\n## Reference(s):\n\n- [ClawHub Supabase Skill](https://clawhub.ai/oomol/skills/oo-supabase)\n- [OOMOL oo CLI](https://github.com/oomol-lab/oo-cli)\n- [Supabase](https://supabase.com)\n\n## Skill Output:\n\n**Output Type(s):** [Shell commands, Configuration, Code, Guidance]\n\n**Output Format:** [Markdown with inline shell commands and JSON payloads]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Produces oo CLI commands that inspect live action schemas and run Supabase connector actions; write and destructive actions require explicit user confirmation.]\n\n## Skill Version(s):\n\n1.0.6 (source: artifact frontmatter and release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":1501,"uniquenessScore":39,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T17:29:04.525Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T17:29:04.525Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T20:56:57.769Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}