Back to catalog
Human reviewedDevelopment

Skill dossier

wordpress-pro

Source declaration

Develops custom WordPress themes and plugins, creates and registers Gutenberg blocks and block patterns, configures WooCommerce stores, implements WordPress REST API endpoints, applies security hardening (nonces, sanitization, escaping, capability checks), and optimizes performance through caching and query tuning. Use when building WordPress themes, writing plugins, customizing Gutenberg blocks, extending WooCommerce, working with ACF, using the WordPress REST API, applying hooks and filters, or improving WordPress performance and security.

The author's original description, preserved in English. It describes intent, not verified performance.

Develops custom WordPress themes and plugins, creates and registers Gutenberg blocks and block patterns, configures WooCommerce stores, implements WordPress REST API endpoints, applies security hardening (nonces, sanitization, escaping, capability checks), and optimizes performance through caching and query tuning. Use when building WordPress themes, writing plugins, customizing Gutenberg blocks, extending WooCommerce, working with ACF, using the WordPress REST API, applying hooks and filters, or improving WordPress performance and security.

developmentreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

Guides WordPress theme, plugin, Gutenberg block and WooCommerce development with security hardening (nonces, sanitization, escaping, capability checks) and performance work.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Plans theme or plugin structure, hooks and data flow.
  • Implements code following WordPress Coding Standards, validated with phpcs --standard=WordPress.
  • Applies nonces, input sanitization, output escaping, prepared queries and capability checks.
  • Applies transient or object caching, query optimization and proper asset enqueuing.

Limitations & scope

  • Needs phpcs with the WordPress standard installed to run the validation step.
  • Targets WordPress 6.4+ and PHP 8.1+, so older installs may differ.
  • The skill asks for a security audit checklist but does not replace a real security review.

Relevant for

  • WordPress theme and plugin developers
  • Teams extending WooCommerce or building Gutenberg blocks
  • Developers hardening existing WordPress code

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
136.9 KB
Structural complexity
Moderate

File inventory

PathTypeBytes
skills/wordpress-pro/references/gutenberg-blocks.mdReference26.1 KB
skills/wordpress-pro/references/hooks-filters.mdReference21.6 KB
skills/wordpress-pro/references/performance-security.mdReference25.5 KB
skills/wordpress-pro/references/plugin-architecture.mdReference32 KB
skills/wordpress-pro/references/theme-development.mdReference25.4 KB
skills/wordpress-pro/SKILL.mdInstruction6.3 KB

SKILL.md frontmatter

{
  "name": "wordpress-pro",
  "description": "Develops custom WordPress themes and plugins, creates and registers Gutenberg blocks and block patterns, configures WooCommerce stores, implements WordPress REST API endpoints, applies security hardening (nonces, sanitization, escaping, capability checks), and optimizes performance through caching and query tuning. Use when building WordPress themes, writing plugins, customizing Gutenberg blocks, extending WooCommerce, working with ACF, using the WordPress REST API, applying hooks and filters, or improving WordPress performance and security.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "platform",
    "triggers": "WordPress, WooCommerce, Gutenberg, WordPress theme, WordPress plugin, custom blocks, ACF, WordPress REST API, hooks, filters, WordPress performance, WordPress security",
    "role": "expert",
    "scope": "implementation",
    "output-format": "code",
    "related-skills": "php-pro, laravel-specialist, fullstack-guardian, security-reviewer"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Analyze requirements

    Understand the WordPress context, existing setup and goals.

  2. 02
    Action

    Implement to standards

    Build using WordPress coding standards and security best practices.

  3. 03
    Decision

    Validate and check manually

    Run phpcs --standard=WordPress to catch violations and verify nonce handling and capability checks manually.

  4. 04
    Output

    Deliver WordPress output

    Provide the main plugin or theme file, templates or block code, hooks, security implementations and notes.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

496 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

27 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 27 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

468 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 468 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Test generated plugin code on a staging site and review every database query, nonce and capability check before deploying to production.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/wordpress-pro # .claude/skills/wordpress-pro
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/wordpress-pro/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Copy the skill directory into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Confirm SKILL.md is discoverable at the destination, then ask Claude Code to use wordpress-pro on a small task.

Prerequisites

  • Needs phpcs with the WordPress standard installed to run the validation step.
  • Targets WordPress 6.4+ and PHP 8.1+, so older installs may differ.
  • The skill asks for a security audit checklist but does not replace a real security review.

Example prompts

Representative task

Use the wordpress-pro skill to build a plugin with an admin settings page that saves options safely using a nonce, sanitization and a manage_options capability check, then run phpcs with the WordPress standard.

Inspect before use

Read the wordpress-pro skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/wordpress-pro/SKILL.md. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Concrete PHP snippets for nonces, escaping, prepared statements and capability checks.
  • Long, specific MUST NOT list, including no core edits and no unescaped output.

Considerations

  • Broad scope across themes, blocks, WooCommerce and ACF, so references must be loaded by topic.
  • Generated plugins should still be tested on a staging site.
Research conclusion

A security-minded WordPress skill that fits custom theme and plugin work done to WordPress standards.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/wordpress-pro
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.