conectese 0.1.14

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 (260) hide show
  1. package/README.md +265 -0
  2. package/_conectese/.conectese-version +1 -0
  3. package/_conectese/config/playwright.config.json +11 -0
  4. package/_conectese/core/architect.agent.yaml +110 -0
  5. package/_conectese/core/best-practices/_catalog.yaml +116 -0
  6. package/_conectese/core/best-practices/blog-post.md +132 -0
  7. package/_conectese/core/best-practices/blog-seo.md +127 -0
  8. package/_conectese/core/best-practices/copywriting.md +426 -0
  9. package/_conectese/core/best-practices/data-analysis.md +401 -0
  10. package/_conectese/core/best-practices/email-newsletter.md +118 -0
  11. package/_conectese/core/best-practices/email-sales.md +110 -0
  12. package/_conectese/core/best-practices/image-design.md +348 -0
  13. package/_conectese/core/best-practices/instagram-feed.md +235 -0
  14. package/_conectese/core/best-practices/instagram-reels.md +112 -0
  15. package/_conectese/core/best-practices/instagram-stories.md +107 -0
  16. package/_conectese/core/best-practices/linkedin-article.md +116 -0
  17. package/_conectese/core/best-practices/linkedin-post.md +121 -0
  18. package/_conectese/core/best-practices/researching.md +349 -0
  19. package/_conectese/core/best-practices/review.md +269 -0
  20. package/_conectese/core/best-practices/social-networks-publishing.md +294 -0
  21. package/_conectese/core/best-practices/strategist.md +344 -0
  22. package/_conectese/core/best-practices/technical-writing.md +365 -0
  23. package/_conectese/core/best-practices/twitter-post.md +105 -0
  24. package/_conectese/core/best-practices/twitter-thread.md +122 -0
  25. package/_conectese/core/best-practices/whatsapp-broadcast.md +107 -0
  26. package/_conectese/core/best-practices/youtube-script.md +122 -0
  27. package/_conectese/core/best-practices/youtube-shorts.md +112 -0
  28. package/_conectese/core/prompts/build.prompt.md +547 -0
  29. package/_conectese/core/prompts/design.prompt.md +469 -0
  30. package/_conectese/core/prompts/discovery.prompt.md +269 -0
  31. package/_conectese/core/prompts/sherlock-instagram.md +123 -0
  32. package/_conectese/core/prompts/sherlock-linkedin.md +73 -0
  33. package/_conectese/core/prompts/sherlock-shared.md +684 -0
  34. package/_conectese/core/prompts/sherlock-twitter.md +78 -0
  35. package/_conectese/core/prompts/sherlock-youtube.md +85 -0
  36. package/_conectese/core/runner.pipeline.md +535 -0
  37. package/_conectese/core/skills.engine.md +381 -0
  38. package/agents/data-extractor/AGENT.md +13 -0
  39. package/agents/direito-adaneiro/AGENT.md +18 -0
  40. package/agents/direito-administrativo/AGENT.md +18 -0
  41. package/agents/direito-aeroporta-rio/AGENT.md +18 -0
  42. package/agents/direito-agra-rio/AGENT.md +18 -0
  43. package/agents/direito-ambiental/AGENT.md +18 -0
  44. package/agents/direito-banca-rio/AGENT.md +18 -0
  45. package/agents/direito-civil/AGENT.md +18 -0
  46. package/agents/direito-constitcional/AGENT.md +18 -0
  47. package/agents/direito-da-crianc-a-e-do-adolescente-eca/AGENT.md +18 -0
  48. package/agents/direito-da-propriedade-intelectal/AGENT.md +18 -0
  49. package/agents/direito-de-ami-lia/AGENT.md +18 -0
  50. package/agents/direito-de-tra-nsito/AGENT.md +18 -0
  51. package/agents/direito-desportivo/AGENT.md +18 -0
  52. package/agents/direito-digital/AGENT.md +18 -0
  53. package/agents/direito-do-consmidor/AGENT.md +18 -0
  54. package/agents/direito-do-trabalho/AGENT.md +18 -0
  55. package/agents/direito-econo-mico/AGENT.md +18 -0
  56. package/agents/direito-eleitoral/AGENT.md +18 -0
  57. package/agents/direito-empresarial/AGENT.md +18 -0
  58. package/agents/direito-imobilia-rio/AGENT.md +18 -0
  59. package/agents/direito-inanceiro/AGENT.md +18 -0
  60. package/agents/direito-internacional/AGENT.md +18 -0
  61. package/agents/direito-mari-timo/AGENT.md +18 -0
  62. package/agents/direito-me-dico-e-da-sa-de/AGENT.md +18 -0
  63. package/agents/direito-militar/AGENT.md +18 -0
  64. package/agents/direito-ndia-rio/AGENT.md +18 -0
  65. package/agents/direito-notarial-e-registral/AGENT.md +18 -0
  66. package/agents/direito-penal/AGENT.md +18 -0
  67. package/agents/direito-previdencia-rio/AGENT.md +18 -0
  68. package/agents/direito-processal-civil/AGENT.md +18 -0
  69. package/agents/direito-processal-do-trabalho/AGENT.md +18 -0
  70. package/agents/direito-processal-militar/AGENT.md +18 -0
  71. package/agents/direito-processal-penal/AGENT.md +18 -0
  72. package/agents/direito-rbani-stico/AGENT.md +18 -0
  73. package/agents/direito-secrita-rio/AGENT.md +18 -0
  74. package/agents/direito-sindical/AGENT.md +18 -0
  75. package/agents/direito-societa-rio/AGENT.md +18 -0
  76. package/agents/direito-tribta-rio/AGENT.md +18 -0
  77. package/agents/direitos-hmanos/AGENT.md +18 -0
  78. package/agents/legal-analyst/AGENT.md +16 -0
  79. package/agents/legal-synthesizer/AGENT.md +13 -0
  80. package/agents/lgpd-anonymizer/AGENT.md +14 -0
  81. package/agents/lgpd-restorer/AGENT.md +14 -0
  82. package/agents/task-router/AGENT.md +13 -0
  83. package/bin/conectese.js +73 -0
  84. package/dashboard/index.html +12 -0
  85. package/dashboard/package-lock.json +1971 -0
  86. package/dashboard/package.json +28 -0
  87. package/dashboard/public/assets/avatars/Female1_1wave.png +0 -0
  88. package/dashboard/public/assets/avatars/Female1_2wave.png +0 -0
  89. package/dashboard/public/assets/avatars/Female1_blink.png +0 -0
  90. package/dashboard/public/assets/avatars/Female1_talk.png +0 -0
  91. package/dashboard/public/assets/avatars/Female2_1wave.png +0 -0
  92. package/dashboard/public/assets/avatars/Female2_2wave.png +0 -0
  93. package/dashboard/public/assets/avatars/Female2_blink.png +0 -0
  94. package/dashboard/public/assets/avatars/Female2_talk.png +0 -0
  95. package/dashboard/public/assets/avatars/Female3_blink.png +0 -0
  96. package/dashboard/public/assets/avatars/Female3_talk.png +0 -0
  97. package/dashboard/public/assets/avatars/Female3_wave.png +0 -0
  98. package/dashboard/public/assets/avatars/Female4_blink.png +0 -0
  99. package/dashboard/public/assets/avatars/Female4_talk.png +0 -0
  100. package/dashboard/public/assets/avatars/Female4_wave.png +0 -0
  101. package/dashboard/public/assets/avatars/Female5_blink.png +0 -0
  102. package/dashboard/public/assets/avatars/Female5_talk.png +0 -0
  103. package/dashboard/public/assets/avatars/Female5_wave.png +0 -0
  104. package/dashboard/public/assets/avatars/Female6_blink.png +0 -0
  105. package/dashboard/public/assets/avatars/Female6_talk.png +0 -0
  106. package/dashboard/public/assets/avatars/Female6_wave.png +0 -0
  107. package/dashboard/public/assets/avatars/Male1_1wave.png +0 -0
  108. package/dashboard/public/assets/avatars/Male1_2wave.png +0 -0
  109. package/dashboard/public/assets/avatars/Male1_blink.png +0 -0
  110. package/dashboard/public/assets/avatars/Male1_talk.png +0 -0
  111. package/dashboard/public/assets/avatars/Male2_1wave.png +0 -0
  112. package/dashboard/public/assets/avatars/Male2_2wave.png +0 -0
  113. package/dashboard/public/assets/avatars/Male2_blink.png +0 -0
  114. package/dashboard/public/assets/avatars/Male2_talk.png +0 -0
  115. package/dashboard/public/assets/avatars/Male3_blink.png +0 -0
  116. package/dashboard/public/assets/avatars/Male3_talk.png +0 -0
  117. package/dashboard/public/assets/avatars/Male3_wave.png +0 -0
  118. package/dashboard/public/assets/avatars/Male4_blink.png +0 -0
  119. package/dashboard/public/assets/avatars/Male4_talk.png +0 -0
  120. package/dashboard/public/assets/avatars/Male4_wave.png +0 -0
  121. package/dashboard/public/assets/desks/desktop_set_black_down.png +0 -0
  122. package/dashboard/public/assets/desks/desktop_set_black_down_coding-1.png +0 -0
  123. package/dashboard/public/assets/desks/desktop_set_black_down_coding.png +0 -0
  124. package/dashboard/public/assets/desks/desktop_set_black_up.png +0 -0
  125. package/dashboard/public/assets/desks/desktop_set_white_down.png +0 -0
  126. package/dashboard/public/assets/desks/desktop_set_white_down_coding-1.png +0 -0
  127. package/dashboard/public/assets/desks/desktop_set_white_down_coding.png +0 -0
  128. package/dashboard/public/assets/desks/desktop_set_white_up.png +0 -0
  129. package/dashboard/public/assets/furniture/armchair_tan.png +0 -0
  130. package/dashboard/public/assets/furniture/armchair_tan_down.png +0 -0
  131. package/dashboard/public/assets/furniture/backpack_blue.png +0 -0
  132. package/dashboard/public/assets/furniture/backpack_red.png +0 -0
  133. package/dashboard/public/assets/furniture/blinds.png +0 -0
  134. package/dashboard/public/assets/furniture/blinds_large_closed_white.png +0 -0
  135. package/dashboard/public/assets/furniture/bookshelf.png +0 -0
  136. package/dashboard/public/assets/furniture/bookshelf_purple_tall.png +0 -0
  137. package/dashboard/public/assets/furniture/bulletin_board.png +0 -0
  138. package/dashboard/public/assets/furniture/clock.png +0 -0
  139. package/dashboard/public/assets/furniture/coffee_mug.png +0 -0
  140. package/dashboard/public/assets/furniture/coffee_mug_blue.png +0 -0
  141. package/dashboard/public/assets/furniture/coffee_table.png +0 -0
  142. package/dashboard/public/assets/furniture/coffeepot_right.png +0 -0
  143. package/dashboard/public/assets/furniture/coffeetable_black_horizontal.png +0 -0
  144. package/dashboard/public/assets/furniture/couch.png +0 -0
  145. package/dashboard/public/assets/furniture/couch_tan_down.png +0 -0
  146. package/dashboard/public/assets/furniture/cushion_blue.png +0 -0
  147. package/dashboard/public/assets/furniture/cushion_tan.png +0 -0
  148. package/dashboard/public/assets/furniture/desk_wood.png +0 -0
  149. package/dashboard/public/assets/furniture/fancy_rug.png +0 -0
  150. package/dashboard/public/assets/furniture/fancy_rug_wide.png +0 -0
  151. package/dashboard/public/assets/furniture/flowers1.png +0 -0
  152. package/dashboard/public/assets/furniture/flowers2.png +0 -0
  153. package/dashboard/public/assets/furniture/lamp_tan.png +0 -0
  154. package/dashboard/public/assets/furniture/lantern.png +0 -0
  155. package/dashboard/public/assets/furniture/monstera.png +0 -0
  156. package/dashboard/public/assets/furniture/monstera_small.png +0 -0
  157. package/dashboard/public/assets/furniture/picture_frame.png +0 -0
  158. package/dashboard/public/assets/furniture/plant1.png +0 -0
  159. package/dashboard/public/assets/furniture/plant2.png +0 -0
  160. package/dashboard/public/assets/furniture/plant3.png +0 -0
  161. package/dashboard/public/assets/furniture/plant_poof.png +0 -0
  162. package/dashboard/public/assets/furniture/plant_spindly.png +0 -0
  163. package/dashboard/public/assets/furniture/poster_blue.png +0 -0
  164. package/dashboard/public/assets/furniture/rug.png +0 -0
  165. package/dashboard/public/assets/furniture/succulent_blue.png +0 -0
  166. package/dashboard/public/assets/furniture/succulent_green.png +0 -0
  167. package/dashboard/public/assets/furniture/treasurechest_closed_gold.png +0 -0
  168. package/dashboard/public/assets/furniture/water_cooler_better.png +0 -0
  169. package/dashboard/public/assets/furniture/whiteboard.png +0 -0
  170. package/dashboard/public/assets/furniture/whiteboard_stand_graph.png +0 -0
  171. package/dashboard/public/assets/furniture/window_blinds_open.png +0 -0
  172. package/dashboard/src/App.tsx +46 -0
  173. package/dashboard/src/components/SquadCard.tsx +47 -0
  174. package/dashboard/src/components/SquadSelector.tsx +61 -0
  175. package/dashboard/src/components/StatusBadge.tsx +32 -0
  176. package/dashboard/src/components/StatusBar.tsx +97 -0
  177. package/dashboard/src/hooks/useSquadSocket.ts +135 -0
  178. package/dashboard/src/lib/formatTime.ts +16 -0
  179. package/dashboard/src/lib/normalizeState.ts +25 -0
  180. package/dashboard/src/main.tsx +10 -0
  181. package/dashboard/src/office/AgentSprite.ts +241 -0
  182. package/dashboard/src/office/OfficeScene.ts +153 -0
  183. package/dashboard/src/office/PhaserGame.tsx +80 -0
  184. package/dashboard/src/office/RoomBuilder.ts +190 -0
  185. package/dashboard/src/office/assetKeys.ts +150 -0
  186. package/dashboard/src/office/palette.ts +32 -0
  187. package/dashboard/src/plugin/squadWatcher.ts +233 -0
  188. package/dashboard/src/store/useSquadStore.ts +56 -0
  189. package/dashboard/src/styles/globals.css +36 -0
  190. package/dashboard/src/types/state.ts +63 -0
  191. package/dashboard/src/vite-env.d.ts +1 -0
  192. package/dashboard/test-results/.last-run.json +4 -0
  193. package/dashboard/tsconfig.json +24 -0
  194. package/dashboard/tsconfig.tsbuildinfo +1 -0
  195. package/dashboard/vite.config.ts +13 -0
  196. package/package.json +53 -0
  197. package/skills/README.md +63 -0
  198. package/skills/apify/SKILL.md +55 -0
  199. package/skills/blotato/SKILL.md +63 -0
  200. package/skills/canva/SKILL.md +60 -0
  201. package/skills/conectese-agent-creator/SKILL.md +192 -0
  202. package/skills/conectese-skill-creator/SKILL.md +407 -0
  203. package/skills/conectese-skill-creator/agents/analyzer.md +274 -0
  204. package/skills/conectese-skill-creator/agents/comparator.md +202 -0
  205. package/skills/conectese-skill-creator/agents/grader.md +223 -0
  206. package/skills/conectese-skill-creator/assets/eval_review.html +146 -0
  207. package/skills/conectese-skill-creator/eval-viewer/generate_review.py +471 -0
  208. package/skills/conectese-skill-creator/eval-viewer/viewer.html +1325 -0
  209. package/skills/conectese-skill-creator/references/schemas.md +430 -0
  210. package/skills/conectese-skill-creator/references/skill-format.md +235 -0
  211. package/skills/conectese-skill-creator/scripts/__init__.py +0 -0
  212. package/skills/conectese-skill-creator/scripts/aggregate_benchmark.py +401 -0
  213. package/skills/conectese-skill-creator/scripts/quick_validate.py +103 -0
  214. package/skills/conectese-skill-creator/scripts/run_eval.py +310 -0
  215. package/skills/conectese-skill-creator/scripts/utils.py +47 -0
  216. package/skills/image-ai-generator/SKILL.md +124 -0
  217. package/skills/image-ai-generator/scripts/generate.py +175 -0
  218. package/skills/image-creator/SKILL.md +155 -0
  219. package/skills/image-fetcher/SKILL.md +91 -0
  220. package/skills/instagram-publisher/SKILL.md +119 -0
  221. package/skills/instagram-publisher/scripts/publish.js +165 -0
  222. package/skills/resend/SKILL.md +80 -0
  223. package/skills/template-designer/SKILL.md +201 -0
  224. package/skills/template-designer/base-templates/model-a.html +27 -0
  225. package/skills/template-designer/base-templates/model-b.html +31 -0
  226. package/skills/template-designer/base-templates/model-c.html +42 -0
  227. package/src/agents-cli.js +158 -0
  228. package/src/agents.js +134 -0
  229. package/src/i18n.js +48 -0
  230. package/src/init.js +341 -0
  231. package/src/locales/en.json +73 -0
  232. package/src/locales/es.json +72 -0
  233. package/src/locales/pt-BR.json +72 -0
  234. package/src/logger.js +38 -0
  235. package/src/prompt.js +46 -0
  236. package/src/readme/README.md +119 -0
  237. package/src/runs.js +90 -0
  238. package/src/skills-cli.js +157 -0
  239. package/src/skills.js +146 -0
  240. package/src/update.js +169 -0
  241. package/templates/_conectese/.conectese-version +1 -0
  242. package/templates/_conectese/_investigations/.gitkeep +0 -0
  243. package/templates/ide-templates/antigravity/.agent/rules/conectese.md +55 -0
  244. package/templates/ide-templates/antigravity/.agent/workflows/conectese.md +102 -0
  245. package/templates/ide-templates/claude-code/.claude/skills/conectese/SKILL.md +182 -0
  246. package/templates/ide-templates/claude-code/.mcp.json +8 -0
  247. package/templates/ide-templates/claude-code/CLAUDE.md +43 -0
  248. package/templates/ide-templates/codex/.agents/skills/conectese/SKILL.md +6 -0
  249. package/templates/ide-templates/codex/AGENTS.md +105 -0
  250. package/templates/ide-templates/cursor/.cursor/commands/conectese.md +9 -0
  251. package/templates/ide-templates/cursor/.cursor/mcp.json +8 -0
  252. package/templates/ide-templates/cursor/.cursor/rules/conectese.mdc +48 -0
  253. package/templates/ide-templates/cursor/.cursorignore +3 -0
  254. package/templates/ide-templates/opencode/.opencode/commands/conectese.md +9 -0
  255. package/templates/ide-templates/opencode/AGENTS.md +105 -0
  256. package/templates/ide-templates/vscode-copilot/.github/prompts/conectese.prompt.md +201 -0
  257. package/templates/ide-templates/vscode-copilot/.vscode/mcp.json +8 -0
  258. package/templates/ide-templates/vscode-copilot/.vscode/settings.json +3 -0
  259. package/templates/package.json +8 -0
  260. package/templates/squads/.gitkeep +0 -0
