product-description-guardrails
Skill1 starsChanged 18 days agoMITView on GitHub
Generate product titles and descriptions only from catalog facts, and block prices, certifications, and medical claims that are not in the record. Use when writing or reviewing generated product copy, Merchant Center text, or locale-specific descriptions.
In this repository28 other files it gives its agents.
- b2b-pricingSkill
- catalog-import-and-migrationSkill
- checkout-ux-and-conversionSkill
- conversion-event-trackingSkill
- ecommerce-seo-structured-dataSkill
- fraud-and-risk-basicsSkill
- google-merchant-product-feedsSkill
- headless-nextjs-storefrontSkill
- inventory-and-multi-warehouseSkill
- iranian-payment-gatewaysSkill
- marketplace-search-and-rankingSkill
- mcp-store-toolingSkill
- multi-vendor-payoutsSkill
- order-and-webhook-reliabilitySkill
- payment-gateway-integrationSkill
- product-catalog-modelingSkill
- returns-and-refundsSkill
- rtl-and-persian-localizationSkill
- shopify-app-developmentSkill
- storefront-accessibilitySkill
- storefront-performanceSkill
- stripe-paymentsSkill
- subscription-billingSkill
- tax-and-shippingSkill
- vector-product-searchSkill
- woocommerce-plugin-developmentSkill
- woocommerce-rest-apiSkill
- wordpress-plugin-securitySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Write the description from those facts only.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product description guardrails
Use this skill when copy is generated from a catalog record. The feed skill decides which Merchant Center attribute receives that copy. Search text normalization is the search skill. This skill does not claim the copy is true. It keeps the copy inside the facts you passed in.
Procedure
- Pass a source record: name, price, currency, locale, and the facts that may be stated (materials, dimensions, color, care, certifications).
- Write the description from those facts only. If a fact is absent, omit it. Do not fill the gap with a typical value for that category.
- Either omit the price or state the source price and currency. Do not round it into a different amount.
- Refuse medical, safety, and guarantee claims that are not in the source. The checker encodes a short refuse-list, not a legal opinion.
- Match the locale. A
fa_IRdescription is Persian. Do not mix a generated English paragraph into that field. - Run
node scripts/check-description.mjs --description copy.txt --source source.json.
The refuse-list and the Merchant Center labeling rule are in the claim notes. Worked examples and checks are in evals/tasks.json.
Source record
{
"name": "Cotton shirt",
"price": "19.00",
"currency": "USD",
"locale": "en",
"facts": ["short sleeve", "cotton", "blue"],
"allowedClaims": []
}allowedClaims is empty unless the merchant has supplied the exact claim that may be repeated, such as a certification number that is already in facts.
What may be written
- The product name and the facts, in the locale's language.
- Care or sizing text that appears in
facts. - The price only as
{price} {currency}.
What may not be written
- A material, dimension, country of origin, or certification that is not in
facts. - "Cures", "clinically proven", "guaranteed to", "100% effective", or "risk-free", unless that phrase is listed in
allowedClaims. - Another product's name, a competitor, or "free shipping".
- A sale price the source does not contain.
- Stars or review counts that are not in the source.
Merchant Center
Google's product data specification says generated titles and descriptions use structured_title and structured_description with digital_source_type set to trained_algorithmic_media. Text that was not generated uses title and description. The feed skill checks lengths: 150 characters for a title and 5000 for a description.
Checker limits
scripts/check-description.mjs checks:
- non-empty text at most 5000 characters
- any
{amount} {CURRENCY}in the text matchespriceandcurrency - the refuse-list phrases above, unless present in
allowedClaims
It does not detect a made-up material that lacks those phrases. Review the facts list. A passing check is not a statement that the description is accurate.
Gotchas
- Translating a fact is allowed. Adding a fact during translation is not. "Cotton" may become the Persian word for cotton. It may not gain "organic".
- A marketing model will add "perfect for" and a use the catalog never stated. Keep the sentence tied to a fact or delete it.
- Putting the price in Persian digits in the description is a display choice. The checker looks for ASCII
{amount} {CURRENCY}. Do not also embed a different ASCII amount.
Verification
- The checker fails a description that says
15.00 USDwhen the source price is19.00. - The checker fails "clinically proven" when
allowedClaimsis empty. - A
fa_IRrequest does not return an English-only description. - Generated Merchant Center text is labeled
trained_algorithmic_media.
Evaluation
Worked examples and the checks they must satisfy are in evals/tasks.json.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

