cc-skill:notion-database-design

Claude Code skill · anthropic · active

last 30 days

0 calls

0 of 30 days active

explain like I am new to this

what it does

This skill helps you build a Notion database that actually works. It asks the right questions upfront (what is this for, who uses it, what's the main view) and then recommends which properties to use, how to structure relations, and which view type fits your use case. You get a clear blueprint instead of guessing.

who it is for

Anyone setting up a Notion workspace to track leads, manage projects, plan content, or organize information for themselves or their team.

when it fires

When you mention Notion database design, ask for help with a Notion CRM or template, or say things like 'set up Notion' or 'design my Notion workspace'.

say something like

"Help me design a Notion CRM for my sales pipeline"
"I'm building a content calendar in Notion. What should it look like?"
"Set up a Notion database to track my project tasks and deadlines"

what you might get back

For a sales pipeline CRM, use a Board view grouped by stage (prospect, qualified, proposal, closed). Your core properties should be: Client Name (text), Contact (person), Deal Value (currency), Stage (status), Next Step (text), and Follow-up Date (date). Link your Clients database to your Deals database using a relation so you don't duplicate client info. Skip fancy properties until you actually need them.

how to know it worked

You got specific guidance on which Notion view to use as your default, which 3-5 properties are essential, and recommendations on how to connect multiple databases without duplicating data.

is this skill working for me

never used

cloud runs

0 deployments

local fires

Claude Code (optional)

posts published

from drafts

attributed

$0.00

signups + revenue

Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

Deploy this skill

no laptop required

Run this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/notion-database-design/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

Use this skill when designing Notion databases as CRMs, content calendars, project trackers, knowledge bases, or any structured workspace. Triggers on "Notion database", "Notion CRM", "Notion template", "design Notion workspace", "Notion schema", "No

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/notion-database-design/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity

never used

2026-04-03today

cost model

unitincluded

capabilities

{
  "source": "global",
  "description": "Use this skill when designing Notion databases as CRMs, content calendars, project trackers, knowledge bases, or any structured workspace. Triggers on \"Notion database\", \"Notion CRM\", \"Notion template\", \"design Notion workspace\", \"Notion schema\", \"Notion property types\", \"Notion relations\", \"set up Notion\". Covers property selection, view design, relations, rollups, and template architecture."
}

how it gets called

{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/notion-database-design/SKILL.md"
}

This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.