SKILLEMALL.ai

AB huawei-cloud-mrs-redis-meta-check

Checks Redis cluster metadata files (nodes-*.conf) for integrity, detecting 7 categories of metadata issues that cause Redis instance startup failures, connection anomalies, and fault alerts. 执行7项检查:slot槽位完整性、master/slave实例个数、文件格式(4个模块)、文件名端口一致性、端口关系、主备关系、myself标记。 Use this skill when the user mentions Redis metadata file checks, nodes-*.conf checks, or Redis cluster configuration checks. Use it whenever the user asks about Redis startup failures or connection anomalies. Trigger: "Redis元数据检查", "Redis nodes检查", "Redis cluster配置检查", "检查Redis元数据", "Redis元数据校验", "Redis启动失败排查"

ClawHub Agent Skills author: huaweicloud-skills-team v1.0.0 MIT-0 3 files body ≈ 5 244 tokens Open the sourceclawhub.ai analyzed 4 d ago

Checks Redis cluster metadata files (nodes-.conf) for integrity, detecting 7 categories of metadata issues that cause Redis instance startup failures…

As a process B 76/100 · Nearly there — no weak spots found

ProcedureData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
B
76/100
Nearly there
Tools and files w 18
60
Result and completion w 14
60
When it triggers w 12
70
the three weakest of ten parameters · all ten

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5244 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 76/100

  • 60Tools and files. Uses tools (bash, python, node) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 5244 tokens
  • 85Steps. 104 steps, 3 vague phrases
  • 100Failures and branches. 4 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • low 11 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

  • +4Description does not say when NOT to use the skill (false activations)
  • -41 reference files, but SKILL.md never points to them: the model will not open them
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 6 example trigger phrases
  • +3Description length 578: enough signal without eating the budget
  • +4Structure: 31 headings
  • +3Step-by-step instructions: 104 items
  • +3Output format is stated explicitly
  • +4Has examples (9 code blocks)

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

External checks

ClawHub: suspicious
The skill is mostly a Redis metadata checker, but it also includes overbroad cloud permission guidance and production repair steps that users should review carefully before use.
LLM: suspicious (medium) · 10 Sept 2026