CtrlK
BlogDocsLog inGet started
Tessl Logo

feishu-channel-rules

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

66

Quality

80%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 an exemplar of lean, actionable instruction for a simple always-on skill: concise directives, clear sections, and a well-signaled reference to Lark Markdown syntax. The only soft spot is actionability, which relies on prose directives rather than concrete examples.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence ('talk like a coworker, not a manual', 'Get to the point and stop'), with no padding and no explanation of concepts Claude already knows, matching 'Lean and efficient; every token earns its place'.

5 / 5

Actionability

Directives are concrete and specific ('Prefer plain sentences over bullet lists when a brief answer suffices', 'refer to references/markdown-syntax.md'), giving mostly actionable guidance; as an instruction-only skill the absence of code is acceptable, but it stops short of maximally concrete example-rich instruction, fitting 'concrete guidance with minor gaps'.

4 / 5

Workflow Clarity

This is a simple, single-purpose, always-active skill under 50 lines with an unambiguous single action (apply these output-style rules in Lark) and no destructive or batch operations, so per the simple-skills note it qualifies for the top score.

5 / 5

Progressive Disclosure

The body is well-organized into clear sections and signals a real, one-level-deep reference via 'refer to `references/markdown-syntax.md`' (verified to exist), matching 'Clear overview with well-signaled one-level-deep references'.

5 / 5

Total

19

/

20

Passed

Description

68%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 distinctive and carries an explicit always-on trigger, but it stays vague about what the skill actually does, naming the domain without enumerating concrete capabilities. Tightening 'output rules' into specific actions would lift specificity and completeness.

Suggestions

Replace the generic 'output rules' with 1-2 concrete actions, e.g. 'Keep replies short and conversational, prefer plain sentences over bullet lists, and follow Lark Markdown quirks.'

Keep the explicit 'Always active in Lark conversations' trigger but pair it with the concrete actions so the 'what' is as clear as the 'when'.

DimensionReasoningScore

Specificity

The description names the domain ('Lark/Feishu channel output rules') but lists no concrete actions, matching the anchor 'Names the domain but actions are minimal or generic'; it is above 1 because the domain is clearly named, but not 3 because no specific capabilities are enumerated.

2 / 5

Completeness

It states both a 'what' ('channel output rules') and an explicit 'when' ('Always active in Lark conversations'), so it is not capped at 3 for missing trigger guidance; the 'what' is somewhat generic, fitting 'Has both what and when; when could be more explicit or specific' rather than the fully concrete anchor 5.

4 / 5

Trigger Term Quality

It includes natural product terms a user would say ('Lark/Feishu', 'channel', 'Lark conversations') with good synonym coverage of both product names, matching 'Good keyword coverage; a few natural terms missing'; not 5 because no broader synonym set or file extensions are present.

4 / 5

Distinctiveness Conflict Risk

Tightly bound to the Lark/Feishu platform with platform-specific triggers, giving a clear niche with minimal overlap risk, matching 'Clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

15

/

20

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.