Claude Wordpress Skills — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Claude Wordpress Skills (Plugin) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
Aggregate score unchanged between these scans.
The primary manifest — the file an agent reads to learn what this artifact does.
Professional WordPress engineering skills for Claude Code - performance optimization, security auditing, Gutenberg block development, and theme/plugin best practices.
| Skill | Description | Status |
|---|---|---|
| wp-performance-review | Performance code review and optimization analysis | ✅ |
| wp-security-review | Security audit and hardening code review | 🚧 |
| wp-gutenberg-blocks | Block Editor / Gutenberg development | 🚧 |
| wp-theme-development | Theme development best practices | 🚧 |
| wp-plugin-development | Plugin architecture and standards | 🚧 |
Subscribe to receive all skills and updates (Recommended):
# In Claude Code CLI
/plugin marketplace add elvismdev/claude-wordpress-skills
# Install specific skills
/plugin install claude-wordpress-skills@claude-wordpress-skillsgit clone https://github.com/elvismdev/claude-wordpress-skills.git ~/.claude/plugins/wordpressAdd as a git submodule for team-wide access:
# In your project root
git submodule add https://github.com/elvismdev/claude-wordpress-skills.git .claude/plugins/wordpress
git commit -m "Add WordPress Claude skills"Team members get the skills automatically when they clone or update the repo.
Download and extract specific skills:
# Copy just the performance review skill
cp -r skills/wp-performance-review ~/.claude/skills/When installed, these commands become available:
| Command | Description |
|---|---|
/wp-perf-review [path] | Full WordPress performance code review with detailed analysis and fixes |
/wp-perf [path] | Quick triage scan using grep patterns (fast, critical issues only) |
# Full review of current directory
/wp-perf-review
# Full review of specific plugin
/wp-perf-review wp-content/plugins/my-plugin
# Quick scan of a theme (fast triage)
/wp-perf wp-content/themes/my-theme
# Quick scan to check for critical issues before deploy
/wp-perf .| Aspect | /wp-perf-review | /wp-perf |
|---|---|---|
| Speed | Thorough (slower) | Fast triage |
| Depth | Full analysis + fixes | Critical patterns only |
| Output | Grouped by severity with line numbers | Quick list of matches |
| Use case | Code review, PR review, optimization | Pre-deploy check, quick audit |
When installed via marketplace, commands are namespaced:
/claude-wordpress-skills:wp-perf-review [path]
/claude-wordpress-skills:wp-perf [path]Skills also activate automatically based on context. Just ask naturally:
Review this plugin for performance issues
Audit this theme for scalability problems
Check this code for slow database queries
Help me optimize this WP_Query
Check my theme before launch
Find anti-patterns in this pluginClaude will detect the context and apply the appropriate skill.
| Skill | Trigger Phrases |
|---|---|
| wp-performance-review | "performance review", "optimization audit", "slow WordPress", "slow queries", "scale WordPress", "high-traffic", "code review", "before launch", "anti-patterns", "timeout", "500 error", "out of memory" |
Comprehensive performance code review covering:
Output includes severity levels (Critical/Warning/Info) with line numbers and fix recommendations.
🤝 Super welcome to contributions, please! See CONTRIBUTING.md for guidelines.
Ways to contribute:
MIT License — see LICENSE for details.
See CHANGELOG.md for version history.
Note: These skills represent community best practices for WordPress development and are not affiliated with or endorsed by any specific company or platform. Some patterns reflect my own experience with WordPress and from years of working alongside engineers far smarter than me - so bias is inevitable. Contributions are always welcome; I'm genuinely curious to hear different approaches and learn together.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.