Documents & Data · IN-DEPTH PROFILE

lark-attendance

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-08-20

Pinned revision · 755daa4d

Open pinned commit ↗
SkillSignal profileSource-grounded

Updated 2026-08-20

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

30-SECOND BRIEF

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.

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 scope.claude/skills/lark-attendance/
Personal scope~/.claude/skills/lark-attendance/

Use project scope for team sharing and personal scope across repositories. The installer defaults to project scope; add -g for personal scope.

Install command (project scope)

This source cannot produce a reliable command. Open the listed source and copy the complete Skill folder manually.

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 Claude Code + Codex

grill-with-docs

Grill With Docs combines deep design questioning with domain-model documentation.
Tradeoff to check
It assumes the repository has, or is willing to adopt, domain glossaries and decision records.
First risk
Documentation churn · Medium
Source state
Pinned · 885e2ca4
Open profile ↗
02

Same job family · native to Claude Code + Codex

lark-approval

Lark Approval routes approval instances and approval inbox work through lark-cli.
Tradeoff to check
Available actions depend on the approval definition, current state, identity, and tenant permissions.
First risk
Consequential approval action · High
Source state
Pinned · 755daa4d
Open profile ↗
03

Same job family · native to Claude Code + Codex

lark-base

Lark Base covers structured operations on Feishu Base (Bitable), including tables, fields, records, views, and related data workflows after a Base exists.
Tradeoff to check
Field types, permissions, and automation behavior vary between Bases and must be inspected first.
First risk
Bulk data changes · High
Source state
Pinned · 755daa4d
Open 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.

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.