SKILLEMALL.ai

CC web-notepad

(no description)

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

中型企业HR部门希望将纸质审批流程数字化,涉及请假、报销、调岗等多种审批单.

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

IntegrationSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
C
70/100
safety, quality, tests
Safety 60%
75
Quality 40%
63
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
When it triggers w 12
0
Inputs and preconditions w 11
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. 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 · 5

✓ No critical or high findings

Medium and low: 5
  • medium Exfiltration net-credential-use SKILL.md:68
    Credential used in a network call (verify the destination is the intended service)
    curl -X POST -H "Authorization: Bearer $WEB_NOTEPAD_API_KEY" \
  • medium Exfiltration net-credential-use SKILL.md:86
    Credential used in a network call (verify the destination is the intended service)
    curl -X POST -H "Authorization: Bearer $WEB_NOTEPAD_API_KEY" \
  • medium Exfiltration net-credential-use SKILL.md:99
    Credential used in a network call (verify the destination is the intended service)
    curl -X POST -H "Authorization: Bearer $WEB_NOTEPAD_API_KEY" \
  • medium Exfiltration net-credential-use SKILL.md:112
    Credential used in a network call (verify the destination is the intended service)
    curl -X POST -H "Authorization: Bearer $WEB_NOTEPAD_API_KEY" \
  • medium Exfiltration net-credential-use SKILL.md:123
    Credential used in a network call (verify the destination is the intended service)
    curl -X POST -H "Authorization: Bearer $WEB_NOTEPAD_API_KEY" \

Files scanned: 2. 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: Not a YAML token: 功能涵盖:。Use when 需要安全检测、合规审计、漏洞扫描、加密防护时使用。不适用于渗透测试未授权目标。适用于独立开发者、企业团队和自动化工作流场景。支持中文交互,无需复杂配置即开即用。输出结果可直接使用,减少二次加工成本。提供结构化输出和错误处理机制。支持多场景应用和灵活配置。具备完整的输入输出规范。 at line 10, column 17: description: |- 功能涵盖:。Use when 需要安全检测、合规审计、漏洞扫描、加密防护时使用。不适用于渗透测试未授权目标。适用于独立开发者、… ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-long-hermes description is 306 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 "summary_zh"
  • note frontmatter-key unknown frontmatter key "edition"
  • note frontmatter-key unknown frontmatter key "tools"

Process rating: all ten parameters 51/100

  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 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
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 33 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2767 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 0: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 48 headings
  • +3Step-by-step instructions: 33 items
  • +4Has examples (7 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This skill is mostly a form-management guide, but mixed security-review claims and examples for live API changes, webhooks, exports, and permission changes need human review before installation.
LLM: suspicious (high) · 2 Aug 2026