SKILLEMALL.ai
GitHub ↗ RU Sign in

AC feishu-messaging

Best practices for Feishu (Lark) message configuration and formatting. Use when: (1) Configuring Feishu channel settings, (2) Experiencing message formatting issues (raw vs card), (3) Setting up renderMode for stable message display, (4) Understanding differences between auto-replies and proactive messages. Essential for ensuring consistent message formatting in Feishu chats.

modbender/skill-library-mcp Agent Skills author: modbender MIT 4 files body ≈ 1 268 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Best practices for Feishu (Lark) message configuration and formatting.

As a process C 59/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency

GeneratorSoftware developmentWriting and documentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
91
Run on models
none yet
Process rating
C
59/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 59/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 7 mutating operations with no state check
    • 40Consistency. Frontmatter name (feishu-messaging) differs from the folder (feishu-messaging-en)
    • 50Failures and branches. 0 branches, has a failure section
    • 60Result and completion. Output format stated, no completion criterion
    • 100Tools and files. No external tools needed
    • 100Steps. 28 steps
    • 100Execution cost. Instruction body is 1268 tokens

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +1No license
    • +2Single-language instructions
    • +3Description length 378: enough signal without eating the budget
    • +4Structure: 22 headings
    • +3Step-by-step instructions: 28 items
    • +3Output format is stated explicitly
    • +4Has examples (8 code blocks)
    • +4Reference files are cited in the instructions (2 of 2)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.