lark-attendance

To retrieve Feishu attendance punch records automatically, this Skill queries the Feishu attendance API using lark-cli authentication and the attendance:task:readonly permission scope. It automatically applies the required employee_type and user_ids parameters, allowing you to instantly verify work-time history for any specified date range.

Checking Feishu punch records requires lark-cli authentication and the attendance:task:readonly permission scope. The Skill validates the API schema before making requests and automatically fills in default employee_type and empty user_ids parameters, so no manual configuration is needed beyond the initial setup.

Yes, you can investigate missed punches in Feishu without manual lookup by requesting attendance records for a specific date range. The Skill retrieves your punch history directly through the Feishu attendance API, helping you quickly identify discrepancies, confirm working hours, and review attendance history.

Querying Feishu attendance records does not require manually specifying your user ID. The Skill automatically applies empty user ID defaults and sets the employee_type parameter without asking the user, streamlining the retrieval process while respecting the read-only attendance permission scope.

Limitations when accessing Feishu attendance data include being restricted to the read-only attendance scope, meaning you cannot modify records. The Skill enforces schema validation before API calls to prevent errors, and it requires active lark-cli authentication to successfully retrieve personal punch history.