Product description
Writes a store-ready description from a product name and a few details.
Marketing · produces a Document · built in, ready to run
What you give it
Something like this:
Product: OrderDesk Lite. Web + Android app for distributors. Stores place orders themselves from a live price list; reps still see and edit every order and keep commission credit; syncs to SAP B1 or exports CSV; works offline and syncs later; Urdu and English. Setup takes a day. PKR 18,000/month for up to 100 stores.
What you get back
This is a real run of the skill on the input above, not a mock-up:
Done. I've written the product description for OrderDesk Lite following your structure and rules. The document includes:
- **Opening line** positioning it as an ordering app for distributors
- **4 benefit-driven bullets** covering: direct store ordering (with rep oversight), offline capability, multi-system compatibility, and dual-language support
- **Closing line** highlighting the quick setup and pricing
Each benefit is grounded in the features you provided, with no invented claims or unsupported superlatives. The description is ready to open and edit.
The wording changes a little every run. The shape does not — that is what the procedure below is for.
Tools it uses
None of its own. A skill that only writes needs no tools, so this one inherits whatever your assistant can normally reach.
The procedure it follows
This is the skill, in full. Add it to your own skills to change any of it.
Write a product description from the details below.
Shape:
- One opening line that says what it is and who it is for
- Three to five bullets, each a benefit with the feature behind it
- One closing line
Rules: no superlatives you cannot back up, no "revolutionary" or "game-changing", and never invent a specification that is not given.
How to run it
| Where | How |
|---|---|
| Chat | "Run my Product description skill", or pick it from the + menu |
| Skills page | Find Product description under Library and press Add & Use |
| Automations | Invoke it on every trigger |
| API | POST /v1/skills/{id}/run — add it to your own skills first, then take the id from GET /v1/skills |
In chat, on the Skills page and in automations you do not have to add it first — a library skill runs as it is. Adding it makes an editable copy under your own skills, which is what you need to change the wording, and what the API works against.
New to skills? Start with what a skill is.