菜单
Use when users need to query Feishu/Lark attendance records, audit punch-in gaps, summarize abnormal attendance, or reconcile missing check-ins with HR-facing evidence.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | lark-attendance |
| description | Use when users need to query Feishu/Lark attendance records, audit punch-in gaps, summarize abnormal attendance, or reconcile missing check-ins with HR-facing evidence. |
| zh_description | 用于查询飞书考勤记录、核对打卡缺失、整理异常考勤并生成可追溯说明。 |
| version | 1.0.2 |
| author | larksuite |
| source | github:larksuite/cli |
| source_url | https://github.com/larksuite/cli/tree/main/skills/lark-attendance |
| license | MIT |
| tags | [feishu, lark, lark-cli, attendance] |
| created_at | 2026-05-19 |
| updated_at | 2026-06-29 |
| quality | 3 |
| complexity | intermediate |
| metadata | {"requires":{"bins":["lark-cli"]},"cliHelp":"lark-cli attendance --help"} |
CRITICAL — 开始前 MUST 先用 Read 工具读取 ../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"不变。
lark-cli schema attendance.<resource>.<method> # 调用 API 前必须先查看参数结构
lark-cli attendance <resource> <method> [flags] # 调用 API
重要：使用原生 API 时，必须先运行
schema查看--data/--params参数结构，不要猜测字段格式。
query — 查询用户考勤打卡记录| 方法 | 所需 scope |
|---|---|
user_tasks.query | attendance:task:readonly |
This supplement is maintained by the repository sync pipeline. It keeps the imported upstream skill usable inside this curated collection when the upstream source is intentionally concise.
1. Confirm that the user's task matches the skill trigger.
2. Read the relevant project files or user-provided context before acting.
3. Choose the smallest reversible action that advances the task.
4. Run the verification command or manual check that proves the result.
5. Report the outcome, evidence, and any remaining risk.
Use this checklist before returning attendance findings:
open_id, employee number, and user display name in the same API call.employee_type consistent with the identifier type required by the endpoint.Prefer a compact table for user-facing summaries:
| Date | Person | Status | Evidence | Follow-up |
|---|---|---|---|---|
| 2026-06-29 | Example | Missing PM punch | user_tasks.query returned no end record | Ask employee to confirm |
When uncertainty remains, state exactly which API response, scope, or identifier prevented a definitive conclusion.
Designing red team attack scenarios, building threat models, applying MITRE ATT&CK/OWASP frameworks, running Purple Team exercises, and performing AI/LLM red teaming. Use when adversarial security validation is needed.
飞书云文档（Docx / Wiki 文档）：读取和编辑飞书文档内容。当用户给出文档 URL 或 token，或需要查看、创建、编辑文档、插入或下载文档图片附件时使用。文档中嵌入的电子表格、多维表格、画板，先用本 skill 提取 token 再切到对应 skill。当用户给出 doubao.com 的 /docx/ 或 /wiki/ URL/token 时，也应直接使用本 skill；路由依据是 URL 路径模式和 token，而不是域名。不负责文档评论管理，也不负责表格或 Base 的数据操作。当用户明确要操作飞书思维笔记时，也使用本 skill。
Comprehending and investigating codebases. Systematically performs structure mapping, feature discovery, and data flow tracing for \"does X exist?\", \"how does Y work?\", or \"what is this module's responsibility?\". Includes a conversational Q&A mode (\"ask\") for navigator-style, multi-turn questions about a project. Does not write code.
Orchestrating specialist AI agent teams as a meta-coordinator. Decomposes requests into minimum viable chains, spawns each as an independent session in AUTORUN modes, and drives to final output. Use when a task spans multiple specialist domains, requires parallel agent execution, or needs hub-and-spoke routing across the skill ecosystem.
Converting repository changes into detailed learning documents. Use when turning diffs into teaching materials, recording design decisions, or creating onboarding materials for new members.
Specialist orchestrating codex exec / Antigravity CLI through dual paradigms — COMPETE (multi-variant comparison, select best) and COLLABORATE (decompose tasks across engines, integrate). Supports Solo/Team/Quick execution modes.