Install
$ agentstack add skill-navarroido-woocommerce-skill-woo-product-lifecycle-manager ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
woo-product-lifecycle-manager
Purpose
Automate WooCommerce product lifecycle transitions: archive slow-moving products to draft, publish pending products that meet criteria, or move discontinued items to private status. Filters by product age, days since last sale, or zero-sale count. Includes dry-run preview before any status changes.
Prerequisites
- WooCommerce store with REST API enabled
- Consumer Key with Read/Write scope
- Minimum WooCommerce version: 3.5.0
Parameters
| Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| | store_url | string | yes | — | Base URL of the WooCommerce store | | consumer_key | string | yes | — | WooCommerce REST API consumer key (ck_...) | | consumer_secret | string | yes | — | WooCommerce REST API consumer secret (cs_...) | | dry_run | bool | no | true | Preview changes without executing | | format | string | no | human | Output format: human or json | | source_status | string | yes | — | Current product status: publish, draft, pending, private | | target_status | string | yes | — | New status to apply | | filter_no_sales_days | int | no | — | Only include products with no sales in last N days | | filter_min_age_days | int | no | — | Only include products created at least N days ago | | category_id | int | no | — | Limit to this category |
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 oauthconsumerkey, oauthnonce, oauthsignature, oauthsignaturemethod=HMAC-SHA1, oauthtimestamp, oauthversion=1.0
Never log or output consumerkey or consumersecret values.
See docs/AUTHENTICATION.md for full setup instructions.
Safety
Step 3 changes product visibility. Drafting or privatizing published products removes them from the storefront immediately. Always run with dry_run: true first (the default). Verify the product list carefully.
Workflow Steps
Step 1 — Fetch products in source_status
GET /wp-json/wc/v3/products
?status=&per_page=100&page=1
[&category=]
Filter client-side by date_created for filter_min_age_days.
Step 2 — Check sales for each product (if filternosales_days set)
GET /wp-json/wc/v3/orders
?status=completed&after=&per_page=100&page=1
Build set of product IDs with recent sales. Exclude these from the transition list.
Step 3 — Preview or execute
If dry_run: true: output transition preview table and stop.
If dry_run: false and confirmed:
PUT /wp-json/wc/v3/products/{id}
Body: { "status": "" }
API Endpoints Used
GET /wp-json/wc/v3/products — products in source status
GET /wp-json/wc/v3/orders — sales check for filter_no_sales_days
PUT /wp-json/wc/v3/products/{id} — update product status
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) ║
║ TIME: ║
║ MODE: ║
╚══════════════════════════════════════════╝
PER-OPERATION (emit after each API call batch):
[N/TOTAL] → records | params: =
COMPLETION (human format):
╔══════════════════════════════════════════╗
║ COMPLETE: woo-product-lifecycle-manager ║
║ RECORDS PROCESSED: ║
║ OUTPUT: stdout ║
╚══════════════════════════════════════════╝
COMPLETION (json format):
{
"skill": "woo-product-lifecycle-manager",
"store": "",
"completed_at": "",
"records_processed": ,
"output_file": null,
"dry_run":
}
Output Format
Human format: table listing product ID, name, current status, new status, and filter criteria matched.
Error Handling
| Error | Cause | Resolution | |-------|-------|------------| | 401 Unauthorized | Invalid credentials | Verify consumerkey and consumersecret | | 403 Forbidden | Key lacks Read/Write scope | Regenerate with Read/Write scope | | 429 Too Many Requests | Rate limit | Wait 2 seconds and retry |
Best Practices
- Always run with
dry_run: truefirst (the default). Unpublishing products is immediately visible to customers. - Use
filter_no_sales_days: 180to archive products that genuinely haven't sold recently. - Set
filter_min_age_days: 30to avoid archiving newly-listed products that need time to gain traction.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: navarroido
- Source: navarroido/Woocommerce-skill
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.