wordpress-mcp-dev
Skill49 starsChanged 8 months agoMITView on GitHub
Build and maintain modern WordPress plugins and MCP servers, including hybrid WordPress+MCP products. Use when implementing plugin architecture (PHP, REST API, Gutenberg/admin/page-builder integrations), MCP tooling (TypeScript/Python, stdio/HTTP transport), security hardening, licensing/updates, and delivery workflows from scaffold to distribution.
In this repository55 other files it gives its agents.
- activity-report-composerSkill
- art-directionSkill
- brand-voice-synthesizerSkill
- build-elementor-pageSkill
- build-oxygen6-pageSkill
- content-portabilitySkill
- conversion-auditSkill
- custom-post-type-architectSkill
- design-system-synthesizerSkill
- figma-to-bricksSkill
- figma-to-diviSkill
- figma-to-elementorSkill
- figma-to-gutenbergSkill
- html-to-breakdanceSkill
- html-to-bricksSkill
- html-to-pageSkill
- internal-link-builderSkill
- migrate-beaver-builder-to-bricksSkill
- migrate-beaver-builder-to-gutenbergSkill
- migrate-brizy-to-gutenbergSkill
- migrate-divi-to-breakdanceSkill
- migrate-divi-to-bricksSkill
- migrate-divi-to-gutenbergSkill
- migrate-elementor-to-breakdanceSkill
- migrate-elementor-to-bricksSkill
- migrate-elementor-to-gutenbergSkill
- migrate-elementor-to-oxygenSkill
- migrate-oxygen-to-breakdanceSkill
- migrate-oxygen-to-bricksSkill
- migrate-thrive-architect-to-gutenbergSkill
- migrate-visual-composer-to-gutenbergSkill
- migrate-wpbakery-to-bricksSkill
- migrate-wpbakery-to-gutenbergSkill
- mobile-experience-reportSkill
- murmur-review-loopSkill
- page-template-librarySkill
- prime-the-agentSkill
- respira-builder-editsSkill
- respira-setup-assistantSkill
- respira-site-auditSkill
- respira-woocommerceSkill
- respira-workflowSkill
- seo-aeo-amplifierSkill
- site-onboardingSkill
- stale-content-detectorSkill
- technical-debt-auditSkill
- woo-agent-storefrontSkill
- woo-catalog-perfectionSkill
- woocommerce-health-checkSkill
- woo-marketing-campaignsSkill
- woo-pricing-promotionsSkill
- wordpress-ai-image-optimizerSkill
- wordpress-editing-safetySkill
- wordpress-security-reviewSkill
- wordpress-site-dnaSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use this skill to ship production-grade WordPress plugins, MCP servers, or both together.
- Distinctive: line 22
Add safety controls before expanding scope: capability checks, nonce/auth, sanitized errors, and rollback strategy.
- Distinctive: line 27
Keep plugin bootstrap thin.
- Distinctive: line 29
Treat MCP tool schemas/descriptions as API contracts for model behavior.
- Distinctive: line 31
Prefer duplicate-first content edits for AI-assisted write operations.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
WordPress + MCP Development
Use this skill to ship production-grade WordPress plugins, MCP servers, or both together.
Workflow
- Identify target product shape:
plugin,mcp-server, orhybrid. - Choose architecture and scaffold from the relevant reference.
- Implement minimum viable vertical slice first:
- Plugin: one secure REST route + one real feature path.
- MCP: one read-only tool + one mutating tool with safe validation.
- Hybrid: one plugin endpoint consumed by one MCP tool.
- Add safety controls before expanding scope: capability checks, nonce/auth, sanitized errors, and rollback strategy.
- Validate against checklists before release.
Guardrails
- Keep plugin bootstrap thin; place behavior in namespaced classes.
- Prefix all plugin symbols to avoid collisions.
- Treat MCP tool schemas/descriptions as API contracts for model behavior.
- Return actionable errors and avoid leaking secrets.
- Prefer duplicate-first content edits for AI-assisted write operations.
References
- Core guide:
references/full-guide.md - WordPress plugin architecture and security sections:
references/full-guide.md - MCP server design, transport, and tooling sections:
references/full-guide.md - Lifecycle, testing, and distribution checklists:
references/full-guide.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.