2 of 4 — Teach your AI who you are
I'm the [your title] at [association name], a [what it is, one phrase] with about [number] members. Most of my week goes to [your top two or three responsibilities].
How to work with me:
- Give me the draft, not advice about the draft. If I ask for a member email, write the email.
- Be direct. No preamble, no restating my question, no "great question."
- Tables for anything comparative. Bullets for summaries. Headings only when a response is genuinely long.
- Match a warm, professional tone — the way an association writes to its own members.
- If something is unclear, ask me one question at a time before starting.
- Never invent facts about our members, programs, dues, dates, or policies. If you need one and don't have it, ask.
- Tell me when you're not confident, and say what would make you sure.
- Skip the "it's not just X, it's Y" construction. Say the thing plainly.
- Don't pad to seem thorough. Short and right beats long.
- Don't create a Word or Excel file unless I ask for one.
Open a fresh chat, attach your brand guide and about-us boilerplate, and paste this:
Attached are our organization's documents. Turn them into reusable skills for: who we are — our members, programs, and acronyms; our brand and how we sound.
Ask me for anything important that's missing before you write them.
3 of 4 — Create your first reusable skill: One Source → Every Channel
Turns any finished piece into a newsletter item, a member email, a social post, and a web blurb — same facts, different lead.
Get your input. Pick one article or announcement you already published this month. Copy the text.
Open a fresh chat — not an old thread.
Paste this.
Here's an article we just published. Turn it into four things: a newsletter item of 100 words, a member email with a subject line and 150 words, a LinkedIn post, and a 40-word website blurb.
Keep the same facts in all four, but change what leads based on what each audience opens it for. Don't add any claim that isn't in the original.
Then tell me anything in the source that was too vague to repurpose.
Check it. Read the four side by side. If they all lead the same way, tell it so and run again. If it's generic, it needed more input — not a cleverer prompt.
The last line gives you honest feedback on your own writing, which is a second payoff you did not ask for.
The third time you run it, stop retyping. Paste this into that same chat:
This conversation contains a prompt I've now run three times. Turn it into a reusable skill: a name, a description saying when to use it, the steps, the output format, and rules based on what we corrected along the way.
What it should look like
---
name: meeting-notes-to-decisions
description: Turns raw meeting notes or a transcript into decisions, action items with owners and dates, and open questions, then drafts the follow-up email to attendees. Use whenever the user pastes meeting notes or says they have just finished a board, committee, or staff meeting.
---
# Meeting Notes → Decisions & Actions
## How to do it
1. Read the whole thing before writing anything.
2. Sort into three buckets and keep them strictly separate: decisions, actions, open questions.
3. If something was debated and not settled, it is an open question. It is never a decision.
4. Give every action an owner. If none was stated, write OWNER NOT ASSIGNED. Do not guess
based on who talked most.
5. Give every action a date. If none was stated, write NO DATE SET.
6. Draft the follow-up email: what was decided, each person's actions under their name,
the open questions, and a request for corrections by a stated date. Under 200 words.
## Rules
- Never invent a decision, an owner, or a date. Flag the gap instead.
- Never soften or resolve a disagreement. Record it as open.
- Never editorialize about how the meeting went.
- If the notes are too thin to produce actions, say so and list what's missing.
## Test it before you rely on it
Run it on a meeting you already know the outcome of. Check that it caught every decision
and assigned no owner you didn't hear assigned.