@caoscompanybr/merlin 3.5.0

package/.merlin-core/skills/domain/marketing-ops/references/retain/onboarding.md

@@ -0,0 +1,243 @@
+---
+source: coreyhaines31/marketingskills (MIT) v2.0.1
+imported: 2026-05-20
+stage: retain
+upstream_path: skills/onboarding/SKILL.md
+---
+
+> **Adjacency:** This skill is part of the [`marketing-ops`](../../SKILL.md) umbrella, organized by funnel stage (retain). For Brazilian direct-response methodology (3-Document Protocol, Schwartz awareness levels, Anti-AI Copy Detection, ROAS viability, WhatsApp formats), see [`digital-marketing/SKILL.md`](../../../digital-marketing/SKILL.md). For page-level SaaS copy, see [`general/copywriting/SKILL.md`](../../../../general/copywriting/SKILL.md). For email delivery use [`general/resend-email`](../../../../general/resend-email/SKILL.md), for visuals [`general/image-gen`](../../../../general/image-gen/SKILL.md), for decks [`general/blkskrn`](../../../../general/blkskrn/SKILL.md).
+
+---
+
+# Onboarding CRO
+
+You are an expert in user onboarding and activation. Your goal is to help users reach their "aha moment" as quickly as possible and establish habits that lead to long-term retention.
+
+## Initial Assessment
+
+**Check for product marketing context first:**
+If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+Before providing recommendations, understand:
+
+1. **Product Context** - What type of product? B2B or B2C? Core value proposition?
+2. **Activation Definition** - What's the "aha moment"? What action indicates a user "gets it"?
+3. **Current State** - What happens after signup? Where do users drop off?
+
+---
+
+## Core Principles
+
+### 1. Time-to-Value Is Everything
+
+Remove every step between signup and experiencing core value.
+
+### 2. One Goal Per Session
+
+Focus first session on one successful outcome. Save advanced features for later.
+
+### 3. Do, Don't Show
+
+Interactive > Tutorial. Doing the thing > Learning about the thing.
+
+### 4. Progress Creates Motivation
+
+Show advancement. Celebrate completions. Make the path visible.
+
+---
+
+## Defining Activation
+
+### Find Your Aha Moment
+
+The action that correlates most strongly with retention:
+
+- What do retained users do that churned users don't?
+- What's the earliest indicator of future engagement?
+
+**Examples by product type:**
+
+- Project management: Create first project + add team member
+- Analytics: Install tracking + see first report
+- Design tool: Create first design + export/share
+- Marketplace: Complete first transaction
+
+### Activation Metrics
+
+- % of signups who reach activation
+- Time to activation
+- Steps to activation
+- Activation by cohort/source
+
+---
+
+## Onboarding Flow Design
+
+### Immediate Post-Signup (First 30 Seconds)
+
+| Approach      | Best For                         | Risk                       |
+| ------------- | -------------------------------- | -------------------------- |
+| Product-first | Simple products, B2C, mobile     | Blank slate overwhelm      |
+| Guided setup  | Products needing personalization | Adds friction before value |
+| Value-first   | Products with demo data          | May not feel "real"        |
+
+**Whatever you choose:**
+
+- Clear single next action
+- No dead ends
+- Progress indication if multi-step
+
+### Onboarding Checklist Pattern
+
+**When to use:**
+
+- Multiple setup steps required
+- Product has several features to discover
+- Self-serve B2B products
+
+**Best practices:**
+
+- 3-7 items (not overwhelming)
+- Order by value (most impactful first)
+- Start with quick wins
+- Progress bar/completion %
+- Celebration on completion
+- Dismiss option (don't trap users)
+
+### Empty States
+
+Empty states are onboarding opportunities, not dead ends.
+
+**Good empty state:**
+
+- Explains what this area is for
+- Shows what it looks like with data
+- Clear primary action to add first item
+- Optional: Pre-populate with example data
+
+### Tooltips and Guided Tours
+
+**When to use:** Complex UI, features that aren't self-evident, power features users might miss
+
+**Best practices:**
+
+- Max 3-5 steps per tour
+- Dismissable at any time
+- Don't repeat for returning users
+
+---
+
+## Multi-Channel Onboarding
+
+### Email + In-App Coordination
+
+**Trigger-based emails:**
+
+- Welcome email (immediate)
+- Incomplete onboarding (24h, 72h)
+- Activation achieved (celebration + next step)
+- Feature discovery (days 3, 7, 14)
+
+**Email should:**
+
+- Reinforce in-app actions, not duplicate them
+- Drive back to product with specific CTA
+- Be personalized based on actions taken
+
+---
+
+## Handling Stalled Users
+
+### Detection
+
+Define "stalled" criteria (X days inactive, incomplete setup)
+
+### Re-engagement Tactics
+
+1. **Email sequence** - Reminder of value, address blockers, offer help
+2. **In-app recovery** - Welcome back, pick up where left off
+3. **Human touch** - For high-value accounts, personal outreach
+
+---
+
+## Measurement
+
+### Key Metrics
+
+| Metric                | Description                 |
+| --------------------- | --------------------------- |
+| Activation rate       | % reaching activation event |
+| Time to activation    | How long to first value     |
+| Onboarding completion | % completing setup          |
+| Day 1/7/30 retention  | Return rate by timeframe    |
+
+### Funnel Analysis
+
+Track drop-off at each step:
+
+```
+Signup → Step 1 → Step 2 → Activation → Retention
+100%      80%       60%       40%         25%
+```
+
+Identify biggest drops and focus there.
+
+---
+
+## Output Format
+
+### Onboarding Audit
+
+For each issue: Finding → Impact → Recommendation → Priority
+
+### Onboarding Flow Design
+
+- Activation goal
+- Step-by-step flow
+- Checklist items (if applicable)
+- Empty state copy
+- Email sequence triggers
+- Metrics plan
+
+---
+
+## Common Patterns by Product Type
+
+| Product Type     | Key Steps                                                    |
+| ---------------- | ------------------------------------------------------------ |
+| B2B SaaS         | Setup wizard → First value action → Team invite → Deep setup |
+| Marketplace      | Complete profile → Browse → First transaction → Repeat loop  |
+| Mobile App       | Permissions → Quick win → Push setup → Habit loop            |
+| Content Platform | Follow/customize → Consume → Create → Engage                 |
+
+---
+
+## Experiment Ideas
+
+When recommending experiments, consider tests for:
+
+- Flow simplification (step count, ordering)
+- Progress and motivation mechanics
+- Personalization by role or goal
+- Support and help availability
+
+**For comprehensive experiment ideas**: See [references/experiments.md](references/experiments.md)
+
+---
+
+## Task-Specific Questions
+
+1. What action most correlates with retention?
+2. What happens immediately after signup?
+3. Where do users currently drop off?
+4. What's your activation rate target?
+5. Do you have cohort analysis on successful vs. churned users?
+
+---
+
+## Related Skills
+
+- **signup**: For optimizing the signup before onboarding
+- **emails**: For onboarding email series
+- **paywalls**: For converting to paid during/after onboarding
+- **ab-testing**: For testing onboarding changes

package/.merlin-core/skills/domain/marketing-ops/references/retain/revops-lifecycle.md

@@ -0,0 +1,18 @@
+---
+source: coreyhaines31/marketingskills (MIT) v2.0.1
+imported: 2026-05-20 (pointer)
+stage: retain
+pointer_to: ../../../digital-marketing/references/revops-lifecycle.md
+---
+
+# revops-lifecycle — pointer
+
+This skill's authoritative body lives at [`../../../digital-marketing/references/revops-lifecycle.md`](../../../digital-marketing/references/revops-lifecycle.md).
+
+**What's there:** RevOps 7-stage lead lifecycle (Subscriber → Lead → MQL → SQL → Opportunity → Customer → Evangelist), MQL/SQL definitions, scoring, routing, speed-to-lead.
+
+**Why a pointer:** Avoid duplicating the body in two places. The funnel-stage organization under `marketing-ops/` cross-references it; the canonical home stays where it lives.
+
+**Upstream:** Already imported earlier under digital-marketing/. For upstream v2.0.1 deltas: https://github.com/coreyhaines31/marketingskills/blob/main/skills/revops-lifecycle/SKILL.md
+
+**Adjacency:** Part of the [`marketing-ops`](../../SKILL.md) umbrella.

package/.merlin-core/skills/domain/marketing-ops/references/retain/revops-operations.md

@@ -0,0 +1,18 @@
+---
+source: coreyhaines31/marketingskills (MIT) v2.0.1
+imported: 2026-05-20 (pointer)
+stage: retain
+pointer_to: ../../../digital-marketing/references/revops-operations.md
+---
+
+# revops-operations — pointer
+
+This skill's authoritative body lives at [`../../../digital-marketing/references/revops-operations.md`](../../../digital-marketing/references/revops-operations.md).
+
+**What's there:** Pipeline 7-stage operations, CRM automation, deal desk tiers, data hygiene, dashboards.
+
+**Why a pointer:** Avoid duplicating the body in two places. The funnel-stage organization under `marketing-ops/` cross-references it; the canonical home stays where it lives.
+
+**Upstream:** Already imported earlier under digital-marketing/. For upstream v2.0.1 deltas: https://github.com/coreyhaines31/marketingskills/blob/main/skills/revops-operations/SKILL.md
+
+**Adjacency:** Part of the [`marketing-ops`](../../SKILL.md) umbrella.

package/.merlin-core/skills/domain/n8n-automation/SKILL.md

@@ -0,0 +1,149 @@
+---
+name: n8n-automation
+description: "Expert n8n workflow automation — build, validate, deploy, and manage workflows on self-hosted n8n via MCP. Covers 1,084 nodes, 2,709 templates, expression syntax, Code node patterns (JS + Python), validation profiles, and 5 architectural workflow patterns. Requires n8n-mcp MCP server connected to n8n instance."
+license: MIT
+metadata:
+  author: merlin-framework (sources — czlonkowski/n8n-mcp MIT, czlonkowski/n8n-skills MIT)
+  version: "1.0.0"
+  auto_activate:
+    [n8n-workflow, n8n-automation, workflow-automation, n8n-mcp, n8n-node]
+  file_triggers: ["**/n8n-workflows/**", "**/n8n-nodes/**", "**/*.n8n.json"]
+  tool_reminders:
+    - "n8n workflow activation on production is MEDIUM-stake — confirm before activating"
+    - "NEVER edit production workflows directly — copy first, test, then deploy"
+    - "nodeType format DIFFERS: search/validate = SHORT (nodes-base.slack), workflow tools = FULL (n8n-nodes-base.slack)"
+    - "Webhook data is ALWAYS nested under $json.body — the #1 gotcha across all n8n development"
+    - "Python Code nodes have NO external libraries — only stdlib. Use JavaScript for 95% of cases"
+---
+
+## n8n Automation — Domain Skill
+
+Expert knowledge for building production-ready n8n workflows via the n8n-mcp MCP server. This skill covers the full lifecycle: discovery, configuration, validation, deployment, and management of workflows on self-hosted n8n instances.
+
+### When This Activates
+
+This skill activates when working on n8n workflow automation, building integrations, configuring nodes, writing Code node logic, or managing workflows. Current ecosystem:
+
+- **<your-n8n-instance>** — Self-hosted n8n instance (production)
+- **<n8n-mcp-server-project>** (`/path/to/project`) — Standalone MCP server + skills source
+- **Client projects** — e.g., a travel-booking SaaS (lead capture), a knowledge-base assistant (RAG), and others
+
+### Architecture
+
+```
+Claude/Merlin Session
+    ↓ (n8n-mcp MCP tools — stdio)
+n8n-mcp server
+    ↓ (REST API)
+n8n @ <your-n8n-instance>
+    ├── 1,084 nodes (537 core + 547 community)
+    ├── 2,709 workflow templates
+    ├── Encrypted credential vault
+    └── Workflow execution engine
+```
+
+**Three capability layers:**
+
+1. **Documentation tools** (offline, no n8n connection needed) — search_nodes, get_node, search_templates, get_template, validate_node
+2. **Validation tools** (offline) — validate_workflow, tools_documentation, ai_agents_guide
+3. **Workflow management tools** (requires n8n connection) — n8n_create_workflow, n8n_update_partial_workflow, n8n_test_workflow, n8n_executions, etc.
+
+### MCP Tools Quick Reference
+
+| Category          | Tools                                                                                                                                | Performance |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ----------- |
+| **Discovery**     | `search_nodes` (query, source filter), `get_node` (detail: minimal/standard/full)                                                    | <20ms       |
+| **Validation**    | `validate_node` (profiles: minimal/runtime/ai-friendly/strict), `validate_workflow`                                                  | <100ms      |
+| **Templates**     | `search_templates` (keyword/by_nodes/by_task/by_metadata), `get_template`                                                            | <50ms       |
+| **Workflow Mgmt** | `n8n_create_workflow`, `n8n_get_workflow`, `n8n_update_partial_workflow` (17 ops), `n8n_update_full_workflow`, `n8n_delete_workflow` | 50-200ms    |
+| **Execution**     | `n8n_test_workflow`, `n8n_executions`, `n8n_deploy_template`                                                                         | varies      |
+| **System**        | `n8n_health_check`, `n8n_autofix_workflow`, `n8n_workflow_versions`, `tools_documentation`, `ai_agents_guide`                        | <50ms       |
+
+**Most used tool:** `n8n_update_partial_workflow` — 99% success rate, 38,287+ uses. Supports 17 operations: add_node, remove_node, update_node, rename_node, move_node, add_connection, remove_connection, clean_stale_connections, update_settings, activate_workflow, deactivate_workflow, etc. Saves 80-90% tokens vs full updates.
+
+### Decision Matrix: Which Tool When
+
+| Task                          | Tool                          | Key Parameter                      |
+| ----------------------------- | ----------------------------- | ---------------------------------- |
+| Find a node by name/function  | `search_nodes`                | query (e.g., "slack", "email")     |
+| Get node config schema        | `get_node`                    | detail="standard" (default, 1-2KB) |
+| Validate a single node config | `validate_node`               | profile="runtime" (recommended)    |
+| Find workflow examples        | `search_templates`            | mode="keyword" or "by_nodes"       |
+| Create new workflow           | `n8n_create_workflow`         | Full workflow JSON                 |
+| Modify existing workflow      | `n8n_update_partial_workflow` | operation + params (diff-based)    |
+| Test workflow execution       | `n8n_test_workflow`           | workflow ID                        |
+| Check execution history       | `n8n_executions`              | workflow ID                        |
+
+### Recommended Workflow Building Process
+
+```
+1. search_nodes({query: "keyword"})           → Find relevant nodes
+2. get_node({nodeType: "nodes-base.name"})    → Get config schema (SHORT prefix!)
+3. validate_node({nodeType, config})          → Validate before deploying
+4. n8n_create_workflow({...})                 → Create (use FULL prefix: n8n-nodes-base.*)
+   OR n8n_update_partial_workflow({...})      → Modify existing
+5. validate_workflow({id})                    → Final validation
+6. n8n_test_workflow({id})                    → Test execution
+```
+
+### The 5 Workflow Patterns
+
+| Pattern                  | Frequency | Trigger        | Common Use Cases                                                    |
+| ------------------------ | --------- | -------------- | ------------------------------------------------------------------- |
+| **Webhook Processing**   | 35%       | Webhook node   | Form submissions, payment callbacks, chat commands, git events, IoT |
+| **Scheduled Tasks**      | 28%       | Schedule/Cron  | Reports, data sync, monitoring, cleanup, content publishing         |
+| **HTTP API Integration** | 20%       | Manual/Webhook | Data fetching, API-to-API bridges, enrichment, monitoring           |
+| **Database Operations**  | 10%       | Any            | CRUD, migrations, aggregation, backup                               |
+| **AI Agent Workflow**    | 7%        | Any            | RAG, classification, summarization, chat agents                     |
+
+See [references/workflow-patterns.md](references/workflow-patterns.md) for full implementations of each pattern with 30+ use cases.
+
+### Critical Gotchas
+
+1. **Webhook body nesting** — Data from webhooks is under `$json.body`, NOT `$json` root. This applies in expressions (`{{$json.body.email}}`), Code nodes (`$input.first().json.body`), and downstream nodes.
+
+2. **nodeType format differs** — Discovery/validation tools use SHORT: `nodes-base.slack`. Workflow tools use FULL: `n8n-nodes-base.slack`. Mixing them causes silent failures.
+
+3. **Python = no external libs** — Code nodes in Python mode have ZERO external packages. No requests, pandas, numpy. Standard library only (json, datetime, re, base64, hashlib, urllib.parse, math, random, collections, itertools). Use JavaScript for 95% of cases.
+
+4. **Return format** — Code nodes MUST return `[{json: {...}}]` array format. Missing the `json` wrapper is the #1 Code node error (38% of failures).
+
+5. **Auto-sanitization** — `n8n_update_partial_workflow` auto-fixes IF/Switch node structures, binary/unary operators. Don't fight it — let it sanitize, then validate.
+
+6. **get_node detail levels** — Default `standard` (1-2KB) covers 95% of needs. Only use `full` (3-8KB) when standard is insufficient. Never use `full` by default — wastes tokens.
+
+### Approval Levels
+
+| Action                     | Level  | Notes                                     |
+| -------------------------- | ------ | ----------------------------------------- |
+| Search nodes/templates     | LOW    | Read-only, no side effects                |
+| Validate node/workflow     | LOW    | Read-only                                 |
+| Create workflow (inactive) | LOW    | Safe — workflow starts inactive           |
+| Update workflow            | MEDIUM | Confirm with user which workflow          |
+| Activate workflow          | MEDIUM | Starts real execution on triggers         |
+| Delete workflow            | HIGH   | Irreversible — require explicit approval  |
+| Test workflow              | MEDIUM | Executes real nodes with real credentials |
+
+### Reference Documentation
+
+| Document                                                  | Content                                                            | Source                           |
+| --------------------------------------------------------- | ------------------------------------------------------------------ | -------------------------------- |
+| [mcp-tools-expert.md](references/mcp-tools-expert.md)     | Complete MCP tool guide — search, validation, workflow management  | n8n-mcp-tools-expert (4 files)   |
+| [workflow-patterns.md](references/workflow-patterns.md)   | 5 patterns, 30+ use cases — webhook, schedule, API, DB, AI         | n8n-workflow-patterns (6 files)  |
+| [node-configuration.md](references/node-configuration.md) | Operation-aware config, property dependencies, AI connections      | n8n-node-configuration (3 files) |
+| [expression-syntax.md](references/expression-syntax.md)   | Expression rules, variables, common mistakes, examples             | n8n-expression-syntax (3 files)  |
+| [validation-expert.md](references/validation-expert.md)   | Error catalog, validation profiles, false positives, auto-sanitize | n8n-validation-expert (3 files)  |
+| [code-javascript.md](references/code-javascript.md)       | Data access, built-in functions, 10 patterns, error prevention     | n8n-code-javascript (5 files)    |
+| [code-python.md](references/code-python.md)               | Stdlib reference, limitations, 10 patterns, workarounds            | n8n-code-python (5 files)        |
+
+### Related Skills
+
+- **resend-email** (`.merlin-core/skills/domain/resend-email/`) — Email delivery via Resend MCP. Use for email notifications in n8n workflows. The resend-email-mcp skill in the upstream MCP-server project is the source; this domain skill is the Merlin adaptation.
+- **browser-automation** (`.merlin-core/skills/domain/browser-automation/`) — For workflows that need browser interaction (form fills, screenshots, authentication flows).
+
+### Source & Maintenance
+
+**Source project:** `/path/to/n8n-mcp-server-project` (standalone, not a Merlin submodule)
+**n8n-mcp upstream:** [github.com/czlonkowski/n8n-mcp](https://github.com/czlonkowski/n8n-mcp) (MIT)
+**n8n-skills upstream:** [github.com/czlonkowski/n8n-skills](https://github.com/czlonkowski/n8n-skills) (MIT)
+**n8n instance:** <your-n8n-instance> (self-hosted)