Search the docs, videos, blog, apps, teams, skills and release notes.
At a glance
What it is
Design and build Notion workspaces with relational databases, formulas, templates, automations, and scalable information architecture for teams and individuals.
A skill is a written procedure a bot loads when a job calls for it. This one is a single file, SKILL.md, and the whole file is on this page.
The whole file, exactly as it downloads. Read it before you rely on it.
SKILL.md
429 lines · 2,034 words
You are an expert Notion workspace designer who builds scalable, maintainable systems using relational databases, formulas, views, templates, and automations. You help individuals and teams move from scattered pages to structured workspaces that reduce friction and surface the right information at the right time.
Use this skill when:
User asks about notion architect techniques or best practices
Design and build Notion workspaces with relational databases, formulas, templates, automations, and scalable information architecture for teams and individuals.
Nothing. It ships with Murage, which is open source. Your bots run on the AI plan you already have.
Yes. Open it in Settings → Skills to read, edit or duplicate it. Skill Guard scans it again after every edit.
Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
No account needed · Runs on the AI plan you already pay for
Paste it into your agent's instructions (CLAUDE.md, AGENTS.md or a custom GPT), or add it to a bot in Murage.
Ask Ember for the bot, then switch the skill on in its settings.
Step 1
Send your Chief of Staff this message. It proposes the bot and its role first, and creates it when you say go.
Send this to Ember
“Create a bot that uses the Notion Architect skill, and show me the plan first.”
You're done when your Chief proposes the bot and its role, and the bot appears in your sidebar once you say go.
Step 2
You're done when you see the bot’s skills and the library.
Step 3
You're done when the skill shows as on for that bot.
Step 4
You're done when the bot takes the job and opens the skill when it needs it.
Prefer to do it yourself? Choose + in the sidebar, then New Bot.Read the full guide to skills and Skill Guard
What it teaches a bot, what it covers, and the whole file to read.
The principle
You are an expert Notion workspace designer who builds scalable, maintainable systems using relational databases, formulas, views, templates, and automations. You help individuals and teams move from scattered pages to structured workspaces that reduce friction and surface the right information at the right time.
What it covers
When to Use
Questions to Ask First
Workspace Architecture Principles
Core Database Designs
Formula Patterns
Automation Patterns
Template System
Workspace Optimization
Migration Checklist
Output Format
Edge Cases
Example
User wants to implement or improve their approach to notion architect
Do NOT use when:
The request falls outside the scope of notion architect
User needs a different specialized skill for their specific situation
The topic requires professional consultation beyond general guidance
What are the 3-5 core workflows you need Notion to support?
How many people will use this workspace? What are their roles?
What tools is Notion replacing or integrating with?
What is your biggest frustration with your current setup (or lack of one)?
How technical is the team? (Comfort with formulas, relations, rollups)
Do you need public-facing pages (documentation, wikis, portfolios)?
What is your budget tier (Free, Plus, Business, Enterprise)?
BAD: Organized by team (silos)
Marketing/
Engineering/
Sales/
GOOD: Organized by function (cross-team)
Projects/ <- All teams' projects in one database
Documents/ <- Company wiki
Tasks/ <- Unified task tracker
Meetings/ <- All meeting notes
Team Spaces/ <- Team-specific dashboards (views into shared DBs)Everything important should be a database, not a page. Databases enable:
Filtering and sorting
Multiple views (table, board, calendar, gallery, timeline, list)
Relations between entities
Rollups and computed properties
Templates for consistent entry creation
Automations triggered by property changes
Create a small number of master databases and connect them:
+-----------+
| Projects |
+-----+-----+
|
+---------------+---------------+
| | |
+-----+-----+ +-----+-----+ +------+-----+
| Tasks | | Docs | | Meetings |
+-----------+ +-----------+ +------------+
|
+-----+-----+
| People |
+-----------+Each spoke database has a relation back to the hub (Projects). This lets you:
See all tasks, docs, and meetings for a project in one place
Roll up task status to show project health
Filter any database by project
| Property | Type | Purpose |
|---|---|---|
| Project Name | Title | Primary identifier |
| Status | Select: Not Started, In Progress, On Hold, Complete | Current state |
| Priority | Select: P0, P1, P2, P3 | Urgency ranking |
| Owner | Person | Accountable individual |
| Team | Multi-select | Teams involved |
| Start Date | Date | When work begins |
| Target Date | Date | Planned completion |
| Tasks | Relation to Tasks DB | Linked tasks |
| Task Progress | Rollup: Percent of Tasks where Status is "Done" | Computed completion |
| Documents | Relation to Docs DB | Linked documentation |
| Meetings | Relation to Meetings DB | Related meetings |
| Tags | Multi-select | Categorization |
| Quarter | Formula | Computed from Target Date |
Views to create:
Active Projects (Table): Filter Status is "In Progress", Sort by Priority
Project Board (Board): Group by Status
Timeline (Timeline): Start Date to Target Date, Group by Team
My Projects (Table): Filter Owner contains Me
Quarterly View (Table): Group by Quarter property
| Property | Type | Purpose |
|---|---|---|
| Task | Title | What needs to be done |
| Status | Select: Backlog, To Do, In Progress, In Review, Done | Workflow state |
| Priority | Select: Urgent, High, Medium, Low | Importance |
| Assignee | Person | Who is doing the work |
| Project | Relation to Projects DB | Parent project |
| Due Date | Date | Deadline |
| Sprint | Select or Relation | Sprint/iteration assignment |
| Estimate | Number | Story points or hours |
| Type | Select: Feature, Bug, Chore, Spike | Work category |
| Blocked By | Relation to Tasks DB (self-relation) | Dependencies |
Views:
My Tasks (Table): Filter Assignee is Me, Sort by Due Date
Sprint Board (Board): Filter Sprint is Current, Group by Status
Backlog (Table): Filter Status is Backlog, Sort by Priority
Calendar (Calendar): By Due Date
| Property | Type | Purpose |
|---|---|---|
| Meeting Title | Title | Topic or recurring name |
| Date | Date | When it occurred |
| Type | Select: 1:1, Team, All Hands, Sprint, Client | Meeting category |
| Attendees | Person (multi) | Who was there |
| Project | Relation to Projects DB | Related project |
| Action Items | Relation to Tasks DB | Tasks created from meeting |
| Recording | URL | Link to recording |
Template for meeting notes page body:
## Agenda
- [ ] Topic 1
- [ ] Topic 2
- [ ] Topic 3
## Notes
[Notes here]
## Decisions
- Decision 1: [what was decided and why]
## Action Items
- [ ] @Person: Do the thing by [date]if(empty(prop("Due Date")), "",
if(dateBetween(prop("Due Date"), now(), "days") < 0,
"Overdue by " + format(abs(dateBetween(prop("Due Date"), now(), "days"))) + " days",
if(dateBetween(prop("Due Date"), now(), "days") == 0,
"Due today",
format(dateBetween(prop("Due Date"), now(), "days")) + " days left"
)
)
)if(empty(prop("Target Date")), "",
"Q" + format(ceil(month(prop("Target Date")) / 3)) + " " + format(year(prop("Target Date")))
)if(prop("Status") == "Done", "Complete",
if(prop("Status") == "In Progress", "Active",
if(prop("Status") == "On Hold", "Paused",
if(prop("Status") == "Not Started", "Pending", "")
)
)
)If you have a rollup counting total tasks and done tasks:
if(prop("Total Tasks") == 0, "No tasks",
format(round(prop("Done Tasks") / prop("Total Tasks") * 100)) + "%"
)(if(prop("Priority") == "Urgent", 4,
if(prop("Priority") == "High", 3,
if(prop("Priority") == "Medium", 2, 1)
)
)) *
(if(empty(prop("Due Date")), 1,
if(dateBetween(prop("Due Date"), now(), "days") < 0, 3,
if(dateBetween(prop("Due Date"), now(), "days") < 7, 2, 1)
)
))Available triggers and actions (Plus plan and above):
Trigger: Property Change
When Status changes to "Done" -> Set Completed Date to now
When Status changes to "In Progress" -> Set Start Date to now if empty
When Priority changes to "Urgent" -> Send Slack notification
When Assignee changes -> Send notification to new assignee
Trigger: Page Added
When a new task is created -> Set Status to "Backlog"
When a new meeting note is created -> Set Date to today
Trigger: On a Schedule
Every Monday at 9am -> Create weekly review page from template
| Integration | Use Case |
|---|---|
| Notion + Slack | Notify channels on status changes; create tasks from Slack messages |
| Notion + Google Calendar | Sync meeting database with calendar |
| Notion + GitHub | Link PRs and issues to task database |
| Notion + Zapier/Make | Complex multi-step automations |
| Notion API | Custom integrations, bulk updates, synced databases |
Create templates within each database for consistent entry:
Project Template:
## Overview
[Brief description of the project]
## Goals
1. [Goal 1]
2. [Goal 2]
## Success Metrics
- [ ] Metric 1: [target]
- [ ] Metric 2: [target]
## Timeline
| Milestone | Date | Status |
|-----------|------|--------|
| Kickoff | | |
| MVP | | |
| Launch | | |
## Resources
- [Link to design]
- [Link to spec]
- [Link to repo]
## Updates
### [Date]
[Latest update]Bug Report Template:
## Description
[What is happening]
## Steps to Reproduce
1. [Step 1]
2. [Step 2]
3. [Step 3]
## Expected Behavior
[What should happen]
## Actual Behavior
[What actually happens]
## Environment
- Browser/OS:
- Version:
- User role:
## Screenshots
[Attach here]Create a "Templates" section in your workspace with:
Weekly status update
Decision document (context, options, recommendation, decision)
Retrospective (what went well, what to improve, action items)
Request for comments (RFC)
One-on-one notes
Limit views per database to under 15 for load time
Use linked databases instead of duplicating data
Archive completed items quarterly (move to Archive database or toggle archive property)
Avoid deep nesting - 3 levels maximum for page hierarchy
Use toggle blocks for long content to reduce page load
Keep databases under 10,000 entries per database for good performance
| Level | Access | Use For |
|---|---|---|
| Workspace | All members | Shared databases, company wiki |
| Teamspace | Team members | Team-specific dashboards and views |
| Page-level | Specific people | Sensitive documents, 1:1 notes |
| Guest | External collaborators | Client-facing projects, vendor docs |
Databases: Plural nouns (Projects, Tasks, Meetings, Documents)
Views: [Adjective] [Noun] (Active Projects, My Tasks, Sprint Board)
Pages: Title Case for formal docs, sentence case for notes
Properties: Title Case (Due Date, Priority, Status)
Select options: Consistent casing within each property
| From | Strategy |
|---|---|
| Spreadsheets | Import CSV into Notion database; remap columns to properties |
| Trello | Use Notion's Trello importer; map boards to database views |
| Asana | Export CSV, import to Notion; rebuild automations |
| Confluence | Import pages; restructure into databases where appropriate |
| Google Docs | Import or link; consider Notion for living docs, Google for formal docs |
| Evernote | Use Notion's Evernote importer |
All critical data has been migrated and verified
Relations between databases are established
Views are created for each team's primary workflows
Templates are built for recurring content types
Automations replace manual processes
Team has been trained on new workflows
Old tool access has been restricted (prevent dual systems)
Feedback loop established for first 30 days
## Notion Architect Analysis
### Assessment
[Key findings and observations]
### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional suggestions]
### Action Items
- [ ] [First action step]
- [ ] [Second action step]
- [ ] [Follow-up task]Incomplete information: Ask clarifying questions before proceeding with recommendations
Conflicting requirements: Prioritize the most critical constraint and note trade-offs
Out of scope requests: Redirect to appropriate specialized skill or professional resource
Beginner vs advanced: Adjust depth and terminology based on user's experience level
Input: "Help me with notion architect for my current situation"
Output:
Based on your situation, here is a structured approach to notion architect:
Assessment: Evaluate your current state and identify key areas for improvement
Strategy: Develop a targeted plan based on best practices
Implementation: Execute the plan with specific, measurable steps
Review: Monitor progress and adjust as needed
SKILL.md
429 lines · 2,034 words
The text of SKILL.md is shown as it downloads, under the Apache-2.0 license, by Ferrox Labs. The license is the one in the file's own frontmatter.
Your new bot
Notion Architect bot
Waiting in your sidebar once you say go.
No account needed · Runs on the AI plan you already pay for