lark-attendance

Query personal attendance punch records from the Lark attendance service.

Updated Aug 23, 2026

Search Tags:#automation #audit #query #attendance #data-access #records #lark-cli

Ready to run

npx skills add https://github.com/ShunsukeHayashi/lark-harness --skill lark-attendance-shunsukehayashi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lark-attendance
Source: https://github.com/ShunsukeHayashi/lark-harness/tree/main/lark-attendance
Command: npx skills add https://github.com/ShunsukeHayashi/lark-harness --skill lark-attendance-shunsukehayashi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill lets you query your own attendance punching records from Feishu (Lark) attendance service, enabling quick visibility into work hours and attendance history.

Core Features & Use Cases

Automatic parameter filling: ensures employee_type is always "employee_no" and user_ids is always [].
API access: query user_tasks to fetch personal attendance punch records.
Use case: monthly attendance auditing, troubleshooting missing punch-ins, and exporting records for reporting.

Quick Start

Query my attendance records for the current month.

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 own attendance records from the Lark attendance service?▼

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.

Can I audit my monthly attendance records using the Lark CLI?▼

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.

Does querying Lark attendance records require specifying user IDs?▼

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.

What is the best way to retrieve personal attendance data for monthly reporting?▼

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.

How do I troubleshoot missing punch-ins in my Feishu attendance history?▼

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.

Are there limitations when accessing historical attendance records via Lark CLI?▼

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.