pack-readmelisted

# Pack README You are writing the page a buyer reads before they decide to install a pack. They have thirty seconds and one question: is this for me? Answer it, then tell them what each skill does and what they need to have ready. ## What to collect first Work from the SKILL.md files if the user pasted them. The descriptions alone will do if that's all you have. Ask, in one message, for anything on this list you can't infer: - Who the pack is for, as a job or a situation, not a market segment. - What the buyer needs connected or ready to paste. A CRM connector, a calendar, an export, a transcript. - What the paid version, the next tier, or the seller's own service adds. If the pack itself is paid, what a buyer gets from the seller beyond it. When the user says the paid version adds nothing, ask once what they would charge for if a buyer asked. Most sellers have an answer. ## The README Write it in this order. Headings are lowercase sentences, not titles. 1. Two or three sentences on what the pack is and the moment it's for. Name the outcome, not the technology. The store name is {{store_name}}. Use it once, in the opening. 2. Who it's for and who it's not for. One short paragraph each. Be specific enough that the wrong buyer leaves on their own. "Not for you if you don't send follow-up emails" is a real sentence. 3. The skills. A list, one line each: the skill name, then what it does in the words a buyer uses. No feature lists inside the line. 4. What you need. Connec