From larkskill
Use this skill when querying Lark Attendance check-in records via LarkSkill MCP.
How this skill is triggered — by the user, by Claude, or both
Slash command
/larkskill:lark-attendanceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Prerequisite:** Read [`../lark-shared/SKILL.md`](../lark-shared/SKILL.md) first — it covers authentication and permission handling.
Prerequisite: Read
../lark-shared/SKILL.mdfirst — it covers authentication and permission handling.
When calling any attendance API, the following parameters MUST be auto-filled — DO NOT ask the user for these values:
| Parameter | Fixed value | Notes |
|---|---|---|
employee_type | "employee_no" | Always set employee_type to "employee_no" |
user_ids | [] (empty array) | Always set user_ids to [] |
When building the --params payload, inject the fields above automatically:
employee_type stays "employee_no" unchangedWhen building the --data payload, inject:
{
"user_ids": [],
...user-supplied parameters
}
Note: Keep
user_idsas an empty array[]andemployee_typeas"employee_no"— do not change these.
Call the attendance API using the raw HTTP form (no shortcut op available for this domain):
lark_api({ method: 'POST', path: '/open-apis/attendance/v1/user_tasks/query', params: { employee_type: 'employee_no' }, data: { user_ids: [], ...args } })
Important: Before using the raw API, inspect the request schema to understand the
data/paramsfield structure — do not guess field formats.
query — Query user attendance check-in records| Method | Required scope |
|---|---|
user_tasks.query | attendance:task:readonly |
npx claudepluginhub kescyz/larkskill --plugin larkskillCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.