CtrlK
BlogDocsLog inGet started
Tessl Logo

feishu-channel-rules

Lark/Feishu channel output rules. Always active in Lark conversations.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./资料/feishu-openclaw-plugin/package/skills/feishu-channel-rules/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a tight, well-organized instruction-only skill: concise writing directives, an unambiguous single action, and a single clearly-signaled reference to a real bundle file. It exemplifies lean progressive disclosure appropriate to its scope.

DimensionReasoningScore

Conciseness

The body is lean — five short bullets and two sections — assumes Claude's competence, and every token earns its place, matching the 'Lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

It gives concrete, specific directives such as 'Prefer plain sentences over bullet lists when a brief answer suffices'; as an instruction-only skill, code is not required and the guidance is actionable, fitting the top anchor.

3 / 3

Workflow Clarity

This is a simple, single-purpose skill whose single action (apply these writing rules) is unambiguous; per the simple-skills note, workflow clarity scores 3 without a multi-step sequence, and no destructive/batch operation needs validation.

3 / 3

Progressive Disclosure

The body is under 50 lines with well-organized sections (Writing Style, Note) plus one clearly-signaled, one-level-deep reference to references/markdown-syntax.md, which exists in the bundle, matching the top anchor.

3 / 3

Total

12

/

12

Passed

Description

40%

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 names the Lark/Feishu domain and gives an explicit 'when' (always active in Lark conversations), but it is thin and category-style, listing no concrete actions and relying on the generic phrase 'output rules'. Trigger-term and distinctiveness coverage are present but mediocre.

Suggestions

Replace 'channel output rules' with concrete actions the skill performs, e.g. 'Formats Lark/Feishu channel messages for brevity, plain-sentence replies, and Lark-compatible Markdown.'

Add a 'Use when...' trigger clause listing natural user phrases (e.g. 'Use when replying in Lark/Feishu channels or when the user mentions Feishu/Lark formatting').

Add common term variations (Feishu, Lark, channel messages, group chat replies) to strengthen trigger-term quality and distinctiveness.

DimensionReasoningScore

Specificity

The phrase 'channel output rules' names a domain but lists no concrete actions, matching the 'Vague or no actions; abstract language' anchor; it does not reach score 2 because no specific actions are named.

1 / 3

Completeness

An explicit when is given ('Always active in Lark conversations'), but the what ('channel output rules') is vague rather than comprehensive; it is above 1 because both what and when are present, but below 3 because the what is not clearly comprehensive.

2 / 3

Trigger Term Quality

Natural platform keywords 'Lark/Feishu', 'channel', and 'conversations' are present, but 'output rules' is generic and common variations are missing, fitting the 'Some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

It is tied to the Lark/Feishu niche, but 'output rules' is generic and could overlap with general output-style skills, matching the 'Somewhat specific but could still overlap' anchor.

2 / 3

Total

7

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
op7418/CodePilot
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.