SKILLEMALL.ai

BF feishu-omni-todo

飞书全场景Todo管理器,深度整合飞书生态。必须触发场景:用户发送待办事项、用户提到'/todo'指令、用户询问待办列表、用户要求保存待办、用户发送包含时间的任务安排、用户询问日历日程、用户要求同步到日历。支持多渠道消息(飞书/微信/短信等)接收Todo,自动同步飞书日历。

ClawHub Agent Skills author: zhangyu68 vv1.0.1 MIT-0 10 files body ≈ 1 039 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process F 35/100 · Will not run — References files that are not bundled: 链接

ReferencePersonal productivityInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
56
Run on models
none yet
Process rating
F
35/100
Will not run
References files that are not bundled: 链接
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
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.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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: 9. 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")
  • warning missing-ref reference to a missing file: 链接

Process rating: all ten parameters 35/100

Will not run. References files that are not bundled: 链接
  • 0Tools and files. 1 referenced file(s) missing: 链接
  • 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
  • 20When it triggers. No condition that starts the skill
  • 100Steps. 85 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1039 tokens
  • 100Running it twice. No mutating operations
  • medium 5 test cases, all positive: not one "should refuse" or "should ask first"
  • low No test case covers injection arriving through data

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)
  • +3Output format is not stated: the model decides each time
  • -5TODO / placeholder text left in the skill
  • -221 emoji in the instructions: noise for the model
  • -35 of 5 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 137: enough signal without eating the budget
  • +4Structure: 26 headings
  • +3Step-by-step instructions: 85 items
  • +4Has examples (4 code blocks)

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

External checks

ClawHub: suspicious
This Feishu todo skill is mostly aligned with todo and calendar management, but it can store and transmit task details using broad automatic triggers and hard-coded Feishu recipients.
LLM: suspicious (high) · VirusTotal: · 29 May 2026