Build an Accio Skill for RFQ Quotation Packs (2026)

Core rule: Formal RFQ quotations use uploadable alibaba-rfq-quotation (pack rfq-quotation-pack): lock Opportunity Radar facts first, draft the four-part English quote with cost breakdown, keep send_gate=pending for human send. Never invent RFQ title/qty/buyer. Search-only hands off to discovery; casual inquiry uses K02; follow-up priority uses K05.

1. Why an RFQ quotation-pack Skill (vs K02 / K05 / encyclopedia)

When RFQs pile up in Opportunity Radar, the failure mode is rarely “English not pretty enough.” It is drafting a formal quote before detail is pulled, pasting a price list, inventing lead time, or treating a binding quotation like a casual TM reply. Once provided, the supplier is committed to the price. Low-quality quotes get dismissed while buyers compare multiple suppliers.

K06 turns “draft a high-quality English RFQ quotation” into an uploadable Accio Work Skill: lock facts first, write the official four-part structure, keep send in human hands. Boundary vs K02 four-factors: K02 serves casual inquiry/TM with gap tables and first replies; K06 serves formal quotations and requires official RFQ detail plus cost breakdown.

Boundary vs K05 triage: K05 decides who deserves human time; K06 drafts only after a human chooses to pursue a formal RFQ. Triage notes must not invent unit prices; quotation drafts must not decide strategic pursuit.

The encyclopedia piece RFQ conversion mastery teaches human/org conversion methods. This tutorial turns Seller Central “Quality quotations win quality deals” into a pack you can upload, dry-run, and accept. New to Skills? Start with K01. Hubs: tutorials and skills.

Acceptance is simple: invented title/qty/buyer means fact-lock failure; send_gate marked sent means gate failure; price-list-only with no RFQ answers means quality failure. Any hit blocks customer send.

Shipping this as a Skill—not “write English by feel”—keeps day and night shifts on one Hard-rules sheet. Agents draft; institutions keep fact locks, stop conditions, and the send key.

Train newcomers with a side-by-side: a price-list email that sits read-and-ignored versus a four-part quote with breakdown and validity. The gap is usually RFQ coverage and attainability—not “more native English.”

Say what the Skill cannot do: it will not set your floor strategy, run radar search patrols, or invent a “reasonable” price when master data is missing. Writing non-goals into onboarding reduces post-launch rule vandalism.

2. Download rfq-quotation-pack

Open SKILL.md first. Confirm YAML name: alibaba-rfq-quotation, description, triggers, and excludes: facts only from Opportunity Radar; no auto-send; search-only hands off to discovery; casual inquiry hands off to inquiry-conversion.

Also useful: inquiry-triage-priority.zip (K05) and inquiry-reply-four-factors.zip (K02). The pack is small—value is discipline and templates, not prose flair. Encode unit prices, cert filenames, and lead-time triggers in your local copy.

Right after download: (1) put SKILL.md in version control or a read-only share; (2) name a master-data owner; (3) name who may press send. Without those three, the Skill becomes a grey channel where anyone can change price.

Re-check the zip by unzipping locally: you must see rfq-quotation-pack/SKILL.md. Some OS “compress” flows nest an extra folder and break Accio detection—repack from the inner folder.

Open references/official-rules.md and confirm the official URL plus ten enforceable points remain. Project those two pages in training—more effective than saying “write quality quotes.” If you already have an internal Word quotation template, map authorized paragraphs under the four headings and delete any “flexible price change” language that conflicts with Hard rules.

3. Read SKILL.md (Capabilities / Hard rules / Workflow)

Key excerpts match the download file for side-by-side editing:

---
name: alibaba-rfq-quotation
description: "Alibaba.com seller RFQ quotation: pull RFQ facts via alibaba-rfq-discovery, then draft a high-quality English quotation with the official four-part structure (company background, echo needs plus product recommendation, total price including or excluding plus lead times, CTA or expiration). Once sent the quote is a binding cost-breakdown document. Use for RFQs, formal quotes, follow-up before expiry, agreed-quote change control. Search-only RFQ goes to alibaba-rfq-discovery. Not for casual inquiry first replies."
version: "2.0.0"
enabled: true
triggers:
  - RFQ报价
  - 正式报价
  - quotation
  - 四段报价
  - 报价跟进
  - 锁价
  - 收悉
  - cost breakdown
