Lark Event Skill for Codex: Inspect an Event Schema Locally
Use the Lark CLI event schema to design a parser before connecting a live event stream. Pick an event type, inspect its shape, and identify which fields the parser needs.
中文Setup for Codex (requires Lark CLI)
Codex with terminal access, Node.js/npm, and the official Lark CLI. This example uses the command’s schema and a local fixture, with no company event stream required.
- Install the official Lark CLI using the pinned repository quick start.
- Copy lark-event and lark-shared from the pinned snapshot into .agents/skills in the practice project. Start a Codex session and select $lark-event.
- Use lark-cli event list --json to select the event key and lark-cli event schema with --json to inspect its field descriptions before working with the fixture.
Example task
Use $lark-event to inspect the schema for task.task.update_user_access_v2. In a local practice note, identify the root object and the documented paths you would need to count task-change events. Sketch one synthetic record that matches the displayed schema and one invalid record for a parser test. Use schema inspection only.Expected result
The note uses the CLI’s actual schema and records the types of the selected fields. The synthetic test accepts a matching record and rejects an incompatible shape. It does not depend on any live event data.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
Why inspect the event schema before writing a parser?
The event catalog describes the envelope and each field’s type. The schema makes it possible to distinguish top-level fields from nested payload fields and design a small fixture before connecting any authorized stream.