[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MPFWND3WG5781Z98RBV258":3,"skill-same:01M6MPFWND3WG5781Z98RBV258":109},{"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":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6MPFWND3WG5781Z98RBV258","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, 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.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\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, 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 stderr diagnostics. **AI should not use this** — it silences the ready marker |\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# 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\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 with a **PreConsume hook** (those that register server-side subscriptions via OAPI), `kill -9` skips the OAPI unsubscribe and leaks server-side subscriptions (symptoms: \"subscription already exists\" on restart, duplicate event delivery). Prefer SIGTERM or closing stdin.\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| 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 4 VC EventKeys (`vc.meeting.participant_meeting_started_v1`, `vc.meeting.participant_meeting_joined_v1`, `vc.meeting.participant_meeting_ended_v1`, `vc.note.generated_v1`) + field reference + source type semantics (meeting only) |\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 stderr diagnostics. **AI should not use this** — it silences the ready marker |\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# 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\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 with a **PreConsume hook** (those that register server-side subscriptions via OAPI), `kill -9` skips the OAPI unsubscribe and leaks server-side subscriptions (symptoms: \"subscription already exists\" on restart, duplicate event delivery). Prefer SIGTERM or closing stdin.\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| 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 4 VC EventKeys (`vc.meeting.participant_meeting_started_v1`, `vc.meeting.participant_meeting_joined_v1`, `vc.meeting.participant_meeting_ended_v1`, `vc.note.generated_v1`) + field reference + source type semantics (meeting only) |\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","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-event",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill lark-event",{"tool":71,"command":72},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill lark-event",{"tool":74,"command":75},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill lark-event","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-event\u002FSKILL.md",true,[79,85,89,93,97,101,105],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Flark-event-application.md","REFERENCE","参考文档",1288,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-event\u002Freferences\u002Flark-event-application.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Flark-event-approval.md",9000,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-event\u002Freferences\u002Flark-event-approval.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Flark-event-im.md",4600,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-event\u002Freferences\u002Flark-event-im.md",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Flark-event-minutes.md",2368,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-event\u002Freferences\u002Flark-event-minutes.md",{"path":98,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Flark-event-task.md",2677,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-event\u002Freferences\u002Flark-event-task.md",{"path":102,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Flark-event-vc.md",4558,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-event\u002Freferences\u002Flark-event-vc.md",{"path":106,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Flark-event-whiteboard.md",3637,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-event\u002Freferences\u002Flark-event-whiteboard.md",[110,120,128,136,144,152],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":114,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":119},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":114,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":119},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":114,"licenseFileUrl":132,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":119},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":114,"licenseFileUrl":140,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":119},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":114,"licenseFileUrl":148,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":119},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":114,"licenseFileUrl":156,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":119},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]