← LeaderboardThe Skill Leaderboard

wordpress-plugin-development

WordPress plugin development workflow covering plugin architecture, hooks, admin interfaces, REST API, security best practices, and WordPress 7.0 features: Real-Time Collaboration, AI Connectors, Abilities API, DataViews, and PHP-only blocks.

Published by sickn33 ↗sickn33/agentic-awesome-skills

Try your first task

wordpress-plugin-development

Start a fresh conversation. Replace the highlighted placeholders.

Use wordpress-plugin-development to build [plugin purpose] in [plugin directory], with a maintainable plugin architecture, secure hooks and admin interface; document the supported WordPress/PHP versions and complete the documented quality gates before presenting the result.

Required inputs

  • [plugin purpose]
  • [plugin directory]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: wordpress-plugin-developmentdescription: "WordPress plugin development workflow covering plugin architecture, hooks, admin interfaces, REST API, security best practices, and WordPress 7.0 features: Real-Time Collaboration, AI Connectors, Abilities API, DataViews, and PHP-only blocks."category: granular-workflow-bundlerisk: safesource: personaldate_added: "2026-02-27"

WordPress Plugin Development Workflow

Detailed Guide

Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.

When to Use This Workflow

Use this workflow when:

  • Creating custom WordPress plugins
  • Extending WordPress functionality
  • Building admin interfaces
  • Adding REST API endpoints
  • Integrating third-party services
  • Implementing WordPress 7.0 AI/Collaboration features

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.