lark-attendance

Retrieve Feishu attendance punch-in/out task records via the attendance API.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lark-cli.

What problem does it solve?

It solves the problem of manually checking your Feishu (Lark) attendance punch-in/out history by giving you a direct way to query your own attendance task records.

Core Features & Use Cases

  • Self Attendance Lookup: Retrieves your attendance punch records via the Feishu attendance task API using your authenticated identity.
  • Schema-First, Correct Parameters: Enforces that API payload structure is inspected with the schema command before calling the action, preventing field guessing.
  • Guardrailed Request Fields: Automatically injects employee_type="employee_no" and keeps user_ids as an empty array to align with the required query contract.

Quick Start

Ask the assistant to run the lark-attendance query to fetch your attendance punch records.

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 punch records?

You can query your Feishu attendance punch records by instructing the assistant to run the attendance query, which calls the Feishu attendance API to retrieve your personal punch-in and punch-out task history.

Can I look up attendance history for other employees using this tool?

No, you cannot look up attendance history for other employees. The query enforces a read-only scope with an empty user_ids array, restricting retrieval to your own personal attendance task records.

Do I need lark-cli to retrieve my attendance punch-in history?

Yes, you need lark-cli installed to retrieve your attendance punch-in history. The Skill executes the attendance.user_tasks.query command through the lark-cli dependency to fetch your records.

What parameters are required for the Feishu attendance API query?

The Feishu attendance API query requires the parameter employee_type set to employee_no and user_ids as an empty array. It also enforces schema-first parameter validation to prevent field guessing before calling the action.

Why does my Feishu attendance query require schema-first validation?

Schema-first validation is required for your Feishu attendance query to inspect the API payload structure with the schema command beforehand, preventing field guessing and ensuring the request parameters match the query contract.