lark-attendance

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

2|Updated Aug 9, 2026
One-click install
npx skills add https://github.com/DeepJH/doubao-skill-and-info --skill lark-attendance-deepjh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-attendance
Source: https://github.com/DeepJH/doubao-skill-and-info/tree/main/skills/lark-attendance
Command: npx skills add https://github.com/DeepJH/doubao-skill-and-info --skill lark-attendance-deepjh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It lets you retrieve your own Feishu (Lark) attendance check-in records directly from the command line without manually navigating the Feishu app or guessing API parameter formats. ## Core Features & Use Cases - Attendance Record Query: Calls the user_tasks.query API to fetch your personal clock-in and clock-out records. - Automatic Parameter Filling: Automatically injects required fields (employee_type as "employee_no" and user_ids as an empty array) so you never have to supply them manually. - Schema-First Invocation: Uses lark-cli schema to inspect parameter structures before calling the API, preventing malformed requests. - Use Case: Ask the assistant to show your check-in records for this week, and it queries the Lark attendance API with the correct scope and parameters, returning your punch records. ## Quick Start Ask the assistant to query my Feishu attendance check-in records for this month using lark-cli.

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 automatically fills employee_type as employee_no and user_ids as an empty array, so you only provide date or filter parameters.

What permissions are needed to query Lark attendance records?

The user_tasks.query method requires the attendance:task:readonly scope. Without this scope granted to the lark-cli application, the API call will be rejected.

Can I query attendance records for other employees with lark-cli?

This skill is scoped to querying your own attendance records, and user_ids is always set to an empty array. Querying other employees' records is not covered by this configuration.

Why does my Lark attendance API call fail with parameter errors?

Failures usually come from guessing the --data or --params field formats. Run lark-cli schema attendance.user_tasks.query first to inspect the exact parameter structure before invoking the API.

What tool is required to run the Lark attendance query?

The lark-cli binary must be installed and available in the environment. All API interactions, including schema inspection and the attendance query itself, are executed through this CLI.