← Back to the catalog 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).
View on GitHub ↗ Copy repo URL Copy SKILL.md link /plugin marketplace add aiskillstore/marketplace The exact command may vary by repository. Check the README on GitHub.
For the skill author
Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.
Markdown HTML
[](https://www.skillteca.com.br/skills/wordpress-router?utm_source=badge&utm_medium=readme&utm_campaign=badge) Copy snippet Team Mode security research skill orchestrates 3 vulnerability hunters and 2 PoC engineers to audit a codebase in parallel, prove exploitability, classify root causes, and calibrate severity. It is used for security review, vulnerability research, exploitability audit, and threat model validation.
Segurança by code-yeongyu
Provide a comprehensive, structured reference for the 100 most critical web application vulnerabilities organized by category. This skill enables systematic vulnerability identification, impact assessment, and remediation guidance across the full spectrum of web security threats.
Segurança #github #git by sickn33
Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA.
Segurança #github #git by sickn33
Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.
Segurança #github #git by sickn33
Category alert
One short email with only the new Segurança skills. 4 minutes of reading, no spam, unsubscribe with one click.
You confirm your email on the first send. No spam. Unsubscribe with one click.
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?”
Read full description↓
Comments · No comments No comments yet. Be the first. 