CtrlK
BlogDocsLog inGet started
Tessl Logo

feishu-notify

Send notifications to Feishu/Lark. Internal utility used by other skills, or manually via /feishu-notify. Use when user says "发飞书", "notify feishu", or other skills need to send status updates.

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/skills-codex/feishu-notify/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

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

The body is well-structured and actionable, with concrete curl commands, a config schema, and a clear branching workflow plus an explicit verification step. Its main weakness is conciseness: the zero-impact / fail-open guarantee is repeated across five sections, inflating the token budget without adding information.

Suggestions

Consolidate the repeated fail-open / no-config guarantee into one place (e.g. Configuration) and have other sections reference it instead of restating it.

Provide at least one fully-resolved curl example (real title, body, color) for a representative event like review_scored so the push template is copy-paste ready.

Consider moving the Event Catalog table to a references file so SKILL.md stays a lean overview, reducing token load when the catalog is not needed.

DimensionReasoningScore

Conciseness

Mostly efficient (tables and code rather than concept exposition), but the fail-open / no-config-still-works point is restated across Overview, Configuration, Workflow Step 1, Helper Function, and Key Rules — unnecessary repetition that could be tightened, matching anchor 3.

3 / 5

Actionability

Provides concrete executable curl commands for push and interactive modes, a config JSON schema, and a specific card-template table; minor gaps remain because the curl payloads use unresolved placeholders (TITLE, BODY, COLOR) rather than a fully filled example, keeping it at 4.

4 / 5

Workflow Clarity

A clear four-step sequence (read config → branch on mode → send → verify delivery) with an explicit Verify step (check curl exit code, bridge-unreachable fallback) and a Key Rules checklist; not a 5 because fail-open design means there is no validate→fix→retry feedback loop.

4 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers and tables, and an appropriate external link to the feishu-claude-code bridge; the Helper Function and Key Rules sections partly restate earlier content and the Event Catalog could conceivably be a reference file, so it is not a 5.

4 / 5

Total

15

/

20

Passed

Description

82%Weight 40%Scale 1-5

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 strong: it explicitly covers both what the skill does and when to use it, with bilingual and slash-command trigger phrases that make it highly distinctive. Its only weakness is specificity — it states one generic action ("send notifications") rather than enumerating the concrete push/interactive capabilities.

DimensionReasoningScore

Specificity

"Send notifications to Feishu/Lark" names the domain and one concrete action, matching anchor 3 (domain + 1-2 actions); it does not list the multiple specific actions (push cards, interactive approve/reject, checkpoints) that would push it to 4-5.

3 / 5

Completeness

Explicitly answers both what ("Send notifications to Feishu/Lark... internal utility used by other skills, or manually via /feishu-notify") and when ("Use when user says \"发飞书\", \"notify feishu\", or other skills need to send status updates") with concrete trigger phrases, matching anchor 5.

5 / 5

Trigger Term Quality

Includes natural terms users would say — "发飞书", "notify feishu", plus synonyms Feishu/Lark and the /feishu-notify slash command — giving good coverage; a few natural variations (e.g. "lark notify", "send lark message") are missing, keeping it at 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Feishu/Lark notification is a clear niche with distinct, specialized triggers (发飞书, notify feishu, /feishu-notify) and minimal overlap risk with other skills, matching anchor 5.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
wanshuiyin/Auto-claude-code-research-in-sleep
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.