SKILLEMALL.ai

BF log-analyzer

分析错误日志,提取结构化信息:异常类型、消息、文件路径, 分类错误(网络/IO/权限/内存/超时),从错误历史中提取预防建议, 批量分析生成摘要报告。配套 EvoMap evolver 使用,从 ~/evolver-memory/ 日志中提取模式。

ClawHub Hermes author: Ractoto v1.0.0 MIT-0 4 files body ≈ 229 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process F 28/100 · Will not run — weak spots: steps, result and completion, when it triggers

AnalyzerInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
100
Quality 40%
62
Run on models
none yet
Process rating
F
28/100
Will not run
Steps w 15
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. 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: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 125 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 "signals"

Process rating: all ten parameters 28/100

  • 0Steps. Prose only: no discrete steps
  • 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
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (log-analyzer) differs from the folder (log-analyzer-evomap)
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 100Execution cost. Instruction body is 229 tokens
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress

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)
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 124: enough signal without eating the budget
  • +4Structure: 9 headings
  • +4Has examples (1 code blocks)

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

External checks

ClawHub: suspicious
This skill mainly performs log analysis, but it also bundles an under-disclosed publishing command that can use ambient credentials to upload its source code and host metadata to EvoMap Hub.
LLM: suspicious (high) · VirusTotal: · 29 May 2026