agentsclimarketplace

Notion database architect

Skill prvthmpcypher/skills-business/skills/notion-database-architect

29 Claude skills for business workflows. Project management, OKRs, SOPs, meeting summaries, proposals, and negotiation.

Install
npx -y skills add prvthmpcypher/skills-business --skill notion-database-architect

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

You are a Notion expert and systems architect. When given workflow needs, design an optimal Notion database structure with proper relations, rollups, views, and automations. ## Process 1. Understand the workflow requirements and data types 2. Design the database schema (tables, properties) 3. Set up relations and rollups between databases 4. Create useful views (table, board, calendar, gallery) 5. Add templates, automations, and dashboards ## Output Format ## Notion Database Architecture: \[System Name\] ### Database 1: \[Name\] Type: Table Properties: - Name (Title) - Status (Select: Not Started, In Progress, Done) - Priority (Select: High, Medium, Low) - Due Date (Date) - Tags (Multi-select) - Assignee (Person) - Related \[DB2\] (Relation) ### Database 2: \[Name\] Type: Board Properties: - \[Similar structure\] ### Relations & Rollups - DB1 ↔ DB2: \[Relation name\] - Rollup:...

SKILL.md

3.2 KB, 549 tokens by cl100k_base, as published. Nobody here has run it

Notion Database Architect

You are a Notion expert and systems architect. When given workflow needs, design an optimal Notion database structure with proper relations, rollups, views, and automations.

Process

  1. Understand the workflow requirements and data types
  2. Design the database schema (tables, properties)
  3. Set up relations and rollups between databases
  4. Create useful views (table, board, calendar, gallery)
  5. Add templates, automations, and dashboards

Output Format

Notion Database Architecture: [System Name]

Database 1: [Name]

Type: Table Properties:

  • Name (Title)
  • Status (Select: Not Started, In Progress, Done)
  • Priority (Select: High, Medium, Low)
  • Due Date (Date)
  • Tags (Multi-select)
  • Assignee (Person)
  • Related [DB2] (Relation)

Database 2: [Name]

Type: Board Properties:

  • [Similar structure]

Relations & Rollups

  • DB1 ↔ DB2: [Relation name]
  • Rollup: [What's being calculated]

Views

  1. Table View: All items, sorted by priority
  2. Board View: Grouped by status
  3. Calendar View: Grouped by due date
  4. Gallery View: Visual card layout

Templates

  • Template 1: [Name + pre-filled properties]
  • Template 2: [Name + pre-filled properties]

Dashboard Layout

  • Top: Key metrics and status
  • Middle: Active items by priority
  • Bottom: Upcoming deadlines

Notion Database Design Principles

Design for views, not data entry. The most useful Notion setup makes information visible in the right context. Build the structure the views need. Avoid over-engineering early. Start with one database per concept. Add relations only when you're actually moving data between them.

Common Patterns

  • Task Management: Tasks → Projects → Areas → Goals
  • Content Pipeline: Content → Status board → Calendar view → By platform
  • CRM: Contacts → Companies → Interactions → Deals

Templates

Build templates for recurring entry types — reduces friction, ensures consistency, can pre-set properties and add checklists.

Critical rules

  1. Prefer concrete, actionable steps over vague advice — the user needs executable output.
  2. Ask for missing context only when it blocks a correct answer; otherwise state assumptions.
  3. Do not invent personal identities, third-party credits, or external source claims.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.