lark-attendance

Retrieve personal Lark attendance records via the lark-cli API.

Updated Aug 17, 2024
One-click install
npx skills add https://github.com/LinoWhy/.dotfiles --skill lark-attendance-linowhy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lark-attendance
Source: https://github.com/LinoWhy/.dotfiles/tree/main/agents/.agents/skills/lark-attendance
Command: npx skills add https://github.com/LinoWhy/.dotfiles --skill lark-attendance-linowhy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill enables you to quickly view and audit your own Lark attendance punches by querying the attendance records through the lark-cli, reducing manual lookups and potential errors.

Core Features & Use Cases

  • Retrieve your attendance records for a given period using lark-cli attendance.
  • Review punch-in/out history to verify work hours, absences, and timestamps.
  • Use for payroll support, leave verification, and personal timekeeping audits.

Quick Start

Ask the AI to fetch your own attendance records for the current month using the 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 Lark attendance records for a specific time period?▼

To query Lark attendance records, you specify a date range and the Skill retrieves your punch-in history automatically using the lark-cli attendance command, filling required parameters like employee_type and user_ids.

Can I use this to review my punch-in history for monthly attendance summaries?▼

Yes, you can review your punch-in history to generate monthly attendance summaries, verifying work hours, absences, and timestamps directly from the retrieved Lark attendance records.

Does querying Lark attendance records require manual parameter configuration?▼

No manual parameter configuration is needed for querying Lark attendance records because the Skill automatically enforces required fields, setting employee_type to 'employee_no' and user_ids as an empty array.

What is the best way to audit my personal Lark attendance punches?▼

The best way to audit personal Lark attendance punches is using this automated query approach, which reduces manual lookups and errors by retrieving your punch-in and punch-out history via the lark-cli.

Can I use Lark attendance data for leave verification and payroll support?▼

You can use the retrieved Lark attendance data for leave verification and payroll support by reviewing the extracted punch-in history and timestamp validations to confirm work hours and absences.

Why does my Lark attendance query automatically set the employee type?▼

Your Lark attendance query automatically sets the employee_type to 'employee_no' and user_ids as an empty array to enforce required fields, ensuring the lark-cli command correctly targets and retrieves your own records.