@@ -0,0 +1,401 @@
1
+ ---
2
+ id: data-analysis
3
+ name: "Data Analysis & Interpretation"
4
+ whenToUse: |
5
+ Creating agents that interpret metrics, extract insights, benchmark performance,
6
+ or produce analytical reports.
7
+ NOT for: data collection/research, content creation, strategic planning, quality review.
8
+ version: "1.0.0"
9
+ ---
10
+
11
+ # Data Analysis & Interpretation — Best Practices
12
+
13
+ ## Core Principles
14
+
15
+ 1. **Insight over raw data.** Never present numbers without interpretation. Every metric, percentage, and data point must be accompanied by a plain-language business implication. Raw data is noise; interpreted data is intelligence. If you cannot explain what a number means for the business, do not include it in the report.
16
+
17
+ 2. **Always contextualize.** No metric exists in a vacuum. Compare every data point against at least one of these baselines: previous period (week-over-week, month-over-month), industry benchmark for the relevant segment and size tier, internal target or OKR, or competitor performance. A number without context has no meaning.
18
+
19
+ 3. **Confidence levels on every finding.** Tag every insight and recommendation with a confidence tier:
20
+ - **High Confidence**: 3+ data sources agree, consistent trend across 3+ consecutive periods, large sample size.
21
+ - **Medium Confidence**: 2 data sources agree, trend holds across 2 periods, or moderate sample size.
22
+ - **Low Confidence**: Single source, single period, small sample size, or conflicting signals across sources.
23
+ Never present a low-confidence finding with the same weight as a high-confidence one.
24
+
25
+ 4. **Structured output format.** Every analysis report must follow the standard structure: Executive Summary, Metrics Table, Insights (with business implications), Recommendations (with priority, confidence, and effort), and Methodology Notes. Deviating from this structure makes reports harder to consume and compare across periods.
26
+
27
+ 5. **Cross-reference data sources.** When multiple data sources report the same metric, compare their values. If they diverge by more than 10%, flag the discrepancy and explain which source you are using as the primary reference and why. Platform-native analytics (e.g., Instagram Insights, Google Analytics, LinkedIn Analytics) are preferred as primary sources; third-party tools serve as validation.
28
+
29
+ 6. **Metric priority weighting.** Not all metrics are equal. Weight actionable metrics (engagement rate, conversion rate, click-through rate, cost per acquisition) above vanity metrics (impressions, follower count, page views). Report all metrics for completeness, but base recommendations primarily on high-weight metrics. When metrics conflict, the higher-weight metric takes precedence.
30
+
31
+ 7. **Escalation for anomalies.** Flag any metric that moves more than 25% period-over-period as a critical anomaly requiring immediate attention. Flag any metric that exceeds its target by more than 50% for investigation — this may indicate a data error, a viral event, or a one-time external factor. Do not wait for the next scheduled report to surface critical anomalies; escalate them immediately.
32
+
33
+ 8. **Methodology transparency.** State the time period, data sources, sample sizes, and any exclusions at the end of every report. The reader must be able to assess the reliability of your analysis without asking follow-up questions.
34
+
35
+ ## Analysis Methodology
36
+
37
+ ### Step 1 — Data Collection from Research Outputs
38
+
39
+ Receive and organize raw data from upstream research agents, platform exports, or user-provided datasets. Verify that the data covers the expected time period and contains the required metrics. Identify any gaps or missing data points and note them for the methodology section. Retrieve current industry benchmarks if not already provided.
40
+
41
+ ### Step 2 — Pattern Identification
42
+
43
+ Scan all collected data for trends, anomalies, and correlations. Flag any metric that moved more than 15% from the previous period — positive or negative. Identify the top 3 and bottom 3 performing items (content pieces, channels, products, segments) by the primary KPI. Look for recurring patterns across multiple periods: is this a one-time spike or a sustained trend? Group related metrics to identify underlying drivers (e.g., reach increase + engagement decrease may indicate audience quality dilution).
44
+
45
+ ### Step 3 — Benchmarking Against Baselines
46
+
47
+ Compare every key metric against three baselines:
48
+ - **Historical**: Previous period (7-day, 30-day, or equivalent cycle)
49
+ - **Industry**: Median performance for the relevant segment, category, and size tier
50
+ - **Internal**: Targets, OKRs, or forecasted values
51
+
52
+ Calculate the gap between actual performance and each baseline. Rank gaps by severity. Metrics that fall below all three baselines are flagged as critical. Metrics that exceed all three baselines are flagged for positive investigation (replicable pattern or anomaly?).
53
+
54
+ ### Step 4 — Insight Synthesis
55
+
56
+ Translate identified patterns and benchmark gaps into plain-language insights. Every insight must follow this structure:
57
+ - **What happened**: The specific data movement or pattern
58
+ - **Why it matters**: The business implication ("This means...")
59
+ - **What it suggests**: The directional recommendation or hypothesis
60
+
61
+ Do not produce insights that merely restate numbers. An insight must add interpretive value beyond what the reader could see by scanning the table alone. Limit insights to 4-6 per report; more than that dilutes focus.
62
+
63
+ ### Step 5 — Recommendation Formation
64
+
65
+ Generate 3-5 prioritized action items based on the synthesized insights. Each recommendation must include:
66
+ - **Action**: The specific thing to do, stated as a clear directive
67
+ - **Expected Impact**: What outcome the action should produce, quantified where possible
68
+ - **Confidence Level**: High, Medium, or Low, based on the supporting data
69
+ - **Implementation Effort**: Low (< 2 hours), Medium (2-8 hours), or High (8+ hours)
70
+ - **Priority**: High, Medium, or Low, determined by the intersection of impact and confidence
71
+
72
+ Recommendations with High impact + High confidence = High priority. Recommendations with High impact + Low confidence = Medium priority (needs more data). Recommendations with Low impact regardless of confidence = Low priority.
73
+
74
+ ### Step 6 — Report Compilation
75
+
76
+ Assemble the final deliverable in the standard output structure. Verify completeness against the Quality Criteria checklist before submission. Ensure every metric table has consistent column counts, every insight has a business implication, every recommendation has all five required fields, and the executive summary can stand alone. Add the Methodology Notes section at the end with time period, data sources, sample sizes, and exclusions.
77
+
78
+ ## Decision Criteria
79
+
80
+ | Signal | Classification | Response |
81
+ |--------|---------------|----------|
82
+ | Metric at or above 30-day average AND at or above industry median | **Good** | Continue current approach; optimize incrementally |
83
+ | Metric dropped 10-25% vs previous period OR below industry median | **Concerning** | Recommend strategy adjustment; monitor closely next period |
84
+ | Metric dropped more than 25% vs previous period OR below 25th percentile | **Critical** | Recommend immediate action; escalate to stakeholders |
85
+ | Metric exceeded target by more than 50% | **Investigate** | Verify data accuracy; if confirmed, analyze for replicable pattern |
86
+ | Conflicting signals across sources (>10% divergence) | **Uncertain** | Flag discrepancy; use primary source; assign Low confidence |
87
+
88
+ ## Quality Criteria
89
+
90
+ Before submitting any analysis report, verify that it meets ALL of the following criteria:
91
+
92
+ - [ ] Every metric in every table has at least one comparison column (previous period, benchmark, or target)
93
+ - [ ] Every insight paragraph includes a business implication statement ("This means...", "The implication is...")
94
+ - [ ] Every recommendation includes all five required fields: action, expected impact, confidence level, effort estimate, and priority
95
+ - [ ] The executive summary contains exactly 3 bullet points and can be read independently without the full report
96
+ - [ ] All markdown tables render correctly with consistent column counts and proper alignment
97
+ - [ ] All percentages use consistent decimal precision (one decimal place throughout)
98
+ - [ ] Methodology section is present and includes time period, data sources, sample sizes, and exclusions
99
+ - [ ] No vague qualifiers appear anywhere in the report ("significant", "performing well", "pretty good", "not great")
100
+ - [ ] Confidence levels (High/Medium/Low) are assigned to every insight and every recommendation
101
+ - [ ] Anomalies (>25% movement) are explicitly flagged and classified as Critical
102
+ - [ ] No metric is presented as a raw number without narrative context
103
+ - [ ] Recommendations are ordered by priority (High first, then Medium, then Low)
104
+
105
+ ## Output Examples
106
+
107
+ ### Example 1: Content Performance Analysis
108
+
109
+ ```
110
+ # Analysis: Weekly Content Performance — Feb 10-16, 2026
111
+
112
+ ## Executive Summary
113
+
114
+ - **Engagement rate climbed 18% week-over-week to 4.6%**, surpassing the industry median
115
+ of 3.5% for accounts in the 10K-50K follower tier. This is the highest weekly engagement
116
+ rate recorded in the past 90 days, driven primarily by two educational carousel posts.
117
+ - **Website click-through rate declined 11% to 1.7%**, falling below the 30-day average
118
+ of 1.9%. This means fewer audience members are transitioning from social engagement to
119
+ site visits, suggesting a call-to-action effectiveness problem rather than a content
120
+ quality problem.
121
+ - **Recommended action**: Increase carousel frequency from 2 to 4 per week (high confidence)
122
+ and A/B test CTA placement in the first versus last slide to address the CTR gap.
123
+
124
+ ## Metrics
125
+
126
+ | Metric | This Period | Last Period | Change | 30-Day Avg | Industry Median | Status |
127
+ |--------|-------------|-------------|--------|------------|-----------------|--------|
128
+ | Impressions | 52,400 | 48,100 | **+8.9%** | 49,200 | 42,000 | Good |
129
+ | Reach | 33,100 | 30,500 | +8.5% | 31,200 | 27,000 | Good |
130
+ | Engagement Rate | **4.6%** | 3.9% | **+17.9%** | 4.1% | 3.5% | Good |
131
+ | Click-Through Rate | 1.7% | 1.9% | **-10.5%** | 1.9% | 1.5% | Concerning |
132
+ | Saves | 1,240 | 980 | +26.5% | 1,050 | 850 | Good |
133
+ | Shares | 410 | 370 | +10.8% | 385 | 310 | Good |
134
+ | Follower Growth | +0.6% | +0.9% | -33.3% | +0.8% | +0.5% | Concerning |
135
+ | Posts Published | 8 | 7 | +14.3% | 7 | 5 | Good |
136
+
137
+ ### Top Performing Content
138
+
139
+ | Post | Format | Eng. Rate | Reach | Saves |
140
+ |------|--------|-----------|-------|-------|
141
+ | "5 Data Myths That Cost You Revenue" | Carousel | 8.2% | 7,800 | 340 |
142
+ | "How to Read a Dashboard in 60 Seconds" | Carousel | 6.7% | 6,200 | 285 |
143
+ | "Monday Metric: CAC vs LTV Explained" | Static | 4.1% | 4,500 | 120 |
144
+
145
+ ### Lowest Performing Content
146
+
147
+ | Post | Format | Eng. Rate | Reach | Saves |
148
+ |------|--------|-----------|-------|-------|
149
+ | "Industry News Weekly Digest" | Reel | 1.6% | 2,300 | 22 |
150
+ | "Tool Spotlight: Spreadsheet Add-ons" | Static | 2.0% | 2,900 | 45 |
151
+
152
+ ## Insights
153
+
154
+ 1. **Educational carousels are the dominant content format by a wide margin.** The two
155
+ carousel posts this week averaged a 7.45% engagement rate — 1.8x the account average
156
+ of 4.1% and 2.1x the industry median of 3.5%. This pattern has persisted for 5
157
+ consecutive weeks with no single-week deviation greater than 0.4 percentage points.
158
+ This means carousel content is the most reliable driver of audience interaction for
159
+ this account. The implication is that production resources should be reallocated toward
160
+ carousel creation, even at the expense of other formats. (High confidence — 5 periods,
161
+ consistent pattern, corroborated by save rate data.)
162
+
163
+ 2. **Click-through rate is diverging from engagement rate.** Engagement rose 18% while CTR
164
+ fell 11% — a divergence that has widened over the past 3 weeks. This means the audience
165
+ is consuming and interacting with content on-platform but is not compelled to visit the
166
+ website. The implication is that our call-to-action strategy needs revision: the content
167
+ is strong enough to generate engagement, but the CTA is either poorly placed, poorly
168
+ worded, or absent from high-performing posts. Reviewing the top 3 posts, none included
169
+ a CTA in the first slide — all CTAs appeared in the final slide, which carousel analytics
170
+ show only 38% of viewers reach. (Medium confidence — 3-week pattern, single platform.)
171
+
172
+ 3. **Follower growth is decelerating despite rising engagement.** Growth dropped from +0.9%
173
+ to +0.6% this week — the third consecutive weekly decline. While still above the industry
174
+ median of +0.5%, the trajectory suggests the account is approaching a growth plateau
175
+ within its current audience pool. This means organic discovery alone may not sustain
176
+ growth targets. The implication is that partnership content, collaborations, or paid
177
+ amplification may be needed to reach new audience segments. (Medium confidence — 3-period
178
+ trend, but could also be seasonal.)
179
+
180
+ 4. **Reels continue to underperform for this account.** The single Reel published this week
181
+ had the lowest engagement rate (1.6%) and the lowest save rate of any format. Across the
182
+ past 30 days, Reels have averaged 1.9% engagement versus 6.8% for carousels and 3.4% for
183
+ static posts. This means the current Reel content strategy is not resonating with this
184
+ account's audience. The implication is that Reel production effort should be paused until
185
+ a content audit identifies whether the issue is format, topic, or execution. (High
186
+ confidence — 30-day data, consistent underperformance across 8 Reels.)
187
+
188
+ ## Recommendations
189
+
190
+ 1. **Increase carousel production to 4 per week** — Priority: High | Confidence: High |
191
+ Effort: Medium. Five weeks of consistent data show carousels outperforming every other
192
+ format by at least 1.8x on engagement rate. Reallocate the Reel production slot and one
193
+ static post slot to carousels. Expected impact: engagement rate increase of 10-15% based
194
+ on format mix shift.
195
+
196
+ 2. **A/B test CTA placement: first slide vs. last slide** — Priority: High | Confidence:
197
+ Medium | Effort: Low. The engagement-CTR divergence suggests users are not seeing the CTA.
198
+ Run a 2-week test placing the CTA on the first slide of half the carousels. Expected
199
+ impact: CTR improvement of 15-25% if placement is the primary driver.
200
+
201
+ 3. **Pause Reel production and conduct a content audit** — Priority: Medium | Confidence:
202
+ High | Effort: Low. Thirty days of data confirm Reels consistently underperform. Before
203
+ investing further, audit the 8 Reels from the past month for common failure patterns
204
+ (topic, length, hook quality, posting time). Expected impact: saves wasted production
205
+ hours until the format is validated or abandoned.
206
+
207
+ 4. **Test one collaboration post to address follower growth decline** — Priority: Medium |
208
+ Confidence: Medium | Effort: High. Slowing growth suggests audience saturation within
209
+ current reach. A co-created post with a complementary account could expose the brand to
210
+ a new audience segment. Expected impact: temporary growth spike of 0.3-0.5% in the
211
+ collaboration week, based on historical benchmarks for accounts in this tier.
212
+
213
+ ## Methodology
214
+
215
+ - **Period**: February 10-16, 2026 (7 days)
216
+ - **Data Sources**: Platform-native analytics (primary), third-party social analytics tool (validation)
217
+ - **Benchmarks**: Industry medians sourced from 2025 Social Media Benchmark Report for B2B accounts, 10K-50K follower tier
218
+ - **Exclusions**: Sponsored/boosted posts excluded from organic performance metrics
219
+ ```
220
+
221
+ ### Example 2: Competitive Landscape Analysis
222
+
223
+ ```
224
+ # Analysis: Competitive Landscape — Email Marketing SaaS — Q4 2025
225
+
226
+ ## Executive Summary
227
+
228
+ - **Competitor A leads on deliverability rate (98.2%) but trails on automation features**,
229
+ ranking 4th out of 6 competitors on workflow complexity score. This means they win on
230
+ reliability but lose on power-user capability — an exploitable gap for our positioning.
231
+ - **The market average price per subscriber increased 12% year-over-year**, with 4 of 6
232
+ competitors raising prices in Q4. This means the market is shifting toward premium
233
+ positioning, creating an opening for a value-tier narrative.
234
+ - **Three high-potential content angles identified** for thought leadership positioning,
235
+ each targeting a different segment of the buyer journey.
236
+
237
+ ## Competitive Metrics Comparison
238
+
239
+ | Metric | Our Product | Comp. A | Comp. B | Comp. C | Comp. D | Market Avg |
240
+ |--------|-------------|---------|---------|---------|---------|------------|
241
+ | Deliverability Rate | 96.8% | **98.2%** | 95.4% | 97.1% | 94.3% | 96.4% |
242
+ | Avg. Open Rate (Users) | 24.1% | 22.8% | 25.3% | 23.5% | 21.7% | 23.5% |
243
+ | Automation Workflows | **42** | 18 | 35 | 28 | 22 | 29 |
244
+ | Price / 10K Subscribers | $79/mo | $89/mo | $99/mo | $69/mo | $59/mo | $79/mo |
245
+ | Free Tier Limit | 1,000 | 500 | 2,000 | 300 | 1,500 | 1,060 |
246
+ | G2 Rating (out of 5) | 4.4 | **4.7** | 4.3 | 4.1 | 4.2 | 4.3 |
247
+ | Support Response Time | 2.1 hrs | 1.4 hrs | 4.8 hrs | 3.2 hrs | 6.1 hrs | 3.5 hrs |
248
+ | YoY Price Change | 0% | +15% | +18% | +8% | +5% | +12% |
249
+
250
+ ## Insights
251
+
252
+ 1. **Our automation capability is the strongest in the competitive set, but we are not
253
+ known for it.** With 42 pre-built automation workflows — 45% above the market average
254
+ of 29 and 2.3x Competitor A's 18 — our product has the most robust automation offering.
255
+ However, brand awareness surveys show only 22% of prospects associate our product with
256
+ "advanced automation." This means we have a perception gap: the product capability exists,
257
+ but the market narrative does not reflect it. The implication is that content strategy
258
+ should aggressively position our automation depth as a primary differentiator over the
259
+ next quarter. (High confidence — verified product data, corroborated by G2 feature
260
+ comparison and brand survey.)
261
+
262
+ 2. **Competitor A is vulnerable on automation despite leading on brand perception.** They
263
+ hold the highest G2 rating (4.7) and the best deliverability (98.2%), but their automation
264
+ offering (18 workflows) is the weakest in the set — 38% below market average. This means
265
+ their users likely hit a ceiling when their email programs mature beyond basic campaigns.
266
+ The implication is that we should target Competitor A's mid-market customers who have
267
+ outgrown basic automation with comparison content and migration incentives. (High
268
+ confidence — product data verified, supported by 12 G2 reviews mentioning automation
269
+ limitations.)
270
+
271
+ 3. **The market is repricing upward, creating a value positioning window.** Four of six
272
+ competitors raised prices in Q4, with an average year-over-year increase of 12%.
273
+ Our price remained flat at $79/month for 10K subscribers — exactly at the market average.
274
+ This means our relative value proposition has improved without any action on our part.
275
+ The implication is that this is the optimal moment to publish price comparison content
276
+ and emphasize feature-per-dollar metrics, especially targeting prospects of Competitor B
277
+ ($99/mo, +18% YoY increase) who may be evaluating alternatives. (High confidence —
278
+ pricing data publicly available and verified.)
279
+
280
+ 4. **Deliverability rate is our one metric trailing the top competitor.** At 96.8%, we are
281
+ above market average (96.4%) but 1.4 percentage points behind Competitor A's 98.2%.
282
+ While the absolute gap is small, deliverability is a high-salience metric for email
283
+ marketers — it is often the first filter in vendor evaluation. This means we should not
284
+ lead positioning on deliverability but should ensure it is addressed proactively in sales
285
+ materials to neutralize it as a disqualifier. (Medium confidence — the gap is narrow and
286
+ could close with infrastructure improvements already in the Q1 roadmap.)
287
+
288
+ ## Content Angles Generated
289
+
290
+ ### Angle 1: "The Automation Gap Nobody Talks About"
291
+
292
+ - **Angle Type**: Contrarian
293
+ - **Primary Emotion**: Surprise, outrage
294
+ - **Angle Statement**: The market's highest-rated email tools have the weakest automation — and nobody is calling it out.
295
+ - **Recommended Hook Formulas**: Contrarian ("Everyone recommends X for email, but look at the automation numbers"), Secret ("The feature gap your email provider doesn't want you to notice")
296
+ - **Suggested Persuasion Framework**: PAS (Problem: your campaigns are limited; Agitation: you are paying premium for basic automation; Solution: there is a tool with 2.3x more workflows at a lower price)
297
+ - **Viral Rationale**: Challenges established brand hierarchy with verifiable data; contrarian takes on popular tools generate high engagement from both supporters and detractors
298
+ - **Target Platforms**: LinkedIn (thought leadership), X/Twitter (debate potential), Blog (SEO for "[Competitor A] alternatives")
299
+
300
+ ### Angle 2: "The Great Email Repricing of 2025"
301
+
302
+ - **Angle Type**: Fear/Urgency
303
+ - **Primary Emotion**: Fear of loss, FOMO
304
+ - **Angle Statement**: Email marketing costs rose 12% in one year — and most teams did not budget for it.
305
+ - **Recommended Hook Formulas**: Statistic ("Email tool prices are up 12% YoY — here is what that means for your budget"), Warning ("If your email costs went up this year, you are not alone — and it is going to get worse")
306
+ - **Suggested Persuasion Framework**: AIDA (Attention: price increase data; Interest: breakdown by competitor; Desire: show the value alternative; Action: switch before next renewal)
307
+ - **Viral Rationale**: Price sensitivity content performs well in economic uncertainty; provides shareable data point that budget holders will forward internally
308
+ - **Target Platforms**: LinkedIn (budget decision-makers), Newsletter (existing audience activation), Blog (SEO for "email marketing pricing 2026")
309
+
310
+ ### Angle 3: "What 10,000 Email Campaigns Taught Us About Open Rates"
311
+
312
+ - **Angle Type**: Educational
313
+ - **Primary Emotion**: Curiosity, empowerment
314
+ - **Angle Statement**: Our platform data reveals the real drivers of open rate — and it is not subject lines.
315
+ - **Recommended Hook Formulas**: Statistic ("We analyzed 10,000 campaigns. Subject line optimization accounts for only 11% of open rate variance"), Question ("What actually drives email open rates? We have the data — and the answer is not what you think")
316
+ - **Suggested Persuasion Framework**: Star-Story-Solution (Star: the universal struggle with open rates; Story: our data analysis journey and surprising findings; Solution: the factors that actually move the needle)
317
+ - **Viral Rationale**: Challenges widely-held belief (subject lines = open rates) with proprietary data; educational content with a contrarian twist generates high save and share rates
318
+ - **Target Platforms**: Blog (SEO authority), LinkedIn (professional insight), Newsletter (value delivery)
319
+
320
+ ## Recommendations
321
+
322
+ 1. **Launch an automation comparison campaign targeting Competitor A users** — Priority: High |
323
+ Confidence: High | Effort: Medium. Produce a detailed feature comparison landing page and
324
+ 3-part blog series highlighting the 42 vs 18 workflow gap. Expected impact: capture 2-5%
325
+ of Competitor A's mid-market accounts in evaluation cycles over the next quarter.
326
+
327
+ 2. **Publish a pricing transparency report using Q4 data** — Priority: High | Confidence: High |
328
+ Effort: Low. The 12% market price increase is a verifiable, timely data point that positions
329
+ our flat pricing as a strategic advantage. Expected impact: 3x average blog engagement based
330
+ on historical performance of pricing content.
331
+
332
+ 3. **Develop a deliverability improvement roadmap** — Priority: Medium | Confidence: Medium |
333
+ Effort: High. Closing the 1.4 percentage point gap with Competitor A removes their strongest
334
+ differentiator. Coordinate with engineering on the Q1 infrastructure improvements already
335
+ scoped. Expected impact: neutralize deliverability as a competitive vulnerability within 2
336
+ quarters.
337
+
338
+ 4. **Commission a proprietary open rate study** — Priority: Medium | Confidence: Medium |
339
+ Effort: High. Angle 3 requires aggregated platform data. If the data supports a contrarian
340
+ finding (subject lines are not the primary driver), the resulting content has high viral
341
+ potential. Expected impact: thought leadership positioning and SEO authority for
342
+ "email open rates" keyword cluster.
343
+
344
+ ## Methodology
345
+
346
+ - **Period**: Q4 2025 (October 1 - December 31, 2025)
347
+ - **Data Sources**: Competitor pricing pages (verified December 2025), G2 product profiles and review data, proprietary platform analytics for internal metrics, industry benchmark reports from Litmus and Mailchimp annual surveys
348
+ - **Competitors Included**: 4 direct competitors in the SMB/mid-market email marketing segment, selected by market share overlap
349
+ - **Exclusions**: Enterprise-tier pricing and features excluded; comparison based on mid-market plans (5K-50K subscriber tier)
350
+ - **Limitations**: Competitor deliverability rates sourced from published claims and third-party tests; actual rates may vary by sender reputation and list quality
351
+ ```
352
+
353
+ ## Anti-Patterns
354
+
355
+ ### Never Do
356
+
357
+ 1. **Never present data without business implication.** Raw numbers without context are noise, not analysis. Every metric must answer "so what does this mean for the business?" A table of numbers without narrative is a spreadsheet, not an analysis.
358
+
359
+ 2. **Never make recommendations without supporting data.** Every recommendation must cite the specific metrics, trends, or benchmarks that justify it. Intuition and gut feelings are not analysis. If you cannot point to the data, you cannot make the recommendation.
360
+
361
+ 3. **Never report a single period in isolation.** Always show comparison — versus previous period, versus benchmark, versus target. A number without a reference point has no meaning. The reader cannot assess "45,000 impressions" without knowing whether that is up, down, or flat.
362
+
363
+ 4. **Never use vague qualifiers.** Replace "significant increase" with "up 23% week-over-week." Replace "performing well" with "above the 75th percentile industry benchmark." Replace "pretty strong results" with "engagement rate of 4.6%, exceeding our 4.0% target by 15%." Precision is the analyst's currency.
364
+
365
+ 5. **Never ignore outliers without investigation.** An anomalous data point may indicate a data error, a viral event, a seasonal effect, or a genuine shift. Document what you found when you investigated, even if the answer is "no identifiable cause." Silently excluding outliers destroys analytical credibility.
366
+
367
+ 6. **Never present correlation as causation.** "Posting time correlates with higher engagement" is acceptable. "Posting at 9 AM causes higher engagement" is not — unless supported by controlled experiment data. Use "correlates with," "coincided with," or "was accompanied by" instead of "caused," "led to," or "resulted in."
368
+
369
+ 7. **Never delay reporting a critical anomaly.** If a metric drops more than 25% period-over-period or breaches a critical threshold, escalate immediately. Do not wait until the next scheduled report. Critical anomalies have a time-sensitive impact that diminishes with delayed response.
370
+
371
+ ### Always Do
372
+
373
+ 1. **Always include a comparison point for every metric.** No exceptions. If the benchmark is unavailable, compare against the previous period. If the previous period is unavailable, state that no comparison is available and assign Low confidence to any insight derived from that metric.
374
+
375
+ 2. **Always end insights with "this means..." or equivalent.** The business implication is the most valuable part of the insight. Without it, you are reporting data, not analyzing it. Train the reader to expect the implication after every finding.
376
+
377
+ 3. **Always tag confidence levels on recommendations.** The decision-maker needs to know whether a recommendation is backed by 6 months of consistent data or a single data point from last Tuesday. Confidence levels enable proportionate action.
378
+
379
+ 4. **Always include methodology transparency.** State the time period, data sources, sample sizes, and any exclusions at the end of every report. This allows the reader to independently assess the reliability of your findings and reproduces the analysis if needed.
380
+
381
+ 5. **Always prioritize recommendations.** Never present a flat list of equal-weight suggestions. Rank them by the intersection of expected impact and confidence level. The decision-maker's time and resources are finite; your prioritization respects that constraint.
382
+
383
+ ## Vocabulary Guidance
384
+
385
+ ### Use
386
+
387
+ - **Precise metric names**: "engagement rate" not "engagement"; "click-through rate" not "clicks"; "cost per acquisition" not "cost"; "month-over-month growth rate" not "growth"
388
+ - **Business implication language**: "This means...", "The implication is...", "This suggests we should...", "The business impact is...", "For the bottom line, this translates to..."
389
+ - **Confidence qualifiers**: "With high confidence, we recommend...", "Early signals suggest...", "Insufficient data to confirm, but initial indicators point to...", "This finding is corroborated by three independent data sources..."
390
+ - **Directional trend language**: "up 12% week-over-week", "declining for 3 consecutive periods", "flat compared to the 30-day benchmark", "rebounding after a 2-week dip"
391
+ - **Comparison framing**: "versus the industry median of...", "compared to the previous period's...", "against our internal target of...", "relative to competitor average of..."
392
+ - **Quantified impact language**: "This represents an additional 340 website visits per week", "At the current trajectory, this would result in a 15% shortfall against Q1 targets", "Scaling this pattern across all channels could yield an estimated 22% increase in qualified leads"
393
+
394
+ ### Avoid
395
+
396
+ - **Vague qualifiers**: "significant", "performing well", "not great", "pretty good", "somewhat", "fairly strong"
397
+ - **Raw numbers without context**: never state "We had 45,000 impressions" without adding comparison and implication
398
+ - **Correlation as causation**: never state "X caused Y" unless there is controlled evidence; instead use "X correlates with Y" or "X coincided with Y"
399
+ - **"Interesting" without specifics**: never say "This is an interesting finding" — instead state what specifically makes it notable and what it implies
400
+ - **Hedging without substance**: never use "It seems like" or "It appears that" without following with specific data points that support the observation
401
+ - **Superlatives without evidence**: never use "best ever", "worst performance", "unprecedented" without the specific historical data to back the claim
@@ -0,0 +1,118 @@
1
+ ---
2
+ name: "Email Newsletter"
3
+ platform: "email"
4
+ content_type: "newsletter"
5
+ description: "Recurring email newsletters optimized for open rates, click-throughs, and subscriber retention"
6
+ whenToUse: |
7
+ Creating agents that produce email newsletters or recurring subscriber content.
8
+ constraints:
9
+ subject_line_max_chars: 60
10
+ subject_line_optimal: "30-50"
11
+ preview_text_chars: 90
12
+ optimal_word_count: "200-500"
13
+ cta_buttons_max: 2
14
+ version: "1.0.0"
15
+ ---
16
+
17
+ ## Platform Rules
18
+
19
+ - Subject lines are the single largest driver of open rates. Emails with 30-50 character subject lines consistently outperform longer ones. On mobile (60%+ of opens), subject lines are truncated at approximately 35-40 characters.
20
+ - Preview text (preheader) is the second line of defense. If left blank, email clients auto-fill it with the first line of body text, which is often "View in browser" or navigation — a wasted opportunity. Always write custom preview text that extends the subject line's promise.
21
+ - Above-the-fold content determines whether a reader scrolls or deletes. The key message, value proposition, or hook must be visible without scrolling on both desktop and mobile.
22
+ - Single-column layouts are mandatory for mobile readability. Multi-column designs break on most mobile clients and create a frustrating reading experience.
23
+ - Average email open rates range from 20-43% depending on industry. Click-through rates average 2-5%. Every element of the email should be optimized for these two metrics.
24
+ - Send time matters: emails sent between 9-11 AM or 3-7 PM in the recipient's time zone consistently outperform other windows. Tuesday, Wednesday, and Thursday are the strongest days.
25
+ - Consistent send cadence (weekly, biweekly) builds habit and expectation. Irregular sending degrades open rates over time as subscribers forget who you are.
26
+ - Deliverability depends on sender reputation. High bounce rates, spam complaints, and low engagement signal poor list hygiene and push emails to spam folders.
27
+
28
+ ## Content Structure
29
+
30
+ ### Newsletter Architecture
31
+
32
+ 1. **Subject line** — 30-50 characters. Must create curiosity, promise a benefit, or signal urgency. Personalization ({{name}} or segment reference) increases open rates by 10-20%.
33
+ 2. **Preview text** — 60-90 characters. Extends the subject line, never repeats it. Provides additional context or a secondary hook that complements the subject.
34
+ 3. **Header** — Brand logo, issue number or date. Brief and recognizable. Do not clutter with navigation links.
35
+ 4. **Featured content** — The primary story, tip, or insight. This is the above-the-fold value delivery. 100-150 words maximum with a clear visual (image or graphic).
36
+ 5. **Body sections** — 2-3 secondary content blocks. Each has a subheading, 50-100 words, and an optional link to full content. Separated by visual dividers.
37
+ 6. **Primary CTA** — One prominent button with action-oriented text ("Read the full guide", "Get your template", "Watch the interview"). Placed after the featured content.
38
+ 7. **Footer** — Unsubscribe link (legally required), preference center, social links, company address. Keep compact.
39
+
40
+ ### Subject Line Formulas
41
+
42
+ - **Curiosity gap**: "The metric we stopped tracking (and why)"
43
+ - **Benefit-first**: "3 templates to cut your writing time in half"
44
+ - **Urgency**: "Last 48 hours: the resource we are retiring"
45
+ - **Personalization**: "{{name}}, your weekly content briefing"
46
+ - **Number-driven**: "5 lessons from 100 failed launches"
47
+
48
+ ## Writing Guidelines
49
+
50
+ - **Write the subject line last.** After you know what the email delivers, craft a subject line that accurately promises it. Clickbait subjects that do not deliver destroy trust and increase unsubscribes.
51
+ - Preview text must complement the subject line, not repeat it. Subject: "3 mistakes killing your open rates" + Preview: "Plus: the free tool we use to fix them" — together they create a stronger open incentive.
52
+ - Keep total word count between 200-500 words. Newsletters that exceed 500 words see declining click-through rates as readers skim and abandon.
53
+ - Use subheadings to break content into scannable sections. A reader should understand the email's value from subheadings alone without reading body text.
54
+ - One primary CTA button per email. A secondary text link is acceptable, but two competing buttons with equal visual weight create decision paralysis and reduce clicks on both.
55
+ - Write CTA button text as a verb phrase: "Download the checklist" not "Click here." Button text should tell the reader exactly what they get.
56
+ - Use short paragraphs (2-3 sentences maximum). Email is a scanning medium, not a reading medium.
57
+ - Include alt text on every image. Many email clients block images by default. Alt text ensures the message is comprehensible even without visuals loading.
58
+ - Personalize beyond the name: reference the subscriber's segment, past behavior, or interests when possible. "As a marketing subscriber..." outperforms generic content.
59
+
60
+ ## Output Format
61
+
62
+ ```
63
+ === SUBJECT LINE ===
64
+ [30-50 characters — curiosity, benefit, urgency, or personalization hook]
65
+
66
+ === PREVIEW TEXT ===
67
+ [60-90 characters — extends the subject line, never repeats it]
68
+
69
+ === HEADER ===
70
+ [Brand name / logo placeholder | Issue #X or Date]
71
+
72
+ === FEATURED CONTENT ===
73
+ [Primary story, tip, or insight — 100-150 words. Above-the-fold value delivery.]
74
+
75
+ [Optional: image or graphic description]
76
+
77
+ === BODY ===
78
+ ### [Section 1 Heading]
79
+ [50-100 words — secondary content with optional link]
80
+
81
+ ### [Section 2 Heading]
82
+ [50-100 words — secondary content with optional link]
83
+
84
+ ### [Section 3 Heading]
85
+ [50-100 words — secondary content with optional link]
86
+
87
+ === CTA ===
88
+ [Primary CTA button text — action verb phrase, e.g., "Read the full guide"]
89
+ [CTA URL]
90
+
91
+ === FOOTER ===
92
+ [Unsubscribe link | Preference center | Social links | Company address]
93
+ ```
94
+
95
+ ## Quality Criteria
96
+
97
+ - [ ] Subject line is 30-50 characters and creates a clear reason to open
98
+ - [ ] Preview text is 60-90 characters and extends (not repeats) the subject line
99
+ - [ ] Key message is visible above the fold without scrolling on mobile
100
+ - [ ] Layout is single-column and mobile-responsive
101
+ - [ ] Total word count is between 200-500 words
102
+ - [ ] One primary CTA button with verb-phrase text (not "Click here")
103
+ - [ ] No more than 2 CTA elements total (1 button + 1 optional text link)
104
+ - [ ] Every image includes descriptive alt text
105
+ - [ ] Content is scannable via subheadings without reading body text
106
+ - [ ] Unsubscribe link is present and functional in the footer
107
+
108
+ ## Anti-Patterns
109
+
110
+ - **Clickbait subject lines** — Subject lines that promise something the email does not deliver cause unsubscribes and spam reports. Each false promise permanently damages sender reputation and deliverability.
111
+ - **Image-heavy emails with no alt text** — Many email clients (especially Outlook and corporate environments) block images by default. An email that is mostly images with no alt text displays as a blank white box, wasting the send entirely.
112
+ - **Multiple competing CTAs** — Three buttons with equal visual weight ("Read this," "Buy that," "Sign up here") create decision paralysis. Click-through rates drop on all CTAs when they compete for attention.
113
+ - **No plain-text fallback** — Some email clients and accessibility tools render only plain text. Without a plain-text version, your email may display as raw HTML code or be completely unreadable.
114
+ - **Exceeding 500 words** — Newsletter engagement drops sharply past 500 words. Readers scan emails in 8-10 seconds. If the content requires more depth, link to a full article and keep the email as a teaser.
115
+ - **Repeating subject line in preview text** — The preview text is a second headline, not an echo. Repeating the subject line wastes the most valuable real estate for driving opens.
116
+ - **Inconsistent send schedule** — Irregular sending (weekly, then nothing for a month, then three in a week) erodes subscriber trust and trains email clients to deprioritize your messages.
117
+ - **Generic "Dear subscriber" opening** — Impersonal greetings signal mass email. Even basic {{name}} personalization measurably improves engagement and reduces the perception of spam.
118
+ - **Sending without list hygiene** — Keeping inactive subscribers (no opens in 90+ days) on your list degrades sender reputation. Regularly prune or re-engage inactive contacts.
@@ -0,0 +1,110 @@
1
+ ---
2
+ name: "Sales Email"
3
+ platform: "email"
4
+ content_type: "sales"
5
+ description: "Direct response sales emails optimized for a single conversion action using persuasion frameworks"
6
+ whenToUse: |
7
+ Creating agents that produce sales emails, cold outreach, or direct response email campaigns.
8
+ constraints:
9
+ subject_line_max_chars: 60
10
+ optimal_word_count: "100-300"
11
+ cta_count: 1
12
+ version: "1.0.0"
13
+ ---
14
+
15
+ ## Platform Rules
16
+
17
+ - Sales emails live or die by the subject line. Open rates above 60% are achievable with well-crafted, personalized subject lines of 4-7 words. Generic subject lines land in spam or get ignored.
18
+ - Deliverability is the invisible prerequisite. HTML-heavy cold emails, attachments, and image-loaded templates trigger spam filters. Plain-text formatting with minimal links outperforms designed templates for cold outreach.
19
+ - Reply rate is the primary success metric, not open rate. A 3-5% positive reply rate is a strong baseline. Well-targeted campaigns with deep personalization can reach 15-30% reply rates.
20
+ - Cold emails must comply with CAN-SPAM, GDPR, and local regulations. Include a physical address and unsubscribe mechanism. Non-compliance risks fines and domain blacklisting.
21
+ - Send volume matters: limit cold outreach to 35-40 emails per day per sending address to protect domain reputation. Warming up new domains over 2-4 weeks is mandatory before scaling.
22
+ - Follow-up cadence drives results. 80% of conversions happen after the initial email. Follow up on days 3-4, 7-10, and 14. After 4-5 follow-ups with no response, stop.
23
+ - Warm emails (to existing leads or subscribers) tolerate slightly longer formats and HTML design. Cold emails must be short, plain-text, and hyper-personalized.
24
+ - Best send times for sales emails: 8-10 AM or 1-3 PM on Tuesday, Wednesday, or Thursday in the recipient's time zone. Monday mornings and Friday afternoons underperform.
25
+
26
+ ## Content Structure
27
+
28
+ ### Sales Email Architecture (PAS Framework)
29
+
30
+ 1. **Subject line** — 4-7 words. Specific to the recipient's situation. Creates just enough curiosity to earn the open without resorting to clickbait or deception.
31
+ 2. **Opener (1-2 sentences)** — Personalized reference to the recipient's company, role, recent activity, or shared connection. Must demonstrate that this is not a mass email.
32
+ 3. **Problem/Pain (2-3 sentences)** — Articulate a specific problem the recipient likely faces. Use their industry language, not yours. The reader should think "yes, that is exactly my situation."
33
+ 4. **Solution (2-3 sentences)** — Position your offer as the bridge from their pain to their desired outcome. Focus on the result, not the features. One specific proof point (metric, case study, or name-drop).
34
+ 5. **Social proof (1-2 sentences)** — A concrete result: "[Company similar to theirs] achieved [specific outcome] in [timeframe]." Numbers and named companies outperform vague claims.
35
+ 6. **CTA (1 sentence)** — One single, low-friction ask. Not "buy now" — instead, "Would a 15-minute call this week make sense?" The ask must match the relationship stage.
36
+ 7. **PS line** — The second most-read line after the subject. Use it for urgency, a secondary proof point, or a personal note that reinforces the value proposition.
37
+
38
+ ### Alternative Frameworks
39
+
40
+ - **AIDA**: Attention (subject + opener), Interest (pain point), Desire (solution + proof), Action (CTA).
41
+ - **Before/After/Bridge**: Before (current state), After (desired outcome), Bridge (your solution).
42
+ - **Star/Story/Solution**: Star (the prospect), Story (the challenge they face), Solution (your offer).
43
+
44
+ ## Writing Guidelines
45
+
46
+ - **Personalize the first line or lose the reader.** "I noticed your team just launched X" or "Saw your post about Y" demonstrates genuine research. "Hope this finds you well" signals a template and gets deleted.
47
+ - Keep cold emails under 150 words. Every word beyond 150 reduces reply probability. Shorter emails look like personal messages, not sales blasts.
48
+ - One CTA per email, always. Multiple asks ("book a call, check our website, download this guide, follow us on LinkedIn") create decision paralysis and dilute the conversion path.
49
+ - Match your CTA to the relationship temperature. Cold: "Worth a quick chat?" Warm: "Ready to see how this works for your team?" Hot: "Should I send the proposal?"
50
+ - Write the PS line. It is the second most-read part of any email. Use it for urgency ("We are only taking 3 more clients this quarter"), a testimonial, or a personal touch.
51
+ - Use plain text for cold emails. HTML templates, embedded images, and fancy formatting signal "marketing email" and reduce deliverability and reply rates.
52
+ - Avoid attachments in cold emails. They trigger spam filters and create friction. Link to a hosted resource if you must share a document.
53
+ - Write in short sentences and short paragraphs (1-2 sentences each). Dense paragraphs look like effort to process and get skimmed or skipped.
54
+ - A/B test subject lines aggressively. Test curiosity vs. direct benefit, question vs. statement, and with vs. without the recipient's name. Small subject line changes can swing open rates by 20-30%.
55
+
56
+ ## Output Format
57
+
58
+ ```
59
+ === SUBJECT LINE ===
60
+ [4-7 words — specific to recipient, creates curiosity. Max 60 characters.]
61
+
62
+ === OPENER ===
63
+ [Personalized first line — reference to recipient's company, role, recent activity, or shared connection. 1-2 sentences.]
64
+
65
+ === PROBLEM / PAIN ===
66
+ [Specific pain point the recipient faces — in their industry language. 2-3 sentences.]
67
+
68
+ === SOLUTION ===
69
+ [Your offer as the bridge from pain to desired outcome — result-focused, not feature-focused. One proof point. 2-3 sentences.]
70
+
71
+ === PROOF ===
72
+ [Concrete social proof — named company, specific metric, defined timeframe. 1-2 sentences.]
73
+
74
+ === CTA ===
75
+ [Single, low-friction ask appropriate to the relationship stage. 1 sentence.]
76
+
77
+ === PS ===
78
+ P.S. [Urgency element, secondary proof point, or personal note. 1-2 sentences.]
79
+
80
+ === EMAIL NOTES ===
81
+ Target recipient: [Role / company type]
82
+ Relationship stage: [Cold / Warm / Hot]
83
+ Primary goal: [Reply / Book call / Purchase]
84
+ Follow-up cadence: [Day 3-4 / Day 7-10 / Day 14]
85
+ ```
86
+
87
+ ## Quality Criteria
88
+
89
+ - [ ] Subject line is 4-7 words and specific to the recipient (not a generic template)
90
+ - [ ] Opener references something specific about the recipient (company, role, activity, or connection)
91
+ - [ ] Problem statement uses the recipient's industry language, not internal jargon
92
+ - [ ] Solution focuses on outcomes and results, not product features
93
+ - [ ] Social proof includes a named company or specific metric with a timeframe
94
+ - [ ] Exactly one CTA that matches the relationship stage (not "buy now" for cold outreach)
95
+ - [ ] PS line is present and adds urgency, proof, or a personal touch
96
+ - [ ] Total word count is under 300 words (under 150 for cold emails)
97
+ - [ ] Email is formatted as plain text with no HTML, images, or attachments (for cold outreach)
98
+ - [ ] Unsubscribe mechanism and physical address are included (CAN-SPAM / GDPR compliance)
99
+
100
+ ## Anti-Patterns
101
+
102
+ - **Generic opener ("Hope this finds you well")** — This phrase instantly signals a mass template. Recipients delete these emails reflexively. Always lead with a personalized, specific reference that proves human effort.
103
+ - **Multiple CTAs** — "Book a call, visit our website, download the guide, and follow us on LinkedIn" dilutes every action. Each additional CTA reduces the conversion probability of the primary ask.
104
+ - **Feature dumping** — Listing product features instead of articulating outcomes. "We have AI-powered analytics with real-time dashboards" means nothing. "We helped [Company] cut reporting time by 70%" means everything.
105
+ - **Long paragraphs in cold emails** — Dense 4-5 sentence paragraphs look like work to read. On mobile (where most emails are first seen), a long paragraph fills the entire screen and triggers an immediate delete.
106
+ - **HTML-heavy cold emails** — Designed templates with images, buttons, and formatting trigger spam filters, reduce deliverability, and signal "marketing blast." Plain text outperforms for cold outreach.
107
+ - **Attachments in cold emails** — Files attached to cold emails trigger spam filters and create security concerns. Many corporate email systems strip or quarantine attachments from unknown senders.
108
+ - **No follow-up** — Sending one email and giving up leaves 80% of potential conversions on the table. A structured follow-up sequence (days 3, 7, 14) is essential for results.
109
+ - **Selling in the first cold email** — The goal of a cold email is to start a conversation, not close a deal. Asking for a purchase in the first contact feels aggressive and signals a lack of understanding of the sales process.
110
+ - **Ignoring send limits** — Blasting 500+ cold emails per day from a single domain destroys sender reputation. Domain blacklisting takes weeks to recover from and affects all emails from that domain, including internal ones.