メニュー
Use when converting a Notion markdown export to a Docusaurus blog post for the dbt docs site, or when given a path to a Notion export folder/file.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/dbt-labs/docs.getdbt.com --skill converting-notion-to-docusaurus-blogコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
| name | converting-notion-to-docusaurus-blog |
| description | Use when converting a Notion markdown export to a Docusaurus blog post for the dbt docs site, or when given a path to a Notion export folder/file. |
Automates conversion of Notion markdown exports into properly formatted Docusaurus blog posts for docs.getdbt.com. Handles frontmatter generation, image processing, content cleanup, and file organization.
Parse the markdown file and locate the accompanying image folder (same name as the .md file, without the hash suffix).
From the Notion export, extract:
Search website/blog/authors.yml for a matching name from the Owner field.
If not found, prompt user:
Author "[Name]" not found in authors.yml.
How would you like to proceed?
1. Enter details now (name, title, photo URL, LinkedIn)
2. Scaffold empty entry to fill in manually later
Option 2 creates:
firstname_lastname:
name: Full Name
title: "" # TODO
image_url: /img/blog/authors/firstname-lastname.png # TODO
socials:
linkedin: "" # TODO
page: true
Slug guidelines: Keep 2-4 words, include primary keywords, drop "introducing", "a", "the", "how to".
dbt-agent-skillsgit-branching-strategies-dbtTag selection: Check website/blog/categories.yml for available tags and their descriptions. Select the most appropriate tag based on the post content. Fall back to analytics craft only if no other tag fits.
For each image in the Notion export folder:
skills-mcp-diagram.png not 74cb2aed-fe53-481b-89d0-eefd0054e0c2.png)website/static/img/blog/YYYY-MM-DD-slug/Copy the Notion markdown file to website/blog/YYYY-MM-DD-slug.md first. This establishes the baseline for git diffs.
Stage the new blog file and any copied images and create a commit (e.g. chore: import raw Notion export for <slug>) before making any edits. This anchors the baseline in git history so that all subsequent transformations appear as a single, reviewable diff against the import commit.
Apply transformation rules (see below) as individual edits to the copied file. This makes changes visible in git diff, allowing review of exactly what was modified.
Run a spellcheck on the content and fix any typos or spelling errors. Be careful to preserve technical terms, product names (dbt, MetricFlow, BigQuery), and intentional stylistic choices.
Summarize: files created, images processed, spelling corrections made, any TODO items (e.g., incomplete author entry).
Generate YAML frontmatter:
---
title: "Title from H1"
description: "A compelling sentence from the article that captures the key value or insight"
slug: seo-optimized-slug
authors: [author_slug]
tags: [appropriate-tag]
hide_table_of_contents: false
date: YYYY-MM-DD
is_featured: true
---
| Notion | Docusaurus |
|---|---|
 | <Lightbox src="/img/blog/YYYY-MM-DD-slug/semantic-name.png" width="85%" alt="generated alt text" /> |
| Image with caption on next line | Merge caption into title attribute |
| Pattern | Action |
|---|---|
| H1 title | Remove (comes from frontmatter) |
| Status/Owner/Created time block | Remove |
| Trailing sections after conclusion | Remove (internal notes) |
Code blocks with language markdown | Change to bash if shell commands |
Notion callouts (> **Note**) | Convert to :::note admonitions |
URL-encoded paths (%20) | Decode |
asterisks for emphasis (*emphasised* content) | Replace with underscores (_emphasised_ content) |
Internal Notion links (notion.so, notion.site) | Flag for review - replace with public resource links |
Absolute docs site links (https://docs.getdbt.com/...) | Convert to relative paths (/docs/..., /reference/...) |
Insert <!-- truncate --> after the introduction (1-3 paragraphs, ~150-300 words) and before the first ## heading.
Notion Export:
my-post abc123.md
my-post abc123/
image.png
image 1.png
Step 1 - Copy original + images, then commit:
website/blog/YYYY-MM-DD-slug.md (raw Notion content)
website/static/img/blog/YYYY-MM-DD-slug/
semantic-name.png
another-semantic-name.png
→ git commit (baseline import)
Step 2 - Apply edits (diffable against baseline commit):
website/blog/YYYY-MM-DD-slug.md (transformed)
Add or resolve an `availability` frontmatter field for a docs.getdbt.com page, so the page renders the correct applicability badge (where a feature runs, what plan/access it needs, which dbt engine version). Use when asked to add an availability badge, mark a page as platform/local/Enterprise-only, or figure out what availability value a feature needs.
Scaffold a new skeleton markdown doc for docs.getdbt.com — standard guide, reference page, feature/product page, or release note entry. Use when asked to create a new doc page, scaffold a doc, start a new page, or add a page to the sidebar.
Use this skill to triage, score, and label GitHub issues in the docs.getdbt.com repo. Triggers when the user asks to triage issues, rank issues by priority or size, label GitHub issues, review the issue backlog, or score open docs issues. Also use this skill when the user says things like "what should we work on next", "rank our issues", "apply priority labels", "apply size labels", or "what are our highest priority issues". Always use this skill for any request involving prioritizing or sizing docs GitHub issues.