@roilab/crm-cli 0.1.0 → 0.6.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.
Files changed (69) hide show
  1. package/CHANGELOG.md +195 -25
  2. package/SKILL.md +256 -7
  3. package/SURFACE.txt +237 -69
  4. package/dist/bin/crm.js +28 -2
  5. package/dist/bin/crm.js.map +1 -1
  6. package/dist/src/commands/access.js +104 -0
  7. package/dist/src/commands/access.js.map +1 -0
  8. package/dist/src/commands/brief.js +52 -0
  9. package/dist/src/commands/brief.js.map +1 -0
  10. package/dist/src/commands/chat.js +220 -0
  11. package/dist/src/commands/chat.js.map +1 -0
  12. package/dist/src/commands/commands.js +89 -0
  13. package/dist/src/commands/commands.js.map +1 -0
  14. package/dist/src/commands/comment.js +1 -0
  15. package/dist/src/commands/comment.js.map +1 -1
  16. package/dist/src/commands/generic.js +335 -5
  17. package/dist/src/commands/generic.js.map +1 -1
  18. package/dist/src/commands/integrations.js +236 -0
  19. package/dist/src/commands/integrations.js.map +1 -0
  20. package/dist/src/commands/mention.js +139 -0
  21. package/dist/src/commands/mention.js.map +1 -0
  22. package/dist/src/commands/options.js +21 -1
  23. package/dist/src/commands/options.js.map +1 -1
  24. package/dist/src/commands/rank.js +300 -0
  25. package/dist/src/commands/rank.js.map +1 -0
  26. package/dist/src/commands/report.js +209 -0
  27. package/dist/src/commands/report.js.map +1 -0
  28. package/dist/src/commands/review.js +136 -0
  29. package/dist/src/commands/review.js.map +1 -1
  30. package/dist/src/commands/skill.js +1005 -0
  31. package/dist/src/commands/skill.js.map +1 -0
  32. package/dist/src/commands/task.js +298 -4
  33. package/dist/src/commands/task.js.map +1 -1
  34. package/dist/src/commands/time.js +242 -0
  35. package/dist/src/commands/time.js.map +1 -0
  36. package/dist/src/lib/skillBundles.js +84 -0
  37. package/dist/src/lib/skillBundles.js.map +1 -0
  38. package/dist/src/lib/skillManifest.js +77 -0
  39. package/dist/src/lib/skillManifest.js.map +1 -0
  40. package/dist/src/lib/skillSidecar.js +69 -0
  41. package/dist/src/lib/skillSidecar.js.map +1 -0
  42. package/dist/src/lib/skillWriter.js +162 -0
  43. package/dist/src/lib/skillWriter.js.map +1 -0
  44. package/dist/src/transport/envelope.js +12 -2
  45. package/dist/src/transport/envelope.js.map +1 -1
  46. package/dist/src/transport/http.js +27 -0
  47. package/dist/src/transport/http.js.map +1 -1
  48. package/dist/src/transport/run.js +6 -0
  49. package/dist/src/transport/run.js.map +1 -1
  50. package/dist/src/types.js.map +1 -1
  51. package/dist/src/utils/server-nudge.js +57 -0
  52. package/dist/src/utils/server-nudge.js.map +1 -0
  53. package/dist/src/utils/version-check.js +68 -0
  54. package/dist/src/utils/version-check.js.map +1 -1
  55. package/package.json +58 -57
  56. package/skill-bundles/tools/ahrefs-tool/SKILL.md +134 -0
  57. package/skill-bundles/tools/brightlocal-tool/SKILL.md +154 -0
  58. package/skill-bundles/tools/dataforseo-tool/SKILL.md +118 -0
  59. package/skill-bundles/tools/google-analytics-tool/SKILL.md +143 -0
  60. package/skill-bundles/tools/google-search-console-tool/SKILL.md +133 -0
  61. package/skill-bundles/tools/local-falcon-tool/SKILL.md +142 -0
  62. package/skill-bundles/tools/localseodata-tool/SKILL.md +388 -0
  63. package/skill-bundles/tools/lsa-spy-tool/SKILL.md +113 -0
  64. package/skill-bundles/tools/screaming-frog-tool/SKILL.md +166 -0
  65. package/skill-bundles/tools/semrush-tool/SKILL.md +121 -0
  66. package/skill-bundles/tools/serpapi-tool/SKILL.md +148 -0
  67. package/skill-bundles/tools/task-preflight/SKILL.md +149 -0
  68. package/skill-bundles/tools/tool-routing/SKILL.md +59 -0
  69. package/skill-bundles/tools/whitespark-tool/SKILL.md +129 -0
