lark-attendance

Name: lark-attendance
Availability: InStock
Author: 466852675

Query Lark attendance punch-in records via lark-cli.

Updated Aug 23, 2026

Search Tags:#attendance #feishu #lark #lark-cli #timekeeping #attendance-records #employee-attendance

Ready to run

npx skills add https://github.com/466852675/Skills-2026 --skill lark-attendance

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrieve personal attendance punch-in records from Lark (Feishu) without manual field mapping or guessing API parameters, ensuring correct authentication and permission usage.

Core Features & Use Cases

Direct Query: Uses lark-cli to query user attendance tasks and return punch-in records.
Automatic Parameter Injection: Enforces employee_type to be employee_no and keeps user_ids as an empty array to comply with the API contract.
Permissions & Safety: Requires reading the shared authentication guide before use and the attendance:task:readonly scope for safe, read-only access.
Use Cases: Quick personal attendance checks, HR spot-checks, and automated reporting scripts that fetch punch-in history.

Quick Start

Retrieve my attendance records for March 2026 using the lark-attendance skill with the configured 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 retrieve my Lark attendance records using lark-cli?▼

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.

What permissions do I need to query Feishu attendance tasks?▼

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.

Why does my Lark attendance API request fail with parameter mapping errors?▼

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.

Can I use lark-cli for automated attendance reporting and HR spot-checks?▼

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.

Does the Lark attendance query support modifying or writing punch-in 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.