Bot de fábrica de contenido
Un Grok Bot que explora ángulos en X el lunes y redacta los posts de la próxima semana para el jueves.
por GetKits
Mira la diferencia
El ángulo que tu nicho está debatiendo
Antes
Rutina del lunes 8:00. Nicho: onboarding y retención para agencias pequeñas. 16 cuentas y 5 búsquedas en X, últimos 7 días. Fuentes anteriores de Lena en el calendario de contenido de Notion.
Después
"Enviamos a las agencias nuevas 7 correos de onboarding con temporizador. El 9% hizo clic. Lo recortamos a 4." Borrador de gancho para el Ángulo 1: secuencias por días frente a correos enviados cuando los usuarios se atascan. La pregunta de un fundador de operaciones de agencia reunió unas 140 respuestas y nadie contestó con datos [enlace]. Tu ventaja: tu prueba del 29 sep, clics del 9% al 31%. Inicio de un INFORME DE ÁNGULOS con 4 ángulos y una lista de descartes. Solo lectura: no se publicó, ni se dio me gusta, ni se siguió a nadie.
Thursday pack from the angle you picked
Antes
Routine: Thursday weekly-pack prep, Thu 2026-11-05, 9:00 AM America/Toronto. Lena's reply to Monday's ANGLE REPORT: "Angle 3, the 'where are the files' emails. Source: my Oct 27 blog post, it has the number now." Blog post "Where are the files? 18 agencies counted", about 1,100 words: 18 agencies counted client "where is it?" emails for two weeks before and two weeks after turning on the Files tab. Median 11 a week before, 3 after. The tab: one per client, sorted by project, a "new" badge, a last-updated date. Lena: "I'd assumed clients were lazy. They were lost." Maya Chen, Northwind Creative: "My clients stopped asking because they stopped having to." Content calendar: no rows for 2026-W46 yet. RED note: yes. Newsletter: Thursday. Premium: no.
Después
Pack check: no row uses this source. Pack ID: 2026-W46-file-requests. VOICE PROFILE loaded. SOURCE BRIEF Thesis: Clients ask "where is it?" when files have no fixed home. Give each client one place. Ideas: 1. One place per client cuts file requests | Proof: 18 agencies, median 11 a week before the Files tab, 3 after | Type: number 2. The clients were lost | Proof: "I'd assumed clients were lazy. They were lost." | Type: story 3. Four details in the tab | Proof: one per client, sorted by project, "new" badge, last-updated date | Type: example 4. A customer said it plainly | Proof: Maya Chen, Northwind Creative | Type: quote To confirm: how the 18 agencies were chosen; Maya Chen's OK to be quoted beyond the blog X THREAD Hook formula: Specific result 1/ 18 agencies counted every "where is that file?" email from their clients for two weeks. The median was 11 a week. Two weeks after each client got one Files tab, it was 3. (posts 2 to 5: one tab detail each; post 6: takeaway and blog link) X POSTS Post 3 | Confession | 202 chars I'd assumed the clients who kept asking agencies for files were lazy. 18 agencies counted those emails for us. 11 a week. After each client got one place to look, 3. They weren't lazy. They were lost. LINKEDIN POST Hook formula: Cold open | 1,210 chars "My clients stopped asking because they stopped having to." Maya Chen, Northwind Creative, was one of the 18 agencies that counted. NEWSLETTER SECTION Subject line options: 11 file emails a week, then 3 (29) | Why clients ask where the files are (35) | What 18 agencies counted (24) Link line: All 18 agencies' numbers: [confirm link] VIDEO SCRIPT Length: 35 seconds | Spoken words: 84 [0:00-0:03] HOOK | Say: "Eleven emails a week asking where the files are." | On screen: "11 a week" RED NOTE 标题:每周11封“文件在哪”,后来只剩3封 CALENDAR | Mon 2026-11-09 08:30 | LinkedIn | My clients stopped asking because they stopped having to | Retention | Cold open | 2026-W46-file-requests | Ready for review | (8 more rows: thread Tue, video and X post Wed, newsletter and X post Thu, X post and RED Fri, X post Sat) OPEN ITEMS - [confirm] Maya Chen agreed to be quoted outside your blog (LINKEDIN POST) - [confirm] How the 18 agencies were picked (X THREAD post 1) - [confirm link] Blog post (X THREAD post 6, NEWSLETTER SECTION) - Asset needed: screenshot of one client's Files tab (VIDEO SCRIPT, RED NOTE) - Anti-AI fixes made: 5 Approve adding these 9 rows to Content calendar as Ready for review?
Friday performance review
Antes
Routine: Friday performance review, Fri 2026-10-09, 4:00 PM America/Toronto. Content calendar, Pack ID 2026-W41-chatbot, 9 rows planned: Mon LinkedIn "We turned off our support chatbot": 14,200 impr, 61 replies, 88 saves Tue X thread "Our chatbot wrote 200-word answers to a 40-word doc": 9,800 / 34 / 41, 57 clicks Wed X post "Most features need to be shorter": 3,100 / 4 / 6 Wed Video: 2,400 views / 9 / 12 Thu Newsletter: 3,080 delivered, 212 clicks (Lena pasted) Thu X post "Tickets went up 6%": 4,600 / 18 / 22 Fri X post (9:00 AM): 5,200 / 22 / 19 Fri RED (8:00 AM): 1,900 views / 11 / 45 Sat X post: Killed, note "too close to the thread" Notes: "Time: 52 min"
Después
PERFORMANCE REVIEW Week: 2026-W41 | Pack: 2026-W41-chatbot | Shipped: 8 of 9 (Sat X post killed: "too close to the thread") | Time per pack: 52 min (target under 45) | Date | Channel | Name | Hook formula | Impr. | Replies | Saves | Clicks | Depth per 1k | | Mon 10-05 | LinkedIn | We turned off our support chatbot | Confession | 14,200 | 61 | 88 | 0 | 10.5 | | Tue 10-06 | X thread | Our chatbot wrote 200-word answers | Curiosity detail | 9,800 | 34 | 41 | 57 | 7.7 | | Wed 10-07 | X post | Most features need to be shorter | Contrarian | 3,100 | 4 | 6 | 0 | 3.2 | | Wed 10-07 | Video | A 200-word answer to a 40-word doc | Curiosity detail | 2,400 | 9 | 12 | 0 | 8.8 | | Thu 10-08 | X post | Tickets went up 6%. Churn didn't move | Specific result | 4,600 | 18 | 22 | 0 | 8.7 | | Fri 10-09 | X post | A client asked why we have no chatbot | Cold open | 5,200 | 22 | 19 | 0 | 7.9 | | Fri 10-09 | RED | 我们把客服机器人关掉了 | Confession | 1,900 | 11 | 45 | 0 | 29.5 | Median depth per 1k (excluding newsletter and RED): 8.3, last week 6.1 Newsletter: 212 / 3,080 = 6.9%, 4-week median 5.4% RED: compared only with RED. 29.5 vs 21.0 last week. Friday pieces are 8 hours old or less; their numbers will still move. Top piece: LinkedIn, Monday. Data: most replies and saves; 23 of 61 replies asked what replaced the chatbot. Guess: Confession hook, with the 6% in the first three lines. Bottom piece: Wednesday X post. Data: lowest depth, and the only post with no number. Guess: an opinion without proof reads as a platitude. Questions from replies: 1. "What did you replace the chatbot with?" (23 replies, LinkedIn) 2. "Did you track CSAT?" (4 replies, thread) 3. "How short should a help doc be?" (3 replies, thread) Next week: - Do more: Confession hooks with a number in the first three lines - Do less: opinion posts with no number. Add one or skip the slot - Test one thing: newsletter link in the thread's last post as well as the reply; compare with this week's 57 clicks Approve writing this review to Notion?
Reply drafts on a busy post
Antes
Lena: /reply-drafts for my LinkedIn chatbot post. Replies include: - Priya Nair, Head of CS at Orbit: "What did you replace the chatbot with? Docs only?" - Jun Park, founder of Lumen: "6% more tickets but same churn. Did you look at CSAT?" - Marco: "Bots are fine. Yours was badly configured." - An account offering "10x growth, DM me"
Después
REPLY DRAFTS 1. Link: [link] | Author: Priya Nair, Head of CS at Orbit What they said: asked what replaced the chatbot Draft: "Mostly shorter docs. The invite-a-client doc is 40 words, and that was always the real answer. [confirm: anything else that replaced it]" Intent: answer | Risk: needs [confirm] 2. Link: [link] | Author: Jun Park, founder of Lumen What they said: asked whether you tracked CSAT Draft if yes: "We did. CSAT went from [confirm] to [confirm] over the same three weeks." Draft if no: "We didn't track it then. Fair hole in the story." Intent: add proof | Risk: needs [confirm] 3. Link: [link] | Author: Marco What they said: the bot was badly configured Draft: "Maybe. But the doc it summarised was 40 words. Any setup that turns 40 words into 200 is solving the wrong problem." Intent: push back | Risk: none Skipped: 1 (spam offer) Post these yourself. Nothing was liked, replied to or followed.
Qué incluye
- content-factory-bot-setup.md
Sobre este Kit
Content Factory Bot is a Grok Bot teammate that runs the outside half of your content week. Every Monday it reads what is drawing replies in your niche on X and brings you up to five angles you can credibly own. Every Thursday it turns the source you picked into next week's drafts in your voice. Every Friday it tells you what worked and why. It reads X and never posts, and nothing lands in Notion without your yes. Setup takes about 15 minutes.
What you get
- A setup file that builds the Bot step by step: profile, description, one setup message, plugin connections and a test run that proves the approval gates work.
- Four skills:
angle-scout,weekly-pack,performance-reviewandreply-drafts, each with inputs, a sequence, validation and a fixed return format. - Three routines: Monday angle scout, Thursday weekly-pack prep and Friday performance review. Each one has a time zone, an approval boundary and a rule for missing or stale data.
- Fixed reports: ANGLE REPORT (angles with links, your edge, hook draft, risk), PERFORMANCE REVIEW (depth per 1,000 impressions, top and bottom piece, next week's test) and REPLY DRAFTS.
- The same content pack blocks as the Content Factory Skill and Dot: SOURCE BRIEF, X THREAD, X POSTS, LINKEDIN POST, NEWSLETTER SECTION, VIDEO SCRIPT, RED NOTE, CALENDAR, OPEN ITEMS.
- The Notion "Content calendar" spec, so drafts land as rows with Status, Channel, Pack ID and Hook formula, ready for the Friday review.
Who it is for
- Founders and operators who post on X and LinkedIn and want to know what their niche is arguing about before they write.
- Newsletter writers who want a weekly loop: pick an angle, get drafts, see what worked.
- Anyone who already has a VOICE PROFILE from the Content Factory Skill and wants it used every week without reminding.
- Small teams where one person drafts and another approves: the Bot's approval gates match that split.
What it will not do
- Post, reply, quote, like, follow or DM on X. Every reply is a draft you post yourself.
- Create, edit or move anything in Notion without your approval. One yes per batch is enough.
- Copy other people's posts. It links them and learns from the pattern.
- Estimate numbers it cannot read. If X or Notion has no data, it asks you.
- Write without your VOICE PROFILE. It stops and asks instead of falling back to a generic voice.
- Pick a source for you. If you have not chosen one by Thursday, it asks once and waits.
Reseñas
Aún no hay reseñas.
Más Kits de Contenido

Kit de fábrica de contenido
De una pieza larga a una semana de posts con tu voz, programados en Notion y con revisión semanal.
Dot de fábrica de contenido
Tu dot mantiene lleno tu calendario de contenido en Notion y empaqueta cada entrevista que compartes.
Skill de fábrica de contenido
Convierte un artículo o transcripción en una semana de posts con tu voz, no con voz de IA.