SKILLEMALL.ai
RU Sign in

BC sample-customer-q2-faq

示例客户季度业务分析问答集（演示脱敏版）。仅保留分析框架与问答结构，项目编号、线路地名、中标细节、业务费成因等事实层信息均已虚构化或泛化，不含真实商业安排。面向销售/管理层演示查询流程，或作为同类 FAQ skill 模板。

ClawHub Hermes author: longtel-skill v1.0.0 MIT-0 6 files body ≈ 1 496 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

示例客户季度业务分析问答集（演示脱敏版）。仅保留分析框架与问答结构，项目编号、线路地名、中标细节、业务费成因等事实层信息均已虚构化或泛化，不含真实商业安排。面向销售/管理层演示查询流程，或作为同类 FAQ skill 模板。

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

ReferenceCustomer supportInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
61
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.
  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: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 112 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 "maintainer"
  • note frontmatter-key unknown frontmatter key "created-at"
  • note frontmatter-key unknown frontmatter key "updated-at"

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. 33 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1496 tokens
  • 100Running it twice. No mutating operations
  • low 16 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 112: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 29 headings
  • +3Step-by-step instructions: 33 items
  • +4Has examples (1 code blocks)
  • +1License stated

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

External checks

ClawHub: clean
This is a static, disclosed demo FAQ skill using redacted business-analysis sample content and does not request execution, credentials, persistence, or external access.
LLM: benign (high) · VirusTotal: · 27 Aug 2026