ClawHub

Wordpress Pro

v0.1.0

Use when developing WordPress themes, plugins, customizing Gutenberg blocks, implementing WooCommerce features, or optimizing WordPress performance and security.

⭐ 9· 4.3k·23 current·24 all-time
byVeera@veeramanikandanr48
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description (WordPress themes/plugins, Gutenberg, WooCommerce, performance/security) matches the included SKILL.md and reference documents. There are no unrelated environment variables, binaries, or install steps requested.
✓
Instruction Scope
SKILL.md defines a developer role and a scoped workflow (analysis → design → implement → optimize → test). The references contain code examples and best-practice snippets (hooks, block code, DB operations) appropriate for WordPress development. The instructions do not tell the agent to read arbitrary system files, exfiltrate data, or call unknown external endpoints.
✓
Install Mechanism
No install spec and no code files to execute are provided (instruction-only). This minimizes on-disk persistence risk; nothing is downloaded or installed by the skill itself.
✓
Credentials
The skill declares no required env vars, credentials, or config paths. The example snippets show use of WordPress globals/APIs (e.g., $wpdb, ABSPATH) which are expected for WordPress code and do not imply extra secret access.
✓
Persistence & Privilege
always is false and the skill is user-invocable. It does not request permanent presence or modify other skills. Autonomous invocation is enabled (platform default) but this is not combined with other red flags.
Assessment
This skill is an instructional/reference pack for WordPress development and appears internally consistent — it doesn't request credentials or install code. Before using its snippets in a live site: (1) Verify the unknown author/source if you need provenance or liability guarantees; (2) Review and adapt every code sample (some examples perform DB deletions, transients cleanup, or drop tables in uninstall scripts) before running them — do not copy destructive queries into production untested; (3) Test generated code in a staging environment with backups available; (4) Keep security best practices (nonces, sanitization, capability checks) — the skill itself recommends them but automated insertion of snippets without review can still be dangerous. Confidence is high because the package is documentation-only and internally coherent, but always audit any code you paste into a running WordPress site.

Like a lobster shell, security has layers — review code before you run it.

latestvk975jybk1rztdjqrx3ndc0xp3x809dqd

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments