wp-project-security-audit
openbooklet.com/s/wp-project-security-auditopenbooklet.com/s/[email protected]GET /api/v1/skills/wp-project-security-auditUse when auditing a whole WordPress project (a wp-content repo, a full site root, or a Bedrock-style layout) for security and known vulnerabilities, or deciding whether a site is safe as deployed. Triggers: "audit this project", "audit the whole site", "security audit of this WordPress site", "is this site safe", "check every plugin and theme for vulnerabilities", "project security review", "vulnerability sweep", "is production compromised", "supply chain check for our plugins", or any request covering more than one plugin or theme, dependencies, deploy, CI, secrets or production drift. Orchestrates wp-plugin-code-audit and wp-theme-code-audit; requires both.
Cross-project playbook synthesized from real WordPress migrations. Opinionated â these patterns survived production. Other approaches exist; these are the ones that didn't bite.
Use when turning a Claude design into a WordPress block theme (FSE): a Claude Design canvas (the Design artifact type, downloaded as HTML or shared as a claude.ai/artifact link) or an HTML artifact page Claude made. Triggers: "Claude design to WordPress", "turn this canvas into a block theme", "convert this artifact to a WordPress theme", "build the theme from the Claude Code design", a claude.ai/artifact URL or a downloaded canvas .html paired with a WordPress theme request. Requires wp-design-to-block-theme. Not for classic (PHP template) themes.
Use after a WordPress plugin code audit, when findings are being fixed and someone needs to track and verify the remediation. Triggers: "remediation log", "track the fixes", "where are we on the audit findings", "after the audit", "the audit report is done, now what", "prove this refactor is behaviour-neutral", "is this rename safe", "did phpcbf change behaviour", "verify this change is formatting-only", "mark this finding fixed", or any request to record what changed against audit findings, keep the report's citations readable while fixing, or confirm a mechanical change didn't alter behaviour. Companion to wp-plugin-code-audit.
Use when auditing a WordPress theme (block, classic, hybrid or child) for security, performance, theme review standards, and child-theme override safety. Triggers: "audit this theme", "review the theme", "is this theme secure", "theme security review", "theme code review", "is this theme safe to install", "check this theme for vulnerabilities", "review this block theme", "review this child theme", "performance review of this theme", or any request to evaluate the quality / safety of a WordPress theme from a local checkout, a single file/function, or a remote source (wp.org theme slug, GitHub URL). Requires wp-plugin-code-audit.
Auto-indexed from s3rgiosan/wp-skills
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.