docs(calendar): clarify attendee resolution to avoid type guessing - #2195
Conversation
Reword the note under the cross-domain search commands so agents ask the user to clarify an attendee's type when a name cannot be resolved or is ambiguous, instead of guessing the type from the name shape (e.g. treating an unmatched room name as a bot). Co-authored-by: TRAE CLI <noreply@bytedance.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe calendar skill updates participant search guidance. Searches must use ChangesCalendar participant search
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🚀 PR Preview Install Guide🧰 CLI updatenpm i -g https://pkg.pr.new/larksuite/cli/@larksuite/cli@ed8533fb9431c337a110734f271afb66d48f2b18🧩 Skill updatenpx skills add larksuite/cli#docs/calendar-attendee-resolution -y -g |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2195 +/- ##
=======================================
Coverage 75.92% 75.92%
=======================================
Files 962 962
Lines 102197 102197
=======================================
Hits 77591 77591
Misses 18716 18716
Partials 5890 5890 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Summary
When adding calendar attendees, an agent should resolve a name into an ID and, if that fails, ask the user to clarify the attendee type — not guess the type from the name shape. This reworks the note under the cross-domain search commands in the
lark-calendarskill to make that explicit.Changes
skills/lark-calendar/SKILL.md:必须用 --as user).ou_open_id usage sentence with an explicit rule: when a name cannot be resolved or its type is ambiguous, ask the user to clarify the attendee type instead of inferring it from the name shape.Motivation
An evaluation case (
cli_calendar_ext_001) failed because a meeting-room attendee — given only as a long, informal name — was searched as a user, then guessed to be a bot. The agent then triggered an unrelatedsearch:botdevice authorization and stalled on a QR-code prompt, so no event was ever created. The root cause was guessing the attendee type from the name shape; this doc change steers agents to clarify with the user instead.Test Plan
Related Issues
Summary by CodeRabbit