examples:
  - 这条 RFQ 详情已经从商机雷达拉下来了，按主数据出四段英文报价
  - RFQ 已经超过 24 小时，先写收悉
  - 帮我在全网找蓝牙耳机 RFQ
  - 买家只要询盘首复不要 quotation
  - 已达成报价有人要改交期
excludes:
  - skill: alibaba-rfq-discovery
    when: 用户只要搜索/筛选/巡检 RFQ、查详情、报价历史或报价权益，不要求生成报价草稿（官方技能明确不生成报价草稿）
  - skill: alibaba-inquiry-conversion
    when: 用户要回的是普通询盘/TM/站内信，不是正式 quotation
  - skill: alibaba-buyer-bgcheck
    when: 用户只要公网背调买家，不写报价
  - skill: alibaba-trade-assurance
    when: 用户只要 TA 开通/三件套/拒付，不写四段报价
  - skill: alibaba-chat-and-analysis
    when: 需要聊天上下文做已报价 RFQ 跟进话术
  - skill: alibaba-global-chat-analysis-pro
    when: 同上，本机安装文件夹名
  - skill: alibaba-cco-rag
    when: 只咨询 RFQ 平台规则/FAQ
  - skill: alibaba-analysis-brief
    when: 要的是店铺经营日报而不是报价正文
metadata:
  openclaw:
    author: gd-alibaba-ops
    homepage: https://www.accio.com/work
    emoji: "📝"
---

# Alibaba.com RFQ 高质量报价（RFQ Quotation）

对内中文，报价正文英文。报价一旦提供，即对价格负责。官方 `alibaba-rfq-discovery` **不生成报价草稿** — 本技能起草四段报价。

## Quick Demo

用户：「RFQ-88021 硅胶刮刀 2000 pcs，商机雷达 detail 已返回，主数据 FDE-DEMO-001。」

智体：

