A merchant-neutral agent skill and skills-only Codex plugin for preparing, editing, and validating Alibaba.com seller product listings through a supported authenticated browser workflow.
The workflow is intentionally conservative: it does not assume a brand, model prefix, shipping method, template, customs code, image policy, or permission to save or publish. Merchant-specific behavior comes from current-task instructions or an explicit private configuration.
This is an independent community project. It is not affiliated with, endorsed by, or maintained by Alibaba.com or Alibaba Group.
中文说明：README.zh-CN.md
- Normalize product data from spreadsheets, structured records, and material folders.
- Bind each browser page to the correct product identity.
- Fill visible controls through genuine user-facing interactions.
- Handle titles, models, standard and custom attributes, SKUs, prices, delivery periods, packaging, logistics, after-sales settings, templates, and customs codes when applicable.
- Verify written values against source data.
- Detect copied-template residue and cross-product value leakage.
- Resume interrupted batches from verified state.
- Leave verified edit pages ready for human review by default.
- Save or submit only after explicit, current-task authorization for a clear product scope.
- Alibaba.com credentials, cookies, sessions, private APIs, or seller-account access.
- A bundled browser driver, MCP server, or screen-control implementation.
- Merchant-specific brands, templates, prices, logistics rules, or product data.
- Permission to bypass CAPTCHA, account verification, platform controls, or applicable policies.
- A guarantee that Alibaba.com page labels or form structure will remain unchanged.
Use an agent or browser-control adapter that can:
- Reuse the intended authenticated seller session.
- Inspect URLs, visible labels, accessible controls, dialogs, and validation messages.
- Perform real click, type, select, check, and upload actions when authorized.
- Read authoritative post-action state.
- Distinguish concurrent product pages.
- Pause for user-only steps such as CAPTCHA.
See the browser capability contract for the portable interface and evidence requirements.
Use the published GitHub repository:
codex plugin marketplace add ATP-01/alibaba-product-publishing
codex plugin add alibaba-product-publishing@alibaba-product-publishingStart a new Codex task after installation so the new skill is loaded.
The repository contains a repo-local marketplace at .agents/plugins/marketplace.json. The marketplace points to the skills-only plugin under plugins/alibaba-product-publishing/.
Copy this directory:
plugins/alibaba-product-publishing/skills/alibaba-product-publishing
to the user skill location:
$HOME/.agents/skills/alibaba-product-publishing
Codex normally detects skill changes automatically. Restart it if the skill does not appear.
Invoke it explicitly with:
$alibaba-product-publishing
Other agents can use the same SKILL.md when they support an equivalent skills format and implement the browser capability contract. Tool names do not need to match, but interaction and verification semantics must.
Copy the bundled example to a private location outside this repository:
plugins/alibaba-product-publishing/skills/alibaba-product-publishing/references/merchant-config.example.yaml
Rename the copy to merchant-config.yaml, replace only approved values, and pass its path in the task. Do not commit the real configuration.
Important defaults when no private configuration is supplied:
- preserve existing images, selling points, box specifications, templates, logistics, and after-sales settings;
- do not invent brand prefixes, prices, units, weights, certifications, or customs codes;
- do not save, submit, or publish;
- mark ambiguous required fields
needs_attention; - leave edit pages open for review.
Prepare and hand off without saving:
Use $alibaba-product-publishing to map products.xlsx and the product-materials
folder to the open Alibaba.com draft pages. Fill supported fields, verify each
page, and leave every page open. Do not save or submit.
Validate an existing batch:
Use $alibaba-product-publishing to compare these open product pages against
batch.csv. Report identity mismatches, missing required fields, copied-template
residue, and cross-product value leakage. Make no changes.
Use a private merchant configuration:
Use $alibaba-product-publishing with path/to/merchant-config.yaml to prepare
the listed drafts. The configuration applies only to this task. Stop at handoff.
An explicit final action must identify both the action and scope, for example:
After revalidating item IDs 123 and 456, save those two products as drafts.
Do not submit or publish them.
- Current user instructions override configuration defaults.
- Product identity must be verified before any write.
- Page evaluation is read-only; DOM or framework-state injection is prohibited.
- Every write must be followed by authoritative readback.
- Variant fingerprints detect product-to-product contamination.
- A field-level Apply action is not treated as product-level Save or Publish.
- Saving and submission require explicit authorization and server-backed confirmation.
- CAPTCHA and account-verification steps remain user-controlled.
.
├── .agents/plugins/marketplace.json
├── .github/
├── docs/release-checklist.md
├── plugins/alibaba-product-publishing/
│ ├── .codex-plugin/plugin.json
│ └── skills/alibaba-product-publishing/
│ ├── SKILL.md
│ ├── agents/openai.yaml
│ └── references/
├── scripts/validate_repo.py
└── tests/cases.json
Python 3.9 or newer is sufficient; the validator uses only the standard library.
python scripts/validate_repo.pyValidation checks:
- plugin and marketplace JSON;
- semantic version and matching component names;
- Skill frontmatter and reference targets;
- required public-repository documents;
- activation and safety test-case coverage;
- absence of known private merchant strings and local user paths.
GitHub Actions runs the same validator on Linux and Windows for every push and pull request.
Read CONTRIBUTING.md before opening a pull request. Never include real merchant data, credentials, cookies, product spreadsheets, screenshots from private seller pages, or live-account automation logs.
Security issues should follow SECURITY.md, not a public issue.
Released under the MIT License.