postemi 1.0.0 → 1.1.0

package/skills/postemi-growth/SKILL.md

@@ -0,0 +1,221 @@
+---
+name: postemi-growth
+description: Grow an audience and get results from social posting with Postemi. Covers choosing networks and a first niche, a 30-day posting test, reading the numbers (Postemi Insights and analytics), posting cadence per network, turning one topic into 30 post angles and scheduling them as a content plan, repurposing one idea across networks, bios and profile links that turn followers into sign-ups or customers, and a weekly review loop. Use when the user asks how to grow followers or reach, what or how often to post, for a content plan or calendar, why posts do not perform, or how to get customers from social media.
+---
+
+# Postemi growth: from posting to results
+
+This skill is the plan; `postemi-writing` is how each post is written,
+`postemi-templates` has ready drafts, and the main `postemi` skill has the
+tools and commands. If the writing skills are not installed, write the posts
+with the rules of the main skill and offer `postemi skills add writing` (ask
+the user first). Reference files:
+
+- [reference/30-angles.md](./reference/30-angles.md): 30 ways to post about
+  one topic, with a worked example.
+- [reference/review.md](./reference/review.md): the post log and the weekly
+  review, step by step.
+
+## Principles
+
+1. **Focus.** One or two networks done well beat seven done badly. Add more
+   once something works.
+2. **Every post is a test.** Growth early on is learning what this audience
+   wants. Post, read the numbers, keep what works, drop what does not.
+3. **Consistency beats bursts.** A steady rhythm the user can keep for months
+   wins over a busy week followed by silence. Long gaps cost reach.
+4. **Big changes, not tiny tweaks.** With a small audience, a new topic, angle
+   or format teaches more than changing one word.
+5. **Real engagement only.** No bought followers, no engagement swaps, no
+   bots. Comments, shares, saves and replies from real readers are the signal.
+6. **What Postemi does and does not do.** Postemi writes nothing on its own,
+   schedules and publishes, and shows numbers. It does not reply to comments,
+   follow, connect, like or send messages for the user. Those are the user's
+   part, and they matter.
+
+## 1. Choose where to start
+
+Ask who the user wants to reach and what they sell or share, then suggest one
+main network and at most one second one:
+
+| The user | Start with |
+|---|---|
+| Sells to businesses, consultant, founder, job market | LinkedIn (personal profile), then X |
+| Ideas, tech, writing, building in public | X or Threads, then LinkedIn; Bluesky for tech crowds |
+| Visual products, food, fashion, beauty, travel, places | Instagram (Reels and carousels), then TikTok |
+| Local business (shop, cafe, salon, trades) | Facebook and Instagram |
+| Teaching with video | YouTube (Shorts too) and TikTok |
+| An existing community | Telegram, Discord or Slack, next to one public network |
+
+Postemi can send the same idea to several networks at once later (section 6),
+so starting narrow costs nothing.
+
+## 2. The first niche and the 30-day test
+
+A niche is not for life; it is the first topic the user goes deep on. The
+skill of building an audience carries over when the topic changes. Find it
+with data, not by thinking harder:
+
+1. **Pick one network** (usually X or LinkedIn for text, Instagram or TikTok
+   for visuals).
+2. **Post at least once a day for 30 days.** Any idea from the user's
+   experience: use the idea builder and the look-back test in
+   `postemi-writing`. Vary topic, angle (how-to, analysis, inspiration, human
+   nature) and format on purpose, so the data has something to compare.
+3. **Schedule it with Postemi a week at a time.** Write seven posts with the
+   user, preview them, and create them in one go (one `socialPost` entry per
+   day in `create_post`, or a `--json` file with the CLI). The user only has
+   to show up for the replies.
+4. **Log every post** (topic, angle, format, hook, time): see
+   [reference/review.md](./reference/review.md).
+5. **After 30 days, read the numbers** (section 3) and pick the topic and the
+   angle with the strongest early signal.
+6. **Go deep on that topic** for the next weeks. Writing about the same topic
+   again and again is not repetition; it is why people follow someone. The 30
+   angles (section 5) make it easy.
+
+Small numbers still count. If 20 posts got no likes and 10 got one, those 10
+did infinitely better: that is the signal. The method is the same at 10
+followers and at 10,000; only the zeros change.
+
+## 3. Read the numbers
+
+Where the numbers are:
+
+- **Postemi Insights**, in the web app (postemi.com/app/insights): reach,
+  engagement and followers per channel over time.
+- **The CLI:** `postemi analytics:platform <integration-id> -d 30` for a
+  channel, `postemi analytics:post <post-id> -d 7` for one post. If a post
+  answers `{"missing": true}`, link it first (`posts:missing`, then
+  `posts:connect`; see the main skill).
+- **The MCP tools** have no analytics tool. Ask the user to open Insights, or
+  to paste or screenshot the numbers, and work from that. `list_posts` gives
+  the post ids, dates and channels to match them to.
+- The network's own analytics, when the user has it open.
+
+What to look at, in this order:
+
+1. **Conversations:** comments and replies (and how long they are). The
+   strongest sign a post landed.
+2. **Shares, reposts and saves:** people found it worth passing on or keeping.
+3. **Follows and profile visits** after a post: it made people want more.
+4. **Engagement rate:** engagements divided by impressions. Compares posts
+   fairly when reach differs.
+5. **Reach and impressions:** how far it went. Useful, but a post can travel
+   far and change nothing.
+6. **Clicks and sign-ups** from the profile link, when the user tracks them.
+
+Likes alone are the weakest signal. Compare posts with each other, not with
+other people's accounts.
+
+## 4. How often, and when
+
+Starting points, not laws. The best cadence is the one the user can keep.
+
+| Network | Suggested rhythm | Notes |
+|---|---|---|
+| X | At least 2 short posts a day, 5 days a week; to grow faster, 3 to 5 a day, 7 days a week, plus 2 or more threads or long posts a week. Text with an image or video does best. | Every post and thread entry counts toward the account's monthly X allowance in Postemi, so tell the user how many are left when the plan needs more. |
+| LinkedIn | 1 post a day at most, 3 to 5 a week is plenty. | Posting more does not grow faster here. Mornings in the audience's timezone work well. Do not go weeks without posting. |
+| Instagram | 3 to 5 feed posts or Reels a week, Stories in between. | Reels for reach, carousels for saves. |
+| TikTok | Up to 1 or 2 a day. | Postemi allows about 15 posts per account in 24 hours. |
+| Threads, Bluesky, Mastodon | 1 to 3 a day. | Conversation matters more than volume. |
+| Facebook | 3 to 5 a week. | Local and community content. |
+| YouTube | 1 a week; Shorts more often. | Consistency of the day helps viewers. |
+| Blog channels | 1 to 4 a month. | The long versions of the best posts. |
+
+Timing: start with morning and early evening in the audience's own timezone
+(take the user's timezone from Postemi, and ask where the audience is), then
+compare times in the log. `postemi posts:find-slot <id>` suggests the next
+free slot on a channel's schedule.
+
+## 5. One topic, 30 posts
+
+Once the user has a topic, turn it into a month of posts with the 30 angles
+in [reference/30-angles.md](./reference/30-angles.md): tips, mistakes, tools,
+steps, stories, lessons, myths, questions and more. Each angle becomes a
+question, each answer becomes a post.
+
+Mix the 30 across three to five **content buckets** (themes the audience
+expects from the user, for example "how-to", "behind the scenes", "customer
+results", "opinions") and refuse ideas that fit no bucket. That keeps the
+account recognisable.
+
+### Turning the plan into a Postemi schedule
+
+1. Agree the network(s), the number of posts per week and the times.
+2. Write the first week in full (with `postemi-writing`), show it, adjust.
+3. Get the clock and timezone (`get_workspace_context`, or the CLI's saved
+   timezone), and spread the posts over the days at the agreed local times.
+4. Preview all of them in one `preview_post` call (one `socialPost` entry per
+   post), or show the list from the CLI; fix what the preview flags.
+5. On the user's yes, create them in one call with an `idempotencyKey`. Use
+   `type: "draft"` (CLI `-t draft`) if the user wants to review them in the
+   Postemi calendar before they go live.
+6. Repeat weekly, folding in what the numbers say. Writing a month ahead is
+   fine, but leave room for timely posts and for what you learn.
+
+## 6. Repurpose: one idea, every network
+
+A post that worked is the best raw material for the next ones:
+
+- **Across networks, adapted, not copied.** The same idea as an X short post,
+  an X thread, a LinkedIn long post with an image, an Instagram carousel, a
+  Threads post, and later a blog article. Each gets its own hook, length and
+  format (see `postemi-writing`). In Postemi each channel gets its own entry
+  with its own text in the same request.
+- **Never the same post on two X accounts:** one X channel per post.
+- **Up and down in size.** A thread becomes an article; an article becomes
+  five short posts; a popular reply or comment becomes its own post.
+- **Again, later.** Re-share a winner after a few months with a new hook and
+  a fresh example; most followers did not see it the first time.
+- **Collaborations.** Instagram posts can name collaborators (a setting in
+  Postemi); a post together with a partner brand or creator reaches both
+  audiences.
+
+## 7. Profile, bio and the path to a customer
+
+Posts bring people to the profile; the profile decides whether they follow
+and click. Help the user write it:
+
+- **Bio:** "I help [who] [get what]" or "I write about [topic]", plus one line
+  of proof: "Baker for 12 years. 3 shops." Clear beats clever, as with hooks.
+  No list of ten roles.
+- **One link,** to one next step: an e-mail list, a free guide or checklist,
+  a booking page, a product page. On X the bio is the place for links, since
+  Postemi removes links from X posts. On Instagram point to the link in the
+  bio. On LinkedIn, feature the free resource or product in the Featured
+  section.
+- **Name and keywords:** put the topic word people search for in the display
+  name or headline (Instagram, LinkedIn) so the profile can be found.
+- **The path:** post, profile, link, e-mail or sign-up, offer. Most posts just
+  give value; about one in five invites people to the next step (a free
+  resource, a waitlist, the product), with a clear reason to click. On
+  LinkedIn and Facebook that link can go in the first comment.
+- **Pinned post:** the user's best post, or the one that explains what they do
+  and where to start.
+
+## 8. The user's part every day
+
+Share this with the user plainly; Postemi cannot do it for them:
+
+- Reply to every comment in the first hours after a post goes out; replies
+  bring more reach and turn readers into followers.
+- Leave two or three thoughtful comments a day on posts by bigger accounts in
+  the same field. A good comment is a small post of its own, and a comment
+  that does well is an idea for a full post.
+- Thank people who share.
+
+## 9. Review and iterate
+
+Once a week (15 minutes), with the user:
+
+1. Pull the numbers for the week (section 3) into the log.
+2. Name the top three and the bottom three posts, and what they had in common
+   (topic, angle, hook pattern, format, time).
+3. Decide one bigger change for next week: more of the winning angle, a new
+   format, a different time, dropping a topic that never lands.
+4. Write and schedule next week with that change.
+
+Once a month: is the main network working? Is the niche still the right
+first one? Is the profile link getting clicks? Keep, adjust, or try the
+second network. Details and a log template: [reference/review.md](./reference/review.md).

package/skills/postemi-growth/reference/30-angles.md

@@ -0,0 +1,74 @@
+# One topic, 30 angles
+
+Take one narrow topic and ask it 30 different questions. Each answer is a
+post (often a list of three), so one topic fills a month. When the month is
+done, take the same 30 angles with a narrower or neighbouring topic, or run
+them again with new answers.
+
+How to use it with the user:
+
+1. Agree the topic, narrow and with a reader in mind (see the idea builder in
+   `postemi-writing`): not "gardening" but "growing vegetables on a small
+   balcony for people new to it".
+2. Go through the angles, fill each question with the topic, and answer it
+   from the user's own experience or a named source. Skip angles the user has
+   nothing true to say about; never fill one with invented facts.
+3. Give each post a hook (`postemi-writing`, or a hook template from
+   `postemi-templates`) and a format (short post, thread, carousel, video).
+4. Spread them over the month and schedule them with Postemi
+   (`postemi-growth`, section 5).
+
+Mark each angle in the post log, so the review shows which angles this
+audience likes.
+
+## The 30 angles
+
+| # | Angle | The question to answer |
+|---|---|---|
+| 1 | Tips | What are 3 tips for [topic]? |
+| 2 | Skills | Which 3 skills matter most for [topic]? |
+| 3 | Tools | What are the 3 best tools for [topic]? |
+| 4 | Prompts | What are 3 AI prompts that help with [topic]? |
+| 5 | Traits | What do people who are good at [topic] have in common? |
+| 6 | Steps | What are the 3 key steps of [topic]? |
+| 7 | Goals | What are 3 realistic first goals for [topic]? |
+| 8 | Books | Which 3 books help most with [topic]? |
+| 9 | Habits | Which 3 daily habits make [topic] easier? |
+| 10 | Stories | What is a story (the user's own, or a sourced one) of [topic] going well? |
+| 11 | Quotes | Which 3 sayings sum up [topic]? (with the real source) |
+| 12 | Insider knowledge | What do experienced people know about [topic] that beginners do not? |
+| 13 | Insights | What are 3 ideas that change how people see [topic]? |
+| 14 | Benefits | What are the 3 biggest benefits of [topic]? |
+| 15 | Lessons | What did failures in [topic] teach the user? |
+| 16 | Reasons | Why does [topic] work? Give 3 reasons. |
+| 17 | People | Which 3 people or accounts are worth following for [topic]? |
+| 18 | Routines | What routine do people who do [topic] well follow? |
+| 19 | Mistakes | What are the 3 most common mistakes in [topic]? |
+| 20 | Podcasts and videos | Which 3 shows or channels are best on [topic]? |
+| 21 | Examples | What are 3 good real examples of [topic]? |
+| 22 | Questions | Which 3 questions should a beginner ask about [topic]? |
+| 23 | What is new | What are 3 new tools, methods or changes in [topic]? |
+| 24 | Frameworks | Which template or framework helps someone start [topic]? |
+| 25 | Resources | What are the 3 best free resources for learning [topic]? |
+| 26 | Obstacles | What are the 3 hardest parts of [topic], and how do people get past them? |
+| 27 | Organisations | Which 3 companies or groups do [topic] well, and what can we learn? |
+| 28 | Numbers | What are 3 telling facts or figures about [topic]? (sourced) |
+| 29 | Starter kit | What are 3 things to buy or set up when starting [topic]? |
+| 30 | Case study | What happened when someone (the user, a customer) did [topic] for a while? |
+
+## Worked example
+
+Topic: growing vegetables on a small balcony, for people new to it.
+
+| Day | Angle | Hook | Format |
+|---|---|---|---|
+| 1 | Mistakes | 3 balcony garden mistakes that kill seedlings in week one | short post |
+| 2 | Tools | The only 4 tools you need for a balcony vegetable patch | carousel |
+| 3 | Stories | Last spring I grew 9 kilos of tomatoes on a 2 square metre balcony. Here is the full story. | thread |
+| 4 | Benefits | Why a balcony patch saves more than money | long post |
+| 5 | Questions | What do you wish you had known before your first balcony garden? | question post |
+| 6 | Steps | From empty balcony to first salad in 5 steps | how-to post |
+| 7 | Starter kit | Your first balcony garden for under 50 euros | list post |
+
+The other 23 angles fill the rest of the month. Post one or two a day on the
+main network, and adapt the best ones for the second network.

package/skills/postemi-growth/reference/review.md

@@ -0,0 +1,63 @@
+# The post log and the weekly review
+
+## The post log
+
+Keep one row per published post. A spreadsheet, a note or a Markdown table in
+the user's project is enough; offer to keep it for the user if you can write
+files. Fill the planning columns when the post is scheduled and the numbers a
+few days after it goes out (LinkedIn posts can keep growing for days).
+
+| Date | Network | Post id | Topic | Angle | Hook pattern | Format | Time | Impressions | Comments | Shares | Saves | Follows | Clicks |
+|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
+| 2026-11-02 | LinkedIn | ... | pricing | Lessons | honest admission | long post + image | 08:30 | 1,840 | 14 | 3 | 9 | 6 | 11 |
+
+- **Post id:** from `create_post`, `list_posts` or the CLI, so the numbers can
+  be matched later (`postemi analytics:post <post-id>`).
+- **Angle:** how-to, analysis, inspiration, human nature, or one of the 30
+  angles.
+- **Hook pattern:** which opener or pattern from `postemi-writing` or which
+  template from `postemi-templates`.
+- Leave a number empty rather than guessing it.
+
+## Getting the numbers
+
+- Postemi Insights in the web app, per channel and per period.
+- CLI: `postemi analytics:post <post-id> -d 7` per post;
+  `postemi analytics:platform <integration-id> -d 30` per channel.
+- MCP clients: ask the user for the numbers from Insights or the network's
+  own analytics (there is no analytics tool on MCP).
+
+## The weekly review (15 minutes)
+
+1. **Fill the log** for last week's posts.
+2. **Rank** by comments plus shares plus saves (or engagement rate when reach
+   differs a lot). Look at the top three and the bottom three.
+3. **Find the pattern.** What do the winners share: topic, angle, hook,
+   format, length, time, media? What do the losers share?
+4. **One decision.** Pick one bigger change for next week and write it down:
+   "two more posts on pricing lessons", "carousels instead of text on
+   LinkedIn", "move X posts to the evening". Change one main thing at a time,
+   so next week's numbers can show whether it helped.
+5. **Plan and schedule** next week with that change, in Postemi.
+6. **Reuse the winner:** schedule an adapted version of the best post on the
+   second network, or a follow-up post that goes deeper.
+
+## The monthly review
+
+- Followers and reach per network over the month (Insights): growing, flat,
+  falling?
+- The niche: which topic and angle won most weeks? Go deeper there.
+- The profile link: are people clicking and signing up? If not, change the
+  offer or the bio before posting more.
+- Cadence: could the user keep it? Lower it rather than skip weeks.
+- Networks: keep the main one; add, keep or drop the second one.
+
+## Reading small numbers
+
+- Compare posts with each other, not with other accounts.
+- A post with two thoughtful comments beat a post with ten likes and no
+  comments.
+- Wait for at least two or three posts of the same kind before calling a
+  pattern; one post can be luck.
+- When everything is low, change something big (topic, format, network), not
+  a word in the hook.

package/skills/postemi-templates/SKILL.md

@@ -0,0 +1,107 @@
+---
+name: postemi-templates
+description: Postemi's library of ready post templates and hooks, the same ones the Postemi composer offers under Templates. Everyday posts, product launches, LinkedIn post types, X formats, conversation starters and more than 100 hooks (stories, contrarian takes, how-to, lists, books, habits, questions), each with [placeholders] to fill. Use when the user wants a quick draft of a common post type, a hook or opening line, a post idea for a goal (launch, engagement, teaching, story), or asks for templates.
+---
+
+# Postemi templates and hooks
+
+The templates in [reference/](./reference/index.md) are generated from the
+Postemi app, so they match what the user sees in the composer's Templates
+column. Each has a title, a line on when to use it, and a body with
+[placeholders] in square brackets.
+
+Pair with `postemi-writing` (how to make the filled template good) and the
+main `postemi` skill (how to preview and schedule it).
+
+## Files
+
+- [reference/index.md](./reference/index.md): every group and every template
+  in one table (id, title, network, when to use it). Read this first, then
+  open only the group file you need.
+- Group files, with the full bodies:
+  - [everyday.md](./reference/everyday.md): launch, behind the scenes, tip,
+    roundup, customer story, event, question, milestone.
+  - [launch.md](./reference/launch.md): announcing and explaining what the
+    user builds.
+  - [linkedin.md](./reference/linkedin.md): 30 LinkedIn post types in six
+    sections (building in public, founder story, industry, team, teaching,
+    conversation).
+  - [x.md](./reference/x.md): short X formats.
+  - Hooks, by what the post does:
+    [hook-stories.md](./reference/hook-stories.md) (lessons and stories),
+    [hook-contrarian.md](./reference/hook-contrarian.md) (contrarian takes),
+    [hook-how-to.md](./reference/hook-how-to.md) (frameworks and how-to),
+    [hook-lists.md](./reference/hook-lists.md) (lists and tools),
+    [hook-learning.md](./reference/hook-learning.md) (books and learning),
+    [hook-growth.md](./reference/hook-growth.md) (habits and growth),
+    [hook-talk.md](./reference/hook-talk.md) (problems and questions).
+  - [engagement.md](./reference/engagement.md): questions, polls and prompts
+    that get replies.
+
+## Pick a template
+
+Start from the user's goal, then the network:
+
+| Goal | Look in |
+|---|---|
+| Announce a product, feature or event | `launch.md`, `everyday.md` (`launch`, `eventReminder`) |
+| Build trust as a founder or expert | `linkedin.md` (founder story, building in public), `hook-stories.md` |
+| Teach something useful | `hook-how-to.md`, `everyday.md` (`quickTip`), `linkedin.md` (teach) |
+| Start a debate, stand out | `hook-contrarian.md`, `linkedin.md` (`liHotTake`), `x.md` |
+| Get comments and replies | `engagement.md`, `hook-talk.md` |
+| Share tools, books, resources | `hook-lists.md`, `hook-learning.md` |
+| Motivate, habits, personal growth | `hook-growth.md` |
+| Show the team and culture | `linkedin.md` (team), `everyday.md` (`behindScenes`) |
+| Social proof | `everyday.md` (`customerStory`, `milestone`) |
+
+Network fit:
+
+- Ids starting with `li` were written for LinkedIn and ids starting with `x`
+  for X; the index says so in its Network column. The rest fit anywhere.
+- A LinkedIn template on X: shorten it to the hook and one or two lines, or
+  turn it into a thread (one point per entry). Check the account's limit.
+- An X template on LinkedIn: add the context and a story; the hook must sit
+  in the first two or three lines.
+- For Instagram, TikTok and YouTube the template becomes the caption; the
+  picture or video still carries the post.
+- Remove any link from text going to X (Postemi strips links from X posts).
+
+Offer two or three templates that fit and let the user choose, or pick one
+and say why in a sentence.
+
+## Fill it in
+
+1. Ask the user for what the placeholders need, in one short message: the
+   facts, the numbers, the story. Never invent them. A template with made-up
+   details is worse than no post.
+2. Replace every `[placeholder]`. Remove a line whose placeholder the user
+   cannot fill, rather than leaving it vague.
+3. Number placeholders (`[number]`) must be true numbers, and a list must
+   have as many items as its hook promises.
+4. Rewrite in the user's voice. The template is a skeleton, not a script:
+   change words, order and length freely. Keep the shape that makes it work
+   (the hook, the turn, the takeaway).
+5. Hooks are openings: a hook template gives the first lines; write the rest
+   with `postemi-writing` (keep the promise of the hook, lead with the best
+   part, end with one takeaway or question).
+6. Run the check in `postemi-writing` (section 7), then preview and schedule
+   with the main `postemi` skill.
+
+## Example
+
+User: "I want to post on LinkedIn that we finally shipped dark mode."
+
+1. Goal: announce a feature; network: LinkedIn. Candidates: `liFeature`,
+   `liBuiltWrong` (if customer feedback changed the plan).
+2. `liFeature` body: "We just shipped [feature]. It took us [time], longer than
+   we planned. The reason: [...]".
+3. Ask: how long did it take, what was harder than expected, what can people
+   do now, one lesson.
+4. Fill, rewrite in the user's voice, check, `preview_post` (or show the text
+   in the CLI flow), schedule on the user's yes.
+
+## Keeping this in sync
+
+These files are generated. In the agent repository:
+`pnpm sync:templates <path to the app's templates folder>`, then
+`pnpm sync:skills`, then commit. Do not edit the reference files by hand.

package/skills/postemi-templates/reference/engagement.md

@@ -0,0 +1,155 @@
+<!-- Generated by scripts/sync-templates.mjs from the Postemi app's template library (en.ts, catalog.ts). Do not edit by hand: change the app, then run the script again. -->
+
+# Conversation starters
+
+Questions, polls and prompts that get people to reply.
+
+11 templates. Square brackets are placeholders: replace every one before you post.
+
+## Question for your audience (`question`)
+
+- Network: any network
+- Use it when: Start a conversation and hear what people think.
+
+```text
+We would love your view: [your question]?
+
+A) [first option]
+B) [second option]
+
+Reply with A or B, or tell us what we missed. We read every answer.
+```
+
+## Ask a question (`liQuestion`)
+
+- Network: LinkedIn
+- Use it when: Simple, as long as you ask something people want to answer.
+
+```text
+[audience]: what is one [tool, habit or idea] you could not work without?
+
+Mine: [your answer].
+```
+
+## Ask for hot takes (`liOpinionPrompt`)
+
+- Network: LinkedIn
+- Use it when: Invite others to share their unpopular opinions, and go first.
+
+```text
+What is an unpopular opinion you hold about [topic]?
+
+I will go first: [your take].
+```
+
+## A poll (`liPoll`)
+
+- Network: LinkedIn
+- Use it when: Polls make it easy to take part. Use them now and then, not every week.
+
+```text
+What matters more for [audience or stage]?
+
+• [option A]
+• [option B]
+
+Vote, then tell me why in the comments.
+```
+
+## What would you do? (`liScenario`)
+
+- Network: LinkedIn
+- Use it when: Share a real dilemma and let people weigh in.
+
+```text
+Scenario: [the situation you faced].
+
+What would you do?
+
+I will share what we did in the comments tomorrow.
+```
+
+## Say thank you (`liThanks`)
+
+- Network: LinkedIn
+- Use it when: Thank someone who helped. They reply, and their network sees it.
+
+```text
+A thank you to [person] for [what they did].
+
+It helped more than they know: [the difference it made].
+```
+
+## Quick vote (`xPoll`)
+
+- Network: X
+- Use it when: Easy to join, and you learn what your audience thinks.
+
+```text
+Quick question for [audience]:
+
+[your question]
+
+A) [option]
+B) [option]
+C) [option]
+
+Reply with a letter.
+```
+
+## Describe it in one word (`xOneWord`)
+
+- Network: X
+- Use it when: An easy ask that gets a lot of replies. Good for reach, less so for authority.
+
+```text
+Describe [thing] in one word.
+
+I will start: [your word].
+```
+
+## Best examples, add yours (`hExamples`)
+
+- Network: any network
+- Use it when: Share your favourites and ask people to add more.
+
+```text
+The best examples of [topic] I have seen:
+
+• [example]
+• [example]
+• [example]
+
+What would you add?
+```
+
+## Questions that are hard to answer (`hHardQuestions`)
+
+- Network: any network
+- Use it when: Ask the questions your audience struggles with.
+
+```text
+[number] questions every [role] struggles to answer:
+
+1. [question]
+2. [question]
+3. [question]
+
+Which one is hardest for you?
+```
+
+## Which problem is yours? (`hFourProblems`)
+
+- Network: any network
+- Use it when: Sort your audience's problems so each person finds theirs.
+
+```text
+Most [audience] struggle with one of these:
+
+1. They do not [problem]
+2. They do not [problem]
+3. They cannot [problem]
+4. They have no [problem]
+
+Which one is yours?
+```