メニュー
Import Notion workspaces into Obsidian vaults and process results into usable structure. Covers API export setup, landscape mapping, routing decisions, and cleanup. Use when migrating content from Notion or processing a Notion export.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | notion-import |
| description | Import Notion workspaces into Obsidian vaults and process results into usable structure. Covers API export setup, landscape mapping, routing decisions, and cleanup. Use when migrating content from Notion or processing a Notion export. |
Guide for importing Notion workspaces into an Obsidian vault and processing the results into a usable structure.
Why API over ZIP: API import preserves Notion Databases as Obsidian .base files. ZIP/HTML import loses all database structure — you get flat markdown only.
Create Notion Integration Token
ntn_... tokenRun Obsidian Importer
Project/notion-import/) — never import directly into your working folders.md files with notion-id in frontmatter.md files with frontmatter containing all database properties + base: "[[DatabaseName.base]]" link.base files (Obsidian's native database format) with filters, properties, and view definitionsPeople functions (name(), email()) not availableText functions (style(), unstyle()) not available📦 Archive/)---
notion-id: 1d0be9d0-0a42-808f-9795-d946fcdc690a
base: "[[DatabaseName.base]]"
Property Name: value
Another Property: value
Sub-item: []
Parent item:
- notion-id-of-parent
---
# Database Name
filters:
and:
- note["base"] == link("DatabaseName.base")
properties:
file.name:
displayName: Name
Property1:
displayName: Property 1
views:
- type: table
name: Table View
order:
- file.name
- Property1
After import completes, you need to understand what you have before routing anything.
Run a structural census to understand the shape of the import:
# Total file count
find "path/to/notion-import/" -type f | wc -l
# File types breakdown
find "path/to/notion-import/" -type f | sed 's/.*\.//' | sort | uniq -c | sort -rn
# Database (.base) files — these are the structured data
find "path/to/notion-import/" -name "*.base"
# Top-level folder structure (Notion's page hierarchy)
ls -la "path/to/notion-import/"
# Deepest nesting
find "path/to/notion-import/" -type f | awk -F/ '{print NF-1}' | sort -rn | head -5
Each .base file represents a Notion database. Read each one to understand:
base: "[[ThatDatabase.base]]")Map top-level folders to their destination:
.base files and their items togetherOption A: Manual audit (small imports, <100 files) Read through folders, move things where they belong.
Option B: Agent team (large imports, 500+ files) Use subagents to parallelize the landscape mapping:
Option C: QMD indexing (very large imports, searchable archive) Index all imported markdown into QMD for full-text + semantic search. Good when you need to query across the import rather than just route it.
For each top-level folder/database, decide:
Untitled/Untitled.base, making identification harder. Check the properties and items to understand what they are.AI summary property — this can actually be useful for quick triage.notion-import/ folder once everything is routed.base files, verify they work in Obsidian's Base viewEach Notion workspace needs its own integration token. Import one at a time to keep things manageable. The second import benefits from lessons learned on the first.
Creative Intelligence Agency/Notion/Podcast Name for Guests/, 📦 Archive/, loose pageswiki-projects/ content.base file found for an unnamed database with AI summary, Sub-item, Parent item columnsnotion-id in frontmatter — good for dedupBuild and use an affirmation practice based on Scott Adams' specific methodology. Use when someone says 'how do affirmations work', 'teach me affirmations', 'does Adams really write affirmations', 'how to manifest goals', 'affirmation practice', 'I want to try affirmations', or 'what's Adams' affirmation system.' Teaches Adams' specific 15x daily writing practice with his caveats and track record.
Resolve apparent contradictions using Zakery Kline's three-strategy framework from How to Think. Use when someone says 'these two things both seem true but they contradict each other', 'how can X and Y both be right', 'this doesn't make sense — on one hand... but on the other hand', 'I'm confused by an apparent contradiction', 'these claims seem incompatible', or 'help me reconcile these two positions.' Walks through distinction-making, level analysis, and temporal resolution to determine whether the contradiction is real or resolvable.
Analyze text for logical fallacies using Zakery Kline's framework from Chapter 3 of How to Think. Use when someone says 'check this argument', 'find the fallacies', 'is this reasoning valid', 'analyze this debate', 'what's wrong with this argument', 'logical fallacies', 'is this logically sound', 'audit this essay', 'check my reasoning', or 'fallacy check.' Scans for all 10 named fallacies, quotes the specific passages, and shows how to fix each one.
Audit any belief, claim, or assumption by running it through Zakery Kline's first-principles methodology. Use when someone says 'audit my belief', 'is this actually true', 'what am I taking for granted', 'check my assumptions', 'first principles', 'what's really certain here', 'am I wrong about this', 'how do I know this is true', 'what can I actually prove', 'challenge this idea', or 'what's bedrock vs assumption'. Walks the user through the Undeniability Test, Cartesian Doubt, Phenomenological Certainty, and Logical Necessity to classify beliefs as bedrock, strong inference, assumption, or interpretation.
Identify and fix cognitive errors in your thinking using Scott Adams' Loserthink framework. Use when someone says 'am I thinking about this wrong', 'what cognitive biases am I missing', 'loserthink', 'I want to think more clearly', 'what errors am I making', 'check my reasoning', 'mental models', or 'help me think better about this.' Diagnoses thinking errors and teaches the multi-disciplinary correction.
Understand and apply Scott Adams' moist robot hypothesis — humans as programmable biological systems. Use when someone says 'moist robot', 'are humans programmable', 'how to change someone's behavior', 'why won't people listen to reason', 'how to influence people', 'human behavior is irrational', 'people are predictable', or 'help me understand why people act the way they do.' Teaches the framework and its practical applications.