feishu-calendar

飞书日历与日程管理工具集。包含日历管理、日程管理、参会人管理、忙闲查询。

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./nexu-skills/skills/feishu-calendar/SKILL.md

The canonical home for this skill is feishu-calendar in op7418/CodePilot

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with concrete JSON examples and a clear intent-to-tool index, and it captures valuable Feishu-specific constraints Claude would not know. It loses points for general-concept padding in the appendix, missing validation checkpoints on batch/destructive operations, and a monolithic single-file structure with no progressive disclosure to separate references.

Suggestions

Trim or remove the appendix "背景知识" sections (calendar architecture model, event lifecycle) that describe concepts Claude already knows, keeping only Feishu-specific facts.

Add explicit validation/verification steps for batch and destructive operations (e.g. confirm event_id and attendee list before batch_delete, verify patch results with a follow-up get).

Move the reference-style material (ID format tables, calendar type table, RSVP status table, OAPI limits) into a separate REFERENCES.md and link to it from a concise overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and information-dense with Feishu-specific knowledge Claude lacks (user_open_id requirement, ID format conventions, async meeting-room booking, OAPI limits), but the appendix "背景知识" explains general concepts like the calendar/event/attendee hierarchy and event lifecycle that Claude already knows, fitting the score-2 anchor of mostly efficient with some unnecessary explanation.	2 / 3
Actionability	The quick-index table maps intent to tool/action/required params and the six scenario blocks provide complete, copy-paste-ready JSON payloads with concrete field values, matching the score-3 anchor of fully executable examples that are copy-paste ready.	3 / 3
Workflow Clarity	Sequenced workflows exist (e.g. get→check recurrence→instances, async meeting-room create→wait→list rsvp_status) and an error-troubleshooting table aids recovery, but batch/destructive operations like attendee batch_delete and event patch lack explicit validation checkpoints, which per the guidelines caps workflow clarity at 2.	2 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and all content is inline in a single ~240-line SKILL.md; sections are well-organized but background material such as the appendix could live in a separate reference, matching the score-2 anchor of content that should be separate being inline.	2 / 3
	Total	9 / 12 Passed

Description

57%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is clearly scoped to Feishu calendar management and lists relevant capability areas, but it relies on category nouns rather than concrete actions and omits an explicit "Use when" trigger clause, which caps specificity, trigger quality, and completeness at the mid level.

Suggestions

Rewrite the description with concrete verbs (e.g. "创建、修改、查询飞书日程，邀请与移除参会人，查询成员忙闲") instead of capability categories.

Add an explicit trigger clause such as "Use when the user asks to create or manage Feishu/飞书 calendar events, check schedules, or query free/busy time."

Include common user phrasings ("会议", "日程安排", "空闲时间") as trigger terms to improve natural keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ("飞书日历与日程管理工具集") and lists capability categories ("日历管理、日程管理、参会人管理、忙闲查询"), but these are noun categories rather than concrete verb actions like "create events" or "reply to invites", matching the score-2 anchor "Processes PDF files and extracts content" rather than the multi-verb score-3 example.	2 / 3
Completeness	It states what the skill does (calendar/schedule/attendee/free-busy management) but provides no explicit "when to use" guidance; per the judging guidelines, a missing "Use when..." clause caps completeness at 2.	2 / 3
Trigger Term Quality	It includes relevant natural terms a user might say ("日历", "日程", "忙闲查询") but offers no "Use when..." trigger clause and misses common phrasings like "创建会议" or "查询日程", fitting the score-2 anchor of some relevant keywords missing common variations.	2 / 3
Distinctiveness Conflict Risk	Scoping to "飞书日历" (Feishu calendar) carves out a clear niche with distinct triggers unlikely to conflict with other skills, matching the score-3 anchor of a clear niche with distinct triggers.	3 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/nexu
Path: nexu-skills/skills/feishu-calendar/SKILL.md
Commit: dadfb1c

Reviewed: about 16 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.