@@ -0,0 +1,149 @@
1
+ ---
2
+ name: task-preflight
3
+ description: Cómo interpretar la respuesta de `crm task preflight` antes de crear una tarea. Decisión rápida sobre duplicados, sobrecarga de dominio y profundización con datos de GSC/GA4 cuando hace falta. Cárgalo SÓLO si el envelope del preflight tiene `similarTasks` con score alto, `urlScopedTasks` no vacío, o vas a crear una tarea URL-scoped y dudas si ya existe.
4
+ when_to_use: "el preflight devolvió Posible duplicado", "urlScopedTasks no vacío", "openTaskCounts alto", "necesito profundizar con GSC/GA4 antes de crear", "la URL ya tenía un task pero está en done"
5
+ ---
6
+
7
+ # Task preflight — interpretación
8
+
9
+ `crm task preflight` se llama **antes** de cualquier `crm task create`. Este
10
+ skill explica cómo leer la respuesta sin volver a leerse cli/SKILL.md (que ya
11
+ te dijo el ritual). Cárgalo sólo si el envelope te deja en duda; en el 80% de
12
+ los casos los `hints[]` ya te dicen qué hacer.
13
+
14
+ ## Forma de la respuesta (recordatorio)
15
+
16
+ ```jsonc
17
+ {
18
+ "ok": true,
19
+ "data": {
20
+ "similarTasks": [ { id, title, status, score, sameDomain, when } ],
21
+ "recall": [ { type, id, when, score, snippet } ], // [] si no pasaste --url
22
+ "recentChanges": [ { id, url, occurredAt, note, types[] } ],
23
+ "urlScopedTasks": [ { id, title, status, when } ], // [] si no pasaste --url
24
+ "recentBacklinks": [ { id, sourceUrl, targetUrl, status, anchorText, when } ],
25
+ "openTaskCounts": { todo, doing, blocked, done } | null, // null si no pasaste --domain
26
+ "hints": [ "Posible duplicado: ...", ... ],
27
+ "meta": { title, url, domainId, sinceMs, limit }
28
+ },
29
+ "summary": "preflight: N similar · M recall · ..."
30
+ }
31
+ ```
32
+
33
+ ## Árbol de decisión
34
+
35
+ ```
36
+ similarTasks[0].score >= 0.55
37
+ ├── status ∈ {todo, doing, blocked}
38
+ │ → COMENTA en la existente (`crm comment create --task <id>`).
39
+ │ NO crees una nueva. Si tu trabajo es escope adicional, edita la
40
+ │ descripción con `crm task update <id> --description`.
41
+ │
42
+ └── status == done
43
+ → Pregunta: ¿es regresión?
44
+ - Sí: crea NUEVA citando la cerrada con `#[Title](id)` en la
45
+ descripción + `--kind decision` en un comentario explicando
46
+ por qué se reabre.
47
+ - No: es trabajo de seguimiento real → crea nueva con `#link`.
48
+
49
+ similarTasks[0].score ∈ [0.45, 0.55) y sameDomain == true
50
+ → Lectura rápida con `crm task get <id>`. Si el title coincide en >2/3
51
+ tokens, trátalo como duplicado fuerte (rama de arriba). Si no, sigue.
52
+
53
+ urlScopedTasks no vacío (sin importar similarTasks)
54
+ → La URL YA tiene KPIs ligados. Tu nueva tarea probablemente debería
55
+ enlazar a la misma propertyLink (mismo scope) en vez de duplicar la
56
+ medición. Mira `crm task get <id>` para ver el `keyMetric` y reusa.
57
+
58
+ openTaskCounts.todo + .doing + .blocked >= 8
59
+ → Dominio sobrecargado. Si el humano no pidió explícitamente "más",
60
+ responde con la cuenta y pregunta qué priorizar.
61
+
62
+ recentChanges contiene tu URL en los últimos 30 días con tipo coincidente
63
+ → Lo pediste pero ya se hizo. Lee el `note` y la lista de `types[]`. Si
64
+ coincide, NO crees — informa al humano con un resumen de lo que ya cambió.
65
+
66
+ Nada de lo de arriba aplica
67
+ → Adelante con `crm task create`. Pasa `#[Title](id)` referenciando los
68
+ `recall` o `urlScopedTasks` si son tangenciales pero útiles.
69
+ ```
70
+
71
+ ## Cuándo cargar datos vivos (después del preflight, no antes)
72
+
73
+ Si decides crear pero tu propuesta de KPI no es obvia, **entonces** carga la
74
+ vista en vivo — no antes:
75
+
76
+ | Necesitas... | Comando | Coste |
77
+ |---|---|---|
78
+ | Clicks/impresiones/CTR/posición agregados del dominio | `crm domain metrics dom_xyz --start … --end …` | Tinybird, ~50ms, sin cuota |
79
+ | Mismo, filtrado a una URL | `crm gsc query --property prop_X --dimension page --filters "page=<url>"` | live GSC + queryPageCache 6h, cuenta cuota GSC en miss |
80
+ | Tráfico/conversiones por URL | `crm ga4 query --property prop_X --filters "pagePath=<url>"` | live GA4, cuenta cuota |
81
+ | Backlinks/anchors actuales hacia la URL | `crm backlink list --domain dom_xyz --target-url <url>` | Convex, gratis |
82
+
83
+ Regla: **el preflight es Convex puro (gratis). Tinybird es barato. GSC/GA4
84
+ live cuestan cuota — sólo si hay decisión real que tomar.**
85
+
86
+ ## Qué no pre-crawlees
87
+
88
+ - **Nunca** lances Screaming Frog para entender una URL puntual. Si necesitas
89
+ ver el HTML, usa `WebFetch` (1 GET, sin cuota). SF se justifica cuando la
90
+ tarea es "audita el sitio entero", no antes de crear cada tarea.
91
+ - **No corras `crm gsc query` para todas las páginas del dominio** sólo para
92
+ "tener contexto". Eso quema cuota. Si necesitas un overview, ya tienes
93
+ `crm domain metrics`.
94
+
95
+ ## Anti-patrones
96
+
97
+ - **Pasar `--title` con palabras de relleno** ("Hacer cosa en pricing").
98
+ Hace que `similarTasks` traiga ruido y los `hints` no detecten duplicados.
99
+ Usa el verbo + sustantivo + URL/sección como en la propia tarea final.
100
+ - **Ignorar `hints` y mirar sólo `similarTasks`.** Los hints están escritos
101
+ por el server con la lógica completa (recall + scoped + counts). Confía en
102
+ ellos.
103
+ - **Crear sin `--domain`.** Sin dominio, `openTaskCounts` queda en `null` y
104
+ `recentChanges` se restringe a coincidencias por URL. El preflight pierde
105
+ la mitad de su valor.
106
+ - **Llamar `crm recall` después del preflight "por si acaso".** El preflight
107
+ ya hace recall (con cap de 10 items en lugar de 50, pero suficiente). Sólo
108
+ llama `crm recall` directamente si necesitas más profundidad histórica
109
+ (ej. `--since-ms` mayor a 180 días).
110
+
111
+ ## Ejemplo de decisión (no ejecutar — sólo lectura)
112
+
113
+ ```bash
114
+ $ crm task preflight \
115
+ --title "Reescribir meta title /seo-tools" \
116
+ --url https://example.com/seo-tools \
117
+ --domain dom_abc \
118
+ --jq .data
119
+ ```
120
+
121
+ ```jsonc
122
+ {
123
+ "similarTasks": [
124
+ { "id": "tsk_x1", "title": "Optimizar meta title de /seo-tools",
125
+ "status": "done", "score": 0.78, "sameDomain": true,
126
+ "when": 1741..., "reviewRequired": false }
127
+ ],
128
+ "recall": [
129
+ { "type": "change", "id": "che_a", "when": 1741..., "score": 0.92,
130
+ "snippet": "meta_title: 'SEO Tools — guía 2026'" }
131
+ ],
132
+ "urlScopedTasks": [],
133
+ "recentChanges": [
134
+ { "id": "che_a", "url": ".../seo-tools", "occurredAt": "2026-04-12",
135
+ "types": ["meta_title"], "note": "rev2" }
136
+ ],
137
+ "openTaskCounts": { "todo": 3, "doing": 1, "blocked": 0, "done": 14 },
138
+ "hints": [
139
+ "Posible duplicado: \"Optimizar meta title de /seo-tools\" (estado: done). Revísala con `crm task get tsk_x1` antes de crear."
140
+ ]
141
+ }
142
+ ```
143
+
144
+ Lectura: el meta title ya se reescribió hace 3 semanas (`change` con `score`
145
+ muy alto y `recentChanges` confirma). La tarea original está en `done`. Si
146
+ estás aquí porque el humano dijo "está mal otra vez", esto es regresión →
147
+ crea nueva citando `#[Optimizar meta title de /seo-tools](tsk_x1)` y deja un
148
+ `--kind decision` explicando qué falla del rev2. Si no, NO crees — comenta
149
+ al humano la fecha del último cambio.
@@ -0,0 +1,59 @@
1
+ ---
2
+ name: tool-routing
3
+ description: Elige entre las herramientas externas de SEO local que tiene la agencia (Screaming Frog, Ahrefs, BrightLocal, LocalSEOData, Local Falcon, Semrush, SerpAPI, DataForSEO, Whitespark, LSA Spy, Google Search Console, Google Analytics). Úsalo cuando hay que decidir qué tool atacar una tarea antes de cargar el skill específico de esa herramienta.
4
+ when_to_use: "qué tool uso para X", "con qué herramienta audito Y", "¿Screaming Frog o Ahrefs?", "cuál es la mejor para citations", "qué tool tiene datos de backlinks", "tool para geogrid", "tool para reviews"
5
+ ---
6
+
7
+ # Tool Routing
8
+
9
+ Decide qué herramienta externa usar para cada tipo de tarea antes de cargar
10
+ el skill detallado. Cada fila de la tabla apunta al skill con la doc completa
11
+ de ese tool.
12
+
13
+ ## Matriz de decisión
14
+
15
+ | Necesitas | Tool primario | Skill a cargar | Alternativas |
16
+ |---|---|---|---|
17
+ | Decidir si crear una tarea (duplicados + recall + cargas) | `crm task preflight` | `task-preflight` | — (siempre primero, antes de cualquier task create) |
18
+ | Auditoría técnica de sitio (crawl completo) | Screaming Frog | `screaming-frog-tool` | Semrush site audit (ligero) |
19
+ | Análisis de páginas de ubicación a escala | Screaming Frog | `screaming-frog-tool` | — |
20
+ | Extracción custom (NAP, schema) | Screaming Frog | `screaming-frog-tool` | — |
21
+ | Backlinks / referring domains / link gap | Ahrefs | `ahrefs-tool` | LocalSEOData (`backlink_summary`, `backlink_gap`) para overviews rápidos |
22
+ | Anchor text / lost links | Ahrefs | `ahrefs-tool` | — |
23
+ | Auditoría de citations + NAP consistency | BrightLocal / LocalSEOData | `brightlocal-tool` / `localseodata-tool` | Whitespark (más profundo) |
24
+ | Descubrir listings desconocidos | LocalSEOData | `localseodata-tool` | — |
25
+ | Geogrid scan (rankings por geolocalización) | Local Falcon | `local-falcon-tool` | LocalSEOData `geogrid_scan` (one-off) |
26
+ | Auditoría integral en una llamada | LocalSEOData | `localseodata-tool` | — |
27
+ | Keyword research (volumen, dificultad, intent) | Semrush | `semrush-tool` | Ahrefs (secundario) |
28
+ | SERP snapshots / análisis de SERPs | SerpAPI | `serpapi-tool` | DataForSEO SERP |
29
+ | Datos crudos de Google (SERP + Ads) | DataForSEO | `dataforseo-tool` | SerpAPI (más simple) |
30
+ | Local Services Ads (LSA) ranking / precios | LSA Spy | `lsa-spy-tool` | — |
31
+ | Descubrimiento de directorios / data aggregators | Whitespark | `whitespark-tool` | BrightLocal |
32
+ | Performance orgánico (clicks, impresiones, queries) | Google Search Console | `google-search-console-tool` | — (única fuente de verdad) |
33
+ | Tráfico y conversiones | Google Analytics | `google-analytics-tool` | — (única opción) |
34
+ | Reviews (Google Maps) | LocalSEOData | `localseodata-tool` | BrightLocal |
35
+
36
+ ## Preguntas que el agente debería hacer antes de elegir
37
+
38
+ 1. ¿El usuario ya tiene exportado un CSV de alguna herramienta? → lo analizas tú, no hace falta tool nuevo.
39
+ 2. ¿Es monitoreo recurrente o análisis puntual? → monitoreo → LocalSEOData/Local Falcon; puntual → Screaming Frog / Ahrefs.
40
+ 3. ¿El cliente paga esa herramienta? Pregunta si no está claro — no asumas acceso.
41
+ 4. ¿Lo pide la agencia (IP interno) o es investigación pública? → para IP interno, GBP/GSC/GA4; para investigación, SerpAPI/DataForSEO.
42
+
43
+ ## Anti-patrones
44
+
45
+ - **No cargues varios tool-skills a la vez.** Cada uno trae una tabla "When to Use X vs Y" — si cargas ahrefs-tool + semrush-tool simultáneamente, duplicas contexto. Usa este skill para elegir, luego carga uno.
46
+ - **No inventes endpoints.** Si no hay skill cargado, dile al usuario que exporte el CSV y tú lo lees — es más realista que pretender una integración que no existe.
47
+ - **No recomiendes el tool de mayor precio por defecto.** Ahrefs + Semrush son caros. Si el cliente solo necesita un overview, LocalSEOData o GSC cubren el 80% gratis.
48
+
49
+ ## Workflow típico
50
+
51
+ ```
52
+ 1. Usuario: "Audítame el SEO local de cliente X"
53
+ 2. Agente: carga `tool-routing` (este skill)
54
+ 3. Agente: identifica qué subtareas componen la auditoría
55
+ 4. Agente: carga los 2-3 skills específicos necesarios
56
+ (ej. `local-seo-audit` como playbook + `localseodata-tool` + `screaming-frog-tool`)
57
+ 5. Agente: ejecuta la auditoría. Si un tool no está disponible, degrada
58
+ a la alternativa de la matriz arriba y avisa al usuario.
59
+ ```
@@ -0,0 +1,129 @@
1
+ ---
2
+ name: whitespark-tool
3
+ description: When the user wants citation gap analysis, managed citation building, review generation campaigns, or local rank tracking. Trigger on "Whitespark," "citation finder," "where are my competitors listed," "citation gap," "build citations," "review generation tool," or "get more reviews." Note that Whitespark does NOT have an MCP server — it's dashboard-driven with limited API.
4
+ ---
5
+
6
+ # Whitespark Tool
7
+
8
+ > **Note:** LocalSEOData (`localseodata-tool`) now covers citation audits via `citation_audit`. Use LocalSEOData as default for citation data. Whitespark remains the preferred tool for citation building and review generation campaigns (Reputation Builder).
9
+
10
+ Whitespark does NOT currently have an MCP server. It's primarily a dashboard tool with managed services. The agent's role is to guide what to do in Whitespark and interpret data the user provides from it.
11
+
12
+ ## When to Use Whitespark vs Other Tools
13
+
14
+ | You Need | Use Whitespark | Use Instead |
15
+ |----------|---------------|-------------|
16
+ | Citation gap analysis (competitor vs you) | ✅ Local Citation Finder | BrightLocal (also does this, has MCP) |
17
+ | Managed citation building (done-for-you) | ✅ Best quality service | BrightLocal (also offers this) |
18
+ | Review generation campaigns (email/SMS) | ✅ Reputation Builder | — |
19
+ | Review monitoring | ✅ | BrightLocal (has MCP, may be better for agent access) |
20
+ | Local rank tracking | ✅ | Local Falcon (geogrid is superior for local) |
21
+ | Citation accuracy audit | ⚠️ Can do it | BrightLocal (better for NAP accuracy scoring) |
22
+ | Keyword research | ❌ | Semrush, Ahrefs |
23
+ | Backlink analysis | ❌ | Ahrefs |
24
+ | Technical audit | ❌ | Screaming Frog |
25
+ | Geogrid rankings | ❌ | Local Falcon |
26
+
27
+ ## Whitespark vs BrightLocal
28
+
29
+ These two overlap significantly. Here's when to use which:
30
+
31
+ | Feature | Whitespark | BrightLocal |
32
+ |---------|-----------|-------------|
33
+ | Citation building quality | ✅ Higher quality (manual review) | Good but more automated |
34
+ | Citation gap finder | ✅ More thorough | ✅ Also good |
35
+ | NAP accuracy scoring | Basic | ✅ Better scoring system |
36
+ | MCP server available | ❌ No | ✅ Yes |
37
+ | Review generation | ✅ Reputation Builder | ✅ Also has this |
38
+ | White-label reports | Basic | ✅ Better reporting |
39
+ | Industry reputation | ✅ Citation specialists | ✅ All-in-one local SEO |
40
+ | Pricing | Per-service | Subscription |
41
+
42
+ **Recommendation:** If MCP connectivity matters (agent can pull data directly), use BrightLocal. If citation building quality is the priority and the user is willing to use the dashboard, Whitespark's managed service is excellent.
43
+
44
+ ## Core Workflows
45
+
46
+ ### Citation Gap Analysis
47
+
48
+ **When:** User wants to find directories where competitors are listed but they aren't.
49
+
50
+ **What to do in Whitespark:**
51
+ 1. Run Local Citation Finder for target business AND 2-3 competitors
52
+ 2. Compare citation sources across all businesses
53
+ 3. Identify directories where competitors appear but user doesn't
54
+
55
+ **What the agent can do:**
56
+ - Guide the user on which competitors to check
57
+ - Interpret the citation gap report when the user shares results
58
+ - Prioritize which directories to target first
59
+
60
+ **Citation priority framework:**
61
+ 1. **Tier 1** (must-have): Google, Apple, Bing, Yelp, Facebook, data aggregators
62
+ 2. **Tier 2** (important): Industry-specific directories (Healthgrades, Avvo, Angi, etc.)
63
+ 3. **Tier 3** (nice-to-have): Local directories, chamber of commerce, BBB
64
+ 4. **Tier 4** (low priority): General web directories, niche sites
65
+
66
+ ### Managed Citation Building
67
+
68
+ **When:** Citation gaps identified and user wants help building them.
69
+
70
+ **What Whitespark does:**
71
+ - Manual submission to directories (higher quality than automated tools)
72
+ - Verification that listings are live and accurate
73
+ - Ongoing maintenance options
74
+
75
+ **What to tell the user:**
76
+ 1. Provide exact NAP (must match GBP)
77
+ 2. Provide business description, categories, photos
78
+ 3. Specify target directories from the gap analysis
79
+ 4. Expect 2-4 week turnaround for most directories
80
+ 5. Re-audit in 6-8 weeks to verify everything is live and accurate
81
+
82
+ ### Review Generation (Reputation Builder)
83
+
84
+ **When:** User needs to systematically generate more Google reviews.
85
+
86
+ **How Reputation Builder works:**
87
+ - Import customer list (email or phone)
88
+ - Send automated review request via email or SMS
89
+ - Directs happy customers to Google review page
90
+ - Tracks who received requests, who left reviews
91
+
92
+ **What the agent should guide:**
93
+ 1. **Timing**: Send review requests 1-3 days after service completion
94
+ 2. **Message**: Keep it short, personal, include direct Google review link
95
+ 3. **Volume**: Steady stream (5-10/week) is better than burst of 50
96
+ 4. **Filtering**: Don't send to known unhappy customers (avoid negative reviews)
97
+ 5. **Compliance**: Don't incentivize reviews, don't gate (filter based on rating)
98
+
99
+ **Review velocity targets by business type:**
100
+ | Business Type | Monthly Review Target | Rationale |
101
+ |---------------|----------------------|-----------|
102
+ | Restaurant | 15-30 | High transaction volume |
103
+ | Medical practice | 8-15 | Moderate patient volume |
104
+ | Home services | 5-10 | Lower transaction frequency |
105
+ | Legal | 3-5 | Fewer clients, harder to ask |
106
+ | B2B services | 2-4 | Low volume, high value |
107
+
108
+ ### Local Rank Tracking
109
+
110
+ **When:** User uses Whitespark's rank tracker.
111
+
112
+ **Whitespark's rank tracker** is point-based (single location), not geogrid.
113
+
114
+ **What the agent should know:**
115
+ - This shows ranking at ONE point for a keyword — not geographic coverage
116
+ - For local businesses, Local Falcon geogrid is far more useful
117
+ - Whitespark rank tracking is fine for organic keyword tracking alongside geogrid
118
+
119
+ ## What to Do Next
120
+
121
+ | What You Found | Next Action | Skill |
122
+ |----------------|-------------|-------|
123
+ | Citation gaps identified | Build missing citations, starting with Tier 1 | `local-citations` |
124
+ | Citations built, waiting for propagation | Work on other optimization while waiting (4-8 weeks) | `gbp-optimization`, `review-management` |
125
+ | Review generation campaign running | Monitor velocity and adjust messaging if response rate is low | `review-management` |
126
+ | Citation data needs to go in a report | Include in audit or monthly report | `client-deliverables`, `local-reporting` |
127
+ | Need MCP-accessible citation data | Use BrightLocal instead | `brightlocal-tool` |
128
+
129
+ **Default next step:** Whitespark's strength is managed citation services. If you need automated, agent-accessible citation data, use BrightLocal. If you need the highest-quality citation building, use Whitespark's managed service.