# wp-project-triage

The skill inspects a WordPress repo and prints JSON: project kind, tooling and tests found, version hints. Handy before you touch an unfamiliar plugin or theme.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 5400 installs · ★ 2298
- Author: WordPress
- License: LicenseRef-Unknown · policy=link-only · description only; the file stays with the author
- Source: https://github.com/WordPress/agent-skills/tree/HEAD/skills/wp-project-triage/SKILL.md
- Updated: 2026-10-21
- HTML: https://affpapa.org/en/nevibecode/skills/wp-project-triage

## What it does

Point it at a WordPress folder and it tells you what lives there: a plugin, a classic theme, a block theme, WP core, Gutenberg, or a whole site. The answer comes back as JSON with the project kind, the signals it found, and the tooling in place.

Mechanically it is one script. `node skills/wp-project-triage/scripts/detect_wp_project.mjs` writes the report to stdout, and `skills/wp-project-triage/references/triage.schema.json` documents the expected shape. The agent then reads that report to pick guardrails: which commands exist, whether tests are set up, which versions the code targets. When a signal is missing, the author's advice is to extend the detector instead of guessing.

It targets WordPress 7.0+ and PHP 7.4.0+; the agent needs bash and node, and some workflows call for WP-CLI. That is worth checking before the first run. Got `unknown` back? Confirm the repo root. Scan dragging? Add ignore directories to the script. Re-run it once `theme.json`, `block.json` or a build config shows up.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add WordPress/agent-skills --skill wp-project-triage -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/wp-project-triage/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/wp-project-triage/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add WordPress/agent-skills --skill wp-project-triage -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/wp-project-triage/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add WordPress/agent-skills --skill wp-project-triage -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/wp-project-triage/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install WordPress/agent-skills wp-project-triage
```

2. **Manually: put the files in place**
- File: `.github/skills/wp-project-triage/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add WordPress/agent-skills --skill wp-project-triage -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/WordPress/agent-skills --path skills/wp-project-triage
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/wp-project-triage/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add WordPress/agent-skills --skill wp-project-triage -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/WordPress/agent-skills/tree/HEAD/skills/wp-project-triage/SKILL.md

## When to use it
- tell a plugin apart from a block theme before editing
- see which tests and build scripts the repo already carries
- find the WordPress and PHP versions the code aims at
- hand a machine-readable report to agent guardrails
- re-check the structure after adding `theme.json` or a build config

## Example prompts
- Run `node skills/wp-project-triage/scripts/detect_wp_project.mjs` and tell me what kind of project this folder is.
- Look at the triage report first: which tests can I actually run here?
- The report says `unknown` — check the repo root and run the detector again.

## Similar
- [wordpress-pro](https://affpapa.org/en/nevibecode/skills/wordpress-pro.md) — skill · 9700 installs
- [wordpress-advanced-architecture](https://affpapa.org/en/nevibecode/skills/wordpress-advanced-architecture.md) — skill · 441 installs
- [wordpress-setup](https://affpapa.org/en/nevibecode/skills/wordpress-setup.md) — skill · 1500 installs
- [wordpress-elementor](https://affpapa.org/en/nevibecode/skills/wordpress-elementor.md) — skill · 2900 installs
- [wordpress-testing-qa](https://affpapa.org/en/nevibecode/skills/wordpress-testing-qa.md) — skill · 413 installs
- [wordpress-master](https://affpapa.org/en/nevibecode/agents/wordpress-master.md) — subagent · 763 installs

From the same set: [wordpress/agent-skills](https://affpapa.org/en/nevibecode/by/wordpress/agent-skills.md) — 19 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md