Lark Attendance
- 337k installs
- 15.9k repo stars
- Updated July 28, 2026
- larksuite/cli
This is a copy of lark-attendance by open.feishu.cn - installs and ranking accrue to the original listing.
lark-attendance is an agent skill that queries a developer's own Feishu (Lark) attendance and punch records through lark-cli attendance for developers who need terminal access without manual API parameter assembly.
About
lark-attendance is a v1.0.0 agent skill in larksuite/cli that wraps lark-cli attendance commands to fetch the authenticated user's punch and attendance history. It auto-fills required API parameters—employee_type is always employee_no and user_ids is always an empty array—so agents never prompt users for those fields. Developers must read lark-shared/SKILL.md first for authentication and permission handling, matching other lark-cli skills. Reach for lark-attendance when you need punch records, clock-in/out history, or attendance summaries from a coding agent or shell workflow instead of opening the Feishu HR attendance UI or constructing Lark Open API requests manually.
- Automatically injects required defaults (employee_type=employee_no, empty user_ids array) so you never have to remember
- Provides schema inspection command before every API call to prevent guesswork.
- Exposes the user_tasks.query resource to fetch personal attendance punch records.
- Single required permission: attendance:task:readonly.
- Designed as a thin, safe wrapper around lark-cli for repeated personal attendance checks.
Lark Attendance by the numbers
- 336,967 all-time installs (skills.sh)
- +12,880 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/larksuite/cli --skill lark-attendanceAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 337k |
|---|---|
| repo stars | ★ 15.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 28, 2026 |
| Repository | larksuite/cli ↗ |
How do you query Lark attendance from terminal?
Query their own Lark attendance and punch records directly from the terminal or via an agent without manual parameter fiddling.
Who is it for?
Feishu/Lark employees who want agents or CLI to pull their own attendance records with zero parameter prompting.
Skip if: HR admins querying other employees' attendance or teams not using Feishu/Lark attendance modules.
When should I use this skill?
User asks to check Lark punch records, view attendance history, or query clock-in data via lark-cli.
What you get
Attendance punch records and clock-in/out history returned from Lark via lark-cli attendance commands.
- attendance punch records
- clock-in/out history
By the numbers
- v1.0.0 skill requiring lark-cli binary with lark-cli attendance --help
- Auto-injects 2 fixed API fields: employee_type and user_ids on every call
Files
attendance (v1)
CRITICAL — 开始前 MUST 先用 Read 工具读取 [`../lark-shared/SKILL.md`](../lark-shared/SKILL.md)，其中包含认证、权限处理
默认参数自动填充规则
调用任何 API 时，以下参数 必须自动填充，禁止向用户询问：
| 参数 | 固定值 | 说明 |
|---|---|---|
employee_type | "employee_no" | employee_type始终等于"employee_no" |
user_ids | []（空数组） | user_ids始终等于[] |
填充示例
当构建 --params 参数时，自动注入上述字段：
employee_type保持"employee_no"不变
当构建 --data 参数时，自动注入上述字段：
{
"user_ids": [],
...用户提供的参数
}注意：user_ids数组保持为空[]，employee_type保持"employee_no"不变。
API Resources
lark-cli schema attendance.<resource>.<method> # 调用 API 前必须先查看参数结构
lark-cli attendance <resource> <method> [flags] # 调用 API重要：使用原生 API 时，必须先运行schema查看--data/--params参数结构，不要猜测字段格式。
user_tasks
query— 查询用户考勤打卡记录
权限表
| 方法 | 所需 scope |
|---|---|
user_tasks.query | attendance:task:readonly |
Related skills
Agent BrowserGive their coding agent reliable, high-fidelity control over any website or Electron desktop app.577k39.1k
Lark ApprovalLet their AI coding agent create, read, update, and approve items in Lark (Feishu) approval workflows without leaving the coding environment.471kLark EventHandle Feishu/Lark bot events, webhooks, and subscription callbacks in agent-driven backend code.471kLark Workflow Meeting SummaryAutomatically generate structured meeting summaries and action items from Lark/Feishu calls without manual note-taking.470kLark Workflow Standup ReportAutomatically generate and post daily standup reports in Lark/Feishu from their workflow and activity data.470kLark Vc AgentGive their coding agent the ability to read, create, and update documents, tasks, and wiki pages inside Feishu (Lark).415kHow it compares
Pick lark-attendance over generic Lark API skills when you only need self punch-record lookup with parameter auto-fill baked in.
FAQ
Which API parameters does lark-attendance auto-fill?
lark-attendance always sets employee_type to employee_no and user_ids to an empty array on both --params and --data payloads. Agents must inject these fields automatically and must not ask the user for them.
Can lark-attendance query other employees' records?
lark-attendance is scoped to querying your own attendance punch records. The skill keeps user_ids as an empty array and targets self-service lookup via lark-cli attendance, not cross-employee HR administration.
Is Lark Attendance safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.