postemi 1.0.0 → 1.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/PROVIDER_SETTINGS.md +183 -7
- package/README.md +87 -9
- package/SKILL.md +83 -30
- package/dist/index.js +435 -332
- package/dist/index.js.map +1 -1
- package/package.json +23 -7
- package/skills/postemi/SKILL.md +1121 -0
- package/skills/postemi-growth/SKILL.md +221 -0
- package/skills/postemi-growth/reference/30-angles.md +74 -0
- package/skills/postemi-growth/reference/review.md +63 -0
- package/skills/postemi-templates/SKILL.md +107 -0
- package/skills/postemi-templates/reference/engagement.md +155 -0
- package/skills/postemi-templates/reference/everyday.md +132 -0
- package/skills/postemi-templates/reference/hook-contrarian.md +227 -0
- package/skills/postemi-templates/reference/hook-growth.md +210 -0
- package/skills/postemi-templates/reference/hook-how-to.md +266 -0
- package/skills/postemi-templates/reference/hook-learning.md +296 -0
- package/skills/postemi-templates/reference/hook-lists.md +195 -0
- package/skills/postemi-templates/reference/hook-stories.md +282 -0
- package/skills/postemi-templates/reference/hook-talk.md +199 -0
- package/skills/postemi-templates/reference/index.md +251 -0
- package/skills/postemi-templates/reference/launch.md +145 -0
- package/skills/postemi-templates/reference/linkedin.md +449 -0
- package/skills/postemi-templates/reference/x.md +139 -0
- package/skills/postemi-writing/SKILL.md +310 -0
- package/skills/postemi-writing/reference/headline-patterns.md +109 -0
- package/skills/postemi-writing/reference/networks.md +113 -0
|
@@ -0,0 +1,310 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: postemi-writing
|
|
3
|
+
description: Write social media posts people stop for and read to the end, then schedule them with Postemi. Covers finding post ideas, hooks and headlines, opening lines, formatting and rhythm, threads, the writing rules of each network (X, LinkedIn, Instagram, Threads, Bluesky, Facebook, TikTok, YouTube and more) and a check before publishing. Use when the user asks to write, rewrite or improve a post, thread, caption, hook or headline, asks what to post about, or wants a post to reach more people.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Postemi writing: posts that get read
|
|
7
|
+
|
|
8
|
+
This skill is about the words. Other Postemi skills sit next to it:
|
|
9
|
+
|
|
10
|
+
- `postemi` (the main skill): the tools or commands that preview, schedule and
|
|
11
|
+
publish. Its rules win over anything here.
|
|
12
|
+
- `postemi-templates`: ready post templates and hooks with [placeholders],
|
|
13
|
+
the same ones the Postemi composer shows. Start there when the user wants a
|
|
14
|
+
quick draft of a known type (a launch, a tip, a poll).
|
|
15
|
+
- `postemi-growth` (optional, may not be installed): the plan over weeks: a
|
|
16
|
+
niche, a 30-day test, cadence per network, reading the numbers,
|
|
17
|
+
repurposing. If it is missing and the user wants a plan, tell them how to
|
|
18
|
+
add it (`postemi skills add growth`, or the `postemi-growth` plugin); ask
|
|
19
|
+
first, never install it yourself.
|
|
20
|
+
|
|
21
|
+
Reference files in this skill:
|
|
22
|
+
|
|
23
|
+
- [reference/headline-patterns.md](./reference/headline-patterns.md): 25 hook
|
|
24
|
+
and headline patterns with examples.
|
|
25
|
+
- [reference/networks.md](./reference/networks.md): what works on each
|
|
26
|
+
network, and what Postemi does there.
|
|
27
|
+
|
|
28
|
+
## Ground rules
|
|
29
|
+
|
|
30
|
+
1. Write in the user's voice, about the user's real experience. Ask for facts
|
|
31
|
+
you do not have; never invent a number, a customer, a quote, a result or a
|
|
32
|
+
credential. A made-up detail is the fastest way to lose a reader's trust.
|
|
33
|
+
2. A strong hook is fine only when the post pays it off. If the body cannot
|
|
34
|
+
keep the promise, make the hook smaller, never the truth bigger.
|
|
35
|
+
3. Plain words, short sentences, one idea per post.
|
|
36
|
+
4. Show the user the draft before anything is scheduled (the main skill's
|
|
37
|
+
preview step). The user decides; you suggest.
|
|
38
|
+
|
|
39
|
+
## 1. Find the idea
|
|
40
|
+
|
|
41
|
+
### The look-back test
|
|
42
|
+
|
|
43
|
+
People who "have nothing to write about" are usually writing for the wrong
|
|
44
|
+
reader. Ask the user three questions:
|
|
45
|
+
|
|
46
|
+
- What did you not know two years ago that you know now?
|
|
47
|
+
- What have you been through since then that you had not been through before?
|
|
48
|
+
- Where were you two years ago, and where are you today?
|
|
49
|
+
|
|
50
|
+
Every answer is a post. The reader is the person the user was two years ago:
|
|
51
|
+
someone a step or two behind, who wants to hear from someone who just did it,
|
|
52
|
+
not from a distant expert.
|
|
53
|
+
|
|
54
|
+
### The idea builder: topic, proof, angle
|
|
55
|
+
|
|
56
|
+
Build each idea from three choices.
|
|
57
|
+
|
|
58
|
+
**Topic, made narrow.** Start broad, then go down at least two levels, then
|
|
59
|
+
add who it is for and what they get:
|
|
60
|
+
|
|
61
|
+
- Broad: cooking.
|
|
62
|
+
- Narrower: cooking on weeknights.
|
|
63
|
+
- Narrower still: cooking dinner in 20 minutes after work.
|
|
64
|
+
- For whom, so that: for parents who get home at 6, so that the family eats
|
|
65
|
+
together without takeaway every night.
|
|
66
|
+
|
|
67
|
+
The narrower the topic, the easier the post is to write and the quicker the
|
|
68
|
+
right reader knows it is for them.
|
|
69
|
+
|
|
70
|
+
**Proof: why should anyone listen?** Two kinds:
|
|
71
|
+
|
|
72
|
+
- Own proof: "This is what happened to me." Lived experience needs no title;
|
|
73
|
+
say plainly that it is your experience.
|
|
74
|
+
- Borrowed proof: what someone with the experience says or showed: a study,
|
|
75
|
+
a well-known practitioner, a customer, a book. Name the source honestly. On
|
|
76
|
+
X, links are removed, so name it in words.
|
|
77
|
+
|
|
78
|
+
If the user has neither for a topic, pick another topic or borrow proof.
|
|
79
|
+
|
|
80
|
+
**Angle: which road do you take the reader down?**
|
|
81
|
+
|
|
82
|
+
| Angle | The post says | Example idea |
|
|
83
|
+
|---|---|---|
|
|
84
|
+
| How-to | Here is how to do it, step by step. | 5 steps to plan a week of dinners in 15 minutes |
|
|
85
|
+
| Analysis | Here is what the data or the trend shows, and why. | Why grocery bills rose more for small households this year |
|
|
86
|
+
| Inspiration | I did it, so you can too. | How I went from takeaway five nights a week to one |
|
|
87
|
+
| Human nature | Here is the hidden human reason behind it. | Why we buy vegetables we never cook |
|
|
88
|
+
|
|
89
|
+
Readers come back for the angle they liked. Try all four early; once the
|
|
90
|
+
numbers show which one the user's audience prefers, lean on it. Mixing is
|
|
91
|
+
fine later.
|
|
92
|
+
|
|
93
|
+
### A short interview when the user has no idea yet
|
|
94
|
+
|
|
95
|
+
Ask one question at a time, then offer three ideas, each with a hook:
|
|
96
|
+
|
|
97
|
+
1. What do you do, and for whom?
|
|
98
|
+
2. What question do people ask you most?
|
|
99
|
+
3. What did you get wrong at the start?
|
|
100
|
+
4. What do most people in your field believe that you disagree with?
|
|
101
|
+
5. What happened this week that taught you something?
|
|
102
|
+
|
|
103
|
+
For a whole month of ideas from one topic, use `postemi-growth` (30 angles)
|
|
104
|
+
if it is installed.
|
|
105
|
+
|
|
106
|
+
## 2. The hook
|
|
107
|
+
|
|
108
|
+
The first line (or the title, on YouTube and blogs) decides whether anyone
|
|
109
|
+
reads the rest. A good hook has these five qualities:
|
|
110
|
+
|
|
111
|
+
1. **Clear, not clever.** A pun makes a friend smile and a stranger scroll
|
|
112
|
+
past. The reader must see at once what this is about and who it is for.
|
|
113
|
+
2. **A promise.** Not only "this is about X" but "after reading, you will
|
|
114
|
+
have Y". No promise, no reason to give it 30 seconds.
|
|
115
|
+
3. **Specific.** Name the problem, the reader, or both. Vague reads as
|
|
116
|
+
"not for me".
|
|
117
|
+
4. **A stance.** Lean one way. The right reader thinks "this is exactly my
|
|
118
|
+
problem"; the wrong one thinks "not for me", and that is fine. A post for
|
|
119
|
+
everyone is a post for no one.
|
|
120
|
+
5. **An open loop.** Say what they will get, hold back the answer. "Coffee
|
|
121
|
+
makes you anxious" gives it away; "The one coffee habit behind my 3 pm
|
|
122
|
+
anxiety" makes them read on.
|
|
123
|
+
|
|
124
|
+
### Build the hook from six parts
|
|
125
|
+
|
|
126
|
+
| Part | Question | Example |
|
|
127
|
+
|---|---|---|
|
|
128
|
+
| Number | How many things? | 4 |
|
|
129
|
+
| Kind | Tips, mistakes, lessons, reasons, steps? | mistakes |
|
|
130
|
+
| Topic | What exactly, two or three levels deep? | new runners make in their first month |
|
|
131
|
+
| Reader | Who is it for? (often implied by the topic) | new runners |
|
|
132
|
+
| Payoff | What does it get them, or save them from? | that lead to shin pain |
|
|
133
|
+
| More stakes | What else is at risk or to win? | missed races, quitting by spring |
|
|
134
|
+
|
|
135
|
+
Write the long version first, with every part:
|
|
136
|
+
|
|
137
|
+
> 4 mistakes new runners make in their first month that lead to shin pain,
|
|
138
|
+
> missed races and quitting by spring
|
|
139
|
+
|
|
140
|
+
Then cut to fit the network: drop extra stakes first, then adjectives.
|
|
141
|
+
|
|
142
|
+
> 4 first-month running mistakes that end in shin pain
|
|
143
|
+
|
|
144
|
+
Starting long and cutting is easier than trying to be short and sharp at once.
|
|
145
|
+
|
|
146
|
+
Ready patterns: [reference/headline-patterns.md](./reference/headline-patterns.md)
|
|
147
|
+
and the hook groups in the `postemi-templates` skill. Offer the user two or
|
|
148
|
+
three hooks for the same post and let them pick.
|
|
149
|
+
|
|
150
|
+
### Where the hook has to land
|
|
151
|
+
|
|
152
|
+
| Network | The hook is |
|
|
153
|
+
|---|---|
|
|
154
|
+
| X, Threads, Bluesky, Mastodon | the first line, and the first entry of a thread on its own |
|
|
155
|
+
| LinkedIn | the first two or three lines, before "see more" |
|
|
156
|
+
| Instagram | the first sentence of the caption (about 125 characters show), plus the image or the first second of the Reel |
|
|
157
|
+
| TikTok, Reels, Shorts | the first one to three seconds and the on-screen text |
|
|
158
|
+
| YouTube | the title (and the thumbnail the user makes) |
|
|
159
|
+
| Facebook | the first line; long posts fold after a few lines |
|
|
160
|
+
| WordPress, Ghost, Dev.to, Tumblr | the title |
|
|
161
|
+
|
|
162
|
+
## 3. The first sentence: six openers
|
|
163
|
+
|
|
164
|
+
Open with one sentence that does one of these:
|
|
165
|
+
|
|
166
|
+
1. **A bold statement.** "Most small shops do not need a website. They need a
|
|
167
|
+
good photo on their map listing."
|
|
168
|
+
2. **A question that makes them think.** "Why do the best bakers in town
|
|
169
|
+
never run out of bread at noon?"
|
|
170
|
+
3. **A contrary opinion.** "Posting every day is bad advice for most
|
|
171
|
+
businesses."
|
|
172
|
+
4. **A moment in time.** "At 6:40 on a Monday, our only oven died with 200
|
|
173
|
+
orders due."
|
|
174
|
+
5. **An honest admission.** "For three years I priced my work too low and
|
|
175
|
+
called it being kind."
|
|
176
|
+
6. **A surprising fact or detail.** "Our slowest product sells best on rainy
|
|
177
|
+
Tuesdays."
|
|
178
|
+
|
|
179
|
+
Facts in openers must be true and, where it matters, sourced.
|
|
180
|
+
|
|
181
|
+
## 4. Shape the post
|
|
182
|
+
|
|
183
|
+
**Outline before writing.** Four lines, then fill them in:
|
|
184
|
+
|
|
185
|
+
1. Working hook.
|
|
186
|
+
2. One line of proof (why the user can say this).
|
|
187
|
+
3. The main points (two to five).
|
|
188
|
+
4. The takeaway (the one thing to remember or do).
|
|
189
|
+
|
|
190
|
+
**Lead with the best part.** Do not make the reader wade through setup to
|
|
191
|
+
reach the useful bit. Every line should earn the next.
|
|
192
|
+
|
|
193
|
+
**Points that tell the story.** In a long post, a thread or a carousel, make
|
|
194
|
+
each main point a line that reads well on its own, so a skimmer gets the
|
|
195
|
+
whole story from the points alone. Use the points as section lines or as the
|
|
196
|
+
first line of each thread entry.
|
|
197
|
+
|
|
198
|
+
**The 1-3-1 rhythm.** Alternate a one-sentence paragraph with a paragraph of
|
|
199
|
+
about three sentences, then a single line again. Vary sentence length the same
|
|
200
|
+
way. It gives the reader a breath between ideas. On LinkedIn and Instagram,
|
|
201
|
+
read mostly on phones, keep most paragraphs to one or two sentences.
|
|
202
|
+
|
|
203
|
+
**End on purpose.** One of: a takeaway line, a question that is easy to
|
|
204
|
+
answer ("Which of these did you make?"), or one call to action. Never three.
|
|
205
|
+
|
|
206
|
+
**Text plus a picture or a video** usually beats text alone. Use the user's
|
|
207
|
+
own photos and videos (Postemi uploads them; it does not generate images or
|
|
208
|
+
video). A screenshot, a photo of the work or a short clip is enough.
|
|
209
|
+
|
|
210
|
+
**Format.** Postemi post content is HTML: each line in `<p>`, plus `strong`,
|
|
211
|
+
`ul`/`li` and `h1` to `h3` (never `u` and `strong` together). Networks show
|
|
212
|
+
formatting differently; line breaks and short lists are safe everywhere. The
|
|
213
|
+
preview shows the result.
|
|
214
|
+
|
|
215
|
+
## 5. Formats
|
|
216
|
+
|
|
217
|
+
- **Short post:** one idea, one to five lines. The daily bread on X, Threads
|
|
218
|
+
and Bluesky.
|
|
219
|
+
- **Long post:** a hook, three to seven short paragraphs or a list, a
|
|
220
|
+
takeaway. Strong on LinkedIn and Facebook, and on X for accounts with a
|
|
221
|
+
higher character limit (the limit comes from the account, never guess it).
|
|
222
|
+
- **Thread** (X, Threads, Bluesky): the first entry must work alone and make
|
|
223
|
+
people open the rest. One point per entry. The last entry sums up and asks
|
|
224
|
+
for a reply or a follow. Ask the user whether they want a thread or one long
|
|
225
|
+
post. On X, every thread entry counts toward the account's monthly X post
|
|
226
|
+
allowance in Postemi.
|
|
227
|
+
- **Carousel** (LinkedIn image carousel, Instagram multi-image): one point per
|
|
228
|
+
slide, the hook on the first slide, the takeaway on the last. The user
|
|
229
|
+
supplies the images.
|
|
230
|
+
- **Video caption** (TikTok, Reels, Shorts, YouTube): the caption supports
|
|
231
|
+
the video; the hook lives in the first seconds of the video itself.
|
|
232
|
+
- **Post plus first comment** (LinkedIn, Facebook): put the main text in the
|
|
233
|
+
post and a link or extra detail in the first comment. In Postemi, the
|
|
234
|
+
entries after the first are comments on these networks.
|
|
235
|
+
|
|
236
|
+
## 6. Network by network
|
|
237
|
+
|
|
238
|
+
Short version; details in [reference/networks.md](./reference/networks.md).
|
|
239
|
+
|
|
240
|
+
- **X:** short and direct; one X channel per post; no links (Postemi removes
|
|
241
|
+
them, so put the link in the bio or tell the user to post it on X
|
|
242
|
+
themselves); the character limit depends on the account; threads and every
|
|
243
|
+
entry count toward the monthly X allowance.
|
|
244
|
+
- **LinkedIn:** the hook before "see more", short paragraphs, a question at the
|
|
245
|
+
end to draw comments; long text with an image, or an image carousel, does
|
|
246
|
+
well. Personal profiles only today (company pages are coming soon).
|
|
247
|
+
- **Instagram:** the picture or Reel first, then a caption whose first sentence
|
|
248
|
+
hooks; a clear call to action; a few relevant hashtags. Reels want 9:16.
|
|
249
|
+
- **Threads, Bluesky, Mastodon:** conversational, short; threads work.
|
|
250
|
+
- **Facebook:** a friendly, local voice; questions and photos; links are fine.
|
|
251
|
+
- **TikTok, YouTube:** the video carries it; write a caption and (YouTube) a
|
|
252
|
+
title that make a clear promise. TikTok takes about 15 posts per account per
|
|
253
|
+
day.
|
|
254
|
+
- **Blog channels (WordPress, Ghost, Dev.to, Tumblr; beta):** a home for the
|
|
255
|
+
long version of the user's best posts, with a title.
|
|
256
|
+
|
|
257
|
+
Never offer a network Postemi does not support (the main skill has the list;
|
|
258
|
+
Pinterest, Google Business Profile and LinkedIn company pages are not
|
|
259
|
+
schedulable yet).
|
|
260
|
+
|
|
261
|
+
## 7. Check before publishing
|
|
262
|
+
|
|
263
|
+
Go through this list for every draft, then show the user:
|
|
264
|
+
|
|
265
|
+
1. The hook is clear, specific, promises something and leaves a question open.
|
|
266
|
+
2. The body keeps the promise of the hook.
|
|
267
|
+
3. The best part comes first; nothing is padding.
|
|
268
|
+
4. Every fact, number and quote is true and came from the user or a named
|
|
269
|
+
source.
|
|
270
|
+
5. One idea, one call to action at most.
|
|
271
|
+
6. Short paragraphs; the 1-3-1 rhythm; it reads well on a phone.
|
|
272
|
+
7. Every [placeholder] from a template is filled or removed.
|
|
273
|
+
8. It fits the account's character limit (from the schema, not from memory).
|
|
274
|
+
9. Network rules: no link in X posts; the LinkedIn hook sits above "see more";
|
|
275
|
+
media where the network needs it (Instagram, TikTok, YouTube).
|
|
276
|
+
10. It sounds like the user, not like an advert. Read it aloud.
|
|
277
|
+
11. Hashtags, if any: few and relevant. Emojis, if any: where the user would
|
|
278
|
+
use them.
|
|
279
|
+
|
|
280
|
+
## 8. From draft to scheduled, with Postemi
|
|
281
|
+
|
|
282
|
+
The workflow is always: **draft, preview, confirm, schedule.** The exact
|
|
283
|
+
calls are in the main `postemi` skill; in short:
|
|
284
|
+
|
|
285
|
+
Use whichever your client has. If the Postemi MCP tools are connected, use
|
|
286
|
+
them and never install the CLI; the CLI is for agents with a terminal.
|
|
287
|
+
|
|
288
|
+
With the Postemi MCP tools (Claude, ChatGPT, Cursor, Grok and other chat
|
|
289
|
+
clients):
|
|
290
|
+
|
|
291
|
+
1. `get_workspace_context` for the clock and the user's timezone.
|
|
292
|
+
2. `list_integrations`; pick channels by id; say the `@handle` back.
|
|
293
|
+
3. `get_integration_schema` for each channel: the real character limit and
|
|
294
|
+
the required settings. Write within them.
|
|
295
|
+
4. `preview_post` with one `socialPost` entry per channel (each with its own
|
|
296
|
+
text, so every network gets its own version) and show the result.
|
|
297
|
+
5. After the user says yes: `create_post` with the same payload and a new
|
|
298
|
+
`idempotencyKey`. `type: "draft"` saves without scheduling.
|
|
299
|
+
|
|
300
|
+
With the `postemi` CLI (coding agents with a terminal):
|
|
301
|
+
|
|
302
|
+
1. `postemi auth:status`, then `postemi integrations:list`.
|
|
303
|
+
2. `postemi integrations:settings <id>` for the limit and the settings.
|
|
304
|
+
3. Show the user the text per channel and the local time; wait for a yes.
|
|
305
|
+
4. `postemi posts:create ... -t draft` to save, or with `-s "<date>"
|
|
306
|
+
--timezone <IANA>` to schedule; `--json` for different text per channel.
|
|
307
|
+
`postemi posts:find-slot <id>` suggests the next free slot.
|
|
308
|
+
|
|
309
|
+
After it goes out, the numbers tell you which hooks and angles work: see
|
|
310
|
+
`postemi-growth` (optional).
|
|
@@ -0,0 +1,109 @@
|
|
|
1
|
+
# Hook and headline patterns
|
|
2
|
+
|
|
3
|
+
25 patterns for a first line, a thread opener, a LinkedIn hook or a title.
|
|
4
|
+
Brackets are slots. Each pattern has two made-up examples; write the user's
|
|
5
|
+
own version, with their real topic, numbers and experience.
|
|
6
|
+
|
|
7
|
+
Rules that hold for every pattern:
|
|
8
|
+
|
|
9
|
+
- The body must deliver what the pattern promises. A list pattern needs the
|
|
10
|
+
full list; a "guaranteed" or "secret" pattern needs a real, specific answer.
|
|
11
|
+
- Use real numbers only. "7 mistakes" means seven.
|
|
12
|
+
- Cut to the network: long titles for blogs and YouTube, short hooks for X.
|
|
13
|
+
|
|
14
|
+
## Problems and mistakes
|
|
15
|
+
|
|
16
|
+
1. **[N] overlooked [things] behind your [problem]**
|
|
17
|
+
- 5 overlooked settings behind your slow laptop
|
|
18
|
+
- 3 overlooked habits behind your afternoon crash
|
|
19
|
+
2. **The [N] biggest mistakes people make when [doing something]**
|
|
20
|
+
- The 6 biggest mistakes people make when they open a second shop
|
|
21
|
+
- The 4 biggest mistakes people make when they adopt a puppy
|
|
22
|
+
3. **[N] in 10 people [have this problem]. Are you one of them?**
|
|
23
|
+
- 8 in 10 small online shops lose sales at checkout. Is yours one of them?
|
|
24
|
+
(only with a real source for the number)
|
|
25
|
+
- Most new managers skip one-to-ones in their first month. Are you one of
|
|
26
|
+
them?
|
|
27
|
+
4. **How to get rid of [problem] for good, even if you have tried everything**
|
|
28
|
+
- How to stop procrastinating on invoices for good, even if you have tried
|
|
29
|
+
everything
|
|
30
|
+
- How to get rid of fruit flies in the kitchen for good, even if you have
|
|
31
|
+
tried everything
|
|
32
|
+
5. **How [industry] takes advantage of [audience], and how to fix it**
|
|
33
|
+
- How phone contracts take advantage of older customers, and how to fix it
|
|
34
|
+
- How ticket fees take advantage of fans, and what organisers can do
|
|
35
|
+
|
|
36
|
+
## How-to and guides
|
|
37
|
+
|
|
38
|
+
6. **A step-by-step guide to [doing something]**
|
|
39
|
+
- A step-by-step guide to selling your first handmade candle online
|
|
40
|
+
- A step-by-step guide to running your first community meetup
|
|
41
|
+
7. **How to [get a result] in [a short time]**
|
|
42
|
+
- How to tidy your inbox to zero in one afternoon
|
|
43
|
+
- How to learn the basics of a spreadsheet in a weekend
|
|
44
|
+
8. **How to [get something good] without [giving up something you like]**
|
|
45
|
+
- How to save for a holiday without giving up your weekend coffee
|
|
46
|
+
- How to grow on LinkedIn without posting every day
|
|
47
|
+
9. **The best ways to get [result] without needing [usual requirement]**
|
|
48
|
+
- The best ways to get your first clients without a portfolio
|
|
49
|
+
- The best ways to eat well on a budget without meal prepping all Sunday
|
|
50
|
+
10. **The complete guide to [topic]**
|
|
51
|
+
- The complete guide to renting your first flat
|
|
52
|
+
- The complete guide to starting a vegetable patch on a balcony
|
|
53
|
+
11. **Want [result]? Try [this one thing]**
|
|
54
|
+
- Want more replies to your cold emails? Try this two-line opener
|
|
55
|
+
- Want calmer mornings? Try packing the bag the night before
|
|
56
|
+
12. **How to survive your first [big experience]**
|
|
57
|
+
- How to survive your first trade fair as an exhibitor
|
|
58
|
+
- How to survive your first week as a team lead
|
|
59
|
+
|
|
60
|
+
## Lessons and stories
|
|
61
|
+
|
|
62
|
+
13. **[N] lessons from [doing something hard or long]**
|
|
63
|
+
- 7 lessons from running a bakery for 10 years
|
|
64
|
+
- 5 lessons from my first 100 customer calls
|
|
65
|
+
14. **A day in the life of a [profession]**
|
|
66
|
+
- A day in the life of a hospital night porter
|
|
67
|
+
- A day in the life of a one-person design studio
|
|
68
|
+
15. **[Insight], from someone who does it for a living**
|
|
69
|
+
- Why restaurant prices keep rising, from a restaurant owner
|
|
70
|
+
- What makes a CV stand out, from a recruiter who reads 200 a week
|
|
71
|
+
16. **What [a credible kind of person] can teach us about [topic]**
|
|
72
|
+
- What an air traffic controller can teach us about focus
|
|
73
|
+
- What a chess coach can teach us about making decisions under pressure
|
|
74
|
+
(use a role, or a real person only when the user has a true, sourced
|
|
75
|
+
lesson from them)
|
|
76
|
+
17. **Is [thing] worth it? My honest review**
|
|
77
|
+
- Are online courses worth it? My honest review after 12 of them
|
|
78
|
+
- Is a standing desk worth it? My honest review after a year
|
|
79
|
+
|
|
80
|
+
## Secrets, surprises and science
|
|
81
|
+
|
|
82
|
+
18. **The secret to [something people want]**
|
|
83
|
+
- The secret to a sourdough that rises every time
|
|
84
|
+
- The secret to meetings that end on time
|
|
85
|
+
19. **The [N] things most people do not know about [topic]**
|
|
86
|
+
- The 7 things most people do not know about buying a used car
|
|
87
|
+
- The 5 things most people do not know about how app stores rank apps
|
|
88
|
+
20. **Why [something happens], according to research**
|
|
89
|
+
- Why small talk feels exhausting, according to research
|
|
90
|
+
- Why we remember the end of a holiday most, according to research
|
|
91
|
+
21. **[N] things your [detail] says about you**
|
|
92
|
+
- 5 things your email signature says about your business
|
|
93
|
+
- 3 things your shop window says to people walking past
|
|
94
|
+
22. **A reliable way to [get or avoid something]**
|
|
95
|
+
- A reliable way to never miss a tax deadline
|
|
96
|
+
- A reliable way to avoid scope creep on client projects
|
|
97
|
+
(stronger words like "guaranteed" only when it truly is)
|
|
98
|
+
23. **How to make good money [doing something unexpected]**
|
|
99
|
+
- How a weekend bike repair stall became a full-time income
|
|
100
|
+
- How to earn a living cleaning solar panels
|
|
101
|
+
|
|
102
|
+
## Lists and resources
|
|
103
|
+
|
|
104
|
+
24. **The [N] best [books, tools, podcasts] if you want to [goal]**
|
|
105
|
+
- The 5 best books if you want to write clearer emails
|
|
106
|
+
- The 4 best free tools if you run a one-person shop
|
|
107
|
+
25. **[N] tips for [getting past an obstacle]**
|
|
108
|
+
- 6 tips for staying active when you work from home
|
|
109
|
+
- 4 tips for asking for a raise when you hate negotiating
|
|
@@ -0,0 +1,113 @@
|
|
|
1
|
+
# Writing for each network
|
|
2
|
+
|
|
3
|
+
What tends to work on each network, and what Postemi does there. Postemi's
|
|
4
|
+
rules (character limits, required settings, the X rules) come from the
|
|
5
|
+
account's schema and the main `postemi` skill; when this file and the schema
|
|
6
|
+
disagree, the schema wins.
|
|
7
|
+
|
|
8
|
+
The networks below are the ones Postemi publishes to today. Pinterest, Google
|
|
9
|
+
Business Profile and LinkedIn company pages are coming soon and cannot be
|
|
10
|
+
scheduled yet. Never plan posts for a network Postemi does not offer.
|
|
11
|
+
|
|
12
|
+
## X
|
|
13
|
+
|
|
14
|
+
- **Shape:** short posts of one idea; a thread for anything with steps or a
|
|
15
|
+
story; a longer single post only when the account's limit allows it (read
|
|
16
|
+
the limit from the schema; never assume the account has a paid tier).
|
|
17
|
+
- **Hook:** the first line. In a thread, the first entry must work on its own.
|
|
18
|
+
- **Links:** Postemi removes links from X posts and their threads, because X
|
|
19
|
+
charges for every post with a link. Put the user's link in their X bio, or
|
|
20
|
+
tell the user to post a link on X directly. Name sources in words.
|
|
21
|
+
- **Allowance:** the account has a monthly number of X posts in Postemi; every
|
|
22
|
+
thread entry counts as one. Check what is left before planning a busy X
|
|
23
|
+
calendar; when it runs out, X posts can only be saved as drafts until it
|
|
24
|
+
resets.
|
|
25
|
+
- **One X channel per post.** Two X accounts need two separate posts with
|
|
26
|
+
different text.
|
|
27
|
+
- **Media:** text plus a picture or a short video tends to beat text alone.
|
|
28
|
+
- **Settings:** who can reply is required (see the main skill).
|
|
29
|
+
|
|
30
|
+
## LinkedIn
|
|
31
|
+
|
|
32
|
+
- **Shape:** one post a day at most is plenty; long text with an image, or an
|
|
33
|
+
image carousel (`post_as_images_carousel`), does well. Pure text works when
|
|
34
|
+
the writing is strong.
|
|
35
|
+
- **Hook:** the first two or three lines, before "see more". Put the promise
|
|
36
|
+
there, not a greeting.
|
|
37
|
+
- **Paragraphs:** one or two sentences each; most people read on a phone.
|
|
38
|
+
- **Two kinds of post work together:** insight posts about the user's field
|
|
39
|
+
(most of them) and human posts: a lesson learned the hard way, a funny
|
|
40
|
+
moment, a challenge (about one in three).
|
|
41
|
+
- **Comments:** comments are what spreads a post beyond the user's network.
|
|
42
|
+
End with a question that is easy to answer, and remind the user to reply to
|
|
43
|
+
comments in the first hours.
|
|
44
|
+
- **Links:** a link in the post can pull people off the feed. A common pattern
|
|
45
|
+
is the post on its own and the link in the first comment; in Postemi that is
|
|
46
|
+
the second entry of `postsAndComments`, which LinkedIn shows as a comment.
|
|
47
|
+
- **Today:** personal profiles only; company pages are coming soon.
|
|
48
|
+
|
|
49
|
+
## Instagram
|
|
50
|
+
|
|
51
|
+
- **Shape:** the picture or the Reel carries the post. Feed post, carousel,
|
|
52
|
+
Reel or Story (`post_type` is required).
|
|
53
|
+
- **Caption:** the first sentence (about 125 characters show) is the hook;
|
|
54
|
+
then two or three useful lines that keep its promise; then one call to
|
|
55
|
+
action (save, share, comment, the link in the bio).
|
|
56
|
+
- **Reels:** vertical 9:16 video; the hook in the first one to three seconds;
|
|
57
|
+
on-screen text for people watching without sound.
|
|
58
|
+
- **Hashtags:** a few relevant ones; they help people find the post.
|
|
59
|
+
- **Links:** captions do not make links clickable; point to the link in the
|
|
60
|
+
bio.
|
|
61
|
+
|
|
62
|
+
## Threads and Bluesky
|
|
63
|
+
|
|
64
|
+
- **Shape:** short, conversational posts; threads for longer ideas; replies
|
|
65
|
+
matter. Bluesky's limit is short, so read it from the schema.
|
|
66
|
+
- **Links:** allowed.
|
|
67
|
+
|
|
68
|
+
## Mastodon (beta)
|
|
69
|
+
|
|
70
|
+
- **Shape:** conversational; people value plain, useful posts and dislike
|
|
71
|
+
marketing tone. About 500 characters on mastodon.social; other servers set
|
|
72
|
+
their own limit (read it from the schema).
|
|
73
|
+
|
|
74
|
+
## Facebook
|
|
75
|
+
|
|
76
|
+
- **Shape:** a friendly, local voice; photos and short videos; questions
|
|
77
|
+
people can answer in a word. Links are fine.
|
|
78
|
+
- **Comments:** entries after the first are comments in Postemi, useful for a
|
|
79
|
+
link or a follow-up detail.
|
|
80
|
+
- **Story:** `post_type: "story"` with a picture or a video.
|
|
81
|
+
|
|
82
|
+
## TikTok
|
|
83
|
+
|
|
84
|
+
- **Shape:** the video is the post; the caption adds context and a question.
|
|
85
|
+
- **Hook:** the first one to three seconds of the video.
|
|
86
|
+
- **Volume:** TikTok accepts about 15 posts per account in 24 hours; spread
|
|
87
|
+
bigger batches over more days.
|
|
88
|
+
- **Settings:** privacy and posting method are required.
|
|
89
|
+
|
|
90
|
+
## YouTube
|
|
91
|
+
|
|
92
|
+
- **Shape:** a title, a description and the video; Shorts are 9:16.
|
|
93
|
+
- **Title:** clear promise, specific, front-load the topic words people
|
|
94
|
+
search for. The thumbnail is the user's.
|
|
95
|
+
- **Settings:** a title and a type are required; ask the user about privacy.
|
|
96
|
+
|
|
97
|
+
## Telegram, Discord, Slack, Google Chat, Microsoft Teams
|
|
98
|
+
|
|
99
|
+
- **Shape:** messages to a community the user already has. Be direct: what
|
|
100
|
+
is new, why it matters to them, what to do. Discord and Slack need a channel
|
|
101
|
+
id from their `channels` tool.
|
|
102
|
+
|
|
103
|
+
## WordPress, Ghost, Dev.to, Tumblr (beta)
|
|
104
|
+
|
|
105
|
+
- **Shape:** the long version: a title that makes a promise, an opening line,
|
|
106
|
+
section headings that tell the story, a takeaway. A title is required on
|
|
107
|
+
WordPress, Ghost and Dev.to.
|
|
108
|
+
- **Use:** republish the user's best long posts and threads here as articles,
|
|
109
|
+
so they keep working and can be found by search.
|
|
110
|
+
|
|
111
|
+
## Pixelfed (beta)
|
|
112
|
+
|
|
113
|
+
- **Shape:** picture first, like Instagram; a picture is required.
|