Lark Attendance
Query your own Feishu/Lark clock-in attendance records from the terminal through the lark-cli
- What
- Query your own Feishu/Lark clock-in attendance records from the terminal through the lark-cli
- Cost
- Free
- Needs
- a Muse account with skill installation enabled
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a small, focused Lark skill: it queries your own clock-in attendance records through the `lark-cli`. The skill's real content is operational discipline — default parameters are auto-filled and never asked of the user, the API schema must be inspected before every call, and only one resource is exposed (`user_tasks.query`, scope `attendance:task:readonly`). By @larksuite, listed here with credit to its creator. Honest caveats: deliberately narrow — it covers your own records only, not team attendance management; requires a Feishu/Lark account, the `lark-cli` binary, and auth, with the shared `lark-shared` skill read first; documentation is in Chinese. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Muse account with skill installation enabled Install "Lark Attendance" for me. Query your own Feishu/Lark clock-in attendance records from the terminal through the lark-cli Repository: https://github.com/larksuite/cli/blob/main/skills/lark-attendance/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "larksuite-lark-attendance". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.