1. `rfq_source.skill=alibaba-rfq-discovery`（或中文名 国际站商机雷达）。事实只来自 `workctl workflow rfq detail`（及需要时 `search` / `quote-history` / `quote-detail` / `workctl icbu rfq rfq-quote-rights-detail`）。
2. 按 [Quality quotations win quality deals](https://seller.alibaba.com/businessblogs/quality-quotations-win-quality-deals-px7uo467) 写四段英文 + 成本拆解。
3. `send_gate=pending`。输出 `lock_price_warning`。
4. 用户说「帮我找 RFQ」且不要报价 → `handoff` `alibaba-rfq-discovery`，`quote_kind=none`。

## Capabilities

- 从官方商机雷达拉取 RFQ 标题/数量/买家，禁止发明字段。
- 完整四段报价或 24h 超时先 ack。
- 锁价警告：达成后未经双方书面同意不得改价改期。
- Search-only → 排除到 `alibaba-rfq-discovery`；inquiry-reply → `alibaba-inquiry-conversion`。
- 报价权益/额度查询交给官方 `workctl icbu rfq rfq-quote-rights-detail`，本技能不编额度。

## How It Works

1. **必须先取事实**：调用/交接 `alibaba-rfq-discovery`（frontmatter name: 国际站商机雷达）。允许的 workctl 仅：
   - `workctl workflow rfq detail`
   - `workctl workflow rfq search`
   - `workctl workflow rfq quote-history`
   - `workctl workflow rfq quote-detail`
   - `workctl icbu rfq rfq-quote-rights-detail`
2. 官方技能明确：**不生成报价草稿**；不处理询盘/买家消息/聊天/跟进话术。本技能补「起草四段报价」这一层。
3. Search-only 意图：不要在本技能里搜。`excludes` → `alibaba-rfq-discovery`。
4. 主数据：单价、成本拆解、交期、证书必须可指回 schema 行或用户当次确认。
5. 买家公开页研究：只记 RFQ 原文、用户补充、可见句。输出「已知 / 未见」。
6. 超过 24 小时：先 `quote_kind=ack`，告知完整报价送达时间，不报死价。
7. 不点「发送报价」。`send_gate=pending`。

## Agent Instructions

官方硬约束（`references/official-rules.md`）：https://seller.alibaba.com/businessblogs/quality-quotations-win-quality-deals-px7uo467

- 报价是带详细成本拆解的正式文件。一旦提供，供应商对价格负责。
- 低质量 = 通用邮件、不称呼到人、只丢价目表。高质量 = 称呼询价人、回答 RFQ 要点、按需求推荐、成本拆解。
- 先研究买家公司。尽量 24 小时内回复 RFQ；来不及则先发收悉并告知报价何时到达。
- 结构：(1) Company background / capability (2) Echo requirements + recommend + why (3) Total price, included, excluded, timeframes (4) CTA / valid-through。
- 报价一旦达成，价格或交期未经双方书面同意不得更改。无回复要跟进，尤其存在有效期时。
- 「Win Your Business With Such Quotations」：研究买家；写清产品描述与付款条款；管理跟进；丢单征求反馈。本包无独立 URL，按标题引用。

逐步：

1. 盖到达时间。完整报价能在 24h 内完成则研究；否则先英文 ack。Ack 也须用户确认后发。
2. 确认 `rfq_facts_available`。没有官方 detail 成功返回：不得填写 `rfq_title` / `quantity` / `buyer_company`，不得 `quote_kind=full`。
3. 拆 RFQ 要点表。每条：已答 / 缺主数据。
4. **停顿（完整报价不得发出）**：缺可授权单价或成本拆解；交期不能兜底；要求的证书未持有；付款/模具/运费/检测费未授权；推荐型号不在主数据。
5. 按 `references/quotation-template.md` 写四段。有效期天数由用户指定。`four_parts_present=true` 或列出 `four_part_headings`。
6. 核对：总价与拆解相加一致；包含/不包含无矛盾；TA 表述遵守 `alibaba-trade-assurance`（不写未证实费用）。
7. 中文风险 + `lock_price_warning`。`official_citations` 必须含 quality-quotations URL（完整报价强制）。
8. 用户意图 `search_only` → `status=handoff` + `handoff.skill=alibaba-rfq-discovery`。`inquiry_reply` → `alibaba-inquiry-conversion`。

禁止：发明 RFQ 标题/数量/买家；提交报价；编造证书/产能/验厂；达成后单方面改价改期；写 TA 费用/赔付/纠纷胜率；劝下平台；发明列表外的 workctl。

## Error Handling

| 情况 | 动作 |
| --- | --- |
| 无官方 RFQ detail | `status=stop/handoff/ack`，`quote_kind` 不得为 `full` |
| 用户只要搜 RFQ | handoff `alibaba-rfq-discovery`（`workctl workflow rfq search`） |
| 用户要回询盘 | handoff `alibaba-inquiry-conversion` |
| RFQ 已过 24h | 先 ack，不要直接 full（除非 status=stop） |
| 缺主数据价/证/期 | STOP，占位符保留，不编 |
| 已达成要改价改期 | 无双方书面 + 用户授权则拒绝出新价草稿；`alibaba-trade-assurance` 锁价 |
| 需要公网背调 | `alibaba-buyer-bgcheck` |
| 拒付 | 不是本技能；见 `alibaba-trade-assurance` → `alibaba-chargeback-appeal-assistant` |
| `invented_rfq_fields` 非空 | 校验失败，删掉发明字段 |

## Related Accio Skills

- `alibaba-rfq-discovery` / 国际站商机雷达：搜索、detail、quote-detail、quote-history、quote-rights。不写报价草稿。
- `alibaba-inquiry-conversion`：非正式询盘。
- `alibaba-buyer-bgcheck`：公网背调。
- `alibaba-trade-assurance`：接单前三件套、禁止下平台。
- `alibaba-listing-quality`：报价依赖的规格缺口。
- `alibaba-cco-rag`：RFQ 规则 FAQ。
- `alibaba-global-chat-analysis-pro` / `alibaba-chat-and-analysis`：已报价跟进需要聊天上下文时。

## 官方硬约束

来源：[Quality quotations win quality deals](https://seller.alibaba.com/businessblogs/quality-quotations-win-quality-deals-px7uo467)（Alibaba.com Seller Central）。摘录见 `references/official-rules.md`。

- 报价是带成本拆解的正式文件；一旦提供即对价格负责。
- 高质量 = 称呼到人、回答 RFQ 要点、按需求推荐、成本拆解。
- 先研究买家（只用官方 detail / 可见原文）。
- 尽量 24 小时内回 RFQ；否则先 ack 并告知送达时间。
- 四段结构：背景能力 / 复述需求并推荐 / 总价+含与不含+交期 / CTA 或有效期。
- 达成后未经双方书面同意不得改价改期。必须可兑现。
- 无回复要跟进，尤其有有效期。

「Win Your Business With Such Quotations」仅按标题引用（本包无独立 URL）。RFQ 事实必须来自 `alibaba-rfq-discovery` / 国际站商机雷达的 `workctl workflow rfq detail`。

## 禁止事项

- 不称呼、只丢价目表。
- 发明 RFQ 标题/链接/数量/买家。
- 报无法兑现的价格或交期；编造证书/产能。
- 提交报价或 `send_gate=sent`。
- 达成后单方面改价改期。
- 发明 TA 费用、转化率、Gold Supplier 价格。
- 发明 workctl 子命令（允许的仅官方商机雷达摘录：search / detail / quote-detail / quote-history / rfq-quote-rights-detail）。
- 劝下平台躲避 TA。

YAML excludes define what must not enter this Skill. A prompt like “find Bluetooth RFQs worldwide and quote them” should hand off to discovery, not force full. “Reply to this TM” should hand off to inquiry-conversion.

Keep Chinese triggers (RFQ报价, 正式报价, 锁价, 收悉) so sellers can invoke the Skill in their own language. Positive/negative examples in YAML are training assets—pair them with the Error Handling table on the wall.

Turn the Agent Instructions checklist into a night-shift toggle: if costing cannot finish, force ack—never force full. Related Skills (discovery, inquiry-conversion, bgcheck, trade-assurance, listing-quality, chat analysis) are a routing map, not optional reading.

4. Four-part English quotation structure (diagram)

Official structure from Seller Central “Quality quotations win quality deals”: (1) company background/capability (2) echo needs + recommend + why (3) total price, included, excluded, timeframes (4) CTA/valid-through. Low quality = generic email, not addressed, price list only. High quality = addressed, answers RFQ points, recommends for needs, cost breakdown.

Template lives in references/quotation-template.md. Unknown money/time fields stay [TO_BE_CONFIRMED]—do not send a complete quote until replaced. Optional internal “source” columns can be deleted before send.

Addressing is not fluff: use the inquirer’s first name when present, else the company—never Dear Sirs + price list. Recommendation reasons must tie to real specs/certs.

Included/Not included is a dispute firewall. Tooling, tests, rush, special packing, destination fees: authorize and price them, or explicitly exclude them.

CTA may invite spec confirmation, Trade Assurance order, or a reply before expiry. Do not pretend an order already exists. Post-expiry follow-up can hand off to chat-analysis skills, still bound by lock-price rules.

5. Fact locks, master-data stops, and send_gate

Three fact locks: (1) rfq_facts_available true with facts from workctl workflow rfq detail (or official discovery); (2) unit price, breakdown, lead time, certs referenceable to schema or user confirmation; (3) public research records only RFQ text, user notes, visible sentences—“known / not seen.”

Lock-price warning is not decoration: after agreement, price/lead time cannot change without written bilateral consent. Without consent + user auth, refuse a new price draft.

Allowed workctl verbs are a whitelist. Inventing “rfq auto-quote” fails Hard rules. Quote-rights queries use the official rights-detail command—never invent quota numbers.

Emit “known / not seen” to stop hallucinated buyer scale. Route public background checks to buyer-bgcheck. Non-empty invented_rfq_fields must fail validation hard.

Chinese risk block can be four fixed lines: draft not sent; price from master-data row X; cert filenames; lock-price warning. Supervisors scan in seconds; English body stays clean.

6. Folder layout, zip upload, Agent bind

Good layout: zip root is rfq-quotation-pack/ containing SKILL.md, then references/, scripts/, evals/. Bad layout: nested shells, or SKILL.md alone without references (templates vanish).

Generic zip / upload / test-run steps: see K01 — What is an Accio Work Skill. Package-specific: assign to an “RFQ quotation / opportunity follow-up” Agent; keep triage on K05 and casual inquiry on K02.

Prompt example: Use the alibaba-rfq-quotation skill. RFQ detail is already available from alibaba-rfq-discovery. Draft a four-part English quotation with cost breakdown from master data. Keep send_gate=pending. Do not submit. If facts are missing, STOP and list gaps.

Search-only → handoff discovery with quote_kind=none. Casual inquiry → inquiry-conversion. Dry-run mixed intents to prove routing.

After upload, confirm description still carries quotation/four-part/lock-price triggers and excludes stay intact. Deleting excludes “to trigger easier” pollutes outputs with search jobs.

Least-privilege: quotation duty can run the Skill; master-data admins edit local appendices; junior sellers read outputs. Do not give send or lock-price rights to intern accounts.

Bind clear Agent duties: this Agent only drafts formal RFQ quotations; search patrol is another Agent; casual inquiry is another. Share a read-only master-data source, but keep triggers and excludes separate so they do not steal each other’s jobs.

7. Dry-run drills (full / ack / search-only)

User: RFQ detail pulled from Opportunity Radar. Title Food-grade silicone spatula 800 pcs; buyer Northwind Imports LLC; master data FDE-DEMO-001, USD 1.85, 18 days after TA confirmation, LFGB file FDE-DEMO-001-LFGB.pdf. Draft four-part EN quote, validity 7 days. Do not send.

Pass shape: quote_kind=full, four_parts_present=true, send_gate=pending, rfq_source.skill=alibaba-rfq-discovery, citations include the quality-quotations URL, Chinese risk + lock_price_warning present. Fail shape: invented buyer scale, unauthorized DDP, or send_gate=sent.

User: This RFQ is past 24 hours; pricing still under review. Write an acknowledgment promising the full quote by 12:00 UTC+8 tomorrow. No hard price. Do not send.

Pass: quote_kind=ack, English receipt with arrival time, no hard unit price, send_gate pending. Fail: fake full with a “temporary” price, or auto-sent ack.

User: Find Bluetooth earphone RFQs for me—no quotation yet.

Pass: status=handoff, handoff.skill=alibaba-rfq-discovery, quote_kind=none. Fail: invent RFQ lists and attach fake quotes. Fixtures pass_exclude_search, pass_handoff_search_only, fail_invent_rfq lock this.

Optional fourth drill: agreed quote, buyer wants one week earlier without price change. Pass refuses unilateral lead-time change + lock_price_warning; fail quietly drafts a new schedule.

Store pass/fail outputs in an internal wiki. Week-one onboarding runs samples only—no live customer send.

Full-quote internal checklist: rfq_source→discovery; four headings present; total equals breakdown; include/exclude consistent; TA wording invents no fees; citations include official URL; send_gate=pending; lock_price_warning present.

8. Failure cases, stop-loss, series handoffs

SOP: drafts sit in a pending-confirm queue, not the buyer thread; full requires four parts + master-data refs + pending gate; lock-price changes need dual sign-off; weekly sample 10 against eval fixtures.

Series: queue explosion → K05; casual inquiry → K02; formal RFQ quote → K06; listing gaps → K03; DDP/duty questions → K04; conversion methods → encyclopedia; human tone → S05.

Boss note: Skills cut structure errors and invented fields—they do not erase price wars. Floor approval, credit, and sample policy stay human.

Quarterly fire drill: inject no-detail, overdue, and search-only tasks; record whether the Agent routes correctly before go-live expansions.

Encyclopedia teaches why conversion works; this Skill teaches how machines draft without overreach. Train encyclopedia first, Skill second—so rookies do not believe “Skill means I need not understand RFQs.”

Weekly review path: sample sent quotes for leftover placeholders, sends without detail, and lock-price disputes. Any true hit pauses automation until Soft prompts and Soft training are fixed—category expansion waits.

9. Acceptance checklist & weekly boss dashboard

1. Zip downloads; unzip shows rfq-quotation-pack/SKILL.md + references/evals;
2. Upload + assign to RFQ quotation Agent succeeds;
3. Three samples stable: full / ack / handoff with send_gate pending;
4. Hard rules not bypassed (no invent, no auto-submit, no unilateral change, no fake TA fees);
5. Master-data refs auditable (SKU, cert filenames, lead-time trigger);
6. Within a week, ≥15 real RFQs reviewed with falling supervisor rewrite rate.

Dashboard six columns: daily full/ack/handoff/stop counts; median detail→human-confirm time; blocked sends with unresolved placeholders; lock-price escalations; invented-field blocks; 7-day reply rate after quote. Friday 20 minutes: change rules or change approvers?

Local field table (7 cols): field, master-data source, authorizer, default validity, allowed in quote?, last calibration, notes. Stale >30 days → yellow.

Roster: full drafts to quotation duty; acks may be confirmed by assistants; search-only to radar patrol; lock-price changes visible only to named owners.

Audit path: store RFQ ID, detail pull time, model output, final human text, sent?, won/dispute. Monthly sample 20 for invent rate, missing-part rate, unauthorized price rate.

If search-only becomes full, harden excludes and prefix prompts. If acks still contain hard amounts, ban currency amounts in ack outputs.

Watch people, not only metrics: is send authority centralized, are lock-price escalations signed, are master-data changes broadcast to quotation duty? A perfect Skill with scattered permissions will be bypassed.

10. Encode company policy into quotation rules

Localize four blocks: authorized company intro; master-data schema (unit/tiers/tooling/tests/packing); cert inventory + filenames; lead-time triggers (deposit / TA confirm / artwork sign-off). Short sentences beat culture essays.

Payment terms and Incoterms require authorization. No DDP auth → do not write DDP. No tooling auth → omit the row. Trade Assurance: state enabled-or-not only; fees/payouts stay on official pages.

Validity defaults: e.g. 7 days standard, 3 days custom, daily refresh for FX-sensitive materials. Put defaults in an appendix; prompts only override exceptions.

Freight unknown → Not included: freight separately quoted—do not invent a round number buyers treat as a promise.

Language split: Chinese risk/checklist internally; English four parts externally. Never paste internal floors, margins, or customer lists into the English quote.

Multi-entity sellers must switch letterhead/certs by booking entity. Sample vs bulk prices: do not sneak unauthorized sample lines into a bulk RFQ.

Compliance lines for EU/US cite held cert filenames and scope—never “meets all regulations.”

For multi-brand entities, switch background, certs, and banking references with the booking entity. Mixing letterheads is a quiet compliance failure.

11. Using eval fixtures as regression

Every SKILL.md/template change runs the suite (scripts/validate_case.py or your runner). Failures block release. Catch “one description tweak killed excludes” before customers do.

Monthly add 2–3 desensitized real fixtures for your category’s worst foot-guns (food-contact, powered goods, tooling customs). Prefix pass_/fail_ for scanning.

Fixture prices/companies must be fake or scrubbed—never commit live customer unit prices to public repos or public tutorials.

Keep fail fixtures with bad sample outputs so rookies see invented fields and fake submits, not only prose rules.

Wire the suite into CI or a Friday script; post failures to the duty chat with an owner.

Treat eval failures as release blockers with a named owner. Without a cadence, fixtures rot into unread JSON within a quarter.

12. Versioning & duty roster

Bump YAML version whenever Hard rules, templates, or excludes change. Wiki changelog: who/why/fixture results. Rollbacks need receipts.

Duty map: who may confirm full on day/night shifts; whether holiday acks may be sent by assistants; lock-price escalation level. Pin the map atop the Agent brief.

Prior customers still require fresh official detail—never override master data with “the old price we remember.” Old prices are internal hints until re-authorized.

Align with radar patrol: morning search/rights via discovery, then quotation-pool RFQs into this Skill. Do not make the quotation Agent double as worldwide search.

When one of SKILL.md / template / official excerpt / SOP changes, check the other three for drift. Stale templates are silent incident sources.

On release day, freeze master-data writes ~30 minutes; blind-test three live RFQs before opening to all sellers.

Publish duty roster with the Skill version. If a buyer claims “last week’s price,” answer with version + change log—not conflicting memories.

If Accio UI labels change after a client upgrade, refresh internal screenshots; keep tutorial diagrams semantic and language-matched.

Pair Skill version numbers with duty rosters in the same announcement. Customer “price last week” disputes become documentation problems, not shouting matches.

13. FAQ