SKILLEMALL.ai
GitHub ↗ RU Sign in

CD feishu-bot-ops

飞书（Feishu/Lark）机器人运维大全 — 从部署到调试的全生命周期。覆盖 @mention 机制、bot 间通信、消息丢失排查、会话串线修复、WebSocket 连接稳定性、认证鉴权陷阱、交互卡片回调等 20+ 故障场景。

ClawHub Hermes author: Femi v1.0.1 MIT-0 5 files · 1 script body ≈ 3 301 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process D 45/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
C
70/100
safety, quality, tests
Safety 60%
70
Quality 40%
70
Run on models
none yet
Process rating
D
45/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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 · 6

✓ No critical or high findings

Medium and low: 6
  • medium Exfiltration net-credential-use references/at-mention-code-fix.md:78
    Credential used in a network call (verify the destination is the intended service)
    curl -s -H "Authorization: Bearer $TOKEN" \
  • medium Exfiltration net-credential-use SKILL.md:163
    Credential used in a network call (verify the destination is the intended service)
    curl -s -H "Authorization: Bearer $TOKEN" \
  • medium Exfiltration net-credential-use SKILL.md:389
    Credential used in a network call (verify the destination is the intended service)
    curl -s -H "Authorization: Bearer $TOKEN" \
  • medium Exfiltration net-credential-use SKILL.md:398
    Credential used in a network call (verify the destination is the intended service)
    curl -s -H "Authorization: Bearer $TOKEN" \
  • medium Exfiltration net-credential-use SKILL.md:447
    Credential used in a network call (verify the destination is the intended service)
    curl -s -H "Authorization: Bearer $TOKEN" \
  • medium Exfiltration net-credential-use SKILL.md:451
    Credential used in a network call (verify the destination is the intended service)
    curl -s -H "Authorization: Bearer $TOKEN" \

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

Against the Agent Skills spec

  • warning description-long-hermes description is 115 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill

Process rating: all ten parameters 45/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 5 mutating operations with no state check
  • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
  • 100Steps. 41 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3301 tokens
  • 100Progress reporting. Reports progress
  • low 14 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (3 tags): a typed call is more reliable

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)
  • +3Description length 115: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 47 headings
  • +3Step-by-step instructions: 41 items
  • +4Has examples (22 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +3All 1 scripts are documented

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

External checks

ClawHub: suspicious
This Feishu bot operations skill is coherent, but it gives broad recovery and access-control instructions that can disrupt a live bot or weaken who can use it.
LLM: suspicious (high) · VirusTotal: · 29 May 2026