lark-attendance 的 SKILL.md description 缺少触发条件，路由语义不够清晰
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Open skills/lark-attendance/SKILL.md and edit the description on line 4 to add trigger conditions, following the style already used by skills/lark-mail/SKILL.md in the same directory. Keep the description on one line and within any length convention the sibling skills follow. Done when the description states when the skill should be used, and the rest of the file is unchanged.
Written by the indexing model from the issue text.
Description
skills/lark-attendance/SKILL.md 第 4 行的 description 目前是：
飞书考勤打卡：查询自己的考勤打卡记录
它只说明了这个 skill 的功能，没有说明何时应该使用这个 skill（触发条件）。agent 在做 skill 路由时主要依赖 description，缺了触发语义容易误用或漏用。
对照同目录的其他 skill，例如 lark-mail 的 description 写明了触发条件：
飞书邮箱：Use when user mentions 起草邮件、写邮件、草稿、发送/回复/转发邮件……
建议把 lark-attendance 的 description 也补上触发条件，例如：
飞书考勤打卡：当用户提到查询考勤打卡记录、上下班打卡情况、迟到早退统计等考勤相关意图时使用；仅用于个人考勤打卡记录查询，不用于其他功能。
This contribution was autonomously selected and produced by agents through Hermes Labs’ engineering infrastructure. Rolando Bosch is the responsible human contributor and authorized publication from his personal GitHub account.
- Dominant language
- Go
- Stars
- 17.5k
- Forks
- 1.4k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 35
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from larksuite/cli
-
domain/core domain/doc enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
domain/core domain/doc enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
docs: update README skill counts to the 28 shipped skillsPossibly taken @dajiaohuang claimed this 45 days ago. Opendomain/core
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
fix(slides): make IconPark JSON output safe on non-UTF-8 Windows consolesPossibly taken @dajiaohuang claimed this 45 days ago. Openbug domain/core
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
fix(binding): accept files nested under trusted directories on WindowsPossibly taken @dajiaohuang claimed this 45 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
Similar issues
-
proxy logs "no user in context" at error level for every data gateway downloadPossibly taken @paul43210 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
txn2/mcp-data-platform#2063 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
kubernetes-sigs/kueue#16990 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
enhancement exporter/awss3 needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
open-telemetry/opentelemetry-collector-contrib#51905 · 1 comment ·
Maintainers usually reply within 1 day