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.
- 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.
- 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.
- 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.
- What you need. Connectors by plain name (a Gmail connector, a CRM connector), inputs the buyer pastes, and any questions the pack will ask on first use because a variable needs a value.
- How to use it. Two sentences. Install it from the store, then ask your AI app in plain words. Name one example phrase.
- Limits. Two or three lines. The AI app can be wrong, read anything before it goes out, and whatever the domain needs (a legal check, a state law, a number from the real system).
- The close. One sentence on what the paid version adds. Nothing after it.
Rules
- Under 350 words. A buyer who wants more will read the skills.
- Plain words. Nothing a person would not say out loud. No "unlock", "supercharge", "effortless", "powerful", "AI-powered".
- Specifics over adjectives. "Turns forty lines of call notes into a six-line recap" beats "saves time".
- Never name an AI vendor. Say "your AI app" or "an AI app that supports connectors".
- Do not describe how the skills are built or what the frontmatter says. Buyers don't care.
- Do not promise results the skills can't produce. Read the bodies before you claim anything.
1---2name: pack-readme3description: Use when a pack is ready to list and someone asks for the README, store page, or buyer summary. Writes who it's for, one line per skill, and what buyers need.4---56# Pack README78You 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.910## What to collect first1112Work 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:1314- Who the pack is for, as a job or a situation, not a market segment.15- What the buyer needs connected or ready to paste. A CRM connector, a calendar, an export, a transcript.16- 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.1718When the user says the paid version adds nothing, ask once what they would charge for if a buyer asked. Most sellers have an answer.1920## The README2122Write it in this order. Headings are lowercase sentences, not titles.23241. 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.252. 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.263. 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.274. What you need. Connectors by plain name (a Gmail connector, a CRM connector), inputs the buyer pastes, and any questions the pack will ask on first use because a variable needs a value.285. How to use it. Two sentences. Install it from the store, then ask your AI app in plain words. Name one example phrase.296. Limits. Two or three lines. The AI app can be wrong, read anything before it goes out, and whatever the domain needs (a legal check, a state law, a number from the real system).307. The close. One sentence on what the paid version adds. Nothing after it.3132## Rules3334- Under 350 words. A buyer who wants more will read the skills.35- Plain words. Nothing a person would not say out loud. No "unlock", "supercharge", "effortless", "powerful", "AI-powered".36- Specifics over adjectives. "Turns forty lines of call notes into a six-line recap" beats "saves time".37- Never name an AI vendor. Say "your AI app" or "an AI app that supports connectors".38- Do not describe how the skills are built or what the frontmatter says. Buyers don't care.39- Do not promise results the skills can't produce. Read the bodies before you claim anything.
adjustleads