BD wordpress-auto-publish
Automatically publish Markdown articles to WordPress blog via REST API
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
IntegrationWordPressWriting and documentstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 7
✓ No critical or high findings
Medium and low: 7
-
low Exfiltration
net-credential-usediagnose-jwt-remote.js:202Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)console.log(` curl -u '${USERNAME}:${PASSWORD}' \\`);quoted -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:49High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…9dM/mwVgvbZJaSNaRk+bshk…Kbz+IoId…W0Q==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:111High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…SDq+2kAA…MOe/+5cdoEdg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:152High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…FrF+LTRo…W3g==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:161High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…A6j+hAmM…GbS+kf5c…csw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:170High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…5bm+c2gQ…aG5+esrLODihIorn+Pe6F…dXA==",
detector -
low Secrets in code
secret-password-literaltest-new-password.js:24Hard-coded password / key literal (may be an example) (test fixture / example file)password: 'SAGI…mP1'
fixture
Files scanned: 69. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 46/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
- 30Running it twice. 6 mutating operations with no state check
- 40Consistency. Frontmatter name (wordpress-auto-publish) differs from the folder (test-wp)
- 100Tools and files. No external tools needed
- 100Steps. 5 steps
- 100Execution cost. Instruction body is 96 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 70: 120–800 characters recommended
- +4Structure: 2 headings, hard to scan
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Step-by-step instructions: 5 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.
External checks
ClawHub: suspicious
This WordPress publishing skill mostly matches its stated purpose, but it ships under-disclosed diagnostic and test scripts that handle credentials unsafely and can modify or permanently delete WordPress content.
LLM: suspicious (high) · VirusTotal: · 29 May 2026