DF wechat-publisher-skill
(no description)
As a process F 30/100 · Will not run — References files that are not bundled: docs/block_layout.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
- The text references files that are not there: add them or drop the references.
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
medium Secrets in code
secret-labelled-tokendocs/install-guide.md:57Labelled token / key literal (vendor format unknown — verify it is not a live credential)? Enter your 公众号 AppSecret: 44c1…454
-
medium Secrets in code
secret-labelled-tokendocs/install-guide.md:285Labelled token / key literal (vendor format unknown — verify it is not a live credential)app_secret: 44c1…454
-
medium Dangerous commands
cmd-execpolicy-bypassdocs/troubleshooting.md:153Runs PowerShell with execution policy bypassedpowershell -ExecutionPolicy Bypass -File ~/.openclaw/workspace/memory/wech…ps1
-
medium Secrets in code
secret-labelled-tokendocs/troubleshooting.md:261Labelled token / key literal (vendor format unknown — verify it is not a live credential)$AppSecret = "44c1…454"
Files scanned: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger - warning
missing-refreference to a missing file: docs/block_layout.md
Process rating: all ten parameters 30/100
- 0Tools and files. 1 referenced file(s) missing: docs/block_layout.md
- 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
- 30Running it twice. 4 mutating operations with no state check
- 100Steps. 41 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 944 tokens
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
- -233 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 22 headings
- +3Step-by-step instructions: 41 items
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (2 of 7)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.