Wordpress Security Validation
CheckedHelps with security, validation as part of implementing security and authentication workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add bobmatnyc/claude-mpm-skills --skill wordpress-security-validation -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
bobmatnyc
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned bobmatnyc/claude-mpm-skills at 718070a7d6.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 718070a7d6
- Scanned
- 3 files, 1,895 lines
About this skill
The wordpress-security-validation skill empowers AI agents to audit WordPress installations for common vulnerabilities and misconfigurations. It systematically checks security headers, plugin integrity, and file permissions to ensure the site adheres to best practices.
When to use it
- Before deploying a new WordPress site to production to catch critical flaws early.
- During routine maintenance cycles to verify that recent updates haven't introduced security gaps.
- When troubleshooting unexplained performance drops or suspicious activity logs.
- As part of a pre-audit checklist for clients requiring compliance with security standards.
Key capabilities
- Validates standard WordPress security headers like X-Frame-Options and Content-Security-Policy.
- Scans installed plugins and themes against known vulnerability databases.
- Checks file permissions on core directories to prevent unauthorized modifications.
- Identifies outdated software versions that may expose the site to exploits.
Example prompts
- "Run a full security validation on my WordPress site at [URL] and list any high-risk issues found."
- "Check if all plugins and themes on this WordPress installation are up to date and free of known CVEs."
- "Audit the file permissions of the wp-content directory and report any world-writable files."
Tips & gotchas
Ensure you have write access or appropriate credentials for the target WordPress site, as some checks require server-level inspection. This skill complements but does not replace a full manual penetration test; it focuses on automated validation of common security configurations.