# Notion Template Furnisher

> Reads a Notion template skeleton built by Skill 3 and enriches it into a ready-to-sell product. Trigger when user says: "furnish the template", "make it sellable", "add sample data", "enrich the notion page", "run Skill 4", or "make it ready to sell". Always runs AFTER Skill 3. Reads the live Notion page, adds sample rows, guided onboarding, callouts, seller copy, and a checklist. Works for any niche. Requires Notion MCP connected.

- Skill: `ralf-claude-skills/notion-template-furnisher` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ralf-claude-skills/notion-template-furnisher`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ralf-claude-skills/notion-template-furnisher/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: ralf-claude-skills (https://skillmd.com/u/ralf-claude-skills)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/ralf-claude-skills/notion-template-furnisher

---


# Notion Template Furnisher — Skill 4

## Role
Read the skeleton Skill 3 built → enrich it into a product a buyer opens and immediately
understands → deliver a ready-to-sell Notion template.

Guiding laws applied throughout:
- Law 1: Every row, callout, and view must serve the buyer's outcome.
- Law 4: Cut everything that doesn't help the buyer act.
- Law 5: Sell a system, not a page. Template must feel like a complete workflow.
- Law 9: Guided onboarding inside the template.
- Law 17: One promise per template. Everything reinforces that promise.
- Law 22: Remove daily friction. Sample data shows how to use each field.
- Law 23: Usefulness over aesthetics.
- Law 44: Copy reflects transformation, not features.
- Law 46: Position as the shortcut. "Skip the setup — it's done."

---

## Step 0: Read the skeleton

Call `notion-fetch` on the parent page ID from Skill 3.
Extract:
- Template name and tagline
- All DB names and collection:// data-source IDs
- Existing content blocks
- Setup guide text

Fetch each DB individually to get full property schemas.
Do NOT furnish until all schemas are read.

---

## Step 1: Enrich the parent page

Update the parent page. Replace bare setup guide with a furnished landing-style page:

```
[EMOJI] [Template Name]
[Outcome tagline — what changes for the buyer]

---
> 🚀 [Fast-start callout: single most important first action]
---

## ⚡ What this solves
[2–3 sentences: the exact pain removed. Buyer's voice. No feature list. Pure problem → solution.]

## 🗺️ How the system works
1. [Step — names specific DB or view]
2. [Step — names specific DB or view]
3. [Step — names specific DB or view]

## 📋 Your databases
[emoji + DB name — one-sentence purpose, per DB]

---
## 🚀 Setup — 3 steps, 10 minutes

**Step 1 — [Action]** ([X] min)
[Specific. Names exact DB and field.]

**Step 2 — [Action]** ([X] min)
[Specific. Names exact view and field.]

**Step 3 — [Power move name]**
[Non-obvious leverage. Separates good users from great ones.]

> 💡 Pro tip: [One sentence. Specific. Only someone who lived this problem would know.]

---
## ✅ Fast-start checklist
- [ ] [Most important first action]
- [ ] [Second action]
- [ ] [Third action]
- [ ] [Fourth action]
- [ ] [Power move activation]
```

---

## Step 2: Add sample data

5–8 rows per database. Rules:

**Must:**
- Reflect exact target audience (real job titles, real scenarios, real language)
- Cover every status/stage option — every state populated
- Tell a mini-story: early stage → active → completed
- Fill every key field — no important fields empty
- Include 1 row demonstrating the "power move" field

**Must not:**
- Use generic placeholders ("Company 1", "Task A")
- Stack all rows in same status
- Leave important fields blank

**Before writing rows:** extract audience's world from template name + DB names.
What industry? What does their Monday look like? What tools/companies/terms do they use?
Use those specifics in every single row.

---

## Step 3: Create "START HERE" subpage

Subpage under parent. Title: "🚀 Start Here"

```
# Welcome — you're 10 minutes from having this running
[2 sentences: what they bought and what it replaces]

---
## Before you start, delete this:
[Specific list of sample data to delete or keep as reference]

## Your first 10 minutes
1. [Named DB + field]
2. [Named view]
3. [Most important field]
4. [Power move activation]
5. [Makes it feel personal/theirs]

## How to use this every day
**[Morning scenario]:** [Specific workflow — views and fields named]
**[Trigger scenario — e.g. "When X happens"]:** [Action sequence]
**[Weekly scenario]:** [Review workflow]

## The one thing most people miss
[The power move explained. 3–5 sentences. The non-obvious insight.]

---
> 💬 Questions? [Placeholder for seller contact or community link]
```

---

## Step 4: Create seller copy subpage

Subpage under parent. Title: "💰 Seller Copy — Do Not Publish"

```
# Seller Copy

## Template name
[Name]

## Tagline
[Outcome-first. Specific number or timeframe. No "ultimate" or "powerful".]

## Description (3–4 sentences for Whop/Gumroad)
1. The exact problem, in buyer's words.
2. What's inside (DBs + key views, plain language).
3. The transformation — what changes after using it.
4. ROI anchor — time saved, money recovered, or stress removed.

## Price
[$X — justified by: time saved / friction removed / one outcome recovered]

## Upsell
[Next logical template — what does buyer need after this? Law 20]

## Search terms (mirror what buyers search — Law 15)
[5–8 specific phrases]

## Before listing — customize these
- [ ] Replace sample data with your own anonymized examples
- [ ] Record 60-sec Loom walkthrough (real use, not slideshow)
- [ ] Make cover image: name + tagline, clean background
- [ ] Add your contact/community link to START HERE page
- [ ] Test as new user: delete everything, start from scratch, time yourself
```

---

## Step 5: Confirm to user

Return:
1. Notion link to parent page
2. What was added: row counts per DB, new subpages created
3. 5-item "ready to sell" checklist

---

## Errors
- Fetch fails → retry with bare UUID
- DB schema unreadable → fetch collection:// URL directly
- Update fails → create new subpage with content instead

## Hard rule
Every word added must serve buyer's outcome or seller's conversion.
If it does neither — cut it.