aliyun-rds-supabase
Use when managing Alibaba Cloud RDS Supabase (RDS AI Service 2025-05-07) via OpenAPI, including creating, starting/stopping/restarting instances, resetting passwords, querying endpoints/auth/storage, configuring auth/RAG/SSL/IP whitelist, and listing instance details or conversations.
Works with
--- name: aliyun-rds-supabase description: Use when managing Alibaba Cloud RDS Supabase (RDS AI Service 2025-05-07) via OpenAPI, including creating, starting/stopping/restarting instances, resetting passwords, querying endpoints/auth/storage, configuring auth/RAG/SSL/IP whitelist, and listing instance details or conversations. license: MIT --- Category: service # Alibaba Cloud RDS Supabase (RDS AI Service 2025-05-07) Manage RDS Supabase app instances and related configurations via RDS AI Service OpenAPI, including lifecycle, auth, storage, RAG, IP whitelist, and SSL. ## Prerequisites - Use least-privilege RAM user/role AccessKey and prefer environment variables for AK/SK. - OpenAPI uses RPC signing; prefer official SDKs or OpenAPI Explorer. ## Workflow 1) Confirm resource type: instance / auth / storage / RAG / security configuration. 2) Locate operations in `references/api_overview.md`. 3) Choose invocation method (SDK / OpenAPI Explorer / custom signing). 4) After changes, verify state and configuration with query APIs. ## AccessKey Priority (Required) 1) Environment variables (preferred):`ALIBABACLOUD_ACCESS_KEY_ID` / `ALIBABACLOUD_ACCESS_KEY_SECRET` / `ALIBABACLOUD_REGION_ID` Region policy: `ALIBABACLOUD_REGION_ID` is optional default; if unset choose the most reasonable region and ask when unclear. 2) Standard credentials file:`~/.alibabacloud/credentials` ## Default Region Strategy - If region is not specified, choose the most reasonable region; ask the user when unclear. - Only run all-region queries when explicitly needed or user-approved (call `ListRegions` first, then query each region). - If user provides region, query only that region. ## Common Operation Map - Instance:`CreateAppInstance` / `DeleteAppInstance` / `StartInstance` / `StopInstance` / `RestartInstance` - Connectivity and auth:`DescribeInstanceEndpoints` / `DescribeInstanceAuthInfo` / `ModifyInstanceAuthConfig` - Storage:`DescribeInstanceStorageConfig` / `ModifyInstanceStorageConfig` - Security:`ModifyInstanceIpWhitelist` / `DescribeInstanceIpWhitelist` / `ModifyInstanceSSL` / `DescribeInstanceSSL` - RAG:`ModifyInstanceRAGConfig` / `DescribeInstanceRAGConfig` ## Clarifying questions (ask when uncertain) 1. What is the target instance ID and region? 2. Is this instance lifecycle management or configuration changes (auth/storage/RAG/IP whitelist/SSL)? 3. Do you need batch operations or an initial state query first? ## Output Policy If you need to save results or responses, write to: `output/database-rds-supabase/` ## Validation ```bash mkdir -p output/aliyun-rds-supabase echo "validation_placeholder" > output/aliyun-rds-supabase/validate.txt ``` Pass criteria: command exits 0 and `output/aliyun-rds-supabase/validate.txt` is generated. ## Output And Evidence - Save artifacts, command outputs, and API response summaries under `output/aliyun-rds-supabase/`. - Include key parameters (region/resource id/time range) in evidence files for reproducibility. ## Prerequisites - Configure least-privilege Alibaba Cloud credentials before execution. - Prefer environment variables: `ALIBABACLOUD_ACCESS_KEY_ID`, `ALIBABACLOUD_ACCESS_KEY_SECRET`, optional `ALIBABACLOUD_REGION_ID`. - If region is unclear, ask the user before running mutating operations. ## Workflow 1) Confirm user intent, region, identifiers, and whether the operation is read-only or mutating. 2) Run one minimal read-only query first to verify connectivity and permissions. 3) Execute the target operation with explicit parameters and bounded scope. 4) Verify results and save output/evidence files. ## References - API overview and operation groups:`references/api_overview.md` - Core API parameter quick reference:`references/api_reference.md` - All-region query examples:`references/query-examples.md` - Official source list:`references/sources.md`
More API Design skills
lark-event
larksuite/cli
Lark/Feishu real-time event listening / subscribing / consuming: stream events as NDJSON via `lark-cli event consume <EventKey>` (covers IM messages/reactions/chat changes, Approval status changes, Task updates, VC meeting started/joined/ended, Minutes generated, Whiteboard updated, etc.). Use for Lark bots, real-time message processing, long-running subscribers, streaming webhook/push handlers. Supports `--max-events` / `--timeout` bounded runs and a stderr ready-marker contract — designed for AI agents running as subprocesses.
lark-contact
larksuite/cli
飞书 / Lark 通讯录:按姓名 / 邮箱解析成 open_id,或按 open_id 反查姓名 / 部门 / 邮箱 / 联系方式 / 个人状态 / 签名,以及按关键词搜索当前用户可见的机器人 / 智能体(agent)。当用户提到一个名字要下一步发消息 / 排日程,或拿到 open_id 想查具体信息时使用。不负责部门树遍历、按部门列员工、组织架构图,这类需求走原生 OpenAPI。
lark-openapi-explorer
larksuite/cli
飞书/Lark 原生 OpenAPI 探索:从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足,需要查找并调用原生飞书 OpenAPI 时使用。

