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, well-crafted skill description. It concisely covers what the skill does (send notifications to Feishu/Lark via webhook or bidirectional modes), when to use it (explicit trigger phrases in both Chinese and English), and how it relates to other skills (internal utility). The multilingual trigger terms and platform-specific focus make it highly distinctive.
| 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 both what ('Send notifications to Feishu/Lark, supports push-only and interactive modes') and when ('Use when user says "发飞书", "notify feishu", or other skills need to send status updates'). Explicit trigger guidance is present. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms in both Chinese ('发飞书') and English ('notify feishu'), plus mentions 'Feishu/Lark' covering both brand names, and 'status updates' as a use case keyword. Good multilingual coverage. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific platform (Feishu/Lark), a specific action (notifications/webhooks), and includes unique trigger terms in Chinese. Very unlikely to conflict with other skills. | 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 curl commands, config format, and branching logic are all concrete and executable. The main weakness is moderate verbosity — the 'zero-impact guarantee' and no-op behavior are restated multiple times, and the event catalog could be externalized to improve conciseness and progressive disclosure.
Suggestions
Move the Event Catalog table to a separate EVENTS.md reference file and link to it, reducing SKILL.md length and improving progressive disclosure.
Consolidate the repeated 'config absent = no-op' messaging into a single clear statement in the Key Rules section rather than restating it in Overview, Configuration, Helper Function, and Key Rules.
| 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 guidance is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 4-step workflow with explicit validation (Step 4: verify delivery), fallback behavior (interactive → push → silent), timeout handling, and error recovery. The branching logic in Step 1 is well-defined with explicit outcomes for each config state. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but the event catalog and helper function pattern could be split into separate reference files. For a skill of this length (~150 lines of content), some inline detail like the full event catalog table would be better as a linked reference. | 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
700fbe2
- 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.