SKILLEMALL.ai

BC skill-discoverer

Skill Discoverer — Skill 广场发现者。自动发现 Skill 广场新上线 skill,或按工作背景智能推荐。将候选 skill 分类为工具型(直接安装)和增强型(会影响 agent 行为),对增强型提供三种处理方式:整体安装 / 内化学习(规则写入 MEMORY.md)/ 只应用无冲突部分。支持创建定时巡查任务,定期推送新 skill 日报。所有操作必须用户确认,保护已有 agent 体验不被破坏。触发词:帮我看看有没有新 skill、有没有新 skill、最近有新 skill 吗、skill 广场有什么新东西、智能推荐 skill、定时发现新 skill、每天帮我看新 skill、skill discoverer、daily skill digest。

ClawHub Agent Skills author: Dr23334444 v1.0.0 MIT-0 9 files body ≈ 1 837 tokens Open the sourceclawhub.ai analyzed 3 d ago

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

ProcedureAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
73
Run on models
none yet
Process rating
C
53/100
Has gaps
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: 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")
  • note frontmatter-key unknown frontmatter key "triggers"

Process rating: all ten parameters 53/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
  • 20When it triggers. No condition that starts the skill
  • 100Tools and files. No external tools needed
  • 100Steps. 29 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1837 tokens
  • 100Running it twice. No mutating operations

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
  • -231 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +3Description length 342: enough signal without eating the budget
  • +4Structure: 24 headings
  • +3Step-by-step instructions: 29 items
  • +4Has examples (15 code blocks)
  • +4Reference files are cited in the instructions (5 of 5)

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

External checks

ClawHub: suspicious
The skill is a coherent marketplace-discovery assistant, but it needs review because it automatically stores chat routing data and can read personal work context, schedule recurring messages, and persistently change agent behavior.
LLM: suspicious (high) · VirusTotal: · 29 May 2026