flask-api-design
Building clean, RESTful APIs with Marshmallow for serialization and OpenAPI documentation.
Works with
--- name: flask-api-design description: Building clean, RESTful APIs with Marshmallow for serialization and OpenAPI documentation. license: MIT --- # Flask API Design APIs should be self-documenting, consistent, and easy to consume. ## Serialization (Marshmallow) - **Schemas**: Transforming complex objects to/from primitive Python types. - **Validation**: Enforcing data constraints at the API layer. ## RESTful Routing - **Nouns not Verbs**: `/users/1` instead of `/getUser/1`. - **HTTP Methods**: GET (read), POST (create), PUT/PATCH (update), DELETE (remove). ## Documentation Use **Flask-Smorest** or **Flasgger** to automatically generate Swagger/OpenAPI UI for your endpoints. ## Best Practices - **Status Codes**: Return appropriate codes (e.g., `201 Created`, `404 Not Found`, `422 Unprocessable Entity`). - **Versioning**: Prefix routes with `/api/v1/`.
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 时使用。

