SKILLEMALL.ai
GitHub ↗ RU Sign in

AD feishu-bot-manager

Manage Feishu bots in OpenClaw configuration. Supports add, delete, update, list, and info operations. Triggers on phrases like "添加飞书机器人", "删除飞书机器人", "修改飞书机器人", "列出飞书机器人", "查看飞书机器人", "add feishu bot", "delete feishu bot", "update feishu bot", "list feishu bot".

ClawHub Agent Skills author: xiangxinag-princess v1.0.0 3 files · 1 script body ≈ 317 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process D 49/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches

ReferenceInfrastructuretype 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
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
D
49/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

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 49/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
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 1 mutating operations with no state check
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 4 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 317 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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 9 example trigger phrases
  • +3Description length 261: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 4 items
  • +4Has examples (6 code blocks)
  • +3All 1 scripts are documented

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

External checks

ClawHub: suspicious
This skill appears intended to manage Feishu bots, but it stores sensitive app secrets and makes broad persistent OpenClaw configuration changes with limited warning.
LLM: suspicious (high) · VirusTotal: · 29 May 2026