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.

68

Quality

81%

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 skill body is concise, well-structured, and presents a clear validated workflow with concrete credential and CLI guidance. The only notable gap is the absence of executable API/token code examples that would lift actionability to fully copy-paste ready.

Suggestions

Add a short executable snippet for a common operation, e.g. obtaining a tenant access token via curl against open.feishu.cn/openapis/auth/v3/tenant_access_token/internal.

Show one minimal webhook send example using the FEISHU_WEBHOOK_URL and FEISHU_WEBHOOK_SECRET env vars so the credential pattern is demonstrated end-to-end.

Optionally note the Feishu-vs-Lark host split inside the workflow step that issues API calls, anchoring the endpoint choice to the clarified target.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it explains no concepts and every line (ground rules, use cases, workflow) earns its place with no padding.

5 / 5

Actionability

Provides concrete env var names and executable CLI commands ('codewhale mcp add', 'codewhale mcp validate', 'codewhale mcp tools'), but lacks actual API-call or token-request code examples, leaving minor gaps in executable detail.

4 / 5

Workflow Clarity

A clear six-step sequence includes an explicit validation checkpoint (step 6: dry run / sandbox / read-back) and a feedback loop before externally visible actions, plus a confirmation gate for destructive operations.

5 / 5

Progressive Disclosure

Under 50 lines, single-purpose, and organized into well-signaled sections (Ground Rules, Common Use Cases, Workflow) with no need for external bundle files — meeting the simple-skill exception for a top score.

5 / 5

Total

19

/

20

Passed

Description

70%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 specific and clearly niche, naming concrete Feishu/Lark surfaces and a credential-safety constraint. It falls short on completeness by omitting an explicit 'Use when...' trigger clause within the description itself.

Suggestions

Add an explicit trigger clause to the description, e.g. 'Use when the user asks for Feishu, Lark, or 飞书 integration.'

Replace the generic verb 'Work with' with discrete actions such as 'send bot messages, read and write docs/sheets/bitables, and configure MCP servers'.

Include the '飞书' synonym in the description so the natural Chinese trigger term is captured at the description level.

DimensionReasoningScore

Specificity

Lists several concrete targets ('bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup') plus a concrete constraint ('without hardcoding credentials'), but uses the generic verb 'Work with' rather than naming discrete actions, leaving minor gaps.

4 / 5

Completeness

Provides a clear 'what' (Feishu/Lark integration across multiple surfaces) but the description itself lacks an explicit 'Use when...' trigger clause — the 'when' appears only in the body — which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes the natural product names 'Feishu' and 'Lark' that users actually say, but omits the common Chinese synonym '飞书' (present only in the body) and lacks file-extension or token-type trigger phrases.

4 / 5

Distinctiveness Conflict Risk

Targets a clearly niche platform (Feishu/Lark) with distinct product-name triggers, making it unlikely to fire for unrelated skills.

5 / 5

Total

16

/

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
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.