How do I install the Notion Template Blueprint skill?

Run npx skillmds@latest add ralf-claude-skills/notion-template-blueprint in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Notion Template Blueprint safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Notion Template Blueprint?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Notion Template Blueprint free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Notion Template Blueprint?

ralf-claude-skills (@ralf-claude-skills) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Notion Template Blueprint by ralf-claude-skills

Name: Notion Template Blueprint
Author: ralf-claude-skills

Notion Template Blueprint

Creates a clean empty Notion template skeleton from any idea — databases, properties, and views, no sample data. Trigger when user says: "build the template", "create the Notion page", "make the skeleton", "set up Notion structure", or provides any template idea to build. Works for any niche or audience. Skill 4 furnishes it later. Requires Notion MCP connected.

File contents

Notion Template Blueprint — Skill 3

Role

Take any template idea → design the structure → create it live in Notion. Output: clean parent page + databases + views. Zero sample data (Skill 4's job).

Step 0: Extract from idea

Derive these four from user input:

Name — specific, outcome-focused ("Freelance Invoice Tracker" not "Productivity System")
Audience — who buys this, their exact pain
Entities — 3–4 things this template tracks (e.g. Applications, Contacts, Prep Notes)
Daily workflow — what does buyer open and do every day

If any four are missing, ask ONE question. Do not build without all four.

Step 1: Design structure (think before building)

Database count

Under $25 → max 4 DBs
$25–$50 → max 6 DBs
No DB without a clear daily use case

Every DB requires

TITLE — primary name (always first)
SELECT — status/stage, 5–8 options with colors
DATE — at least one
RICH_TEXT — Notes field
3–6 additional use-case-specific properties

Views per DB (minimum)

Default table — all records, no filter
Action view — filtered to what needs attention now
Board — GROUP BY Stage (skip for reference-only DBs)

Property types

TITLE         primary name
RICH_TEXT     notes, free text
SELECT        status/stage (single pick)
MULTI_SELECT  tags/skills (multi pick)
DATE          any date
URL           links
CHECKBOX      yes/no
NUMBER        scores, amounts
UNIQUE_ID     auto ID (main tracking DB only)
CREATED_TIME  auto timestamp
FORMULA       computed (max 1–2 per DB, only if obviously needed)

Step 2: Build in Notion

Exact order. No skipping.

2a. Search workspace

notion-search → check for duplicates. Duplicate found → show URL, ask "Update existing or create new?"

2b. Create parent page

Workspace-level. Emoji icon. Content:

# [Template Name]
*[One-sentence outcome tagline]*
---
> 👋 START HERE — [First action]. Takes [X] minutes.
---
## What's inside
- **[DB1]** — [purpose in one sentence]
- **[DB2]** — [purpose in one sentence]
- **[DB3]** — [purpose in one sentence]
---
## Setup Guide
**Step 1 — Setup ([X] min)**
[What to delete, customize, add first]

**Step 2 — Daily use ([X] min/day)**
[What to open, check, update. Name specific views.]

**Step 3 — Power move**
[Non-obvious thing that makes this template 10x more valuable]

> 💡 Pro tip: [One insight only someone who lived this problem would know]

2c. Create databases

One call per DB via notion-create-database. Parent = page ID from 2b. Standalone DBs first, relational DBs last.

2d. Add views

One call per view via notion-create-view after all DBs exist.

Common DSL:

Active:    FILTER "Stage" != "Done"; FILTER "Stage" != "Rejected"; SORT BY "Date" ASC
Board:     GROUP BY "Stage"
Upcoming:  FILTER "Status" = "Scheduled"; SORT BY "Date" ASC
Calendar:  CALENDAR BY "[Date field]"

Step 3: Confirm to user

Notion link to parent page
Summary: DB names + view names
"Ready for Skill 4" note:
- Skill 4 adds: 5+ sample rows per DB, seller copy, Whop listing, cover guidance, customize checklist

Errors

Auth fail → "Reconnect Notion MCP in Settings → Connected Apps"
DB creation fails → log, continue, report at end
View fails → note it, don't block build

Hard rule

Structure only. No sample rows. No seller copy. No polish. That is Skill 4.

---name: notion-template-blueprintdescription: Creates a clean empty Notion template skeleton from any idea — databases, properties, and views, no sample data. Trigger when user says: "build the template", "create the Notion page", "make the skeleton", "set up Notion structure", or provides any template idea to build. Works for any niche or audience. Skill 4 furnishes it later. Requires Notion MCP connected.---# Notion Template Blueprint — Skill 3## RoleTake any template idea → design the structure → create it live in Notion.Output: clean parent page + databases + views. Zero sample data (Skill 4's job).---## Step 0: Extract from ideaDerive these four from user input:- **Name** — specific, outcome-focused ("Freelance Invoice Tracker" not "Productivity System")- **Audience** — who buys this, their exact pain- **Entities** — 3–4 things this template tracks (e.g. Applications, Contacts, Prep Notes)- **Daily workflow** — what does buyer open and do every dayIf any four are missing, ask ONE question. Do not build without all four.---## Step 1: Design structure (think before building)### Database count- Under $25 → max 4 DBs- $25–$50 → max 6 DBs- No DB without a clear daily use case### Every DB requires- `TITLE` — primary name (always first)- `SELECT` — status/stage, 5–8 options with colors- `DATE` — at least one- `RICH_TEXT` — Notes field- 3–6 additional use-case-specific properties### Views per DB (minimum)1. Default table — all records, no filter2. Action view — filtered to what needs attention now3. Board — GROUP BY Stage (skip for reference-only DBs)### Property types```TITLE primary nameRICH_TEXT notes, free textSELECT status/stage (single pick)MULTI_SELECT tags/skills (multi pick)DATE any dateURL linksCHECKBOX yes/noNUMBER scores, amountsUNIQUE_ID auto ID (main tracking DB only)CREATED_TIME auto timestampFORMULA computed (max 1–2 per DB, only if obviously needed)```---## Step 2: Build in NotionExact order. No skipping.### 2a. Search workspace`notion-search` → check for duplicates.Duplicate found → show URL, ask "Update existing or create new?"### 2b. Create parent pageWorkspace-level. Emoji icon. Content:```# [Template Name]*[One-sentence outcome tagline]*---> 👋 START HERE — [First action]. Takes [X] minutes.---## What's inside- **[DB1]** — [purpose in one sentence]- **[DB2]** — [purpose in one sentence]- **[DB3]** — [purpose in one sentence]---## Setup Guide**Step 1 — Setup ([X] min)**[What to delete, customize, add first]**Step 2 — Daily use ([X] min/day)**[What to open, check, update. Name specific views.]**Step 3 — Power move**[Non-obvious thing that makes this template 10x more valuable]> 💡 Pro tip: [One insight only someone who lived this problem would know]```### 2c. Create databasesOne call per DB via `notion-create-database`.Parent = page ID from 2b. Standalone DBs first, relational DBs last.### 2d. Add viewsOne call per view via `notion-create-view` after all DBs exist.Common DSL:```Active: FILTER "Stage" != "Done"; FILTER "Stage" != "Rejected"; SORT BY "Date" ASCBoard: GROUP BY "Stage"Upcoming: FILTER "Status" = "Scheduled"; SORT BY "Date" ASCCalendar: CALENDAR BY "[Date field]"```---## Step 3: Confirm to user1. Notion link to parent page2. Summary: DB names + view names3. "Ready for Skill 4" note: - Skill 4 adds: 5+ sample rows per DB, seller copy, Whop listing, cover guidance, customize checklist---## Errors- Auth fail → "Reconnect Notion MCP in Settings → Connected Apps"- DB creation fails → log, continue, report at end- View fails → note it, don't block build## Hard ruleStructure only. No sample rows. No seller copy. No polish. That is Skill 4.

Frequently asked questions