Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Codex-native supplier sourcing and outreach workflow for Alibaba using LaunchFast research. Use when the user wants supplier shortlists, outreach messages, reply triage, or negotiation support. Requires `supplier_research`. Browser automation is optional but useful when the user wants Codex to interact with Alibaba directly.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-10 | ✗→✓ | ▲ Improved | -42% | 0% |
| case-03 | ✗→✓ | ▲ Improved | -14% | 0% |
| case-05 | ✗→✓ | ▲ Improved | -18% | 0% |
| case-06 | ✗→✓ | ▲ Improved | -21% | 0% |
| case-07 | ✗→✓ | ▲ Improved | 37% | 0% |
This skill has three modes: outreach, reply review, and follow-up drafting.
Use these defaults when the user does not care:
./artifacts/launchfast/supplier-conversations/Ask once for:
Run:
textsupplier_research(keyword="<keyword>", goldSupplierOnly=true, tradeAssuranceOnly=true, maxResults=10)
Present a compact shortlist with:
Use this structure:
Always show the message to the user before sending it anywhere.
If the user wants Codex to send messages and browser automation tools are available, use this concrete flow:
Contact Supplier or reply form.If browser automation is unavailable, stop after drafting the approved message set.
Store outreach notes under:
./artifacts/launchfast/supplier-conversations/[supplier-slug]/conversation.md
Keep a simple index file at:
./artifacts/launchfast/supplier-conversations/index.md
When the user asks to check replies:
If browser automation is unavailable, ask the user to provide exported text or screenshots and continue from that material.
When drafting or sending a reply:
If browser automation is used for the send:
Other measured skills in the registry, with their headline benchmark lift.