CtrlK
BlogDocsLog inGet started
Tessl Logo

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

69

Quality

83%

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

85%

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

The content is concise, well-structured, and has a clear workflow with validation, but actionability is held back by the absence of any executable API-call example for the core Feishu/Lark operations.

Suggestions

Add a short, copy-paste-ready example for a core action (e.g., a curl/Python snippet obtaining a tenant access token or sending a webhook message using the named env vars) to lift actionability to 3.

Optionally show one concrete MCP tool definition (e.g., `send_message`) with its expected inputs so the MCP setup path is fully executable.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with no padding or explanation of concepts Claude already knows; every section earns its place.

3 / 3

Actionability

It gives concrete specifics (env var names, endpoints, `deepseek mcp` commands, tool names) but provides no fully executable API-call example or code block, leaving key details for the core actions missing.

2 / 3

Workflow Clarity

A clear 6-step sequence includes an explicit verification checkpoint ("Verify with a dry run, sandbox document, or read-back call") plus a confirmation gate before externally visible actions.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references, the skill uses well-organized sections (Ground Rules, Common Use Cases, Workflow), satisfying the simple-skill criterion for a top score.

3 / 3

Total

11

/

12

Passed

Description

82%

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 specific and well-targeted to the Feishu/Lark niche with strong trigger terms, but it omits an explicit 'when to use' clause, capping completeness at 2.

Suggestions

Add an explicit trigger clause such as 'Use when integrating with Feishu, Lark, or 飞书 bots, docs, sheets, bitables, or approval workflows.' to raise completeness to 3.

DimensionReasoningScore

Specificity

Enumerates multiple concrete capabilities ("bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup"), matching the anchor for listing several specific actions rather than vague language.

3 / 3

Completeness

It clearly states what the skill does but lacks any explicit "Use when..." trigger clause, so per the judging guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Covers natural terms a user would say ("Feishu", "Lark", bots, docs, sheets, bitable, approval flows, OpenAPI/MCP), giving good keyword coverage.

3 / 3

Distinctiveness Conflict Risk

The Feishu/Lark niche is specific with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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
Hmbown/CodeWhale
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.