json-schema
Use when working with JSON Schema for validation, OpenAPI schemas, type definitions, and data structure specification
Works with
---
name: json-schema
description: Use when working with JSON Schema for validation, OpenAPI schemas, type definitions, and data structure specification
license: MIT
---
# JSON Schema
## Quick Start
```json
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"required": ["id", "email"],
"properties": {
"id": { "type": "string", "format": "uuid" },
"email": { "type": "string", "format": "email" },
"age": { "type": "integer", "minimum": 0, "maximum": 150 },
"role": { "enum": ["admin", "user", "guest"] },
"tags": { "type": "array", "items": { "type": "string" } }
}
}
```
## Type Keywords
| Type | Validation Keywords |
|------|---------------------|
| `string` | `minLength`, `maxLength`, `pattern`, `format` |
| `number/integer` | `minimum`, `maximum`, `exclusiveMinimum`, `multipleOf` |
| `array` | `items`, `minItems`, `maxItems`, `uniqueItems` |
| `object` | `properties`, `required`, `additionalProperties` |
## Composition
```json
{
"allOf": [{ "$ref": "#/$defs/Base" }, { "properties": { "extra": {} } }],
"oneOf": [{ "type": "string" }, { "type": "number" }],
"anyOf": [{ "minimum": 0 }, { "maximum": 100 }],
"not": { "type": "null" }
}
```
## References
```json
{
"$defs": {
"Address": {
"type": "object",
"properties": { "street": { "type": "string" } }
}
},
"properties": {
"billing": { "$ref": "#/$defs/Address" },
"shipping": { "$ref": "#/$defs/Address" }
}
}
```
## Common Formats
`date-time`, `date`, `time`, `email`, `uri`, `uuid`, `ipv4`, `ipv6`, `hostname`
## OpenAPI 3.1 Notes
- OpenAPI 3.1 uses JSON Schema 2020-12
- Use `nullable` via `type: ["string", "null"]`
- `example` for single example, `examples` for multiple
- `$ref` can have siblings in 3.1 (not in 3.0)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 时使用。

