npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

wordpress-qc-skill

v0.1.0

Published

Holistic WordPress brief and staging-site QC with simple-English Google Docs reports.

Readme

wordpress-qc-skill

A public, installable WordPress QC skill for checking a staging site against an English client brief and producing a simple-English report.

Install as an agent skill

This package includes the standard SKILL.md entrypoint used by agent skill loaders. Install it with npm, then point Claude, Codex, or another compatible agent at the installed package directory:

npm install wordpress-qc-skill

The package directory contains SKILL.md, README.md, and the runnable QC command. For a global CLI install, use:

npm install --global wordpress-qc-skill

Run it

npx wordpress-qc-skill

The interactive runner asks for:

  • Public staging URL
  • Brief Google Docs URL, pasted brief, or local brief file
  • Optional previous QC report
  • Optional Google report recipients

For automation:

npx wordpress-qc-skill \
  --staging-url https://staging.example.com \
  --brief-file ./brief.txt \
  --previous-report ./previous-qc.md \
  --browser-adapter ./browser-adapter.mjs \
  --non-interactive --yes

Browser adapter

The package deliberately does not bundle a browser or silently download Chromium. The inbuilt browser or an external browser MCP is supplied by the host through a small adapter module:

export async function inspect({ stagingUrl, criteria, viewports, runId, approvals }) {
  // Use the host's inbuilt browser or external browser MCP here.
  // Return one result for each criterion.
  return {
    criteria: criteria.map((criterion) => ({
      id: criterion.id,
      status: "Pass", // Pass | Fail | Blocked | Not applicable
      expected: criterion.text,
      found: "...",
      fix: "...",
      howToVerify: "...",
      evidence: [{ label: "Mobile screenshot", path: "..." }],
    })),
  };
}

Point the runner at the adapter with either:

npx wordpress-qc-skill --browser-adapter ./browser-adapter.mjs

or:

export WORDPRESS_QC_BROWSER_ADAPTER=./browser-adapter.mjs

The adapter receives these standard viewports:

  • Desktop: 1440 × 900
  • Tablet: 768 × 1024
  • Mobile: 390 × 844

Form submissions and external-link testing are only approved when the corresponding flags are present:

--approve-form-tests --approve-external-links

Google Docs

Set GOOGLE_ACCESS_TOKEN for Google Docs input and report publishing. The token must have suitable Docs and Drive scopes. Reports are private by default; recipients are shared only when explicitly supplied with --report-recipient.

If Google Docs publishing fails, the runner keeps a local Markdown fallback under .scratch/wordpress-qc-skill/runs/.

Safety

The runner is read-only by default. It never edits WordPress, uses admin credentials, submits forms, sends messages, places orders, uploads files, or enters real personal/payment data. Public npm distribution does not publish client briefs, staging screenshots, OAuth tokens, or reports.

Development

npm test
node --test