skilly.
All skills
Human Resources / AGENT SKILL

lark-attendance

open.feishu.cn
719.1K installs
0

View your own Lark attendance clock-in records.
飞书考勤打卡：查询自己的考勤打卡记录

Low community score

lark-attendance: This skill has a community score below −5, meaning it has received more downvotes than upvotes. Review its source and assessment before installing. Community votes are not a security review.
BEFORE YOU INSTALL

Understand the trade-offs.

SECURITY REVIEW

Review incomplete

The available checks do not support a complete conclusion. Review the scope before relying on this result.

No reported risk0 reported findingsIncomplete evidence
Scope & how to read this review

Static inspection of the supplied skill source. “Complete” means the selected source and checks completed; it does not cover every downloaded package, external service, or runtime action.

Source coverage
partial
Reviewed
2026-10-07
Reviewed version
sha256:ec919
Latest catalog version
sha256:ec919

The reported findings score starts at 100 and subtracts 35 for each critical finding, 20 for high, 9 for medium, and 3 for low, with a floor of 0. It is shown only for complete, current reviews with all finding details. A score of 100 means no findings were reported in the reviewed source.

Severity describes potential impact, not the probability of harm. Review the conditions and evidence for each finding. A scan is not a safety guarantee.

SKILL QUALITY

Limited evidence for a verdict

35/100Provisional source score

The source identifies an attendance-query API, fixed parameters, and its required scope. It provides a partial integration guide, but does not establish how to complete and validate a query for the current user.

low confidenceStatic reviewIntegration skill

The reviewer had limited evidence. These scores describe what was available, not a verified measure of reliability.

What works well

  • Names the intended API operation and required permission scope.
  • Requires schema inspection before constructing API arguments.
  • Provides explicit fixed values for employee_type and user_ids.

Before you rely on it

  • Supply the referenced shared skill containing authentication and permission handling.
  • Provide a complete query example, including date inputs and an explanation of how an empty user_ids array selects the current user.
  • Define expected response fields, acceptance checks, and recovery steps for permission errors and empty results.
Clear instructionsCan your agent understand the task and expected outcome?2/4

The intended operation and fixed arguments are clear, but required user inputs and the expected output are unspecified.

EVIDENCE
SKILL.md: "- `query` — 查询用户考勤打卡记录"; "| `user_ids` | `[]`（空数组） | `user_ids`始终等于`[]` |"

To improve: State required inputs, the output to present, and how the fixed empty user_ids array supports querying the current user's records.

Complete workflowAre prerequisites, failure cases, and recovery covered?1/4

Schema inspection and a permission scope are supplied, but setup, authentication, complete query steps, and failure recovery depend on missing or unspecified material.

EVIDENCE
SKILL.md: "**CRITICAL — 开始前 MUST 先用 Read 工具读取 [`../lark-shared/SKILL.md`](../lark-shared/SKILL.md)，其中包含认证、权限处理**"; "| `user_tasks.query` | `attendance:task:readonly` |"

To improve: Supply the shared dependency and document an ordered workflow covering prerequisites, authentication, query construction, pagination where applicable, and error recovery.

Repeatable resultsAre examples and dependencies specific enough to repeat the work?2/4

Fixed argument values and command templates reduce ambiguity, but there is no complete invocation or concrete input/output example. The v1 heading does not identify CLI compatibility.

EVIDENCE
SKILL.md: "lark-cli schema attendance.<resource>.<method>"; "lark-cli attendance <resource> <method> [flags]"; "| `employee_type` | `\"employee_no\"` |"

To improve: Add a complete invocation with representative dates and payload, and specify CLI compatibility if it affects argument or schema behavior.

Checkable outcomesCan you tell whether the task succeeded?1/4

Schema inspection offers a limited argument-structure check, but no observable criteria establish that returned records belong to the intended user and period.

EVIDENCE
SKILL.md: "使用原生 API 时，必须先运行 `schema` 查看 `--data` / `--params` 参数结构，不要猜测字段格式。" No response example, test, or result acceptance criteria were supplied.

To improve: Provide an example response and checks for user identity, requested dates, record completeness, and legitimate empty results.

Supporting filesDo the supplied scripts and references support the workflow?1/4

A supporting authentication and permissions guide is explicitly required but absent, so its coherence with these instructions cannot be assessed.

EVIDENCE
SKILL.md: "[`../lark-shared/SKILL.md`](../lark-shared/SKILL.md)，其中包含认证、权限处理". The referenced file was not supplied.

To improve: Include the referenced shared SKILL.md and any resources it requires so dependency consistency can be reviewed.

Review scope & scoring

Scores describe source evidence: 0 absent or contradicted, 1 weak, 2 incomplete, 3 solid, 4 strong. Supporting files are excluded when not applicable. Instruction skills can demonstrate quality through examples and checkable outcomes without executable tests.

Provisional source score
35/100
Files reviewed
1
Source coverage
skill only
Reviewed
2026-10-09
Rubric
2026-09-25-v3
Assessed version
sha256:ec919
Latest catalog version
sha256:ec919

Review limitations

  • Coverage is skill-only; the mandatory shared dependency was not supplied.
  • CLI implementation, schemas, and response examples were unavailable.
  • This assessment is static and does not establish runtime success.

This review does not execute the skill or verify runtime results. Install counts and publisher reputation do not increase the score.

The full skill.

Original instructions from the publisher’s SKILL.md

# 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` 参数时，自动注入上述字段：
```json
{
  "user_ids": [],
  ...用户提供的参数
}
```

> **注意**：`user_ids` 数组保持为空[]，`employee_type` 保持 `"employee_no"` 不变。

## API Resources

```bash
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` |