lark-attendance

To retrieve Lark attendance records, use lark-cli to query user attendance tasks. The skill automatically enforces the required API parameters, setting employee_type to employee_no and user_ids as an empty array to return punch-in history accurately.

Querying Feishu attendance tasks requires the attendance:task:readonly scope for safe, read-only access. You must also configure lark-cli authentication beforehand by following the shared authentication guide to successfully fetch punch-in records.

Lark attendance API requests fail when parameters are mapped incorrectly. This skill prevents errors by automatically injecting employee_type as employee_no and keeping user_ids as an empty array, ensuring strict compliance with the API contract.

Yes, you can use lark-cli for automated attendance reporting and HR spot-checks. The skill retrieves punch-in history programmatically, making it suitable for automated reporting scripts that fetch user attendance task records.

No, the Lark attendance query does not support modifying or writing punch-in records. It requires the attendance:task:readonly scope, limiting functionality to safe, read-only retrieval of personal attendance task history.