feishu-notify
Send notifications to Feishu/Lark. Internal utility used by other skills, or manually via /feishu-notify. Supports push-only (webhook) and interactive (bidirectional) modes. Use when user says "发飞书", "notify feishu", or other skills need to send status updates.
89
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies its purpose (Feishu/Lark notifications), specifies its modes of operation, and provides explicit trigger guidance in multiple languages. It effectively communicates both its direct user-facing use and its role as an internal utility for other skills, making it easy to distinguish and select appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists concrete actions: send notifications, push-only webhook mode, interactive bidirectional mode. Also specifies it's an internal utility used by other skills and can be triggered manually via /feishu-notify. | 3 / 3 |
Completeness | Clearly answers 'what' (send notifications to Feishu/Lark, supports push-only and interactive modes) and 'when' (explicit 'Use when' clause with trigger phrases and contextual triggers like other skills needing status updates). | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms in both Chinese ('发飞书') and English ('notify feishu'), mentions the slash command '/feishu-notify', and covers the use case of other skills needing to 'send status updates'. Good coverage of how users would naturally invoke this. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche targeting Feishu/Lark specifically, with platform-specific terminology and even Chinese trigger terms. Unlikely to conflict with other notification or messaging skills due to the specific platform focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted utility skill with strong actionability and workflow clarity. The executable curl commands, clear branching logic, and explicit fallback behaviors make it highly usable. The main weaknesses are moderate verbosity from repeated emphasis on the no-op/fail-open behavior and the event catalog being inline rather than in a separate reference file.
Suggestions
Consolidate the repeated 'config absent = no-op' messaging into a single prominent note rather than restating it in Overview, Configuration, Helper Function, and Key Rules sections.
Consider moving the Event Catalog table to a separate EVENTS.md reference file, keeping just a brief mention and link in the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary explanation (e.g., repeated emphasis on 'zero-impact guarantee', multiple restatements that absent config means no-op). The helper function section and event catalog add useful reference but the overall content could be tightened by ~20-30%. | 2 / 3 |
Actionability | Provides fully executable curl commands for both push and interactive modes, concrete JSON config format, specific card templates with color codes, and clear bash commands for each step. The code is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 4-step workflow with explicit validation (Step 4: verify delivery), well-defined branching logic at Step 1, fallback behavior for interactive mode failures, and timeout handling. The feedback loop for interactive mode (send → poll → timeout fallback) is explicit. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but everything is inline in a single file. The event catalog and card templates could be split into separate reference files. For a skill of this length (~150 lines), some separation would improve scannability. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
dc00dfb
- Reviewed
Table of Contents
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.