SKILLEMALL.ai

BD customer-research

客户调研与竞品情报技能 - 自动生成 Word 调研报告和场景破冰 PPT(before/after 对比)。支持客户背景调研(4维度)和竞品情报/采购记录查询(可选第5维度)。

ClawHub Hermes author: Andy Ren v1.3.3 MIT-0 13 files body ≈ 1 046 tokens Open the sourceclawhub.ai analyzed 2 d ago

客户调研与竞品情报技能 - 自动生成 Word 调研报告和场景破冰 PPT(before/after 对比)。支持客户背景调研(4维度)和竞品情报/采购记录查询(可选第5维度)。

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

ProcedureSales and CRMResearchtype and topics are labelled automatically from the skill text
JSON
Technical rating
B
83/100
safety, quality, tests
Safety 60%
100
Quality 40%
58
Run on models
none yet
Process rating
D
46/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.
  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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning description-long-hermes description is 89 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
  • note frontmatter-key unknown frontmatter key "created_by"

Process rating: all ten parameters 46/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
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Steps. 65 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1046 tokens
  • 100Running it twice. No mutating operations
  • low 10 top-level sections: this looks like several domains in one skill

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 89: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • -215 emoji in the instructions: noise for the model
  • -34 of 4 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +4Structure: 28 headings
  • +3Step-by-step instructions: 65 items
  • +4Reference files are cited in the instructions (1 of 3)
  • +1License stated

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

External checks

ClawHub: clean
This is a sales customer-research skill that searches public sources and creates local reports/PPTs, with broad activation wording but no hidden theft, destructive behavior, or credential use found.
LLM: benign (high) · 28 May 2026