Respuesta rápida
- Qué es
- manychat-ig-lead-magnet es una skill de Single Grain (licencia MIT) que le enseña a Claude a armar el circuito «comenta la palabra y te lo mando» de Instagram en ManyChat, con palabras clave, seguimiento y aprobación antes de activar.
- Qué le das
- El recurso a regalar (PDF, enlace o video del que sale), el post o reel donde va, tu cuenta de ManyChat y, si pides correo, tu newsletter
- Qué te devuelve
- La palabra clave y sus variantes, las etiquetas de seguimiento, los mensajes del DM, la automatización armada en ManyChat y una lista de verificación
- Licencia
- MIT
- Repositorio
- ericosiu/ai-marketing-skills
- En GitHub
- 3,8 mil estrellas · actualizada el
- Revisada por Claura
Instálala en una línea para todos tus proyectos, en Claude Code, Cursor, Codex y más:
npx skills add ericosiu/ai-marketing-skills --skill manychat-ig-lead-magnet -g
Funciona en
~/.claude/skills/~/.agents/skills/~/.agents/skills/Pedidos para probarla
Con la skill instalada, copia uno y pégaselo a tu agente tal cual, o cambia los datos por los tuyos.
Arma el circuito «comenta GUÍA y te la mando» para regalar mi PDF de recetas sin gluten desde un reel, con los mensajes de ManyChat.
Revisa mi automatización de ManyChat antes de activarla: palabra clave, mensaje de bienvenida y seguimiento si no abren el enlace.
Quiero pedir el correo antes de entregar el recurso, pero sin perder a los que solo quieren el enlace. ¿Cómo lo armo?
#Qué hace
manychat-ig-lead-magnet es una skill de Single Grain, la agencia de Eric Siu (licencia MIT), que le enseña a Claude a armar de punta a punta el circuito de Instagram que más usan las marcas para conseguir contactos: «comenta la palabra y te lo mando por DM», montado en ManyChat.
Cubre cinco partes:
- El recurso. Un PDF, una página o un enlace público (incluso una skill de GitHub). Si es PDF, verifica que pese menos de 25 MB para subirlo directo a ManyChat, que abra y que no tenga nada interno, y suma al final los enlaces de tus servicios con parámetros de campaña.
- La palabra clave. Una principal de 1 a 3 palabras, fácil de escribir al escucharla en un reel y atada a la promesa, más 2 a 4 variantes (corta, larga y algún error de tipeo probable). Te marca las que no debes usar por genéricas: «IA», «SEO», «GRATIS», «PDF» o «AYUDA» sueltas disparan el flujo con comentarios que no tienen nada que ver.
- El seguimiento. Antes de entregar el recurso, aplica una etiqueta por recurso y campos con la palabra usada y el origen, para medir comentarios, conversaciones iniciadas, entregas, correos capturados y clics.
- La automatización en ManyChat. Como ManyChat se configura desde su pantalla, la arma manejando el navegador: busca una automatización que ya funciona, la duplica en vez de tocar la original, le pone un nombre claro, carga el disparador del post y las palabras, escribe el mensaje y adjunta el recurso.
- La captura de correo. Por defecto pide suscribirse a la newsletter con un sí explícito y un correo válido, y no entrega el recurso si la persona dice que no o si la suscripción no se confirma. Nunca reactiva a alguien que se dio de baja.
Lo más valioso es su disciplina: pide tu aprobación antes de subir el recurso, publicar o activar cualquier cosa en vivo, distingue «guardado» de «activo» y, al final, te dice qué preparó, qué cambió de verdad y qué verificó.
#Cómo aplicarla a tu negocio
Piensa en una contadora de Buenos Aires que publica reels sobre impuestos para monotributistas. Cada vez que dice «comenta GUÍA y te mando el PDF» termina respondiendo a mano cientos de comentarios durante dos días.
Así lo resuelve con la skill:
- Arma el recurso. Le pasa a Claude la transcripción de su reel más visto y su manual de marca. Sale un PDF de 8 páginas con el calendario de vencimientos del año y, al final, el enlace para agendar una consulta con parámetros de campaña.
- Elige la palabra. La skill descarta «GUÍA» por genérica y propone «VENCIMIENTOS» como principal, con «VENCE» y «CALENDARIO» como variantes.
- Define cómo medirlo. Etiqueta del recurso y campos con la palabra y el origen, así después sabe cuántos comentaron, cuántos recibieron el PDF y cuántos agendaron.
- Monta la automatización. Claude abre ManyChat, duplica su flujo de comentarios que ya funcionaba, lo renombra, conecta el reel nuevo, carga las palabras y adjunta el PDF. Como ella no usa newsletter, le pidió al empezar que entregue el recurso sin pedir correo.
- Aprueba y prueba. Recibe el resumen («automatización, reel, palabras, PDF, etiquetas»), lo aprueba y hace un comentario de prueba desde otra cuenta antes de publicar el reel.
La próxima vez que diga la palabra en un video, los mensajes salen solos y cada contacto queda etiquetado. Para más herramientas del tema, mira las skills de Claude para Instagram.
#Cómo instalarla
Es una skill agent-agnostic: el mismo SKILL.md corre en cualquier agente, pero necesita uno que pueda manejar el navegador para configurar ManyChat.
- Con una línea, para cualquier agente:
npx skills add ericosiu/ai-marketing-skills --skill manychat-ig-lead-magnet -gla deja instalada en todos tus proyectos. - A mano: copia la carpeta
manychat-ig-lead-magnet/del repo, con sus carpetasreferences/yagents/, a~/.claude/skills/para Claude Code, o a~/.agents/skills/para Cursor, Codex y Gemini CLI (las tres leen esa carpeta). - App de Claude: comprime la carpeta en un ZIP y súbela desde Customize, Skills, «Upload a skill».
Necesitas una cuenta de ManyChat conectada a tu Instagram y, si pides correo, tu newsletter conectada. El SKILL.md completo (con la licencia MIT y la fuente) está más abajo.
El SKILL.md completo
Skill original de Single Grain (Eric Siu) (MIT). Fuente: github.com/ericosiu/ai-marketing-skills/tree/main/manychat-ig-lead-magnet.
El archivo original está en inglés y va tal cual, sin traducir. Lo de arriba de esta ficha es el resumen en español: qué hace, cómo aplicarla y cómo instalarla.
Leer el archivo (193 líneas)
ManyChat IG Lead Magnet
Version and telemetry
From the repository root, run python3 telemetry/version_check.py to inspect the available version. Follow telemetry/README.md only within the user's existing telemetry choice; never opt them in automatically. This procedure contains no background collector. Log only anonymous skill name/version/outcome through the existing opt-in mechanism, never lead identities, evidence, messages or credentials.
Quick Start
Use this skill to produce the full lead magnet path:
- Identify the source asset, offer, target Instagram post/reel, trigger keywords, and desired follower experience.
- Create or locate the approved resource with an available PDF/page builder; identify its audience, format and delivery promise.
- Read
references/email-and-story-checklist.mdfor the required-newsletter-signup, Story-reply, and Beehiiv/CRM contract. Confirm the requested resource opens and contains no private/internal-only content. For a PDF attachment, verify the file is under 25 MB. For a GitHub skill, deliver its exact public directory link; do not substitute an interactive tool. - Prepare or edit the ManyChat automation from a known working Instagram comment template.
- Generate the keyword set, tracking fields/tags, DM copy, email capture copy, attachment plan, preview/test plan, and saved/update checklist.
- Stop for explicit approval before sending Slack messages, publishing hosted pages, updating live ManyChat flows, or enabling anything external-facing.
For Jev-backed independent client, partnership, sponsorship, M&A and recruiting tiers and approved S-tier Slack alerts, read references/lead-fit-and-routing.md. Unknown is distinct from D; hiring decisions and external outreach remain human-controlled.
For sanitized lessons from the recorded workflow and UI anchors, read references/captured-workflow.md. For the launch packet shape, read references/launch-packet-template.md.
Intake
Default: explicit newsletter opt-in and verified signup to the intended Beehiiv publication are required before resource delivery. No resource on decline, invalid email, pending confirmation or failed signup. Disclose the condition before collection; never silently reactivate unsubscribed contacts. Verify the exact live rollout separately.
Collect or infer:
- Source asset: URL, transcript, file, post, or Slack/Hermes thread.
- Resource type: PDF, landing page, hosted download, existing file, or direct GitHub skill link.
- Brand/design system: use the user-supplied design file or the approved project profile.
- Resource name and promise: concise, follower-facing title.
- Instagram target: exact post/reel/account; separately identify any promoted Story and its direct-reply trigger. A reshare does not inherit the post trigger.
- Comment keywords: include likely misspellings or variants if the user wants them.
- Delivery path: disclose newsletter requirement → affirmative consent + valid stored email → verified subscribed status → resource. Review changes from any prior no-gate or optional-consent promise.
- CTA block: products/services/channels to include at the end of the resource.
If any of these are missing, make a reasonable draft and mark the open field. Ask only when the missing item blocks execution or would risk editing the wrong live automation.
Build The Resource
When creating a PDF/resource:
- Use an available approved resource builder; do not assume a private companion skill is installed.
- Prefer ManyChat native PDF upload when the file is under 25 MB.
- Use hosting only if the file is over 25 MB, the user wants a landing page, or tracking requires web analytics outside ManyChat.
- Include CTA links with campaign tracking parameters inside the PDF when a campaign slug is known.
Useful default resource prompt:
Using the supplied brand design markdown and the source asset below, create a downloadable PDF resource for people who opt in from Instagram. Make it useful for a general marketer/operator, include the key takeaways, add a CTA section at the end, and keep the PDF under 25 MB.
Keyword Selection
Generate one primary keyword and 2-4 backups.
Primary keyword rules:
- 1-3 words.
- Easy to spell from hearing it in a Reel.
- Distinct enough to avoid accidental triggers.
- Closely tied to the resource promise.
- Not so generic that unrelated comments trigger it.
Backup keyword rules:
- Include a short version, a long version, and one likely typo only when useful.
- Avoid broad terms like
AI,SEO,FREE,PDF, orHELPas standalone triggers. - Prefer phrase keywords for generic topics:
AEO MAPbeatsAEO;HERMES GUIDEbeatsHERMES.
Output format:
Primary: <keyword>
Backups: <keyword>, <keyword>, <keyword>
Do not use: <too broad keywords>
Reasoning: <one sentence>
Tracking
When preparing the ManyChat flow, include tracking actions before the PDF delivery step:
- Apply tag:
lm_<resource_slug>. - Set custom field if available:
lead_magnet_slug = <resource_slug>. - Set custom field if available:
ig_comment_keyword = <primary_keyword>. - Add source label if available:
instagram_manychat. - If email is captured, mark:
email_capture_resource = <resource_slug>.
Track:
- Instagram comments using the keyword.
- ManyChat automation starts.
- DM delivery/sent rate.
- Email capture completion rate if used.
- PDF delivered/upload step completion.
- Replies after delivery.
- CTA link clicks from tracked PDF URLs where available.
Do not create or modify custom fields/tags in a live account without approval. If they do not exist, include them in the launch packet as requested tracking setup.
ManyChat Setup
Use Browser or Computer Use for ManyChat because the workflow is UI-driven.
- Open ManyChat and sign in. If Facebook/Instagram reconnect or passkey approval appears, ask the user to complete authentication.
- Navigate to
Automation. - Check
Keywords,Basic, and thenMy Automationsif needed to locate the right existing automation. - Search for a known working base automation, such as a newsletter or existing Instagram comment automation.
- Duplicate the base automation rather than editing the original.
- Open the copied automation and rename it to a clear pattern, such as
[RESOURCE] COMMENT INSTAGRAM. - Configure the Instagram comment trigger:
- Select the correct post/reel if the flow is post-specific.
- Add the trigger keywords, one at a time.
- Include common variants, spacing/capitalization, or misspellings only if the user wants broad matching.
- Edit the immediate public/comment response only if needed.
- Add or verify tracking actions:
- Apply the resource tag.
- Set resource slug and keyword custom fields when available.
- Keep tracking before the PDF delivery step.
- Edit the DM sequence:
- Acknowledge the opt-in.
- After the platform-required opening button, explain that newsletter signup is required for the resource. Obtain explicit consent and a validated email, then verify subscribed status before delivery.
- Attach the PDF directly in ManyChat when under 25 MB.
- Insert a hosted link only when direct upload is not suitable.
- Keep the message natural and short.
- Name the newsletter and publication, explain unsubscribe rights and the resource condition, and provide explicit accept/decline. A comment or email alone is not consent. Decline ends without signup or resource; acceptance enters the verified signup path. Follow
references/email-and-story-checklist.md. - Save and verify the UI shows saved.
- Before pressing
Update, publishing, or enabling the live automation, confirm explicit approval covers the exact rollout. If it does not, show a concise confirmation summary and wait; if it does, proceed without asking again.
Account, Email Integration, and Launch Lessons
- Resolve the account before acting: compare ManyChat workspace ID, connected Instagram handle, and Zapier trigger payload page ID. OAuth display names and saved Zapier connection labels can differ. Resolve the current account mapping from an authorized project source; no account IDs are bundled.
- For email capture plus custom Zap actions, duplicate the working newsletter automation. The Quick Automation builder may not expose the required action controls.
- If a verified shared newsletter event exists, reuse it; otherwise prepare an authorized supported integration. Email capture alone does not invoke Zapier; each intended signup flow must explicitly fire the event after valid email input and newsletter consent.
- Inspect the existing shared Zap and bounded run history before claiming emails were lost or creating a replacement integration. Successful beehiiv API acceptance is distinct from final subscription status and email delivery.
- Before changing a shared email mapping, inspect consuming flows. Prefer validated System Email for new flows, but do not switch a shared Zap to that field when legacy flows leave it blank. Preserve compatible mapping or prepare a separately approved migration. Check the actual saved mapping after Continue and after publishing.
- Verify consent, System Email storage, signup status and delivery routing. No resource on decline, invalid email, failed signup or pending confirmation. Preserve existing legitimate consent; never silently reactivate an unsubscribed contact.
- Newsletter signup runs asynchronously. API/Zap acceptance is not subscribed status. Hold delivery until a supported readback or callback proves the intended email is subscribed. Pending double opt-in stays pending; do not bypass it. If status cannot be verified, hold the gate rather than pretending the signup completed.
- Inspection of live flow settings may require opening its editor. Explain that inspection is read-only and do not change fields or publish unrelated flows.
- Trigger Save can activate a copied trigger. Check its enabled state immediately. Treat content publication and trigger activation as separate states: Saved alone does not mean live.
- For an authorized replacement, publish the reviewed integration, stop the old competing trigger, publish the new content, enable its trigger, and read back both flows in the automation list. Verify account, any-post versus specific-post scope, keywords, event, and exact resource URL.
- Carry forward explicit authorization for the same rollout; do not repeatedly ask after approval. Stop only for a real new scope, access, or permission requirement. Finish agent-solvable verification before returning for a decision.
- If browser inspection returns only an image or screenshots fail, retry the surface and available read-only view. Report the observed access failure; do not assume the Mac is locked. Never infer publication success from a click alone.
- Report verification precisely: draft saved, published content, enabled trigger, successful Zap run, and full Instagram-to-beehiiv signup are different evidence levels. Never call configuration checks an end-to-end test. Keep the local review page current with the actual live state.
Approval Gate
Require explicit approval before any external-facing or production-changing action:
- Sending a Slack/Gmail message or prompt to another live assistant.
- Uploading a PDF into a live ManyChat flow.
- Uploading, publishing, or replacing a hosted public resource.
- Updating, enabling, or publishing a ManyChat automation.
- Connecting/reconnecting Facebook or Instagram accounts if it changes permissions.
- Changing the Instagram post/reel trigger on a live automation.
Use this approval format:
Approve ManyChat update: [automation name] for [IG account/post or reel] with keywords [keywords], uploading [PDF filename], with tracking [tag/custom fields].
Verification
Before reporting done, verify:
- Resource exists and opens.
- PDF is under 25 MB if attached inside ManyChat.
- PDF upload target is under 25 MB.
- Public download link does not require login if using a link instead of PDF upload.
- Automation name matches the resource.
- Trigger keywords are present.
- Tracking tag/custom fields are present or listed as setup requests.
- DM copy references the correct resource.
- Email capture copy references the resource if email is requested.
- ManyChat shows saved, and the final live update has explicit user approval.
- Any live test uses a safe test comment/account or remains a dry run if approval was not given.
Final response should include what was prepared, what was actually changed, evidence checked, and any remaining approval needed.
Copiar el archivo tal cual
--- name: manychat-ig-lead-magnet description: Create or prepare Instagram comment-to-DM lead magnet workflows using a PDF, public resource link, or GitHub skill and ManyChat automation. Use when the user wants to turn a source asset such as a YouTube video, podcast, post, Slack/Hermes output, or existing PDF into a lead magnet, choose the right comment keyword(s), upload the PDF into ManyChat, add tracking tags/fields, QA the flow, and set it up so people can comment on an Instagram post/reel and receive the resource by DM or after an email capture. --- <!-- Skill original: manychat-ig-lead-magnet, de Single Grain (Eric Siu) (https://github.com/ericosiu/ai-marketing-skills/tree/main/manychat-ig-lead-magnet) Licencia: MIT. Reproducida con atribución según los términos de la licencia. Copia publicada en claura-ai.com/skills. --> # ManyChat IG Lead Magnet ## Version and telemetry From the repository root, run `python3 telemetry/version_check.py` to inspect the available version. Follow `telemetry/README.md` only within the user's existing telemetry choice; never opt them in automatically. This procedure contains no background collector. Log only anonymous skill name/version/outcome through the existing opt-in mechanism, never lead identities, evidence, messages or credentials. ## Quick Start Use this skill to produce the full lead magnet path: 1. Identify the source asset, offer, target Instagram post/reel, trigger keywords, and desired follower experience. 2. Create or locate the approved resource with an available PDF/page builder; identify its audience, format and delivery promise. 3. Read `references/email-and-story-checklist.md` for the required-newsletter-signup, Story-reply, and Beehiiv/CRM contract. Confirm the requested resource opens and contains no private/internal-only content. For a PDF attachment, verify the file is under 25 MB. For a GitHub skill, deliver its exact public directory link; do not substitute an interactive tool. 4. Prepare or edit the ManyChat automation from a known working Instagram comment template. 5. Generate the keyword set, tracking fields/tags, DM copy, email capture copy, attachment plan, preview/test plan, and saved/update checklist. 6. Stop for explicit approval before sending Slack messages, publishing hosted pages, updating live ManyChat flows, or enabling anything external-facing. For Jev-backed independent client, partnership, sponsorship, M&A and recruiting tiers and approved S-tier Slack alerts, read `references/lead-fit-and-routing.md`. Unknown is distinct from D; hiring decisions and external outreach remain human-controlled. For sanitized lessons from the recorded workflow and UI anchors, read `references/captured-workflow.md`. For the launch packet shape, read `references/launch-packet-template.md`. ## Intake Default: explicit newsletter opt-in and verified signup to the intended Beehiiv publication are required before resource delivery. No resource on decline, invalid email, pending confirmation or failed signup. Disclose the condition before collection; never silently reactivate unsubscribed contacts. Verify the exact live rollout separately. Collect or infer: - Source asset: URL, transcript, file, post, or Slack/Hermes thread. - Resource type: PDF, landing page, hosted download, existing file, or direct GitHub skill link. - Brand/design system: use the user-supplied design file or the approved project profile. - Resource name and promise: concise, follower-facing title. - Instagram target: exact post/reel/account; separately identify any promoted Story and its direct-reply trigger. A reshare does not inherit the post trigger. - Comment keywords: include likely misspellings or variants if the user wants them. - Delivery path: disclose newsletter requirement → affirmative consent + valid stored email → verified subscribed status → resource. Review changes from any prior no-gate or optional-consent promise. - CTA block: products/services/channels to include at the end of the resource. If any of these are missing, make a reasonable draft and mark the open field. Ask only when the missing item blocks execution or would risk editing the wrong live automation. ## Build The Resource When creating a PDF/resource: - Use an available approved resource builder; do not assume a private companion skill is installed. - Prefer ManyChat native PDF upload when the file is under 25 MB. - Use hosting only if the file is over 25 MB, the user wants a landing page, or tracking requires web analytics outside ManyChat. - Include CTA links with campaign tracking parameters inside the PDF when a campaign slug is known. Useful default resource prompt: ```text Using the supplied brand design markdown and the source asset below, create a downloadable PDF resource for people who opt in from Instagram. Make it useful for a general marketer/operator, include the key takeaways, add a CTA section at the end, and keep the PDF under 25 MB. ``` ## Keyword Selection Generate one primary keyword and 2-4 backups. Primary keyword rules: - 1-3 words. - Easy to spell from hearing it in a Reel. - Distinct enough to avoid accidental triggers. - Closely tied to the resource promise. - Not so generic that unrelated comments trigger it. Backup keyword rules: - Include a short version, a long version, and one likely typo only when useful. - Avoid broad terms like `AI`, `SEO`, `FREE`, `PDF`, or `HELP` as standalone triggers. - Prefer phrase keywords for generic topics: `AEO MAP` beats `AEO`; `HERMES GUIDE` beats `HERMES`. Output format: ```text Primary: <keyword> Backups: <keyword>, <keyword>, <keyword> Do not use: <too broad keywords> Reasoning: <one sentence> ``` ## Tracking When preparing the ManyChat flow, include tracking actions before the PDF delivery step: - Apply tag: `lm_<resource_slug>`. - Set custom field if available: `lead_magnet_slug = <resource_slug>`. - Set custom field if available: `ig_comment_keyword = <primary_keyword>`. - Add source label if available: `instagram_manychat`. - If email is captured, mark: `email_capture_resource = <resource_slug>`. Track: - Instagram comments using the keyword. - ManyChat automation starts. - DM delivery/sent rate. - Email capture completion rate if used. - PDF delivered/upload step completion. - Replies after delivery. - CTA link clicks from tracked PDF URLs where available. Do not create or modify custom fields/tags in a live account without approval. If they do not exist, include them in the launch packet as requested tracking setup. ## ManyChat Setup Use Browser or Computer Use for ManyChat because the workflow is UI-driven. 1. Open ManyChat and sign in. If Facebook/Instagram reconnect or passkey approval appears, ask the user to complete authentication. 2. Navigate to `Automation`. 3. Check `Keywords`, `Basic`, and then `My Automations` if needed to locate the right existing automation. 4. Search for a known working base automation, such as a newsletter or existing Instagram comment automation. 5. Duplicate the base automation rather than editing the original. 6. Open the copied automation and rename it to a clear pattern, such as `[RESOURCE] COMMENT INSTAGRAM`. 7. Configure the Instagram comment trigger: - Select the correct post/reel if the flow is post-specific. - Add the trigger keywords, one at a time. - Include common variants, spacing/capitalization, or misspellings only if the user wants broad matching. 8. Edit the immediate public/comment response only if needed. 9. Add or verify tracking actions: - Apply the resource tag. - Set resource slug and keyword custom fields when available. - Keep tracking before the PDF delivery step. 10. Edit the DM sequence: - Acknowledge the opt-in. - After the platform-required opening button, explain that newsletter signup is required for the resource. Obtain explicit consent and a validated email, then verify subscribed status before delivery. - Attach the PDF directly in ManyChat when under 25 MB. - Insert a hosted link only when direct upload is not suitable. - Keep the message natural and short. 11. Name the newsletter and publication, explain unsubscribe rights and the resource condition, and provide explicit accept/decline. A comment or email alone is not consent. Decline ends without signup or resource; acceptance enters the verified signup path. Follow `references/email-and-story-checklist.md`. 12. Save and verify the UI shows saved. 13. Before pressing `Update`, publishing, or enabling the live automation, confirm explicit approval covers the exact rollout. If it does not, show a concise confirmation summary and wait; if it does, proceed without asking again. ## Account, Email Integration, and Launch Lessons - Resolve the account before acting: compare ManyChat workspace ID, connected Instagram handle, and Zapier trigger payload page ID. OAuth display names and saved Zapier connection labels can differ. Resolve the current account mapping from an authorized project source; no account IDs are bundled. - For email capture plus custom Zap actions, duplicate the working newsletter automation. The Quick Automation builder may not expose the required action controls. - If a verified shared newsletter event exists, reuse it; otherwise prepare an authorized supported integration. Email capture alone does not invoke Zapier; each intended signup flow must explicitly fire the event after valid email input and newsletter consent. - Inspect the existing shared Zap and bounded run history before claiming emails were lost or creating a replacement integration. Successful beehiiv API acceptance is distinct from final subscription status and email delivery. - Before changing a shared email mapping, inspect consuming flows. Prefer validated System Email for new flows, but do not switch a shared Zap to that field when legacy flows leave it blank. Preserve compatible mapping or prepare a separately approved migration. Check the actual saved mapping after Continue and after publishing. - Verify consent, System Email storage, signup status and delivery routing. No resource on decline, invalid email, failed signup or pending confirmation. Preserve existing legitimate consent; never silently reactivate an unsubscribed contact. - Newsletter signup runs asynchronously. API/Zap acceptance is not subscribed status. Hold delivery until a supported readback or callback proves the intended email is subscribed. Pending double opt-in stays pending; do not bypass it. If status cannot be verified, hold the gate rather than pretending the signup completed. - Inspection of live flow settings may require opening its editor. Explain that inspection is read-only and do not change fields or publish unrelated flows. - Trigger Save can activate a copied trigger. Check its enabled state immediately. Treat content publication and trigger activation as separate states: Saved alone does not mean live. - For an authorized replacement, publish the reviewed integration, stop the old competing trigger, publish the new content, enable its trigger, and read back both flows in the automation list. Verify account, any-post versus specific-post scope, keywords, event, and exact resource URL. - Carry forward explicit authorization for the same rollout; do not repeatedly ask after approval. Stop only for a real new scope, access, or permission requirement. Finish agent-solvable verification before returning for a decision. - If browser inspection returns only an image or screenshots fail, retry the surface and available read-only view. Report the observed access failure; do not assume the Mac is locked. Never infer publication success from a click alone. - Report verification precisely: draft saved, published content, enabled trigger, successful Zap run, and full Instagram-to-beehiiv signup are different evidence levels. Never call configuration checks an end-to-end test. Keep the local review page current with the actual live state. ## Approval Gate Require explicit approval before any external-facing or production-changing action: - Sending a Slack/Gmail message or prompt to another live assistant. - Uploading a PDF into a live ManyChat flow. - Uploading, publishing, or replacing a hosted public resource. - Updating, enabling, or publishing a ManyChat automation. - Connecting/reconnecting Facebook or Instagram accounts if it changes permissions. - Changing the Instagram post/reel trigger on a live automation. Use this approval format: ```text Approve ManyChat update: [automation name] for [IG account/post or reel] with keywords [keywords], uploading [PDF filename], with tracking [tag/custom fields]. ``` ## Verification Before reporting done, verify: - Resource exists and opens. - PDF is under 25 MB if attached inside ManyChat. - PDF upload target is under 25 MB. - Public download link does not require login if using a link instead of PDF upload. - Automation name matches the resource. - Trigger keywords are present. - Tracking tag/custom fields are present or listed as setup requests. - DM copy references the correct resource. - Email capture copy references the resource if email is requested. - ManyChat shows saved, and the final live update has explicit user approval. - Any live test uses a safe test comment/account or remains a dry run if approval was not given. Final response should include what was prepared, what was actually changed, evidence checked, and any remaining approval needed.
Preguntas frecuentes sobre la skill manychat-ig-lead-magnet
¿Qué es la skill manychat-ig-lead-magnet y para qué sirve?
manychat-ig-lead-magnet es una skill de Single Grain, la agencia de Eric Siu (github.com/ericosiu/ai-marketing-skills, licencia MIT), que arma el circuito en el que alguien comenta una palabra en tu post o reel y recibe un recurso por mensaje directo. Prepara el recurso, elige la palabra clave y sus variantes, define las etiquetas para medir, escribe los mensajes y configura la automatización en ManyChat, frenando para pedir tu aprobación antes de cualquier cambio en vivo.
¿Cómo la aplico a mi negocio?
Le das el recurso que quieres regalar (o el video del que sale), el post donde va y tu cuenta de ManyChat. Te propone una palabra principal fácil de escribir al oírla en un reel, de 2 a 4 variantes, y te dice cuáles evitar por genéricas. Después duplica una automatización que ya funciona en tu cuenta, la adapta, la guarda y te muestra un resumen para aprobar antes de activarla. Si quieres ver qué hacer con quienes escriben, lee sobre los mensajes de Instagram que quedan sin contestar.
¿Qué necesito para usarla?
Una cuenta de ManyChat conectada a tu Instagram y un agente que pueda manejar el navegador (en Claude Code, con su herramienta de navegador o de uso de la computadora), porque ManyChat se configura desde su pantalla. Si quieres pedir el correo, una newsletter (la skill viene pensada para Beehiiv, a través de Zapier). Tú inicias sesión: la skill te pide que completes cualquier ingreso o reconexión.
¿Sirve para una marca hispanohablante?
Sí. Las reglas de la palabra clave, del seguimiento y de la verificación no dependen del idioma; le pides los mensajes en español. Ten en cuenta dos cosas: viene del flujo interno de una agencia, así que menciona herramientas propias de ellos que puedes ignorar, y por defecto exige suscribirse a la newsletter con consentimiento explícito antes de entregar el recurso. Si prefieres entregar sin pedir correo, díselo al empezar.
Más skills de Redes sociales

social-captions: captions con IA que enganchan (skill de Claura)
Escribe captions con IA para Instagram y TikTok: hook, cuerpo con ritmo, una sola ask y hashtags, con la voz de tu marca.

ig-carousel-planner: planificar carruseles de Instagram
Planifica un carrusel de Instagram lámina por lámina: elige la fórmula según el objetivo, escribe el texto de cada imagen y el caption, y deja la última lámina lista para que la guarden.

ig-hook-extractor: descifrar el hook de un viral
Desarma el gancho de un reel o carrusel viral de Instagram: qué fórmula usa, por qué funcionó, qué buscaba y una plantilla en blanco para tu tema.
Para seguir con este tema
- Guía de Claude e IA para marketingEl orden para empezar y las notas de este tema.Guía
- Skills de Claude y ChatGPT para InstagramLas skills de Claude para Instagram: perfil, reels, reels de prueba, ganchos, captions y mensajes automáticos con ManyChat. Cómo usarlas en Claude y en ChatGPT.Skill
- CRM con agentes de IA para Instagram: no dejes DMs sin contestarArmá el patrón comentario a DM a CRM con un agente de IA que responde, califica y escala a un humano tus DMs de Instagram. Ningún lead queda sin contestar.Nota
AI KID
RE/MAX Patagon
Mateo Caño