[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6J16Z2J7E6VDQ7ET49X9RA4":3,"skill-same:01M6J16Z2J7E6VDQ7ET49X9RA4":111},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M6J16Z2J7E6VDQ7ET49X9RA4","lark-event",null,"Lark\u002FFeishu real-time event listening \u002F subscribing \u002F consuming: stream events as NDJSON via `lark-cli event consume \u003CEventKey>` (covers IM messages\u002Freactions\u002Fchat changes, Approval status changes, Task updates, VC meeting started\u002Fjoined\u002Fended, Minutes generated, Whiteboard updated, Drive doc comment notices, etc.). Use for Lark bots, real-time message processing, long-running subscribers, streaming webhook\u002Fpush handlers. Supports `--max-events` \u002F `--timeout` bounded runs and a stderr ready-marker contract — designed for AI agents running as subprocesses.","larksuite\u002Fcli","larksuite","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54944174?v=4","01M6J14VT8GJAN67PYPEJG4B7W","Lark Technologies Pte. Ltd.","01M6J14VYWNDEHZTM1T14EN0XD",18111,"MIT","https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-event\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"event","lark event","lark","vc","cli","updates","whiteboard","processing","webhook","reactions","time","message","bots","max","ready","generated","messages","streaming","status","ai agents","2026-11-10 10:12:30",false,"---\nname: lark-event\nversion: 1.0.0\ndescription: \"Lark\u002FFeishu real-time event listening \u002F subscribing \u002F consuming: stream events as NDJSON via `lark-cli event consume \u003CEventKey>` (covers IM messages\u002Freactions\u002Fchat changes, Approval status changes, Task updates, VC meeting started\u002Fjoined\u002Fended, Minutes generated, Whiteboard updated, Drive doc comment notices, etc.). Use for Lark bots, real-time message processing, long-running subscribers, streaming webhook\u002Fpush handlers. Supports `--max-events` \u002F `--timeout` bounded runs and a stderr ready-marker contract — designed for AI agents running as subprocesses.\"\nmetadata:\n  requires:\n    bins: [\"lark-cli\"]\n  cliHelp: \"lark-cli event --help\"\n---\n\n# Lark Events\n\n> **Prerequisite:** Read [`..\u002Flark-shared\u002FSKILL.md`](..\u002Flark-shared\u002FSKILL.md) first for authentication, `--as user\u002Fbot` switching, `Permission denied` handling, and safety rules.\n\n## Core commands\n\n| Command | Purpose |\n|------|------|\n| `lark-cli event list [--json]` | List all subscribable EventKeys |\n| `lark-cli event schema \u003CEventKey> [--json]` | Show an EventKey's params and output schema |\n| `lark-cli event consume \u003CEventKey> [flags]` | Blocking consume; events → stdout NDJSON |\n| `lark-cli event status [--json] [--fail-on-orphan]` | Inspect the local bus daemon status |\n| `lark-cli event stop [--all] [--force]` | Stop the bus daemon |\n\n\n## Common flags\n\n| Flag | Description |\n|---|---|\n| `--param key=value` \u002F `-p` | Business params (repeatable; comma-separated for multi-value). Unknown keys fail with valid names listed inline |\n| `--jq \u003Cexpr>` | jq expression to filter \u002F transform each event; empty output skips the event |\n| `--max-events N` | Exit after N events. Default 0 = unlimited |\n| `--timeout D` | Exit after duration D (e.g. `30s`, `2m`). Default 0 = no timeout. Whichever of `--max-events` \u002F `--timeout` fires first wins |\n| `--output-dir \u003Cdir>` | Write each event as a file (relative paths only; prevents traversal) |\n| `--quiet` | Suppress ready\u002Fexit markers and per-event stderr diagnostics, including drop warnings. This can hide event loss. **AI should not use this** — it removes readiness and integrity signals |\n| `--as user\\|bot\\|auto` | Identity for the session (see lark-shared) |\n\n\n## Examples\n\n```bash\n# Default: stream every event for the key (no filter, no projection)\nlark-cli event consume im.message.receive_v1 --as bot\n\n# List every EventKey of one domain (the authoritative, always-current catalog)\nlark-cli event list --domain vc --json\n\n# Grab one sample event to inspect payload shape\nlark-cli event consume im.message.receive_v1 --max-events 1 --timeout 30s --as bot\n\n# Run for 10 minutes then auto-exit\nlark-cli event consume im.message.receive_v1 --timeout 10m --as bot\n\n# Consume multiple EventKeys concurrently (one shape per process, no dispatcher)\nlark-cli event consume im.message.receive_v1          --as bot > receive.ndjson &\nlark-cli event consume im.message.reaction.created_v1 --as bot > reaction.ndjson &\nwait\n\n```\n\n## Call flow\n\n1. `lark-cli event list --json` → pick a legal key. `--domain \u003Cd>` narrows to one domain; the domains are `application`, `approval`, `board`, `card`, `drive`, `im`, `minutes`, `task`, `vc`. An unknown domain fails with the valid set listed in the hint.\n2. `lark-cli event schema \u003Ckey> --json` → read `resolved_output_schema` + `jq_root_path` to determine field paths\n3. `lark-cli event consume \u003Ckey> [--jq '\u003Cexpr>']` → consume\n\n## Subprocess contract\n\n### Ready marker\n\n`event consume`'s stderr emits a fixed line `[event] ready event_key=\u003Ckey>`. **Parent processes should block on stderr until this line appears, then start reading stdout.** Do not fall back to `sleep`.\n\n### stdin EOF = graceful exit\n\n`event consume` treats stdin close as a shutdown signal (wired for AI subprocess callers). **Bounded runs are exempt: when `--max-events` or `--timeout` is set (> 0), stdin EOF is ignored and the run exits only via its own bound, timeout, or SIGTERM.** For unbounded runs, `\u003C \u002Fdev\u002Fnull` \u002F `nohup` \u002F systemd's default `StandardInput=null` will cause an immediate graceful exit (stderr `reason: signal`). To keep an unbounded run alive:\n\n- Feed stdin a source that never EOFs: `\u003C \u003C(tail -f \u002Fdev\u002Fnull)`\n- Or run bounded: `--max-events N` \u002F `--timeout D`\n\n### Exit codes & reason\n\nOn exit, the last stderr line is `[event] exited — received N event(s) in Xs (reason: ...)`.\n\n| exit code | reason | Trigger |\n|---|---|---|\n| 0 | `reason: limit` | `--max-events` reached |\n| 0 | `reason: timeout` | `--timeout` reached |\n| 0 | `reason: signal` | Ctrl+C \u002F SIGTERM \u002F stdin EOF (stdin EOF applies to unbounded runs only) |\n| 1 | JSON error envelope on stderr | Lark API business failure during pre-consume setup (for example subscription create\u002Fdelete) |\n| 2 | JSON error envelope on stderr (no `exited` line) | Validation failure (unknown EventKey, bad `--param` \u002F `--jq`, another bus already connected) |\n| 3 | JSON error envelope on stderr | Auth failure (missing token, missing scopes) |\n| 4 \u002F 5 | JSON error envelope on stderr | Network \u002F internal failure (bus startup, handshake, file I\u002FO) |\n\nStartup and runtime failures emit a structured JSON envelope on stderr: `{\"ok\":false,\"error\":{\"type\",\"subtype\",\"param\",\"message\",\"hint\",...}}` (the envelope may also carry top-level `identity` \u002F `_notice` siblings). Parse `error.type` \u002F `error.subtype` to branch (e.g. `missing_scope` carries a `missing_scopes` list), `error.param` to find the offending flag, and `error.hint` for the recovery action — do not regex-match message text.\n\nOrchestrators should treat `reason: limit\u002Ftimeout\u002Fsignal` (all exit 0) as \"business completion\" and non-zero as \"failure\".\n\n### Never `kill -9`\n\n**Avoid `kill -9` on consume processes** for EventKeys whose PreConsume registers a server-side subscription **and** unsubscribes on exit (minutes, vc, board keys): `kill -9` skips the OAPI unsubscribe and leaks the server-side subscription (symptoms: \"subscription already exists\" on restart, duplicate event delivery). Keys whose subscription is a durable relation with no cleanup (task, approval, drive keys) do not leak this way, but SIGTERM or closing stdin remains the right shutdown for every key.\n\n### One consume, one EventKey (multi-key = multi-shell)\n\nThe command takes exactly one positional argument; `k1,k2` and wildcards are unsupported. Listening to N keys means N subprocesses — this is **intentional**:\n\n- One shape per process stdout; no dispatcher logic required in the AI\n- Fault isolation (one key failing doesn't affect others)\n- Independent `--as` \u002F `--jq` \u002F `--max-events` \u002F `--timeout` per key\n\nAll N consumers share a single bus daemon (UDS local IPC), so the overhead is small\n\n## Writing jq via schema\n\n`event schema \u003Ckey> --json` is the source of truth for writing `--jq`. Four things to look at:\n\n**(1) Where fields start** — see `jq_root_path`\n\n- Value `\".\"` → fields are at the top level, write `.chat_id`\n- Value `\".event\"` → fields are inside a V2 envelope, write `.event.chat_id`\n\n**(2) Field list and types** — see `resolved_output_schema.properties.\u003Cname>`\n\nEach field carries `type` \u002F `description`, and some also have `format`. Snippet (from `event schema im.message.receive_v1 --json`):\n\n```json\n{\n  \"chat_id\":     {\"type\":\"string\", \"format\":\"chat_id\",      \"description\":\"Chat ID, prefixed with oc_\"},\n  \"sender_id\":   {\"type\":\"string\", \"format\":\"open_id\",      \"description\":\"Sender open_id, prefixed with ou_\"},\n  \"create_time\": {\"type\":\"string\", \"format\":\"timestamp_ms\", \"description\":\"Send time as ms-epoch string\"}\n}\n```\n\n**(3) Field semantics** — see the `format` tag\n\nLark-defined semantic tags (**not** JSON Schema's standard `format`). Common values: `open_id` \u002F `chat_id` \u002F `message_id` \u002F `timestamp_ms` \u002F `email`. Purpose: distinguish \"same string type, different meanings\" fields so you can reverse-lookup via API or convert formats.\n\n**(4) Decoded state** — read the field's `description`\n\n`event consume` runs Process hooks that may pre-decode some payload fields (flattening V2 envelopes, rendering `.content` to plain text, etc.) — behavior differs from raw OAPI. **Always read the field's `description` before writing jq**, especially for generic field names like `content` \u002F `data` \u002F `body` \u002F `payload`.\n\n**Why it matters**: blindly applying `fromjson` to an already-decoded text field makes jq error on every event and silently drop it — the consumer looks alive but emits nothing, with only a single `WARN` line buried on stderr. (This is the general behavior: any jq runtime error skips the event with a one-line WARN; the loop does not abort.)\n\n**Don't shortcut the schema**: when projecting `event schema --json` with jq, do not strip `.description` from `properties` — that's the field that tells you whether a field is already decoded. Dump the full property objects, not just keys.\n\n---\n\n**Aside**: `--param`'s valid parameters also live in the schema — the `params` section lists `name` \u002F `type` \u002F `required` \u002F `enum` \u002F `default` \u002F `description`; **section missing = this key accepts no `--param`**.\n\n## Topic index\n\n| Topic      | Reference                                                                    | Coverage |\n|------------|------------------------------------------------------------------------------|---|\n| Application | [`references\u002Flark-event-application.md`](references\u002Flark-event-application.md) | Catalog of Application EventKeys, including `application.bot.menu_v6` for custom bot menu push events + flattened `event_key` \u002F operator fields + jq recipe |\n| Approval   | [`references\u002Flark-event-approval.md`](references\u002Flark-event-approval.md)     | Catalog of 2 Approval EventKeys (`approval.instance.status_changed_v4`, `approval.task.status_changed_v4`) + optional\u002Fmulti `subscription_type` pre-registration + user-auth subscription lifecycle + flat output field reference |\n| Drive      | [`references\u002Flark-event-drive.md`](references\u002Flark-event-drive.md)           | Catalog of 1 Drive EventKey (`drive.notice.comment_add_v1`) for doc comment \u002F reply notices (@bot or @me) + user vs bot receiver semantics + durable subscription + flat field reference + follow-up comment read |\n| IM         | [`references\u002Flark-event-im.md`](references\u002Flark-event-im.md)                 | Catalog of 12 IM EventKeys + shape notes (flat vs V2 envelope) + `im.message.receive_v1` field gotchas (`sender_id` is open_id only; `.content` is plain text except for `interactive` cards) + common jq recipes (filter by chat_type \u002F message_type \u002F sender); for `card.action.trigger` see also [`..\u002Flark-im\u002Freferences\u002Flark-im-card-action-reply.md`](..\u002Flark-im\u002Freferences\u002Flark-im-card-action-reply.md) |\n| Task       | [`references\u002Flark-event-task.md`](references\u002Flark-event-task.md)             | Catalog of 1 Task EventKey (`task.task.update_user_access_v2`) + Native V2 envelope shape + task commit types + user\u002Fbot subscription notes |\n| VC         | [`references\u002Flark-event-vc.md`](references\u002Flark-event-vc.md)                 | Catalog of 7 VC EventKeys (meeting lifecycle `participant_meeting_started\u002Fjoined\u002Fended_v1`, `vc.note.generated_v1`, recording `recording_started\u002Ftranscript_generated\u002Fended_v1`) + field reference + source type semantics; the live list is always `lark-cli event list --domain vc --json` |\n| Minutes    | [`references\u002Flark-event-minutes.md`](references\u002Flark-event-minutes.md)       | Catalog of 1 Minutes EventKey (`minutes.minute.generated_v1`) + field reference + source type semantics (meeting only) |\n| Whiteboard | [`references\u002Flark-event-whiteboard.md`](references\u002Flark-event-whiteboard.md) | Catalog of 1 Board EventKey (`board.whiteboard.updated_v1`) + per-whiteboard subscription model (requires `-p whiteboard_id=\u003Ctoken>`) + payload field reference (whiteboard_id \u002F operator_ids triple-id) |\n","# Lark Events\n\n> **Prerequisite:** Read [`..\u002Flark-shared\u002FSKILL.md`](..\u002Flark-shared\u002FSKILL.md) first for authentication, `--as user\u002Fbot` switching, `Permission denied` handling, and safety rules.\n\n## Core commands\n\n| Command | Purpose |\n|------|------|\n| `lark-cli event list [--json]` | List all subscribable EventKeys |\n| `lark-cli event schema \u003CEventKey> [--json]` | Show an EventKey's params and output schema |\n| `lark-cli event consume \u003CEventKey> [flags]` | Blocking consume; events → stdout NDJSON |\n| `lark-cli event status [--json] [--fail-on-orphan]` | Inspect the local bus daemon status |\n| `lark-cli event stop [--all] [--force]` | Stop the bus daemon |\n\n\n## Common flags\n\n| Flag | Description |\n|---|---|\n| `--param key=value` \u002F `-p` | Business params (repeatable; comma-separated for multi-value). Unknown keys fail with valid names listed inline |\n| `--jq \u003Cexpr>` | jq expression to filter \u002F transform each event; empty output skips the event |\n| `--max-events N` | Exit after N events. Default 0 = unlimited |\n| `--timeout D` | Exit after duration D (e.g. `30s`, `2m`). Default 0 = no timeout. Whichever of `--max-events` \u002F `--timeout` fires first wins |\n| `--output-dir \u003Cdir>` | Write each event as a file (relative paths only; prevents traversal) |\n| `--quiet` | Suppress ready\u002Fexit markers and per-event stderr diagnostics, including drop warnings. This can hide event loss. **AI should not use this** — it removes readiness and integrity signals |\n| `--as user\\|bot\\|auto` | Identity for the session (see lark-shared) |\n\n\n## Examples\n\n```bash\n# Default: stream every event for the key (no filter, no projection)\nlark-cli event consume im.message.receive_v1 --as bot\n\n# List every EventKey of one domain (the authoritative, always-current catalog)\nlark-cli event list --domain vc --json\n\n# Grab one sample event to inspect payload shape\nlark-cli event consume im.message.receive_v1 --max-events 1 --timeout 30s --as bot\n\n# Run for 10 minutes then auto-exit\nlark-cli event consume im.message.receive_v1 --timeout 10m --as bot\n\n# Consume multiple EventKeys concurrently (one shape per process, no dispatcher)\nlark-cli event consume im.message.receive_v1          --as bot > receive.ndjson &\nlark-cli event consume im.message.reaction.created_v1 --as bot > reaction.ndjson &\nwait\n\n```\n\n## Call flow\n\n1. `lark-cli event list --json` → pick a legal key. `--domain \u003Cd>` narrows to one domain; the domains are `application`, `approval`, `board`, `card`, `drive`, `im`, `minutes`, `task`, `vc`. An unknown domain fails with the valid set listed in the hint.\n2. `lark-cli event schema \u003Ckey> --json` → read `resolved_output_schema` + `jq_root_path` to determine field paths\n3. `lark-cli event consume \u003Ckey> [--jq '\u003Cexpr>']` → consume\n\n## Subprocess contract\n\n### Ready marker\n\n`event consume`'s stderr emits a fixed line `[event] ready event_key=\u003Ckey>`. **Parent processes should block on stderr until this line appears, then start reading stdout.** Do not fall back to `sleep`.\n\n### stdin EOF = graceful exit\n\n`event consume` treats stdin close as a shutdown signal (wired for AI subprocess callers). **Bounded runs are exempt: when `--max-events` or `--timeout` is set (> 0), stdin EOF is ignored and the run exits only via its own bound, timeout, or SIGTERM.** For unbounded runs, `\u003C \u002Fdev\u002Fnull` \u002F `nohup` \u002F systemd's default `StandardInput=null` will cause an immediate graceful exit (stderr `reason: signal`). To keep an unbounded run alive:\n\n- Feed stdin a source that never EOFs: `\u003C \u003C(tail -f \u002Fdev\u002Fnull)`\n- Or run bounded: `--max-events N` \u002F `--timeout D`\n\n### Exit codes & reason\n\nOn exit, the last stderr line is `[event] exited — received N event(s) in Xs (reason: ...)`.\n\n| exit code | reason | Trigger |\n|---|---|---|\n| 0 | `reason: limit` | `--max-events` reached |\n| 0 | `reason: timeout` | `--timeout` reached |\n| 0 | `reason: signal` | Ctrl+C \u002F SIGTERM \u002F stdin EOF (stdin EOF applies to unbounded runs only) |\n| 1 | JSON error envelope on stderr | Lark API business failure during pre-consume setup (for example subscription create\u002Fdelete) |\n| 2 | JSON error envelope on stderr (no `exited` line) | Validation failure (unknown EventKey, bad `--param` \u002F `--jq`, another bus already connected) |\n| 3 | JSON error envelope on stderr | Auth failure (missing token, missing scopes) |\n| 4 \u002F 5 | JSON error envelope on stderr | Network \u002F internal failure (bus startup, handshake, file I\u002FO) |\n\nStartup and runtime failures emit a structured JSON envelope on stderr: `{\"ok\":false,\"error\":{\"type\",\"subtype\",\"param\",\"message\",\"hint\",...}}` (the envelope may also carry top-level `identity` \u002F `_notice` siblings). Parse `error.type` \u002F `error.subtype` to branch (e.g. `missing_scope` carries a `missing_scopes` list), `error.param` to find the offending flag, and `error.hint` for the recovery action — do not regex-match message text.\n\nOrchestrators should treat `reason: limit\u002Ftimeout\u002Fsignal` (all exit 0) as \"business completion\" and non-zero as \"failure\".\n\n### Never `kill -9`\n\n**Avoid `kill -9` on consume processes** for EventKeys whose PreConsume registers a server-side subscription **and** unsubscribes on exit (minutes, vc, board keys): `kill -9` skips the OAPI unsubscribe and leaks the server-side subscription (symptoms: \"subscription already exists\" on restart, duplicate event delivery). Keys whose subscription is a durable relation with no cleanup (task, approval, drive keys) do not leak this way, but SIGTERM or closing stdin remains the right shutdown for every key.\n\n### One consume, one EventKey (multi-key = multi-shell)\n\nThe command takes exactly one positional argument; `k1,k2` and wildcards are unsupported. Listening to N keys means N subprocesses — this is **intentional**:\n\n- One shape per process stdout; no dispatcher logic required in the AI\n- Fault isolation (one key failing doesn't affect others)\n- Independent `--as` \u002F `--jq` \u002F `--max-events` \u002F `--timeout` per key\n\nAll N consumers share a single bus daemon (UDS local IPC), so the overhead is small\n\n## Writing jq via schema\n\n`event schema \u003Ckey> --json` is the source of truth for writing `--jq`. Four things to look at:\n\n**(1) Where fields start** — see `jq_root_path`\n\n- Value `\".\"` → fields are at the top level, write `.chat_id`\n- Value `\".event\"` → fields are inside a V2 envelope, write `.event.chat_id`\n\n**(2) Field list and types** — see `resolved_output_schema.properties.\u003Cname>`\n\nEach field carries `type` \u002F `description`, and some also have `format`. Snippet (from `event schema im.message.receive_v1 --json`):\n\n```json\n{\n  \"chat_id\":     {\"type\":\"string\", \"format\":\"chat_id\",      \"description\":\"Chat ID, prefixed with oc_\"},\n  \"sender_id\":   {\"type\":\"string\", \"format\":\"open_id\",      \"description\":\"Sender open_id, prefixed with ou_\"},\n  \"create_time\": {\"type\":\"string\", \"format\":\"timestamp_ms\", \"description\":\"Send time as ms-epoch string\"}\n}\n```\n\n**(3) Field semantics** — see the `format` tag\n\nLark-defined semantic tags (**not** JSON Schema's standard `format`). Common values: `open_id` \u002F `chat_id` \u002F `message_id` \u002F `timestamp_ms` \u002F `email`. Purpose: distinguish \"same string type, different meanings\" fields so you can reverse-lookup via API or convert formats.\n\n**(4) Decoded state** — read the field's `description`\n\n`event consume` runs Process hooks that may pre-decode some payload fields (flattening V2 envelopes, rendering `.content` to plain text, etc.) — behavior differs from raw OAPI. **Always read the field's `description` before writing jq**, especially for generic field names like `content` \u002F `data` \u002F `body` \u002F `payload`.\n\n**Why it matters**: blindly applying `fromjson` to an already-decoded text field makes jq error on every event and silently drop it — the consumer looks alive but emits nothing, with only a single `WARN` line buried on stderr. (This is the general behavior: any jq runtime error skips the event with a one-line WARN; the loop does not abort.)\n\n**Don't shortcut the schema**: when projecting `event schema --json` with jq, do not strip `.description` from `properties` — that's the field that tells you whether a field is already decoded. Dump the full property objects, not just keys.\n\n---\n\n**Aside**: `--param`'s valid parameters also live in the schema — the `params` section lists `name` \u002F `type` \u002F `required` \u002F `enum` \u002F `default` \u002F `description`; **section missing = this key accepts no `--param`**.\n\n## Topic index\n\n| Topic      | Reference                                                                    | Coverage |\n|------------|------------------------------------------------------------------------------|---|\n| Application | [`references\u002Flark-event-application.md`](references\u002Flark-event-application.md) | Catalog of Application EventKeys, including `application.bot.menu_v6` for custom bot menu push events + flattened `event_key` \u002F operator fields + jq recipe |\n| Approval   | [`references\u002Flark-event-approval.md`](references\u002Flark-event-approval.md)     | Catalog of 2 Approval EventKeys (`approval.instance.status_changed_v4`, `approval.task.status_changed_v4`) + optional\u002Fmulti `subscription_type` pre-registration + user-auth subscription lifecycle + flat output field reference |\n| Drive      | [`references\u002Flark-event-drive.md`](references\u002Flark-event-drive.md)           | Catalog of 1 Drive EventKey (`drive.notice.comment_add_v1`) for doc comment \u002F reply notices (@bot or @me) + user vs bot receiver semantics + durable subscription + flat field reference + follow-up comment read |\n| IM         | [`references\u002Flark-event-im.md`](references\u002Flark-event-im.md)                 | Catalog of 12 IM EventKeys + shape notes (flat vs V2 envelope) + `im.message.receive_v1` field gotchas (`sender_id` is open_id only; `.content` is plain text except for `interactive` cards) + common jq recipes (filter by chat_type \u002F message_type \u002F sender); for `card.action.trigger` see also [`..\u002Flark-im\u002Freferences\u002Flark-im-card-action-reply.md`](..\u002Flark-im\u002Freferences\u002Flark-im-card-action-reply.md) |\n| Task       | [`references\u002Flark-event-task.md`](references\u002Flark-event-task.md)             | Catalog of 1 Task EventKey (`task.task.update_user_access_v2`) + Native V2 envelope shape + task commit types + user\u002Fbot subscription notes |\n| VC         | [`references\u002Flark-event-vc.md`](references\u002Flark-event-vc.md)                 | Catalog of 7 VC EventKeys (meeting lifecycle `participant_meeting_started\u002Fjoined\u002Fended_v1`, `vc.note.generated_v1`, recording `recording_started\u002Ftranscript_generated\u002Fended_v1`) + field reference + source type semantics; the live list is always `lark-cli event list --domain vc --json` |\n| Minutes    | [`references\u002Flark-event-minutes.md`](references\u002Flark-event-minutes.md)       | Catalog of 1 Minutes EventKey (`minutes.minute.generated_v1`) + field reference + source type semantics (meeting only) |\n| Whiteboard | [`references\u002Flark-event-whiteboard.md`](references\u002Flark-event-whiteboard.md) | Catalog of 1 Board EventKey (`board.whiteboard.updated_v1`) + per-whiteboard subscription model (requires `-p whiteboard_id=\u003Ctoken>`) + payload field reference (whiteboard_id \u002F operator_ids triple-id) |\n",{"name":5,"version":49,"metadata":50,"description":7},"1.0.0",{"cliHelp":51,"requires":52},"lark-cli event --help",{"bins":53},[54],"lark-cli","main","8d8357d39dd15ac5e9aa815d4ab2639d56bd3239","skills\u002Flark-event",1377,"https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli","https:\u002F\u002Fgithub.com\u002Flarksuite","https:\u002F\u002Fwww.larksuite.com","2026-11-13 17:28:43",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add larksuite\u002Fcli --skill lark-event",{"tool":69,"command":70},"bunx","bunx skills add larksuite\u002Fcli --skill lark-event",{"tool":72,"command":73},"pnpm","pnpm dlx skills add larksuite\u002Fcli --skill lark-event","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-event\u002FSKILL.md",true,[77,83,87,91,95,99,103,107],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Flark-event-application.md","REFERENCE","参考文档",1288,"https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-event\u002Freferences\u002Flark-event-application.md",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Flark-event-approval.md",9000,"https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-event\u002Freferences\u002Flark-event-approval.md",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Flark-event-drive.md",4095,"https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-event\u002Freferences\u002Flark-event-drive.md",{"path":92,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Flark-event-im.md",4600,"https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-event\u002Freferences\u002Flark-event-im.md",{"path":96,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Flark-event-minutes.md",2368,"https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-event\u002Freferences\u002Flark-event-minutes.md",{"path":100,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Flark-event-task.md",2677,"https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-event\u002Freferences\u002Flark-event-task.md",{"path":104,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Flark-event-vc.md",5128,"https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-event\u002Freferences\u002Flark-event-vc.md",{"path":108,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Flark-event-whiteboard.md",3637,"https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-event\u002Freferences\u002Flark-event-whiteboard.md",[112,142,160,177,196,209],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":123,"publishedAt":44},"01M6J19Q42KW26AGS4TRJCFSWK","cli-e2e-testcase-writer","Use when adding or updating Go CLI E2E coverage for one `tests\u002Fcli_e2e\u002F{domain}` domain of the compiled `lark-cli`, especially when the work requires live `--help` or `schema` exploration, scenario-based `clie2e.RunCmd` workflows, and per-domain `coverage.md` maintenance.","https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Ftests\u002Fcli_e2e\u002Fcli-e2e-testcase-writer\u002FSKILL.md",[118],{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[28,124,125,126,127,128,129,130,131,132,133,26,134,135,136,137,138,139,140,141],"e2e","writer","cli e2e testcase writer","help","maintenance","for","scenario","tests","live","domain","exploration","schema","use","coverage","work","when","workflows","go",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":44},"01M6J19MNSEQ2WHAJWS9WDXEYC","lark-workflow-standup-report","日程待办摘要：编排 calendar +agenda 和 task +get-my-tasks，生成指定日期的日程与未完成任务摘要。适用于了解今天\u002F明天\u002F本周的安排。","https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-workflow-standup-report\u002FSKILL.md",[],[26,149,150,151,152,153,154,155,156,157,158,159,28],"lark workflow standup report","workflow","report","standup","calendar","tasks","task","get","生成","agenda","my",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":169,"publishedAt":44},"01M6J19JDF05PZ4WMAWKYSMPFP","lark-workflow-meeting-summary","会议纪要整理工作流：汇总指定时间范围内的会议纪要并生成结构化报告。当用户需要整理会议纪要、生成会议周报、回顾一段时间内的会议内容时使用。","https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-workflow-meeting-summary\u002FSKILL.md",[166],{"categoryNo":167,"categoryName":168,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员",[150,170,171,172,173,26,28,157,174,175,176],"lark workflow meeting summary","summary","meeting","meeting summary","定时","整理","报告",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":44},"01M6J19E0H30T9JRKFXYPDPMTQ","lark-wiki","飞书知识库：管理知识空间、空间成员和文档节点。创建和查询知识空间、查看和管理空间成员、管理节点层级结构、在知识库中组织文档和快捷方式。当用户需要在知识库中查找或创建文档、浏览知识空间结构、查看或管理空间成员、移动或复制节点时使用。当用户给出 doubao.com 的 \u002Fwiki\u002F URL\u002Ftoken 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：上传文件到知识库节点下（走 lark-drive）、编辑文档\u002F表格\u002FBase 内容（走 lark-doc \u002F lark-sheets \u002F lark-base）。","https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-wiki\u002FSKILL.md",[],[26,184,185,186,28,127,187,188,189,190,191,192,193,194,195],"lark wiki","wiki","doc","文档","表格","webfetch","drive","base","token","URL","文件","sheets",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":205,"publishedAt":44},"01M6J198ST9SG3QYYR0HQJGT8M","lark-whiteboard","飞书画板：查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。 当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责：飞书云文档内容编辑（lark-doc）、文档内嵌电子表格\u002FBase（lark-sheets \u002F lark-base）。","https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-whiteboard\u002FSKILL.md",[202],{"categoryNo":203,"categoryName":204,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000016","图像与多媒体",[206,30,26,207,208,28,127,186,187,188,191,195],"lark whiteboard","xlsx","image",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":218,"publishedAt":44},"01M6J191B8WT4V6CCDPXJKPE1N","lark-task","飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。","https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-task\u002FSKILL.md",[215],{"categoryNo":216,"categoryName":217,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000023","Skill与智能体开发",[219,155,26,28,127,220,194,221],"lark task","协作","数据"]