BD wp-seo-publisher
Publish SEO-optimized articles to WordPress via REST API with RankMath meta fields
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, failures and branches
IntegrationWordPressMarketingWriting and documentsInfrastructuretype 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Exfiltration
read-dotenvREADME.md:69Reads a .env filecp .env.example .env
-
low Exfiltration
read-dotenvREADME.md:90Reads a .env fileexport $(cat .env | grep "^WP_" | xargs)
-
low Exfiltration
read-dotenvREADME.md:144Reads a .env fileexport $(cat .env | grep "^WP_" | xargs)
-
low Exfiltration
read-dotenvREADME.md:173Reads a .env filecp skills/wp-seo-publisher/.env.example ~/.openclaw/workspace-marketing/.env
-
low Exfiltration
read-dotenvSKILL.md:49Reads a .env fileexport $(cat .env | grep "^WP_" | xargs)
Files scanned: 4. 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") - note
frontmatter-keyunknown frontmatter key "env_vars" - note
frontmatter-keyunknown frontmatter key "credentials"
Process rating: all ten parameters 48/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 6 mutating operations with no state check
- 40Consistency. Frontmatter name (wp-seo-publisher) differs from the folder (wp-auto-post-api)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 34 steps
- 100Execution cost. Instruction body is 1563 tokens
- 100Progress reporting. Reports progress
- low 12 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 82: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 16 headings
- +3Step-by-step instructions: 34 items
- +4Has examples (6 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.
External checks
ClawHub: clean
This is a disclosed WordPress publishing skill that can create drafts or posts, and its sensitive access matches that purpose.
LLM: benign (high) · VirusTotal: · 29 May 2026