Documents & Data · IN-DEPTH PROFILE

Lark Attendance Skill

Lark Attendance is a narrow, read-only lark-cli Skill for querying the current user's Feishu attendance check-in records.

View listed source ↗Installation guide ↓
Best for

Feishu users checking their own attendance

What you get

Query personal attendance + Inspect the API schema

Main limitation

The Skill only documents the user's own check-in query; it is not a general attendance administration tool.

First risk

Employment data exposure. Attendance records are sensitive employment data. Return only the requesting user's authorized records and avoid retaining them in logs.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-09-23

Pinned revision · a079fd7a

Open pinned commit ↗
SkillSignal profileSource-grounded

Updated 2026-08-20

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

IN PLAIN ENGLISH

What it does—and when it fits

Lark Attendance is a narrow, read-only lark-cli Skill for querying the current user's Feishu attendance check-in records. Its upstream instructions require shared authentication, fixed employee_no semantics, an empty user_ids array, schema inspection before the API call, and the attendance:task:readonly scope.

This is aimed at Feishu users checking their own attendance. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.

What you get
  • Query personal attendanceRetrieve the signed-in user's check-in records with the documented fixed identity parameters.
  • Inspect the API schemaConfirm current request fields before building date or attendance filters.
  • Support attendance reviewPresent returned records for personal review without changing attendance data.
What makes it different
  • This profile is manually organized around the current upstream SKILL.md workflow.
  • The capability boundary remains explicitly tied to open.feishu.cn.
  • Core uses, limitations, and risks are separated for pre-install review.
Community signalskills.sh All-time: #30 · 727.9K installs

No verified review text is in the current dataset. Use the linked source for the latest discussion.

Read the source note ↗

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project install (recommended)
npx skills add larksuite/cli --skill lark-attendance --agent claude-code
Personal install
npx skills add larksuite/cli --skill lark-attendance --agent claude-code -g

Project install stays with this repository for team sharing. Personal install adds -g and works across repositories.

This command adds the Skill instructions only. Install lark-cli and sign in to Feishu separately before use. Official Lark CLI setup ↗

View install paths
Project path.claude/skills/lark-attendance/
Personal path~/.claude/skills/lark-attendance/
Official agent docs

Claude Code discovers custom Skill folders automatically at project or personal scope.

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Query personal attendance

Retrieve the signed-in user's check-in records with the documented fixed identity parameters.

02

Inspect the API schema

Confirm current request fields before building date or attendance filters.

03

Support attendance review

Present returned records for personal review without changing attendance data.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. This profile is manually organized around the current upstream SKILL.md workflow.
  2. The capability boundary remains explicitly tied to open.feishu.cn.
  3. Core uses, limitations, and risks are separated for pre-install review.

Limitations

  1. The Skill only documents the user's own check-in query; it is not a general attendance administration tool.
  2. Fixed user_ids and employee_type rules must not be replaced with guessed employee identifiers.

COMPARE THE TRADEOFF

Consider these close alternatives

These are deterministic nearby candidates, not paid placements or a universal ranking. Open the full profile before choosing.

01

Same job family · native to Codex + Claude Code

create-llms

Create an llms.txt index from repository documentation.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open create-llms profile ↗
02

Same job family · native to Codex + Claude Code

csharp-docs

Write useful XML documentation for C# APIs.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open csharp-docs profile ↗
03

Same job family · native to Codex + Claude Code

java-docs

Write consistent Javadoc for Java types and APIs.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open java-docs profile ↗
Compare more in the directory →

BEST FIT

Who it is for

→

Feishu users checking their own attendance

→

Read-only personal workflow assistants

BEFORE YOU USE IT

Risks to review before use

High

Employment data exposure

Attendance records are sensitive employment data. Return only the requesting user's authorized records and avoid retaining them in logs.

High

External data and identity boundary

Requests access Feishu tenant resources. Use the correct identity, least-privilege scopes, and keep sensitive content out of logs.

SECURITY

What the permission profile means

  • Declared access remains governed by the current upstream SKILL.md and runtime requests.
  • Treat Feishu documents, messages, people, and business records as permission-controlled data.
  • SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

COMMON QUESTIONS

Lark Attendance Skill FAQ

What is the Lark Attendance Skill?

Lark Attendance is a narrow, read-only lark-cli Skill for querying the current user's Feishu attendance check-in records. Its upstream instructions require shared authentication, fixed employee_no semantics, an empty user_ids array, schema inspection before the API call, and the attendance:task:readonly scope.

How do I install the Lark Attendance Skill?

Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Open the listed source and read the current SKILL.md plus only the references required for this task.

Is the Lark Attendance Skill safe to use?

SkillSignal checked the source on 2026-09-23, but that is not a runtime test or security certification. Review the “Employment data exposure” risk first and begin with the least access required.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream Skill instructionsSource-linked

TAGS

feishuattendanceread-only

Manually expanded from the current upstream SKILL.md and linked source at open.feishu.cn, checked 2026-08-19. This is an original summary, not an execution result or security certification.