19926533763/swads-video-product-analysis
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Sync latest SW Ads analysis skill

Browse Source
This commit is contained in:
19926533763
2026-08-24 15:43:32 +08:00
parent 32ff46abea
commit 7d99bd9a23
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SKILL.md
+2 -1
View File
@@ -14,7 +14,8 @@ Produce an evidence-backed creative analysis from `swads` read data. Never mutat
3. Read `metrics_catalog` before querying. Do not guess metric or dimension names.
4. Default to the seven most recent **complete** business days. Use explicit `date_from` and `date_to` so incomplete today is excluded. Honor a user-specified window exactly, but flag incomplete current-day data.
5. If the user supplied product IDs, restrict the analysis to them. Otherwise analyze every product with video delivery in the window.
6. Call the read-only commerce product-list tool and map every `creative_product_id` to its current `product_name`. In Chinese output, translate each resolved product name into concise, natural Chinese for the **商品** column; remove redundant marketplace terms such as repeated “Ready Stock”, “Kitchenware”, hashtags, and duplicated keywords, but preserve material, capacity, size, piece count, and core product type. Keep the original platform `product_name` and numeric ID in JSON/HTML metadata for traceability. In non-Chinese output, use a concise truthful name in the report language. If a name cannot be resolved, use `未命名商品（ID末5位）` in Chinese; never invent product attributes or silently merge distinct product IDs.
6. Call the read-only commerce product-list tool and map every `creative_product_id` to its current `product_name`. In Chinese output, translate each resolved product name into concise, natural Chinese for the **商品** column; remove redundant marketplace terms such as repeated “Ready Stock”, “Kitchenware”, hashtags, and duplicated keywords, but preserve material, capacity, size, piece count, and core product type. Keep the original platform `product_name` and numeric ID in JSON/HTML metadata for traceability. In non-Chinese output, use a concise truthful name in the report language.
7. If a product name cannot be resolved after a reasonable retry, derive a concise category description from consistent, specific evidence in that product's video titles and use it directly in the **商品** column (for example `1.4L 滤油壶` or `304 不锈钢 24cm 汤锅`). Preserve material, capacity, size, piece count, and core product type only when the titles support them. In JSON/HTML metadata, keep the numeric product ID, set the original platform `product_name` to `null`, and record that the display name was inferred from video titles. If title evidence is absent, contradictory, or too generic, use `未命名商品（ID末5位）`. Never silently merge distinct product IDs, even when their inferred category descriptions are identical.
## Query and normalization