원클릭으로 Manus에서 모든 스킬 실행

$pwd:

wordpress-router

Name: Wordpress Router
Author: WordPress

// Use when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core checkouts) and you need to quickly classify the repo and route to the correct workflow/skill (blocks, theme.json, REST API, WP-CLI, performance, security, testing, release packaging).

Manus에서 실행

$ git log --oneline --stat

stars:1,601

forks:222

updated:2026년 1월 28일 04:00

파일 탐색기

2 개 파일

SKILL.md

readonly

name	wordpress-router
description	Use when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core checkouts) and you need to quickly classify the repo and route to the correct workflow/skill (blocks, theme.json, REST API, WP-CLI, performance, security, testing, release packaging).
compatibility	Targets WordPress 6.9+ (PHP 7.2.24+). Filesystem-based agent with bash + node. Some workflows require WP-CLI.

WordPress Router

When to use

Use this skill at the start of most WordPress tasks to:

identify what kind of WordPress codebase this is (plugin vs theme vs block theme vs WP core checkout vs full site),
pick the right workflow and guardrails,
delegate to the most relevant domain skill(s).

Inputs required

Repo root (current working directory).
The user’s intent (what they want changed) and any constraints (WP version targets, WP.com specifics, release requirements).

Procedure

Run the project triage script:
- node skills/wp-project-triage/scripts/detect_wp_project.mjs
Read the triage output and classify:
- primary project kind(s),
- tooling available (PHP/Composer, Node, @wordpress/scripts),
- tests present (PHPUnit, Playwright, wp-env),
- any version hints.
Route to domain workflows based on user intent + repo kind:
- For the decision tree, read: skills/wordpress-router/references/decision-tree.md.
Apply guardrails before making changes:
- Confirm any version constraints if unclear.
- Prefer the repo’s existing tooling and conventions for builds/tests.

Verification

Re-run the triage script if you create or restructure significant files.
Run the repo’s lint/test/build commands that the triage output recommends (if available).

Failure modes / debugging

If triage reports kind: unknown, inspect:
- root composer.json, package.json, style.css, block.json, theme.json, wp-content/.
If the repo is huge, consider narrowing scanning scope or adding ignore rules to the triage script.

Escalation

If routing is ambiguous, ask one question:
- “Is this intended to be a WordPress plugin, a theme (classic/block), or a full site repo?”

related-skills.json

같은 저장소

wp-abilities-api.md

from "WordPress/agent-skills"

Use when working with the WordPress Abilities API (wp_register_ability, wp_register_ability_category, /wp-json/wp-abilities/v1/*, @wordpress/abilities) including defining abilities, categories, meta, REST exposure, and permissions checks for clients.

2026-05-271.6k

wp-abilities-audit.md

from "WordPress/agent-skills"

Audit a WordPress plugin's REST surface and produce a standardized audit document proposing Abilities API registrations. Produces a markdown doc with a YAML schema and prose sections that humans and agents can both consume when planning a registration rollout. Works on any WP plugin.

2026-05-271.6k

wp-abilities-verify.md

from "WordPress/agent-skills"

Verify a WordPress plugin's Abilities API registrations: enumerate abilities, check that callback behavior matches each annotation's claim (the adversarial readonly-but-writes detection), validate permissions and schemas, and validate audit documents produced by wp-abilities-audit.

2026-05-271.6k

wp-plugin-directory-guidelines.md

from "WordPress/agent-skills"

Use when reviewing WordPress plugins for GPL compliance, checking license headers or compatibility, evaluating upsell/freemium/trialware patterns, validating plugin naming or trademark rules, checking plugin slugs, understanding why a plugin was rejected from WordPress.org, or answering any question about the 18 WordPress.org Plugin Directory guidelines — even if the user doesn't mention 'guidelines' explicitly.

2026-04-241.6k

blueprint.md

from "WordPress/agent-skills"

Use when creating, editing, or reviewing WordPress Playground blueprint JSON files. Triggers on mentions of blueprints, playground configuration, or requests to set up a WordPress demo environment.

2026-03-241.6k

wp-rest-api.md

from "WordPress/agent-skills"

Use when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes, schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing CPTs/taxonomies via show_in_rest.

2026-01-281.6k

package.json

"author": "WordPress"

"repository": "WordPress/agent-skills"

GitHub 저장소 열기 Creator 저장소 보기

$ install --global

$ download --local

Manus에서 실행

$ useful --forSOC

소프트웨어 개발자컴퓨터 및 수학직15-1252L4

name	wordpress-router
description	Use when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core checkouts) and you need to quickly classify the repo and route to the correct workflow/skill (blocks, theme.json, REST API, WP-CLI, performance, security, testing, release packaging).
compatibility	Targets WordPress 6.9+ (PHP 7.2.24+). Filesystem-based agent with bash + node. Some workflows require WP-CLI.

WordPress Router

When to use

Use this skill at the start of most WordPress tasks to:

identify what kind of WordPress codebase this is (plugin vs theme vs block theme vs WP core checkout vs full site),
pick the right workflow and guardrails,
delegate to the most relevant domain skill(s).

Inputs required

Repo root (current working directory).
The user’s intent (what they want changed) and any constraints (WP version targets, WP.com specifics, release requirements).

Procedure

Run the project triage script:
- node skills/wp-project-triage/scripts/detect_wp_project.mjs
Read the triage output and classify:
- primary project kind(s),
- tooling available (PHP/Composer, Node, @wordpress/scripts),
- tests present (PHPUnit, Playwright, wp-env),
- any version hints.
Route to domain workflows based on user intent + repo kind:
- For the decision tree, read: skills/wordpress-router/references/decision-tree.md.
Apply guardrails before making changes:
- Confirm any version constraints if unclear.
- Prefer the repo’s existing tooling and conventions for builds/tests.

Verification

Re-run the triage script if you create or restructure significant files.
Run the repo’s lint/test/build commands that the triage output recommends (if available).

Failure modes / debugging

If triage reports kind: unknown, inspect:
- root composer.json, package.json, style.css, block.json, theme.json, wp-content/.
If the repo is huge, consider narrowing scanning scope or adding ignore rules to the triage script.

Escalation

If routing is ambiguous, ask one question:
- “Is this intended to be a WordPress plugin, a theme (classic/block), or a full site repo?”

wordpress-router

WordPress Router

When to use

Inputs required

Procedure

Verification

Failure modes / debugging

Escalation

이 저장소의 다른 Skills

이 저장소의 다른 Skills

WordPress Router

When to use

Inputs required

Procedure

Verification

Failure modes / debugging

Escalation