lark-attendance
Query Lark Attendance Records
Lark attendance data can be hard to check from a chat workflow. This skill helps Claude, Codex, and Claude Code query personal punch records through lark-cli.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "lark-attendance" from https://skillstore.io/skills/larksuite-lark-attendance.md and its manifest at https://skillstore.io/api/skills/larksuite-lark-attendance/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "lark-attendance". Show my attendance records for today.
Expected outcome:
Today's attendance shows one morning check-in and one evening check-out. No missing punch was found in the returned records.
Using "lark-attendance". Review my attendance for this week.
Expected outcome:
- Monday through Thursday include complete check-in and check-out records.
- Friday has no check-out record in the returned data.
- The query used the current user context with readonly attendance access.
Using "lark-attendance". What permission do I need for this query?
Expected outcome:
The attendance user task query requires readonly access for attendance task records. Tenant policy may require an administrator to grant it.
Security Audit
SafeMost external-command alerts are false positives caused by Markdown inline code and fenced examples. One high filesystem concern is confirmed because SKILL.md requires reading ../lark-shared/SKILL.md outside the audited skill directory. No evidence found for prompt injection or data exfiltration intent in SKILL.md.
Capability review items (1)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (14)
📁 Filesystem access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/larksuite-lark-attendance/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/larksuite-lark-attendance?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/larksuite-lark-attendance?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/larksuite-lark-attendance/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/larksuite-lark-attendance.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
larksuite. (2026). lark-attendance security audit report (audit version 8) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/larksuite-lark-attendance/audits/8BibTeX citation
@techreport{larksuite-larksuite-lark-attendance-2026,
author = {larksuite},
title = {lark-attendance security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/larksuite-lark-attendance/audits/8},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "lark-attendance security audit report (audit version 8)"
version: "1.0.0"
type: report
authors:
- name: "larksuite"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/larksuite-lark-attendance/audits/8"
identifiers:
- type: other
value: "skillstore:larksuite-lark-attendance:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Check Daily Punches
Review today's check-in and check-out records from Lark without opening the attendance console.
Prepare Timesheet Review
Collect recent personal attendance entries before completing a weekly or monthly timesheet review.
Support Attendance Questions
Help an operations user verify which readonly scope and query path are needed for attendance lookup.
Try These Prompts
Show my Lark attendance punch records for today. Use the attendance skill and summarize the check-in and check-out times.
Query my Lark attendance records from Monday through Friday this week. Group the results by date and highlight missing punches.
Before querying attendance, check the current lark-cli schema and confirm the readonly scope needed for user task records.
Review my Lark attendance records for last month. Summarize late arrivals, early departures, missing punches, and dates that need follow-up.
Best Practices
- Confirm lark-cli authentication before requesting attendance data.
- Run schema inspection when the attendance API shape may have changed.
- Ask for a clear date range to avoid broad or slow attendance queries.
Avoid
- Do not request attendance records for other users with this skill.
- Do not guess API fields without checking the current schema.
- Do not use the skill to modify, create, or delete attendance records.