SKILLEMALL.ai
GitHub ↗ RU Sign in

AC analyze

对任意输入做结构化分析,数据/代码/文本/决策/可视化。Structured analysis for any input。Data, code,。Use when 需要数据分析、报表生成、统计洞察、数据可视化时使用。不适用于实时流数据处理。适用于独立开发者、企业团队和自动化工作流场景。支持中文交互，无需复杂配置即开即用。 text, decisions, visuals。Prioritize, question,。Use when 需要数据分析、报表生成、统计洞察、数据可视化时使用。不适用于实时数据流处理。

ClawHub Hermes author: 天轰穿 v1.0.0 MIT-0 2 files body ≈ 1 399 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

对任意输入做结构化分析,数据/代码/文本/决策/可视化。Structured analysis for any input。Data, code,。Use when…

As a process C 57/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

AnalyzerSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
79
Run on models
none yet
Process rating
C
57/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: analyze (ClawHub)

How to improve

  1. 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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 257 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • note frontmatter-key unknown frontmatter key "slug"
  • note frontmatter-key unknown frontmatter key "displayName"
  • note frontmatter-key unknown frontmatter key "summary"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "pricing_tier"

Process rating: all ten parameters 57/100

  • 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
  • 40Consistency. Frontmatter name (analyze) differs from the folder (code-analyze-2)
  • 60Result and completion. Output format stated, no completion criterion
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 35 steps
  • 100Execution cost. Instruction body is 1399 tokens
  • 100Running it twice. No mutating operations
  • low 22 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)
  • +2Single-language instructions
  • +3Description length 257: enough signal without eating the budget
  • +4Structure: 34 headings
  • +3Step-by-step instructions: 35 items
  • +3Output format is stated explicitly
  • +4Has examples (3 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
The skill is mostly a Markdown analysis template, but its documentation overstates capabilities like file writing, external API use, and command execution without clear scope or controls.
LLM: suspicious (medium) · 25 Aug 2026