Volcengine AIDAP Database Skill

AIDAP refers to Volcengine's AI 原生 BaaS 平台 Supabase 版 product. This skill manages its deployment-relevant database workspace capabilities and wires them into applications. The stable deploy-facing AIDAP engine choices are supabase and postgresql; resolve current CreateWorkspace EngineType / EngineVersion enums from references/tool-reference.md before creating a workspace. The control plane should use ve aidap directly whenever the action exists. For old-skill data-plane capabilities not exposed by ve, use scripts/supabase_dataplane.py only for Supabase-compatible workspace APIs.

Boundaries

• Supported by ve aidap: workspace, branch, compute, database, DB account, endpoint, API key, ACL, schema diff, start/stop, and deletion operations.
• AIDAP deploy engine choices are supabase and postgresql. Preserve the user's selected engine instead of treating Supabase as an RDS PostgreSQL provider.
• Not covered by current ve CLI: enterprise real-name verification (account_verify/GetVerifyInfo/2018-01-01). Use scripts/aidap_bootstrap.py for that check when needed.
• scripts/aidap_bootstrap.py signs non-public API requests from VOLCENGINE_ACCESS_KEY and VOLCENGINE_SECRET_KEY; it does not reuse ve login cached credentials.
• Not covered by current ve CLI: SQL execution, migration application, Supabase Edge Function management, Supabase Storage bucket management, and TypeScript type generation. Use scripts/supabase_dataplane.py for those old-skill capabilities.
• scripts/supabase_dataplane.py uses ve aidap only to resolve endpoint, default branch, and API keys. The data-plane calls use the Supabase service-role key in apikey and Authorization headers, not Volcengine AK/SK.
• Service activation is a console flow. If the service is not enabled, direct the user to https://console.volcengine.com/iam/service/attach_role/?ServiceName=aidap.

Initial Checks

1. Verify authentication with ve sts GetCallerIdentity.
2. Confirm AIDAP support in the installed CLI: