SKILLEMALL.ai

CD wps-office-suite

WPS Office 全家桶 - 四引擎(WPS/MS Office/LibreOffice/纯Python)智能识别用户已安装软件,纯Python模式支持排序/筛选/图表/公式/统计,含文档模板(代码生成)、最佳实践案例、故障排除大章(20+避坑+15 FAQ+15错误ID 统一索引)、自动重试、硬件自适应、环境自检、Skill更新提醒;v5.0新增:定时任务注册管理(schtasks/crontab)、目录轮询监听(YAML规则+大文件分片)、使用统计与稳定性中心(SQLite埋点+引擎健康+引擎偏好)、COM三步自愈(regsvr32→修复安装→手动指引)、对话式数据查询(NL2SQL式意图解析+查询计划+连续追问)、multi-agent编排引擎桥接(白名单探测+流水线模板注册)

ClawHub Hermes author: fyniujin v5.0.0 MIT-0 48 files body ≈ 8 557 tokens Open the sourceclawhub.ai analyzed 2 d ago

WPS Office 全家桶 - 四引擎(WPS/MS Office/LibreOffice/纯Python)智能识别用户已安装软件,纯Python模式支持排序/筛选/图表/公式/统计,含文档模板(代码生成)、最佳实践案例、故障排除大章(20+避坑+15 FAQ+15错误ID…

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

IntegrationWordExcelPowerPointAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
69/100
safety, quality, tests
Safety 60%
90
Quality 40%
38
Run on models
none yet
Process rating
D
43/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

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

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.
  3. 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 · 2

✓ No critical or high findings

Medium and low: 2
  • medium Exfiltration net-redirectable-api-key scripts/document_translator.py:124
    Helper sends the API key to a host configured by an environment variable — the key can be redirected to another server
    API key + configurable base URL from environment
  • medium Exfiltration net-redirectable-api-key scripts/meeting_minutes.py:411
    Helper sends the API key to a host configured by an environment variable — the key can be redirected to another server
    API key + configurable base URL from environment

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

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: All mapping items must start at the same column at line 41, column 1: - 避坑指南 建议反馈邮箱: njskills@agent.qq.com ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-long-hermes description is 348 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
  • warning body-long SKILL.md body ≈ 8557 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "displayName"
  • note frontmatter-key unknown frontmatter key "slug"
  • note frontmatter-key unknown frontmatter key "permission"
  • note frontmatter-key unknown frontmatter key "dependency"
  • note frontmatter-key unknown frontmatter key "pricing"

Process rating: all ten parameters 43/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
  • 40Execution cost. Instruction body is 8557 tokens: crowds the task out of the window
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Steps. 16 steps
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. No mutating operations
  • low 15 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)
  • +3Output format is not stated: the model decides each time
  • -2167 emoji in the instructions: noise for the model
  • -311 of 41 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 348: enough signal without eating the budget
  • +4Structure: 85 headings
  • +3Step-by-step instructions: 16 items
  • +4Has examples (53 code blocks)

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

External checks

ClawHub: suspicious
This office automation skill needs Review because it under-discloses network AI data flows, scheduled tasks, and high-impact repair actions.
LLM: suspicious (high) · 1 Sept 2026