ads-conciencia
Campaign awareness (conciencia de campaña). Tracks what Claude knows and does NOT know about the real business outcome of lead / WhatsApp / form / call campaigns — results the pixel can't see. Registers campaigns, runs dated check-ins asking the user how many real conversations, qualified leads, closed customers, revenue and junk contacts arrived, cross-references them with platform clicks/messages/spend, and computes the real close rate, cost per closed customer and junk rate. Writes conciencia-de-campana.md. Use when user says conciencia, did it work, closed customers, lead quality, junk leads, ¿me funcionó?, ¿me trajo clientes?, cerré clientes, llegaron mensajes, calidad de leads, leads basura, cuántos cerré.
Hainrixz · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Hainrixz/claude-ads --skill ads-concienciaAbout this skill
name: ads-conciencia description: "Campaign awareness (conciencia de campaña). Tracks what Claude knows and does NOT know about the real business outcome of lead / WhatsApp / form / call campaigns — results the pixel can't see. Registers campaigns, runs dated check-ins asking the user how many real conversations, qualified leads, closed customers, revenue and junk contacts arrived, cross-references them with platform clicks/messages/spend, and computes the real close rate, cost per closed customer and junk rate. Writes conciencia-de-campana.md. Use when user says conciencia, did it work, closed customers, lead quality, junk leads, ¿me funcionó?, ¿me trajo clientes?, cerré clientes, llegaron mensajes, calidad de leads, leads basura, cuántos cerré." user-invokable: false argument-hint: "[registrar | checkin | ver | lista]" allowed-tools: Bash, Read, Write, AskUserQuestion
Campaign awareness: what the platform can't see
Platforms count clicks and messages. Whether those messages turned into
customers — or were garbage — only the user knows. /ads conciencia makes
Claude explicitly aware of that gap: it stores the user's dated answers,
asks again on a schedule, and cross-references them with platform metrics to
compute the campaign's real success rate.
Storage (handled entirely by scripts/conciencia.py, never hand-edited):
- Source of truth:
~/.claude-ads/conciencia/<platform>-<campaign_id>.json(validates againstads/references/conciencia-schema.json). - Human view:
conciencia-de-campana.mdin the working folder (orconciencia-<platform>-<campaign_id>.mdwhen the folder tracks more than one campaign).
Formulas, thresholds and how to read the cross-reference live in
ads/references/conciencia.md. Load it before presenting results.
Core rules
- Profile first.
python3 scripts/profile.py get. Exit 2 → one-line tip to run/ads start, then continue inline. - Never assume a business outcome. Anything the user did not report is
nulland shows asN/Awith what is missing. Never write 0 for "didn't say". A ratio is only computed from check-ins where both sides were reported — the script already enforces this; don't recompute by hand. - Ask once, all together. Each check-in is ONE message with every
question. Whatever the user skips stays
null; say so in one line. - Cite the numbers. Every verdict names the figure that triggered it and how many check-ins it rests on: "tasa de cierre 11.8 % (10 cerrados / 85 conversaciones, 2 check-ins)".
- E-commerce with purchase pixel doesn't need this. The platform already sees the sale.
Subcommand routing
| Arg | Behavior |
|---|---|
| (none) | If conciencia.py due lists overdue campaigns → Check-in. Else if no campaigns → Register. Else → ver for the most recently updated. |
registrar | Phase 2 — register one or more campaigns. |
checkin | Phase 3 — check-in (all overdue, or the one the user names). |
ver [<key>] | Phase 4 — cross-reference + render, no questions. |
lista | python3 scripts/conciencia.py list → short table: name, status, check-ins, close rate, next check-in. |
Phase 1 — Does awareness apply?
Read context.industry and context.primary_goal from the profile (or the
campaign the user names).
industry = ecommerceand conversion is a pixel purchase → tell the user in one line that the pixel already tracks the sale, so this isn't needed. Proceed only if they insist (register with--channel pixel_purchase; such campaigns are never flagged as due).- Objective is leads / messages / calls / forms, or the close happens on WhatsApp, Messenger, IG DM, a form or a phone call → it applies. Continue.
Phase 2 — Register
- Look for campaigns to offer: latest
*-audit-results.jsonin cwd, then~/.claude-ads/history/index.json. Audit JSON hasaccount_id; campaign names / IDs come from the audit'sevidenceor the platform data pulled in the audit (MCP /scripts/api/<platform>_fetch.py/ export). If none found, ask the user. - Ask ONCE for everything missing: which campaigns, conversion channel (WhatsApp / Messenger / IG DM / form / call / landing), average ticket value and currency (optional — unlocks estimated ROAS), how often to check in (default 7 days).
- For each campaign:
python3 scripts/conciencia.py register --platform meta --campaign-id 120210000000001 \
--name "WhatsApp Clínica" --objective messages --channel whatsapp \
--ticket-value 2400 --currency MXN --every 7
- Record what the audit already established as known facts, with source:
python3 scripts/conciencia.py know meta-120210000000001 \
--fact "CPL de plataforma 52 MXN (auditoría 2026-10-20)" --source audit
- Go straight into a first check-in (Phase 3) if the campaign has been running ≥7 days; otherwise tell the user when Claude will ask.
Phase 3 — Check-in
- Platform side — pull spend, clicks and messages/leads for the period
since the last check-in, using the saved tier in
connections.<platform>.tier: MCP →scripts/api/<platform>_fetch.py→ ask for an export / screenshot. Record which one insource_of_platform_metrics. If nothing is available, leave the block null and say so — never estimate. - Business side — one message, all questions:
Read the complete source ↗Sobre , del al (la plataforma contó mensajes):
- ¿Cuántas conversaciones reales te llegaron?
- ¿Cuántas eran gente con intención real (calificados)?
- ¿Cuántos clientes cerraste?
- ¿Cuánto ingreso generaron? (opcional)
- ¿Cuántos fueron basura — spam, fuera de zona, no contestan?
- ¿Algo que notaste? (p. ej. "preguntan precio y desaparecen")
Lo que no sepas, sáltalo: queda como N/A, no