agentleFS
shinobiashishinobiashi/claude-skills/skills/wc-email-editor/SKILL.md

wc-email-editor

Skill0 starsChanged 2 months agoNo licenceView on GitHub

How to bundle and drive WooCommerce's block email editor packages inside your own plugin: Composer woocommerce/email-editor (PHP; Bootstrap, Email_Editor_Container, Renderer, Personalization tags, Templates) and npm @woocommerce/email-editor (JS; initializeEditor, window.WooCommerceEmailEditor). Covers registering a custom post type with the editor via woocommerce_email_editor_post_types, replacing the classic editor screen, Assets_Manager paths and localization, rendering block content to email-safe HTML + text, personalization tags (<!--[ns/tag]-->), the webpack/Strauss setup and release packaging, removing the package's wp_mail() test send, and running one engine per request when WooCommerce core's own block email editor (or another plugin's copy) is also present (shared hook names, REST namespace woocommerce-email-editor/v1, JS global, TypeError when both boot). Use this for any task that mentions the email editor package, "block email editor", "MailPoet-style editor", rendering email blocks, Gutenberg for emails, ssm_campaign editing, or Signal Mail Phase 6 — even when the user just says "let users design the newsletter in the block editor". Facts verified 2026-10-07 against the WooCommerce monorepo and measured 2026-10-24 in a shipped integration (Signal Mail PR-17: PHP 2.19.0, JS 2.5.1, WooCommerce 10.0.6 and 11.2.1 with its block email editor on and off); re-check versions before pinning.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.