Slash Command

/externalize

Convert raw content or files into well-structured Notion-ready markdown documentation

From km-notion
Install
1
Run in your terminal
$
npx claudepluginhub therealchrisrock/basho --plugin km-notion
Details
Argument<file-or-content> [--type concept|process|database|template]
Allowed Tools
ReadWriteGlobGrep
Command Content

Notion Externalize Command

Convert tacit or unstructured knowledge into well-structured Notion-compatible markdown.

Your Task

Transform the provided content into structured documentation optimized for Notion.

Process

1. Analyze Input

If a file path is provided:

  • Read the file content
  • Identify the knowledge type (concept, process, reference, experience)
  • Note any existing structure

If raw content is provided:

  • Parse the input
  • Identify key themes and components
  • Determine appropriate structure

2. Determine Output Type

Based on the content and --type flag if provided:

TypeWhen to UseOutput Structure
conceptIdeas, frameworks, definitionsConcept page template
processHow-to guides, workflowsProcess page template
databaseMultiple items needing trackingDatabase schema + initial entries
templateReusable patternsTemplate page for Notion

If no type specified, infer from content characteristics.

3. Apply Structure

For Concepts:

# {Concept Name}

## Definition
{One clear sentence}

## Why It Matters
{Relevance and importance}

## How It Works
{Detailed explanation}

### Key Components
1. **{Component}**: {Description}

## Examples
- {Concrete illustration}

## Related Concepts
- {Links}

For Processes:

# How to {Process Name}

## Purpose
{What this accomplishes}

## When to Use
- {Trigger condition}

## Prerequisites
- [ ] {Requirement}

## Steps

### Step 1: {Action Verb} {Object}
{Details}

> ๐Ÿ’ก **Tip**: {Expert insight}

### Step 2: {Action Verb} {Object}
{Details}

## Verification
How to confirm success:
- [ ] {Check}

For Databases:

## Database: {Name}

### Purpose
{What this tracks}

### Recommended Properties

| Property | Type | Purpose |
|----------|------|---------|
| Name | Title | Primary identifier |
| Status | Select | Workflow state |
| {Field} | {Type} | {Purpose} |

### Suggested Views

1. **{View Name}** ({Type})
   - Filter: {Criteria}
   - Sort: {Order}

### Sample Entries
{Converted from input content}

For Templates:

---
Template for: {Use case}
PARA Category: Projects | Areas | Resources
---

# {Template Title}

## Metadata
**Created:** {Date}
**Status:** Draft
**Related:**

## {Section 1}
{Placeholder with guidance}

## {Section 2}
{Placeholder with guidance}

4. Output

Write the structured content to a new file:

  • If input was a file: create {original-name}.notion.md in same directory
  • If input was content: create in current working directory with descriptive name

5. Provide Summary

After creating the file, provide:

  • Brief summary of what was externalized
  • PARA recommendation (where this fits)
  • Suggested next steps (add to database, share for review, etc.)

Example Usage

/notion:externalize meeting-notes.txt
โ†’ Creates meeting-notes.notion.md with structured content

/notion:externalize rough-ideas.md --type concept
โ†’ Creates rough-ideas.notion.md formatted as concept documentation

/notion:externalize "Our users are merchants who sell vouchers..."
โ†’ Creates structured content from inline description

Quality Criteria

Ensure the output:

  • Stands alone without requiring prior context
  • Uses clear headings for scanability
  • Includes concrete examples where relevant
  • Suggests related content links
  • Tags SECI phase as "Externalization"
  • Follows Notion markdown conventions (callouts, toggles, etc.)
Stats
Parent Repo Stars0
Parent Repo Forks0
Last CommitJan 8, 2026