Skip to content
TrustedSkillsbeta
Back to all skills

Wordpress Testing Qa

Checked
bobmatnyc·vlatest·testing·MIT

Automates WordPress website testing, identifying bugs and performance issues based on specified scenarios and checklists.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add bobmatnyc/claude-mpm-skills --skill wordpress-testing-qa -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to 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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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

    Only contacts known or declared hosts: www.w3.org.

    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.

    Hosts contacted

    www.w3.orgstandards

  • 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
Manifest
toolchains/php/frameworks/wordpress/wordpress-testing-qa/SKILL.md
Scanned
3 files, 2,283 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to perform comprehensive testing and Quality Assurance (QA) tasks specifically tailored for WordPress sites. It automates the verification of site functionality, ensuring that custom plugins, themes, and core updates operate correctly without breaking existing features.

When to use it

  • Validating new theme or plugin installations before deploying them to a live production environment.
  • Running regression tests after updating WordPress core or server-side dependencies like PHP versions.
  • Verifying that specific user roles have the correct access permissions and content visibility.
  • Checking form submissions and e-commerce checkout flows for errors on staging environments.

Key capabilities

  • Automated functional testing of WordPress site components.
  • Verification of plugin and theme compatibility.
  • Regression analysis to detect unintended side effects from code changes.
  • Validation of user interface elements and interactive features.

Example prompts

  • "Run a full QA suite on my staging WordPress site to check if the new contact form submits correctly."
  • "Test the latest version of the WooCommerce plugin against my current theme to identify any layout conflicts."
  • "Verify that all admin dashboard links work properly after I updated the core WordPress installation."

Tips & gotchas

Ensure you are testing on a staging or local environment first, as automated tests can sometimes cause data inconsistencies if run directly on live production sites. Always back up your database and file system before initiating extensive QA cycles to prevent accidental data loss during test failures.