agentsclimarketplace
Sign in

Alibaba inquiry review

Skill tanghongming0/renyi-alibaba-ops/skills/alibaba-inquiry-review

Prepare an Alibaba International Station inquiry review or weekly inquiry meeting from inquiry, IM conversation, salesperson, and follow-up data. Use when asked to review inquiry handling, identify neglected buyers, evaluate salesperson follow-up quality, prepare a weekly inquiry meeting, or produce owner-and-deadline action items. Keep verified data, interpretation, and missing evidence separate; never send messages or change backend data.From its SKILL.md

Install
npx -y skills add tanghongming0/renyi-alibaba-ops --skill alibaba-inquiry-review

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

3 things to look at

  • 21 days oldThe repository was created 21 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 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.

SKILL.md

2.1 KB, 333 tokens by cl100k_base, as published. Nobody here has run it

Alibaba Inquiry Review

Prepare a manager-ready inquiry review without performing external writes.

Workflow

  1. Confirm the requested period. If unspecified, use Monday 00:00 through the current time and state it.
  2. Inventory available evidence before judging performance.
  3. Normalize inquiry, buyer, salesperson, timestamp, status, and conversation fields.
  4. Identify reply delays, read-without-reply, missing follow-up, shallow replies, unclear next steps, and high-value buyers needing attention.
  5. Rank issues using prioritization.md.
  6. If the user requests Outlook context, follow outlook-integration.md.
  7. Produce the required meeting structure below.

Evidence rules

  • Label platform-visible or source-row facts as verified.
  • Label calculated fields with the calculation and source range.
  • Label interpretation as a review judgment.
  • Mark unavailable data explicitly; never fill gaps with assumed values.
  • Do not call a buyer high-value unless the source supplies a level or concrete buying signals.
  • Do not expose credentials, internal tool names, raw error traces, or private contact details.
  • Draft follow-up language only. Never send messages, upload files, publish products, or change configuration.
  • Treat Outlook as an optional evidence source, not as permission to search the entire mailbox.

Required output

  1. Review period and evidence coverage
  2. Inquiry overview
  3. Salesperson review
  4. Priority inquiry list
  5. Meeting questions
  6. Next-week action table

Every action must contain an owner, buyer or inquiry, deadline, and verification method.

What ships with it: 3 files

2.0 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 326,401. 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.