wordpress
Build WordPress Projects With Guided Workflows
WordPress projects span themes, plugins, performance, security, and deployment. This skill organizes each phase into practical actions and prompts.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "wordpress" from https://skillstore.io/skills/sickn33-wordpress.md and its manifest at https://skillstore.io/api/skills/sickn33-wordpress/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "wordpress". Plan a custom WordPress theme for a service business.
Expected outcome:
A phased build plan covering setup, theme structure, responsive templates, performance checks, security checks, and launch readiness.
Using "wordpress". Create a workflow for a WooCommerce subscription store.
Expected outcome:
A release checklist for products, payment setup, checkout customization, subscription logic, testing, deployment, and post-launch monitoring.
Using "wordpress". Audit a WordPress site before production launch.
Expected outcome:
A quality gate review covering updates, authentication, headers, file permissions, backups, performance metrics, browser tests, and accessibility.
Security Audit
Medium RiskThe 58 static external-command findings are false positives caused by markdown inline code and fenced code blocks, not executable backtick use. No prompt injection or malicious automation was found. One medium semantic issue remains because the REST API example uses an unrestricted permission callback.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (58)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-wordpress/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-wordpress?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-wordpress?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-wordpress/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-wordpress.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). wordpress security audit report (audit version 4) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/sickn33-wordpress/audits/4BibTeX citation
@techreport{sickn33-sickn33-wordpress-2026,
author = {sickn33},
title = {wordpress security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-wordpress/audits/4},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "wordpress security audit report (audit version 4)"
version: "1.0.0"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-wordpress/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-wordpress:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Launch a WordPress Build
Plan setup, theme structure, plugins, quality gates, and deployment tasks for a new site.
Plan a Custom Plugin
Break plugin work into architecture, hooks, admin screens, REST endpoints, and tests.
Prepare a WooCommerce Release
Coordinate payment integration, checkout changes, subscriptions, performance, and security checks.
Try These Prompts
Use the WordPress workflow to plan a new local WordPress project. Include setup, theme choice, required plugins, and first checkpoints.
Use the WordPress workflow to outline a custom theme build. Include template files, component work, styling, accessibility, and testing steps.
Use the WordPress workflow to create a performance and security review plan. Include caching, updates, headers, authentication, and logging checks.
Use the WordPress workflow to build a launch plan for a WooCommerce site. Include development, payments, testing, deployment, rollback, and monitoring.
Best Practices
- Verify each generated WordPress change in a local or staging environment first.
- Review examples for nonce checks, capability checks, sanitization, and escaping.
- Use the phase checklists before moving from development to deployment.
Avoid
- Treating copy-paste prompts as production-ready implementation without review.
- Publishing sample API endpoints without explicit access-control decisions.
- Skipping WordPress core, theme, and plugin updates before security testing.