← Tailor.aiCONTENT HISTORY

Update to Tailor.ai

Snapshot Oct 29, 2026 · 19:13 UTC · version 1.0.2

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Tailor.ai and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Put together a complete outfit from Tailor's shops for an occasion, dress code, season or budget. Use when someone asks what to wear to something (a wedding, interview, date, party, holiday), wants a full look or several pieces that go together, or asks to be styled.",
  "included_files": [],
  "name": "build-an-outfit",
  "skill_md_contents": "---\nname: build-an-outfit\ndescription: Put together a complete outfit from Tailor's shops for an occasion, dress code, season or budget. Use when someone asks what to wear to something (a wedding, interview, date, party, holiday), wants a full look or several pieces that go together, or asks to be styled.\n---\n\n# Build an outfit with Tailor\n\nA good outfit answer is a small set of pieces that clearly go together, fits the\noccasion and the budget, and can be bought in the user's own country. Plan it like a\nstylist, then use Tailor's tools to find each piece.\n\n## 1. Get the brief\n\nWork out these before searching. Infer what you can from the conversation and ask\nonly for what's missing, in one short question:\n\n- **Country**: `za`, `us` or `gb`. Every search needs it, and prices are in that\n  shop's currency.\n- **Who it's for**: `department` is `women`, `men`, `kids` or `baby`.\n- **Occasion and dress code**, plus season or weather if it matters.\n- **Budget** for the whole outfit, if they have one.\n- **What they already own** that the outfit should build around. Don't search for\n  those pieces.\n\nSize is optional. Use the `size` filter only when the user gives one, in the shop's\nown size system.\n\n## 2. Plan the pieces\n\nList the garments before searching, usually 3 to 5: the main piece or pieces (dress,\nor top and bottom, or suit), a layer if the weather needs one, shoes, and one\naccessory or bag. Turn the dress code into concrete descriptions:\n\n| Dress code | What it usually means |\n| --- | --- |\n| Black tie | Floor-length gown, or a dark suit or tuxedo with a white shirt |\n| Cocktail / formal | Knee-to-midi dress or tailored jumpsuit; dark suit, tie optional |\n| Smart casual | Tailored trousers or dark jeans, shirt or fine knit, blazer optional, loafers or clean leather sneakers |\n| Business casual | Chinos or tailored trousers, shirt or blouse, knit or blazer |\n| Daytime wedding guest | Light midi dress or linen suit; avoid white, and avoid all-black unless the user wants it |\n| Beach / resort | Linen, cotton, sandals, swimwear and a cover-up |\n\nPick a palette before searching: one or two neutrals plus at most one accent colour.\n\n## 3. Split the budget\n\nGive each piece a share of the budget and pass it as `price_max` in that country's\ncurrency. As a rough guide, the main piece takes 35 to 45%, shoes 20 to 25%, a layer\n15 to 20% and the bag or accessory the rest. Keep the total within the budget.\n\n## 4. Search one piece at a time\n\nCall `search_products` once per garment, with `country`, `department` and the piece's\n`price_max`. Write the query the way a product page would describe the garment, such as\n\"sage green satin slip midi dress\" or \"tan suede block-heel sandals\", not \"something\nfor a wedding\". Add `colour_family` when the palette fixes a colour.\n\nIf a piece has no good match, rephrase the query or loosen one filter. If something\nis close, try `tailor_product` on it (\"same, but in navy\", with `colour_family` for a\ncolour change) or `find_similar_products` with the same `product_type`.\n\n## 5. Choose and present\n\nPick one item per piece so that colours, formality and fabrics work together. Prefer\nthe better fit over the cheapest option. Then call `show_products` once, with the\nchosen `product_id`s in wearing order (main piece, layer, shoes, bag) and a `title`\nsuch as \"Your summer wedding look\".\n\nThe cards already show photos, prices and links, so don't list the products again in\ntext. Add what cards can't show:\n\n- why the pieces work together, in two or three sentences\n- the total price, in the shop's currency\n- one swap, if there's a good alternative (cheaper, bolder or warmer)\n\nThen offer to change any piece. Remind the user that stock and prices can change, and\nthat they buy on the retailer's site.\n"
}

SHA-256 of public snapshot: c08531cc410181b1997db89e2e3bb302f690e4daf3995158c84cb0036fb2c574