{ }
Resource profile / WordPress Project Triage
About this skill

Workflow & requirements

Installed package paths (BB Skills adaptation, 2026-10-03)

Set BB_SKILL_DIR to the absolute directory containing this installed SKILL.md. For the default CLI destination, run export BB_SKILL_DIR="$PWD/.agents/skills/wp-project-triage" from your project root. If you chose another destination, assign that absolute folder instead. Keep the working directory at the WordPress project root when running the detector commands below; do not change into the skill directory. On PowerShell set $env:BB_SKILL_DIR and use $env:BB_SKILL_DIR in place of the Bash variable in command arguments.

Only helper command paths and this installation note are adapted. The unchanged original instructions are in upstream-original/SKILL.md; references, scripts and license notices retain their upstream bytes. These commands print inspection hints and do not run recommended build or database operations. Review the scripts before executing them.

WP Project Triage

When to use

Use this skill to quickly understand what kind of WordPress repo you’re in and what commands/conventions to follow before making changes.

Inputs required

  • Repo root (current working directory).

Procedure

  1. Run the detector (prints JSON to stdout):
  2. node "$BB_SKILL_DIR/scripts/detect_wp_project.mjs"
  3. If you need the exact output contract, read:
  4. triage.schema.json
  5. Use the report to select workflow guardrails:
  6. project kind(s)
  7. PHP/Node tooling present
  8. tests present
  9. version hints and sources
  10. If the report is missing signals you need, update the detector rather than guessing.

Verification

  • The JSON should parse and include: project.kind, signals, and tooling.
  • Re-run after changes that affect structure/tooling (adding theme.json, block.json, build config).

Failure modes / debugging

  • If it reports unknown, check whether the repo root is correct.
  • If scanning is slow, add/extend ignore directories in the script.
PACKAGE TRANSPARENCY

Inspect before installing

Source: WordPress · GPL-2.0-or-later · SHA-256 shown alongside the download.

9 files18192 ZIP bytes1 script/code file

License file included. A license and checksum are not a security certification. Review package instructions and scripts before running them.

View files and uncompressed sizes
Machine-readable installation guide →
CATALOG REVIEW NOTES

Know what you need before installing

Source and packaging checks recorded on 2026-10-03. These notes are not safety certification or measured task performance.

Requirements

A local WordPress project and a reviewed Node.js installation. Set BB_SKILL_DIR to the absolute installed skill folder; keep the working directory at the project root. Upstream declares WordPress 7.0+ and PHP 7.4.0+; actual project compatibility needs verification.

Costs, access & practical limits

The detector reads project files and prints local JSON; it does not install dependencies or run its suggested commands. Treat version and tooling signals as hints, not certification. The helper can miss a theme name inside a single-line comment; inspect unknown classifications manually. Suggested WP-CLI, build and database commands require separate review and authorization. No production WordPress instance or full agent evaluation was used by this catalog.

View the recorded checks
  • Pinned upstream source and Git blob hashes verified
  • Applicable original license and notices preserved
  • Archive paths and metadata validated
  • Local Markdown and named reference files checked
  • Installed helper paths adapted; original instructions preserved

Upstream commit: 34da134e184ef93d6fb8c074fed309e06b964f34

Runtime status: not tested by this catalog. Configure your client and test the skill in your own environment.

LICENSE & ATTRIBUTION

GPL license & upstream grant

This source package retains the upstream copyright and GPLv2-or-later grant alongside the complete GPLv2 text. Read both before adapting or redistributing it. Keep the notices and supply corresponding source as required by the applicable GPL terms.

GPL-2.0-or-later ↗

Original upstream grant covering the included WordPress skill instructions and references

Attribution: Copyright (C) 2026 WordPress Contributors

Changes: BB Skills adapted primary SKILL.md on 2026-10-03 for installed helper paths and setup notes. Original retained in upstream-original/SKILL.md. Scripts/references unchanged; provenance and complete license added.

Included notice: wp-project-triage/LICENSE.upstream.txt

Declared source ↗

GPL-2.0-or-later ↗

Complete GPLv2 text accompanying the upstream GPLv2-or-later grant

Attribution: Free Software Foundation, Inc.; complete text from SPDX license-list-data

Changes: Complete SPDX licenseText retained unchanged.

Included notice: wp-project-triage/GPL-2.0-or-later.txt

Declared source ↗
SCENARIOS

Inputs, criteria and recorded outcomes

Records are supplied by the site administrator and bound to a specific package. They are not third-party safety certification. This page does not execute skills.

Installed Node helpers: six synthetic project layouts

Reported passed · v34da134e184e

View input and acceptance criteria

Input

Install the bound package into a custom temporary skill directory with spaces. Execute the documented Node helper paths while cwd remains a separate synthetic project. Check empty, multiline classic-theme header, inline theme header, block-theme, multiple-theme and malformed theme.json layouts. Use no credentials, WordPress runtime or user projects.

Acceptance criteria

All helper paths resolve and JSON parses. Multiline classic and block theme fixtures are classified; multiple-theme layouts are counted by the theme detector. The inline-header fixture is unknown in the upstream triage helper, a recorded limitation. Project contents remain unchanged. These are direct script checks only.

Recorded outcome

Direct Node.js helper checks on synthetic files; not a WordPress runtime or AI-agent evaluation
Mode: live CLI HTTPS install; custom destination with spaces, project cwd separate from installed skill directory.
{
  "empty": true,
  "classic": true,
  "inline-header": true,
  "block": true,
  "multiple": true,
  "malformed": true
}
No project files changed during helper runs.
Limitations: The upstream triage helper reports unknown for the inline comment theme-header fixture; use multiline headers and manually inspect unknown results. These are synthetic detector checks, not real theme activation, PHP/WP-CLI execution, traversal-limit coverage or an AI-agent evaluation.
Probe SHA-256: 2f688c4944ec3b0b23fa0abdf2f1d1d554252ea5310462f4f6d03f9fc206a2fa
Evidence SHA-256: b7c86fc123d376b6f08d58e911c29fcb88493e3f10724468bb2f3d16708ac874

Environment

v24.10.0; win32

Package SHA-256: 2ce71669bf71de7cb6ec44de3eb8c56428a5b5e2cdd8231a58300374851145db

Outcome recorded: 2026-10-03 01:50 UTC

Community reviews

★ New

Be the first to share your experience.

Sign in to leave a review →

More to explore

View all ↗