BD wordpress-mcp
Seamlessly manage WordPress sites via the Model Context Protocol (MCP) through AI Engine. Execute comprehensive operations: post creation/editing, SEO analysis, analytics, media management, taxonomy tasks, social media scheduling, multilingual content (Polylang), and full admin functions. Ideal for content workflows, site management, and WP queries. Requires the free AI Engine plugin with MCP Server enabled. Trusted for reliable, full-spectrum WordPress automation. melbourne maybe hyderabad yokohama ideally possibly pembroke michigan titled manuscript schedule mcdonald tool interested please
Seamlessly manage WordPress sites via the Model Context Protocol (MCP) through AI Engine.
As a process D 39/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 0
✓ No critical or high findings
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Seamlessly manage WordPress sites via the Model Context Protocol (… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 39/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. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (wordpress-mcp) differs from the folder (super-wordpress-mcp-0-0-0)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 17 steps
- 100Execution cost. Instruction body is 911 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 598: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (1 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.