CtrlK
BlogDocsLog inGet started
Tessl Logo

feishu-create-doc

创建飞书云文档。从 Lark-flavored Markdown 内容创建新的飞书云文档,支持指定创建位置(文件夹/知识库/知识空间)。

50

Quality

55%

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-create-doc/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 a thorough, highly actionable reference for Feishu document creation with concrete examples, but it is a large monolith with no external reference files and its multi-step workflows lack explicit validation checkpoints.

Suggestions

Move the large '内容格式' (Lark-flavored Markdown block reference) into a separate references file (e.g. LARK_MARKDOWN.md) and keep SKILL.md as a concise overview pointing to it.

Express the media-insertion and long-doc append workflows as explicit numbered steps with validation checkpoints (e.g. verify doc_id returned before appending).

Trim soft stylistic guidance and consolidate the '写作指南' and '最佳实践' sections to reduce token load.

DimensionReasoningScore

Conciseness

Much of the body is Feishu-specific XML syntax Claude does not know, so it earns its place, but the ~720-line length includes soft guidance ('应当尽量结构清晰,样式丰富,有很高的可读性') and writing-guide/best-practice sections that could be tightened or moved out.

3 / 5

Actionability

Provides six concrete, copy-paste-ready JSON call examples plus extensive per-block syntax code samples; minor gaps remain (no end-to-end example with outputs or media-insertion full sequence), keeping it just below a 5.

4 / 5

Workflow Clarity

The main create is a single unambiguous call, but the multi-step workflows that are described (long-doc append via update-doc, media insertion: create-doc → feishu_doc_media → update-doc append) are prose-only with no explicit numbered sequence or validation checkpoints.

3 / 5

Progressive Disclosure

The body is well-structured with clear section headers, but no bundle files exist (references/scripts/assets all missing) and the entire ~600-line Lark-flavored Markdown reference is inlined in SKILL.md rather than split into a one-level-deep reference file.

3 / 5

Total

13

/

20

Passed

Description

53%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 clearly identifies a specific Feishu-doc creation capability and its location options, but it lacks an explicit 'when to use' trigger clause and broader natural synonyms, which limits completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g. when the user asks to create a Feishu/Lark document from markdown).

Broaden trigger terms with natural synonyms users actually say, such as '飞书文档', 'Lark 文档', and '创建文档'.

Mention the relationship to sibling skills (e.g. update-doc, feishu_doc_media) to clarify when create-doc is the right choice versus updating an existing doc.

DimensionReasoningScore

Specificity

Names the domain ('飞书云文档') and concrete actions ('从 Lark-flavored Markdown 内容创建', '支持指定创建位置(文件夹/知识库/知识空间)'), but the core capability is a single create action with location options rather than multiple distinct actions, so it is not comprehensive enough for a 4.

3 / 5

Completeness

It clearly states what the skill does ('创建飞书云文档...从 Lark-flavored Markdown 内容创建') but provides no 'Use when...' trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant natural terms like '飞书云文档', 'Lark-flavored Markdown', '文件夹/知识库/知识空间', but lacks common synonyms or variations users might say (e.g. '飞书文档', 'Lark doc', file tokens), placing it at 'some relevant keywords but missing variations'.

3 / 5

Distinctiveness Conflict Risk

Targets a specific platform niche ('飞书云文档' via MCP create-doc) with distinct triggers, with only minor overlap risk against closely related Feishu doc skills such as update-doc referenced in the body.

4 / 5

Total

13

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (720 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

14

/

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.