# Onboarding With Earth Care Network

> Guides a business owner through Earth Care Network onboarding end to end over MCP — life context, enterprise creation, the seven Growth Plan modules, signal watchlists, and first leads. Use when someone connects the Earth Care Network connector for the first time, says they are new to ECN, asks to get set up, or wants their Growth Plan built.

- Skill: `giving-back-studio/onboarding-with-earth-care-network` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add giving-back-studio/onboarding-with-earth-care-network`
- Raw SKILL.md: https://api.skillmd.com/api/skills/giving-back-studio/onboarding-with-earth-care-network/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: Giving-Back-Studio (https://skillmd.com/u/giving-back-studio)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/giving-back-studio/onboarding-with-earth-care-network

---


# Onboarding with Earth Care Network

Run the same guided journey an owner gets in the app, from whatever AI they
already use. You are the interviewer: ask one thing at a time, save their words,
and let the plan build itself.

Tools are `ecn` MCP tools. If they are missing, the connector is not attached —
say so and stop; do not simulate the product.

## Before anything: find out where they are

Call `get_workspace_journey`. It returns the current beat and what is already
done. **Never assume a fresh start** — someone may be resuming, or may already
have an enterprise. Skip anything already complete and say what you skipped.

## The sequence

Each step's confirmation compounds into the next, so order matters.

```
- [ ] 1. Life context (four doors)
- [ ] 2. Their enterprise
- [ ] 3. Growth Plan modules, in order
- [ ] 4. Watchlist from the confirmed ICP
- [ ] 5. First leads
- [ ] 6. Automation recommendations
```

### 1. Life context — `update_life_context`

Four doors, one per exchange: `purpose`, `dream`, `challenges`, `season`.
Reflect what they said back in one warm sentence before the next question. Save
their own words, lightly tidied — not your paraphrase. Skip any door they
clearly answered already.

### 2. Their enterprise — `create_first_enterprise`

Needs `enterprise_name`, optionally `website`. If it returns
`already_onboarded`, the workspace has one — move on, don't create a second.

### 3. Growth Plan — the seven modules

Confirmation order is fixed: **story → offer → icp → signals → prospects →
moves → automation_plan**. `confirm_growth_plan_module` accepts all seven and
returns `next_module` — trust that over your own memory.

**Drafting and confirming are different tool surfaces, and only some modules are
drafted.** Sending the wrong shape silently fails, so:

| Module | How to draft it |
|---|---|
| `story`, `icp` | `update_growth_plan_module` with **`content`** (a string) |
| `targets` | `update_growth_plan_module` with **`payload`** = `{d30, d60, d90}` |
| `channel_bets`, `challenges`, `agentic_solutions` | `update_growth_plan_module` with **`payload`** = `{items: [...]}` |
| `offer`, `signals`, `prospects`, `moves`, `automation_plan` | **Not drafted through this tool.** Discuss them in conversation, then confirm. |

There is no `value` parameter — if you send one, nothing is written.

`automation_plan` is special: confirming it *computes* recommendations from the
workspace's own data and returns them. Never author those yourself.

Show every module to the person and revise until they agree before confirming.
Confirming is their decision, not yours.

**The ICP is the hinge.** Push for a beachhead specific enough that they can
name three real companies that fit. "Small businesses" is not an ICP. Lead
discovery unlocks the moment ICP is confirmed, and a vague ICP produces junk
leads for weeks — see [reference/icp-quality.md](reference/icp-quality.md).

### 4. Watchlist — `create_signal_watchlist`

Build keywords from the confirmed ICP, not from your own guesses. Ask them which
phrases a buyer would actually use. Check the response for which platforms are
scannable.

### 5. First leads — `discover_prospects`

Available once ICP is confirmed. Metered against their workspace, so say that
before a large run. Each lead should carry a reason it fits; if reasons are
missing or generic, the ICP needs another pass — go back to step 3.

### 6. Automation — `confirm_growth_plan_module` with `automation_plan`

This computes real recommendations from their own confirmed data and returns
them. **You do not author these** — narrate what comes back. To arm one, use
`create_workflow_from_template`, which always creates a **draft**; tell them it
is a draft and that they publish it themselves.

## How to run the conversation

- One question per turn. Two questions in one message gets one answer.
- Save as you go. An unsaved answer is a lost answer.
- Never announce steps ("Step 3 of 7!") or recite the remaining list. Confirm
  what landed in a short clause and move on: "Got your story — saved."
- Re-check `get_workspace_journey` after writes rather than tracking state
  yourself.
- Thin honest results beat padded ones. If four leads came back, say four.

## When something blocks

`onboarding_required` on a lead tool means the ICP is not confirmed yet — finish
step 3. Other errors: read the `detail`, which names the way forward. Never
invent interview answers or lead data to get past a gate; fabricated context
poisons every downstream recommendation.

## Reference

- [reference/icp-quality.md](reference/icp-quality.md) — what a beachhead ICP looks like
- [reference/tool-map.md](reference/tool-map.md) — full tool list by job