lark-attendance

To query your own attendance records from the Lark attendance service, use this skill to fetch personal punch data for the current or a specified period via the Lark CLI. It automatically fills parameters like employee_type and user_ids to retrieve your data.

Yes, you can audit your monthly attendance records using the Lark CLI. This skill queries the user_tasks API method to fetch personal attendance history, making it suitable for monthly reporting, compliance checks, and troubleshooting missing punch-ins.

Querying Lark attendance records does not require specifying user IDs manually. The skill enforces deterministic behavior by automatically setting employee_type to employee_no and user_ids to an empty array, ensuring it reads only your own attendance data.

The best way to retrieve personal attendance data for monthly reporting is using this skill to query the Lark attendance service. It fetches your punch records through the Lark CLI, providing quick visibility into work hours for auditing and exporting.

To troubleshoot missing punch-ins in your Feishu attendance history, query your personal records for the specified period using this skill. It reads your attendance data via the Lark CLI, allowing you to identify gaps and verify compliance.

The primary limitation when accessing historical attendance records via Lark CLI is that this skill's scope is restricted to reading your own personal data. It does not support querying attendance records for other employees or modifying existing punch entries.