Inspect a WordPress checkout and produce structured evidence about project type, tooling and versions.
Editorial review checked 2026-10-29 against this instruction snapshot. Supporting scripts and runtime behavior remain outside this editorial review.
The supplied detector reads repository structure and configuration to identify plugin, theme, core, Gutenberg and site signals. Its JSON report also inventories test tooling and likely commands. This makes it a useful preparation step before choosing a specialist skill or changing unfamiliar code.
Agents and maintainers onboarding to WordPress repositories with uncertain layout or build conventions.
The detector uses file and token heuristics, and its scans have depth and file limits. Detected configuration is evidence of intent rather than proof that a dependency is installed or a recommended command will succeed in the current environment.
Targets WordPress 7.0+ (PHP 7.4.0+). Filesystem-based agent with bash + node. Some workflows require WP-CLI.
Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.
npx skills add https://github.com/WordPress/agent-skills/tree/eff3785fc28c4380d172094518c66a6a997c95d4/skills/wp-project-triage --skill wp-project-triageReview pinned skill folder ↗ · CLI documentation ↗
After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.
Static review only. This is not a security audit or a guarantee of safety.
SKILL.md text only; scripts, dependencies and runtime behavior not audited.
No configured text patterns matched. Unmatched or concealed behavior can still exist.
Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.
A temporary folder-copy check, not an agent installation or runtime safety verdict.
3 files copied and checksummed from this exact source snapshot. No package code or installation scripts were executed.
Inventory SHA-256: c481f49fcc939a1d468345a62cbb2a0ac82ab0718b240d443b7f9c05ec79aee1
Selected helper behavior only. Full agent compatibility and runtime safety remain unverified.
10 synthetic scenarios passed for skills/wp-project-triage/scripts/detect_wp_project.mjs, checked 2026-10-29. The container had no network, production data or credentials, and only read-only fixture and helper mounts.
Script SHA-256: 4920474fd1397f4e3c4251e74500ffdffa3d83d9b0063a13b7ae90c2d8ab5669
25 synthetic helper scenarios across seven skills; not full agent evaluation, live WordPress, transitive dependency audit or safety certification.
Image: node@sha256:fe4f6d74e20370acb04ad889077d14d0f64a9c8ea6a42bc60cddf1e844699914
73/100 · Metadata coverage 80% · Model 1.0
Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.
Bounded source inspection, not a runtime security audit. This inspection does not execute code.
2 text files inspected at this exact repository snapshot. 0 files outside the inspection budget or type allowlist. Dependencies were not installed or independently audited.
Absence of a pattern is not proof of safety. Permission needs and runtime behavior remain Unknown.
f24dd91e56c2268a8026ca97235ada9240c70aded32c1c70985c62af4f3069034920474fd1397f4e3c4251e74500ffdffa3d83d9b0063a13b7ae90c2d8ab5669Run the reviewed detector from the intended repository root, inspect its project classification and trace important signals back to actual files. Confirm the relevant package boundary before adopting its command suggestions or changing the project structure.
Check that the JSON parses and names plausible entrypoints, versions and tooling. Compare representative plugin, block-theme and unknown fixtures, inspect truncation flags and rerun after structural changes. Treat missing or conflicting signals as questions for further inspection rather than guessed facts.
Related by category; compare scope and dependencies before choosing an alternative.
Explore dispatching parallel agents as a productivity & planning workflow from obra/superpowers. Compare its source, maintenance and review signals before choosing it for your agent.
Repository star change: +1264 over 41.38 hours. 2026-10-31
Explore executing plans as a productivity & planning workflow from obra/superpowers. Compare its source, maintenance and review signals before choosing it for your agent.
Repository star change: +1264 over 41.38 hours. 2026-10-31
Explore finishing a development branch as a productivity & planning workflow from obra/superpowers. Compare its source, maintenance and review signals before choosing it for your agent.
Repository star change: +1264 over 41.38 hours. 2026-10-31
Plan reproducible WordPress Playground environments through explicit Blueprint configuration and bundled resources.
Repository star change: +3 over 40.37 hours. 2026-10-31
Choose a WordPress development workflow after identifying the repository and intended change.
Repository star change: +3 over 40.37 hours. 2026-10-31
Design WordPress abilities with explicit schemas, capability checks and controlled REST exposure.
Repository star change: +3 over 40.37 hours. 2026-10-31