Wp Plugin Development
WordPress plugin architecture review for Codex. Use when reviewing plugin structure, lifecycle hooks, Settings API usage, CPT and taxonomy registration, hook design, i18n, and WordPress.org readiness.
Install
$ agentstack add skill-jorgerosal-wordpress-skills-wp-plugin-development ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jorgerosal-wordpress-skills-wp-plugin-development) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Codex WordPress Plugin Development Review
Purpose
Use this skill when Codex needs to review the architecture and standards of a WordPress plugin rather than only its security or performance characteristics.
Focus Areas
- Main plugin file and header quality
- Activation, deactivation, and uninstall flows
- Namespacing, prefixing, and collision avoidance
- Settings API, CPT, taxonomy, and REST registrations
- Hook placement, plugin structure, and i18n
- WordPress.org and Plugin Check readiness
Workflow
- Detect the plugin context: WordPress.org, private plugin, mu-plugin, or drop-in.
- Review the main bootstrap file, structure, and lifecycle hooks first.
- Check CPTs, taxonomies, settings, REST routes, and i18n patterns.
- Use shared reference docs only where deeper detail is needed.
- Report findings with severity, file references, architectural impact, and suggested fixes.
Reference Files
Load only the references you need from:
../../claude-skills/wp-plugin-development/references/architecture-patterns.md../../claude-skills/wp-plugin-development/references/api-patterns.md../../claude-skills/wp-plugin-development/references/hooks-guide.md../../claude-skills/wp-plugin-development/references/oop-patterns.md
Output
- Group findings by severity
- Include file references and plugin-context notes where relevant
- Distinguish review blockers from modernization suggestions
- Suggest fixes that fit common WordPress plugin conventions
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jorgerosal
- Source: jorgerosal/wordpress-skills
- License: MIT
- Homepage: https://jorgerosal.github.io/wordpress-skills/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.