agentsclimarketplace

Woo customer note bulk annotator

Skill navarroido/Woocommerce-skill/skills/customer-ops/woo-customer-note-bulk-annotator

Install
npx -y skills add navarroido/Woocommerce-skill --skill woo-customer-note-bulk-annotator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Append a note to multiple customers matching a role, spend range, or country filter with dry-run preview.

SKILL.md

5.6 KB, as published. Nobody here has run it

woo-customer-note-bulk-annotator

Purpose

Append a text note to the WooCommerce customer note field (customer_note) for multiple customers matching a filter (role, spend range, country, or registration date). Useful for adding internal flags, account status notes, or support context in bulk. Includes dry-run preview.

Prerequisites

  • WooCommerce store with REST API enabled
  • Consumer Key with Read/Write scope
  • Minimum WooCommerce version: 3.5.0

Parameters

ParameterTypeRequiredDefaultDescription
store_urlstringyesBase URL of the WooCommerce store
consumer_keystringyesWooCommerce REST API consumer key (ck_...)
consumer_secretstringyesWooCommerce REST API consumer secret (cs_...)
dry_runboolnotruePreview without executing
formatstringnohumanOutput format: human or json
notestringyesText to append to each customer's note
filter_rolestringnoWordPress role to filter
filter_min_spendnumbernoMinimum total_spent
filter_max_spendnumbernoMaximum total_spent
filter_countrystringnoTwo-letter billing country code
append_modeboolnotrueIf true, append to existing note; if false, overwrite

Authentication

WooCommerce uses OAuth 1.0a for HTTP and Basic Auth over HTTPS.

For HTTPS stores (recommended):

Authorization: Basic base64(consumer_key:consumer_secret)

For HTTP stores (development only): Use OAuth 1.0a — include oauth_consumer_key, oauth_nonce, oauth_signature, oauth_signature_method=HMAC-SHA1, oauth_timestamp, oauth_version=1.0

Never log or output consumer_key or consumer_secret values.

See docs/AUTHENTICATION.md for full setup instructions.

Safety

Step 3 writes to customer records. Always run with dry_run: true first (the default). If append_mode: false, existing customer notes are overwritten.

Workflow Steps

Step 1 — Fetch filtered customers

GET /wp-json/wc/v3/customers?per_page=100&page=1
  [&role=<filter_role>]
  [&country=<filter_country>]

Filter client-side by total_spent range. Extract: id, email, customer_note

Step 2 — Compute new note

If append_mode: true: new_note = existing_note + "\n" + note + " [" + date + "]" If append_mode: false: new_note = note

Step 3 — Preview or execute

If dry_run: true: list customers. Stop.

If dry_run: false and confirmed:

PUT /wp-json/wc/v3/customers/{id}
  Body: { "customer_note": "<new_note>" }

API Endpoints Used

GET  /wp-json/wc/v3/customers        — filtered customer list
PUT  /wp-json/wc/v3/customers/{id}   — write updated note

Pagination Strategy

WooCommerce REST API uses page/per_page pagination (not cursor-based).

Standard pattern:

page = 1
while True:
  response = GET /endpoint?per_page=100&page=page
  process(response)
  if len(response) < 100: break
  page += 1

Maximum per_page is 100 for most endpoints. The X-WP-Total and X-WP-TotalPages response headers report totals. Always read X-WP-TotalPages on the first request to estimate job size.

Session Tracking

Claude MUST emit the following output at each stage. This is mandatory.

STARTUP:

╔══════════════════════════════════════════╗
║  SKILL: woo-customer-note-bulk-annotator ║
║  STORE: <store_url>                      ║
║  TIME:  <ISO-8601 UTC>                   ║
║  MODE:  <DRY RUN | LIVE>                 ║
╚══════════════════════════════════════════╝

PER-OPERATION (emit after each API call batch):

[N/TOTAL] <METHOD> <endpoint> → <result_count> records | params: <key>=<val>

COMPLETION (human format):

╔══════════════════════════════════════════╗
║  COMPLETE: woo-customer-note-bulk-anno.  ║
║  RECORDS PROCESSED: <n>                  ║
║  OUTPUT: stdout                          ║
╚══════════════════════════════════════════╝

COMPLETION (json format):

{
  "skill": "woo-customer-note-bulk-annotator",
  "store": "<store_url>",
  "completed_at": "<ISO-8601>",
  "records_processed": <n>,
  "output_file": null,
  "dry_run": <bool>
}

Output Format

Human format: count of customers to annotate and the first 10 email addresses.

Error Handling

ErrorCauseResolution
401 UnauthorizedInvalid credentialsVerify consumer_key and consumer_secret
403 ForbiddenKey lacks Read/Write scopeRegenerate with Read/Write scope
429 Too Many RequestsRate limitWait 2 seconds and retry

Best Practices

  • Always run with dry_run: true first.
  • Use append_mode: true (the default) to preserve existing notes.
  • Include the date in your note text for a built-in audit trail.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.