Skip to content
TrustedSkillsbeta
Back to all skills

Woocommerce Backend Dev

Checked
secondsky·vlatest·backend·MIT

Automates WooCommerce backend development tasks like product creation, order management, and custom hook implementation using SecondSky's expertise.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add secondsky/claude-skills --skill woocommerce-backend-dev -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

secondsky

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned secondsky/claude-skills at 8837836131.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
8837836131
Manifest
plugins/woocommerce-backend-dev/skills/woocommerce-backend-dev/SKILL.md
Scanned
1 file, 41 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides guidance for developing WooCommerce backend PHP code, ensuring adherence to project standards and conventions. It focuses on helping developers create robust and maintainable WooCommerce extensions by outlining best practices for coding style, naming conventions, dependency injection, data integrity, and unit testing. The skill leverages SecondSky's expertise in WooCommerce development to streamline the process.

When to use it

  • When creating new PHP classes or organizing files within a WooCommerce project.
  • To ensure code adheres to WordPress Coding Standards and PSR-4 autoloading conventions.
  • When implementing custom hooks within WooCommerce.
  • For guidance on writing unit tests for new WooCommerce functionality.
  • When determining the appropriate @since version annotation for new code.

Key capabilities

  • Guidance on creating new code structures (classes, file organization).
  • Enforcement of naming conventions for methods, variables, and parameters.
  • Adherence to general coding standards and best practices.
  • Documentation on hook callback conventions.
  • Instructions on dependency injection container usage.
  • Best practices for ensuring data integrity during CRUD operations.
  • Guidance on unit testing conventions.
  • Determining the next WooCommerce version number for @since annotations by inspecting includes/class-woocommerce.php.

Example prompts

  • "How should I structure a new class in my WooCommerce plugin?"
  • "What are the naming conventions for variables within a WooCommerce backend function?"
  • "Show me an example of a hook callback implementation according to project standards."

Tips & gotchas

  • Always refer to the linked documentation (file-entities.md, code-entities.md, etc.) for detailed guidance on specific aspects of development.
  • The version information is based on the trunk branch, which may be ahead of released versions.
  • Prefer using bun over npm/bunx when applicable for Node.js package management.