Workflow·E-commerce

WooCommerce Email Editor

Setup and develop the WooCommerce block email editor. Use when working on email templates, transactional emails, or the email editor…

You say
Install this skill Read the source first Free Written by woocommerce · unverified publisher
Context cost
900 tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 3.6 kBtext throughout, nothing executable
Licence
GPL-2.0-or-laterfree to use
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

Setup and develop the WooCommerce block email editor. Use when working on email templates, transactional emails, or the email editor feature.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

woocommerceemailordersblocks
Filed under

E-commerce

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md3.6 kB · 154 lines
--- name: woocommerce-email-editor description: Setup and develop the WooCommerce block email editor. Use when working on email templates, transactional emails, or the email editor feature. ---
6# WooCommerce Email Editor Development
7
8This skill provides guidance for developing the WooCommerce block email editor.
9
10## When to Use This Skill
11
12Invoke this skill when:
13
14- Setting up local development for the email editor
15- Working on email templates or transactional emails
16- Modifying the email editor PHP or JS packages
17- Testing email sending functionality
18
19## Development Environment Setup
20
21### 1. Start WooCommerce wp-env
22
23```sh
24pnpm --filter=@woocommerce/plugin-woocommerce -- wp-env start
25```
26
27Site runs at http://localhost:8888 by default. If port 8888 is unavailable, wp-env assigns a different port. Check the startup output or run wp-env info to see your actual URL.
28
29### 2. Start the watcher
30
31Watches and builds admin JS files (including the email editor JS package) and syncs Email Editor PHP package changes:
32
33```sh
34pnpm --filter=@woocommerce/plugin-woocommerce watch:build:admin
35```
36
37### 3. Enable the block email editor feature
38
39Visit <http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=advanced&section=features> and enable the block email editor.
40
41### 4. Edit transactional emails
42
43Visit <http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=email>
44
45## Email Testing with Mailpit
46
47To test email sending locally, use Mailpit as a local SMTP server.
48
49### Configure SMTP
50
51Add to plugins/woocommerce/.wp-env.override.json:
52
53```json
54{
55 "lifecycleScripts": {
56 "afterStart": "./tests/e2e/bin/test-env-setup.sh && wp-env run cli wp plugin install wp-mail-smtp --activate"
57 },
58 "config": {
59 "WPMS_ON": true,
60 "WPMS_MAILER": "smtp",
61 "WPMS_SMTP_HOST": "host.docker.internal",
62 "WPMS_SMTP_PORT": "1025",
63 "WPMS_SMTP_AUTH": false,
64 "WPMS_SMTP_SECURE": ""
65 }
66}
67```
68
69### Start Mailpit
70
71```sh
72docker run --rm --name=mailpit -p 1025:1025 -p 8025:8025 -d axllent/mailpit
73```
74
75Or if the container already exists:
76
77```sh
78docker start mailpit
79```
80
81### View emails
82
83Open <http://localhost:8025> to see captured emails.
84
85### Restart wp-env
86
87After creating or modifying .wp-env.override.json, restart the environment:
88
89```sh
90pnpm --filter=@woocommerce/plugin-woocommerce -- wp-env start --update
91```
92
93## Key Paths
94
95| Path | Description |
96| ---- | ----------- |
97| packages/php/email-editor/ | Email Editor PHP package |
98| packages/js/email-editor/ | Email Editor JS package |
99| plugins/woocommerce/.wp-env.override.json | Local wp-env config (gitignored) |
100
101## Building the Email Editor Package
102
103To rebuild the JS package after changes:
104
105```sh
106pnpm --filter=@woocommerce/email-editor build
107```
108
109## Testing the PHP Package
110
111Run tests from the packages/php/email-editor/ directory.
112
113### Setup
114
115```sh
116cd packages/php/email-editor
117wp-env start
118composer dump-autoload
119```
120
121### Run integration tests
122
123```sh
124wp-env run tests-cli --env-cwd=wp-content/plugins/email-editor ./vendor/bin/phpunit --configuration phpunit-integration.xml.dist
125```
126
127### Run a specific test
128
129```sh
130wp-env run tests-cli --env-cwd=wp-content/plugins/email-editor ./vendor/bin/phpunit --configuration phpunit-integration.xml.dist --filter Table_Test
131```
132
133## Linting the PHP Package
134
135Run from the packages/php/email-editor/ directory.
136
137### PHPStan
138
139```sh
140cd tasks/phpstan && ./run-phpstan.sh
141```
142
143For PHP 7 compatibility:
144
145```sh
146cd tasks/phpstan && ./run-phpstan.sh php7
147```
148
149### PHPCS
150
151```sh
152composer run phpcs
153```
154
In the file
SKILL.md431 words
Files1
LicenceGPL-2.0-or-later
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈50
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
850
on trigger
The instruction body, read only when the skill fires.
0.45%
of a 200k window
Ten skills this size would take about 5% of the window before you open a file.
050k100k150k200k context window

900 tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Small enough to keep loaded permanently without thinking about it.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 3.6 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md3.6 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The GPL-2.0-or-later licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# WooCommerce Email Editor · 900 tokens when loaded npx mcprush@latest skill add woocommerce/woocommerce-email-editor

Writes to .claude/skills/woocommerce-email-editor/ in the current project. Add --global to put it in your home directory instead, for every project.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencewoocommerce/woocommerce-email-editor

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

WO
woocommerce

Publishes on mcprush.

0 servers listed3 skills listednot claimed
Profile
Publisher
Servers0
Claim this skill