lark-attendance

Query personal attendance check-in records via the Lark attendance API.

Updated May 28, 2026
One-click install
npx skills add https://github.com/changfengpro/agent-skills --skill lark-attendance-changfengpro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-attendance
Source: https://github.com/changfengpro/agent-skills/tree/main/skills/lark-attendance
Command: npx skills add https://github.com/changfengpro/agent-skills --skill lark-attendance-changfengpro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lark-cli.

What problem does it solve? Manually checking your own clock-in and clock-out history in Feishu (Lark) requires navigating the app UI; this Skill lets you query your attendance punch records directly through the lark-cli command line. ## Core Features & Use Cases - Attendance Record Query: Calls the user_tasks.query API to retrieve your own clock-in/clock-out records. - Automatic Parameter Filling: Auto-fills employee_type as "employee_no" and user_ids as an empty array, so you never need to provide them. - Schema-First Invocation: Inspects API parameter structures with lark-cli schema before calling, avoiding malformed requests. - Use Case: Ask the assistant to show your punch records for this week, and it queries the Lark attendance API and returns your check-in times. ## Quick Start Ask the assistant to query my Feishu attendance check-in records for this month using the lark-attendance skill.

Frequently Asked Questions about lark-attendance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I query my Feishu attendance check-in records from the command line?

Use lark-cli with the attendance user_tasks query method after checking the parameter structure via lark-cli schema. The skill auto-fills employee_type as employee_no and user_ids as an empty array, so no extra parameters are needed.

What permissions are needed to query Lark attendance records?

The user_tasks.query method requires the attendance:task:readonly scope. Authentication and permission handling details are covered in the shared lark-shared skill documentation.

Can I query attendance records for other employees with this skill?

No, this skill is scoped to querying your own attendance records. The user_ids parameter is fixed to an empty array, which targets the current authenticated user only.

Why must I run lark-cli schema before calling the attendance API?

Running lark-cli schema attendance.<resource>.<method> shows the exact --data and --params structure, preventing errors from guessing field formats when building API requests.

What dependencies does the lark attendance query require?

It requires the lark-cli binary to be installed and available. All API calls are executed through lark-cli attendance commands rather than direct HTTP requests.