product-loader

Name: product-loader
Author: Xuxchloris

17stars2forks

How to install product-loader?

xuxchloris/export_skills/product-loader

$npx -y skills add Xuxchloris/export_skills --skill product-loader

Installs into the current project.

Summary

Use when a trade agent needs product catalog, SKU, specification, packaging, price-rule, MOQ, certification, lead-time, or factory profile data before research, outreach, scoring, or quotation work

Files · 1

View on GitHub

SKILL.md

1	# Product Loader
2
3	## Overview
4
5	Load product and company facts from configured files before any trade workflow uses them. The core rule is simple: no product claim, price, certification, MOQ, packaging size, or delivery promise may be invented.
6
7	## When to Use
8
9	Use this skill when the user asks about product matching, customer development, quotations, product introductions, catalogs, factory advantages, packaging details, model numbers, or delivery terms.
10
11	Do not use it to research a prospect website or write the final email body by itself.
12
13	## Inputs
14
15	- `data/config/PRODUCT.yaml`
16	- `data/config/PRICING.yaml`
17	- Optional product catalog file with multiple SKUs
18	- Optional product query or SKU when the user only wants one product from a catalog
19	- User-provided product notes in the current conversation
20
21	## Outputs
22
23	```json
24	{
25	"company": {},
26	"products": [],
27	"pricing_rules": [],
28	"missing_fields": [],
29	"safe_to_quote": false
30	}
31	```
32
33	## Procedure
34
35	1. Read `PRODUCT.yaml` and extract company profile, SKUs, product names, HS codes, materials, dimensions, packaging, MOQ, lead time, certifications, applications, and keywords.
36	2. Read `PRICING.yaml` and extract currency, incoterm, validity, payment terms, tier prices, sample fees, and remarks.
37	3. If the user names a product, keyword, or SKU, select the matching product from the catalog instead of asking them to rewrite the whole config.
38	4. Prefer current conversation facts only when the user explicitly overrides the configured file.
39	5. Mark missing fields instead of guessing them.
40	6. Set `safe_to_quote` to `true` only when SKU, quantity, unit price, incoterm, payment terms, validity, product size, and packing size are present.
41	7. Return a compact product context for downstream skills.
42
43	## Verification
44
45	- Product names and SKUs match the source file.
46	- Catalog selection returns the named product only.
47	- Prices come only from `PRICING.yaml` or explicit user input.
48	- Missing price, size, packing, MOQ, incoterm, or lead time is listed in `missing_fields`.
49	- Certifications are not added unless present in source data.
50	- `safe_to_quote` is `false` when any required quotation field is missing.
51
52	## Common Mistakes
53
54	\| Mistake \| Fix \|
55	\| --- \| --- \|
56	\| Guessing a price from a similar SKU \| Ask for confirmation or mark price missing \|
57	\| Treating marketing advantages as certifications \| Keep certifications in a separate field \|
58	\| Using one product's packing size for another SKU \| Match by exact SKU \|
59	\| Producing a formal quotation with missing freight terms \| Produce a draft with human review required \|

People who liked this also viewed

6 picks

Type

product-loader

17stars2forks

View on GitHub

How to install product-loader?

xuxchloris/export_skills/product-loader

$npx -y skills add Xuxchloris/export_skills --skill product-loader

Installs into the current project.

Summary

Use when a trade agent needs product catalog, SKU, specification, packaging, price-rule, MOQ, certification, lead-time, or factory profile data before research, outreach, scoring, or quotation work

Files · 1

View on GitHub

SKILL.md

1	# Product Loader
2
3	## Overview
4
5	Load product and company facts from configured files before any trade workflow uses them. The core rule is simple: no product claim, price, certification, MOQ, packaging size, or delivery promise may be invented.
6
7	## When to Use
8
9	Use this skill when the user asks about product matching, customer development, quotations, product introductions, catalogs, factory advantages, packaging details, model numbers, or delivery terms.
10
11	Do not use it to research a prospect website or write the final email body by itself.
12
13	## Inputs
14
15	- `data/config/PRODUCT.yaml`
16	- `data/config/PRICING.yaml`
17	- Optional product catalog file with multiple SKUs
18	- Optional product query or SKU when the user only wants one product from a catalog
19	- User-provided product notes in the current conversation
20
21	## Outputs
22
23	```json
24	{
25	"company": {},
26	"products": [],
27	"pricing_rules": [],
28	"missing_fields": [],
29	"safe_to_quote": false
30	}
31	```
32
33	## Procedure
34
35	1. Read `PRODUCT.yaml` and extract company profile, SKUs, product names, HS codes, materials, dimensions, packaging, MOQ, lead time, certifications, applications, and keywords.
36	2. Read `PRICING.yaml` and extract currency, incoterm, validity, payment terms, tier prices, sample fees, and remarks.
37	3. If the user names a product, keyword, or SKU, select the matching product from the catalog instead of asking them to rewrite the whole config.
38	4. Prefer current conversation facts only when the user explicitly overrides the configured file.
39	5. Mark missing fields instead of guessing them.
40	6. Set `safe_to_quote` to `true` only when SKU, quantity, unit price, incoterm, payment terms, validity, product size, and packing size are present.
41	7. Return a compact product context for downstream skills.
42
43	## Verification
44
45	- Product names and SKUs match the source file.
46	- Catalog selection returns the named product only.
47	- Prices come only from `PRICING.yaml` or explicit user input.
48	- Missing price, size, packing, MOQ, incoterm, or lead time is listed in `missing_fields`.
49	- Certifications are not added unless present in source data.
50	- `safe_to_quote` is `false` when any required quotation field is missing.
51
52	## Common Mistakes
53
54	\| Mistake \| Fix \|
55	\| --- \| --- \|
56	\| Guessing a price from a similar SKU \| Ask for confirmation or mark price missing \|
57	\| Treating marketing advantages as certifications \| Keep certifications in a separate field \|
58	\| Using one product's packing size for another SKU \| Match by exact SKU \|
59	\| Producing a formal quotation with missing freight terms \| Produce a draft with human review required \|

People who liked this also viewed

6 picks

Type