skills/product-tip-series/SKILL.mdView on GitHub
This applies on the release cadence. It produces the drip that keeps customers using what they already paid for and shows prospects the product moving.
Before you start
This skill works on its own. If the person has their own marketing brain (or any folder of context files about their company), read the files listed under reads in the header first and cite them for every fact. If they do not have one, do not look for one: ask for the two or three facts this play needs and go on. Never invent a fact; a blank is a question for the person.
Tools: this play speaks in verbs (check the CRM, pull the call, schedule the post). TOOLS.md at the root of this repo lists the tools recommended for each verb. The company’s own 1-context/stack.md wins when it exists. No tool is required; a spreadsheet and a mail client cover most of it.
The play
- Read the context (see Before you start). Read the release record in
1-context/stack.md, not chat threads, for what shipped and its maturity label. - Pick one feature that is generally available and underused (adoption data where it exists, or success’s read).
- Write the tip: the job it does in the customer’s words, the one step to try it, what to expect, the limit worth knowing. No feature list.
- Produce three forms from one tip: a company post through
social-post, a 20 to 40 second screen clip brief forcustomer-video-cut(real screenshots, padding, music), a line forcustomer-update-email. - Check the label and the claims through
release-to-narrativeandpermission-check. - Schedule on the calendar on a fixed day so customers learn to expect it.
- Track which tips drive adoption (where measurable) and feed that to product.
What good looks like
- The best operator writes the tip from the job, not the feature name, and shows the one click that starts it.
- The mediocre version announces a feature with a screenshot and no reason to try it.
- Good output is a tip a success manager would forward to a customer unprompted.
Rules
- MUST take feature status from the release record, never from chat.
- MUST carry the maturity label.
- NEVER tip a feature that is not generally available to the audience receiving it.
- NEVER use generated-looking art for product tips; real screens only.